Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

Troubleshooting
Research
Professional Opinions
Ask a Question
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE

troubleshooting Question

Cannot add a witness server to a mirrored configuration

Avatar of rtl_support
rtl_supportFlag for United Kingdom of Great Britain and Northern Ireland asked on
Microsoft SQL ServerMicrosoft SQL Server 2005
4 Comments1 Solution1295 ViewsLast Modified:
I've recently installed a new server with Windows 2003 Server R2 o/s, and sql 2005 standard edition. This has been built to be my witness server (i originally installed SQL express, which is what i'll go back to once i resolve the problem).
I've got an existing Mirrored configuration, on two separate servers, but when i try to add this new server as a witness (on the same domain as the principle), it errors. As i stated earlier, i originally installed SQL Express, that generated the same error as the SQL standard thats on it now.
The error message is:

Database Mirroring login attempt failed with error: 'Connection handshake failed. There is no compatible encryption algorithm. State 22.'.  [CLIENT: 192.168.130.3]

This is the event viewer error on the witness server itself. SQL Studio Manager generates a generic "unable to connect to remote server" error.
I've looked at Microsoft for this, and there's a lot of information about people experiencing this problem, but it all seems to be a problem with sql logons (they all need to be the same). Or DNS issues.
I've verified the logons for SQL, and all three servers use the Domain Admin account. I've looked at a hotfix solution from Microsoft and this done nothing.
I've tested the mirror using a different SQL server as a witness and it works fine (all using the same domian admin account). I've checked the account that the services start up in windows, and all servers use the same account.
The problem i'm experiencing seems to be related to this new server, and i'm not sure what other configuration is required on the SQL server instance, that isn't standard "out of the box".

If anyone has any advice it would be appreciated as i've been battling this for about two weeks now, and don't seem to be getting far.

Cheers
ASKER CERTIFIED SOLUTION
Avatar of jorge_toriz
jorge_torizFlag of Mexico imageResearch & Development Manager

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Commented:
This problem has been solved!
Unlock 1 Answer and 4 Comments.
See Answers