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) ***
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.