After setting up a second network adapter in the process of adding some SSL'd sites to ISS, my instance of SQL Server 2005 is no longer accessible – including through SQL Server Management Studio.
The specific error I receive is:
Cannot connect to xxxxxx.
Additional information:
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Mycrosoft SQL Server, Error: 233)
I've verified the following:
- TCP, Shared Memory, and Named Pipe connections are enabled in Configuration Manager
- Connections to anywhere are enabled in Surface Area Configuration
- Surface Area Configuration didn't list my account as having admin credentials; however, when it tried to connect to the server to fix that the connection failed with the same error as Server Management Studio generated. This unfortunately rules out the fix from 203541.
Very little of what I managed to Google pertained to local connections, and what remained wasn't helpful. Is there any way I can fix this, perhaps by running the server with authentication off long enough to fix my permissions a la MySQL?
Any ideas?
Best Answer
You can start SQL Server in single user mode and connect to it that way. Assuming your problem is authenticated-related (I'm not sure it is) this will get you in.
Edit:
Let's try this. Have a look at SQL Server 2000 installation or local connections fail with "SSL Security error :ConnectionOpen (SECDoClientHandshake())" error message. I'm finding threads referring to this article by unhappy people who are seeing the same error you are after installing certificates. There's some more background in this MSDN blog post.