question

Katie 1 avatar image
Katie 1 asked

sql server agent issue

I am trying to configure log shipping between for two databases one being primary in DomainA and Secondary in domain2. But after a day the 2 different domains became one single domain (Domain A). so now the primary and the secondary are in the single domain. But for some reason the LS alert job on the secondary instance is trying to connect to the server in the earlier different domain(DomainB) and the job is failing , and hence even the copy job is failing. I am not sure if this is dns resolution or something like that, that its still looking connect to server in the domain that does not exist. Any help is appreciated. I am not sure which direction to go in now? ** Error: Failed to connect to server DomainB\Instance.(Microsoft.SqlServer.ConnectionInfo) *** 2012-10-18 09:45:16.79 *** Error: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)(.Net SqlClient Data Provider) ***
sql-server-2008securitylog-shippingsql-server-agentdomain
10 |1200
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

2 Answers

·
Fatherjack avatar image
Fatherjack answered
If domains have changed then you may need to review security on the location where the backups are stored. Has either SQL server been restarted since the domain changes?
5 comments
10 |1200
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Katie 1 avatar image Katie 1 commented ·
yes they have been all the services are running and security and service account info also has been validated everything seems ok.
0 Likes 0 ·
Fatherjack avatar image Fatherjack ♦♦ commented ·
So, I'd be looking to have rebooted at least one of the SQL servers after the domain changes took effect. Just to be sure it got the latest state of things from DNS etc. Have a Network Admin guy on standby and have your sa account and password to hand just in case it doesnt restart as you'd expect it to.
0 Likes 0 ·
Grant Fritchey avatar image Grant Fritchey ♦♦ commented ·
And remember, SQL Agent can have a different security context than the rest of the server and that might affect things.
0 Likes 0 ·
Katie 1 avatar image Katie 1 commented ·
it seems like while changing the domain name also changed the computer name and thats the reason it was showing as an error.
0 Likes 0 ·
Blackhawk-17 avatar image Blackhawk-17 commented ·
@Katie - Yup... FQDN includes Domain.
0 Likes 0 ·
Tim avatar image
Tim answered
If you are fully qualifying the servers servera.domaina.xxx and serverb.domainb.xxx then when serverb joined domainA then the FQDN changed. If a DNS recorded was not created to enable name resolution then this would start failing. You can update the entry in MSDB or simply remove log shipping and set it back up again.
10 |1200
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.