0

Using SQL Server 2019. I setup certificates, users and logins for a principal/mirror/witness for 3 SQL Servers that are on 3 separate VM's all on the same ESXI server.

I have the prinicipal and mirror already working and synchronized. I am at my last step in our process where I set the witness with

ALTER DATABASE myDB
SET WITNESS = 'TCP://10.10.10.213:5024'

and I am getting back

Msg 1456, Level 16, State 4, Line 4 The ALTER DATABASE command could not be sent to the remote server instance 'TCP://10.10.10.213:5024'. The database mirroring configuration was not changed. Verify that the server is connected, and try again.

From our principal server we are able to ping the witness computer and open up SSMS to open up the Witness version of SQL Server.

Conversely, from the witness computer, we can also ping the principal and open up the principal DB from SSMS.

I don't think this is a firewall issue - we had mirroring with a witness setup prior with a older version of the database.

The only reason we have to do this again is because we were told by the customer to use a new different version of the database, so we broke mirroring to use it instead. Cleared out the endpoints/certificates/logins, and tried to recreate the mirroring but we keep running into this.

I am at a loss as to what else could be the issue. Any ideas?

1
  • Standard or Enterprise Edition?
    – J.D.
    Mar 13 at 20:27

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Browse other questions tagged or ask your own question.