Steps I followed:

  1. Create DB on primary.
  2. Took full backup and log backup.
  3. Restored full and log on secondary in NORECOVERY mode (now tb shows restoring satus on secondary I guess this is because NORECOVERY mode).
  4. Tried configuring mirror from primary.

I was able to configure it successfully with windows 2012 and SQL server 2012 using SSMS 17.6 but it's giving above error with Win2k16 and SQl server 2016

  • 1
    Did you try to configure mirroring with SSMS or via TSQL ?
    – liotims
    Apr 11 '18 at 11:29
  • Yes, I tried it and it worked like a charm. Thanks a lot Apr 13 '18 at 5:44

It seems there are bugs with SSMS (2016) to configure mirroring https://stackoverflow.com/questions/38008208/sql-server-2016-cant-start-mirror

Try to use TSQL or SSMS 2014


  • ssms 2014 did the trick
    – tomeron11
    Mar 25 '19 at 10:11

Keep in mind that database mirroring has been deprecated. If there are bugs with mirroring (which there are many) they are unsupported and will not be fixed by Microsoft at this time. Please consider using Availability Groups as it will function similarly to mirroring, but provide a more stable environment and greater functionality.


Yes it seems there is a bug in SSMS as configuring mirroring through GUI wizard gives above error. I tried it with TSQL commands and it works smoothly. Commands are

On mirror server

ALTER DATABASE <mirror_db>
   SET PARTNER = 'TCP://<primary_server_hostname>:5022'

On primary server

ALTER DATABASE <mirror_db>
   SET PARTNER = 'TCP://<mirror_server_hostname>:5022'

Service accounts running SQL Server in SQL Config manager need to use the same domain user on both primary and secondary.

  • Could you potentially provide some more information? IE how would you set this up? Why does it fix the problem? Etc. Dec 14 '18 at 8:09

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.