I have experienced SQL Server mirroring the commissioning problems with the 2005 version several
years ago. (2 servers + witness)
I feel reliving the same situation without finding a solution.
I spent many hours (days), peel the forums on the subject of mirroring (unsuccessfully).
Project specifications:
2 Windows Server 2012 R2 64-bit servers
1 pc Windows 7 64-bit (witness)
The 2 servers run SQL Server Standard 2016 and the witness SQL Server 2014 Express.
Here is what has been tried:
- Setting the mirroring from a Windows authentication.
- Setting the mirroring according to the certificates (many tutorials found)
- Added the witness + servers on a domain (because trying in a workgroup before)
- SQL Server Service running with the same domain user.
- Opening the necessary ports on Firewall ...
- disable firewall on all machines ..
- Ping IP and machine name = ok
- Netstat -an (listening of the port=ok)
- The Endpoints exists on the 2 servers (and testing with or without encryption options)
- connexion tests for SQL Server services from other partners ...
- Mirroring configuration via the wizard and... test via t-sql scripts (many found on internet)
- Encoding domain service account via the wizard (or not)
- Etc., etc
-
Currently, after dozens of tests, I get
this error if I try a configuration via the wizard: (FULL backup From the first BD + restore to Server 2 with NORECOVERY option!) when I start the mirroring.
! => WIzard tell the partners + witness well configured.
![]()
I get this error if I try to set mirroring via the T-sql command:
![]()
I turn around, I'm all delete, which restart the servers again ... .. I get the same errors.
1) error : I can ping all partners (name, ip), the Listening of the Endpoint exists, the access are granted to the same user (who run the SQL services)
2) DB restore state ... yes, the DB on server 2 is in restoring states, yes, the LOG has been restored too (NORECOVERY option)..
If you have any tracks, thank you in advance!
Sincerely,