Mirroring Error - The server network address "TCP:// MIRRORDBBNAM" can not be reached or does not exist

• AHWB

  Ten Centuries

  Points: 1096

  More actions

  November 25, 2013 at 6:16 am

  #301690

  I’m trying to set up mirroring however I have the following issue that I want to understand. I understand that ideally, best practice is to use Mirroring within a domain environment.

  I’m using SQL 2005 std sp2.

  When I refer to all 3 servers these are the Principal, Mirror and Witness. I'm using high availability automatic fail over. Firewalls all disabled and DNS ok.

  I have a Principal, Mirror and Witness. All are on a Domain. All can ping each other and successfully browse to the c$.

  Running through the mirroring wizard Mirroring's successfully set up. SQL service is set to the Domain account. This is in my test environment however I want to script the process for easy deployment within live.

  For whatever reason the live site SQL server is set to NetworkService, so although its on a domain a certificate was created. I could change this to a domain name however it was previously working with this local account so want to stick with it.

  I set my test lab to start all 3 servers to NetworkService. There are no connections to the SQL database (no transactions taking place)

  I backup the database and transaction log from the Principal and restore with norecovery to the Mirror.

  End points are successfully created on all 3 servers and started.

  Certificate’s created successfully and applied to all 3 servers. Mirror user created and GRANT CONNECT on endpoint.

  However I keep getting the following error when running the following on the Principal;

  ALTER DATABASE xxxx SET PARTNER = 'TCP://MIRRORDBBNAME:5022'

  The server network address "TCP:// MIRRORDBBNAM" 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.

  I tried setting the service back to the Domain account which is a sys admin and still it fails at this point. I have tried dropping the certificates, endpoints etc to no avail.

  Any other ideas?