Re: transaction log shipping wizard uses wrong computer name?
- From: "geekyguy" <geeky@xxxxxxx>
- Date: Fri, 2 May 2008 10:55:31 -0400
Hi All: I'm still hoping someone can point me to a solution here...It looks like the "jobserver" name is an alias to the machine name that SQL Agent is running on...I presume that the SQL agent picked this up when I first installed SQL2005 on the server before it was joined to the domain.
It seems like uninstalling and reinstalling SQL 2005 might correct this problem, but I'm wondering if there's any way to update this reference without doing that? I would further guess it's in the registry somewhere...maybe someone can point me in that direction?
TIA
"geekyguy" <geeky@xxxxxxx> wrote in message news:eSAms6jqIHA.2188@xxxxxxxxxxxxxxxxxxxxxxx
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?
.
- Prev by Date: Re: isql tool
- Next by Date: Re: SQL Analyse Software
- Previous by thread: Re: isql tool
- Next by thread: Re: SQL Analyse Software
- Index(es):
Relevant Pages
|
