We were having problems setting up the mirroring, so I did it via command lines. I found out the "alter...set partnership" command works on the mirror server going to the principal, but gets a 1418 error when going from the principal to the mirror.
So if A is the principal and B is the mirror, A to B fails but B to A works.
If I reverse it so that B is the principal and A is the mirror, B to A fails and A to B works.
Any suggestions?
Here’s an update on our problem.
We are now doing it thru Management Studio. We set up the mirroring, but answer “no” when it asks to start mirroring and go back to the mirroring screen. One of the default names contains the domain but the other does not.
We replace the address field with the IP addresses for the Principal and Mirror Network Addresses (no witness). When we click on “start mirroring”, the Principal’s name gets changed back to the dns name, but the mirror name remains an IP address. This is true even when we switch which server is the principal and which the mirror.
It seems to me that because it always happens the same way for the mirror and principal addresses, regardless of the server, that this might be a bug.
|||Fixed it!
We did two things:
- Went to C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys and set the administrators permission to Full Control and
- Edited the C:\WINDOWS\system32\drivers\etc\hosts file on each server to include
IP addressDNSname
For each server.
No comments:
Post a Comment