Search code examples
sql-serversql-server-2005mirroringendpointsserver-configuration

SQL Server 2005 DB Mirroring Error


I'm getting the following error when trying to setup SQL Server 2005 DB Mirroring on my servers. I am running two Win2K3 servers with SQL 2005 on each with one of those running alongside a SQL 2000 Version. After restoring the database with NORecovery and configuring the endpoints, I run into the following error when I try to start the mirroring session.

TITLE: Database Properties
------------------------------

An error occurred while starting mirroring.

------------------------------
ADDITIONAL INFORMATION:

Alter failed for Database 'TestDB'.  (Microsoft.SqlServer.Smo)

------------------------------

An exception occurred while executing a Transact-SQL statement or 
batch. (Microsoft.SqlServer.ConnectionInfo)

------------------------------

The server network address "TCP://S-01.ssl.local:5022" can not be reached 
or does not exist. Check the network address name 
and that the ports for the local and remote endpoints are operational. 
(Microsoft SQL Server, Error: 1418)

I'll also note that I can telnet into the port using the full name from both servers.

Update

The secondary server is running SQL Server 2005 as a named instance on local 1434 and over the network as 1433 on the ip addresses that match the FQDN being used.

[EDIT]

I was able to Telnet to port 5022 on both servers.

[SOLUTION]

In the case that you can logging and both ports are active it may be that the underlying account that SQL Server is using is not a domain account. On our servers the local system account was who the service was logged in as. Once this was changed to be the administrator domain account instead the problem was resolved.


Solution

  • In the case that you can logging and both ports are active it may be that the underlying account that SQL Server is using is not a domain account. On our servers the local system account was who the service was logged in as. Once this was changed to be the administrator domain account instead the problem was resolved.