Hopefully this may help someone else...The problem was due to the SQL Server
user groups not matching the corresponding security IDs in the Windows
registry. This happened because I installed SQL before joining the server to
the domain. This explains why the old machine name was showing up when SQL
Agent tried to execute a job referencing the "local machine".
I discovered it only after I was unable to uninstall SQL 2005 successfully.
I kept getting this error:
"The setup has encountered an unexpected error while Setting Internal
Properties. The error is: Fatal error during installation"
The fix involved manually removing the SQL group GUIDs from the
registry...the KB article is here:
http://support.microsoft.com/kb/919945
Hope this helps someone else.
> Hi: I'm trying to configure transaction log shipping using SMS on sql
> 2005.
>
> Both servers are 2008 DCs in a domain, with SQL and SQL Agent running
> under a domain account. I'm configuring log shipping on server1 and
> backingup/restoring to server2.
>
> I've followed the steps in the wizard, but when it comes to saving the
> configuration, I get an error:
>
> "an exception occurred while executing a Transact-SQL statement or batch.
> (
Microsoft.sqlserver.connectionInfor}
>
> the specified @server_name ('WIN-MEKCSMQ3ZNE') does not exist."
>
> where that server name was the default name assigned to server2 before it
> was added to the domain and promoted to BDC.
>
> When I check AD on server1, server2 is correctly identified, and if I
> browse the network on server1, server2 comes up under it's correct name,
> not as the original name in the error.
>
> Just wondering why the old pre-domain server name would be coming up here?
> And how do I work around this?
