provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe
-
Now before you think you know the issue please read. The Error. “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.) (type SqlException)" Two days of scratching my head and searching and I could not find a single answer to this error that worked. The reason this was such a pain is everything was working great until I rebooted the machine. After that SQL 2005 could not connect. I also noticed my SQL 2000 instance could not connect either. I mean not a single device could connect. The servers loaded without error. I could restart services just fine but then I noticed that SQL Agent could not connect either. Connecting with integrated security or even the SA login failed. The most common issue for this is found at MSDN http://msdn2.microsoft.com/en-us/library/aa952081.aspx [^]. The funny thing is everyone on the net would say the same thing and say I just configured my server wrong. But this was not the issue. In my experience things do not just stop working or should I say in most cases. How could a simple reboot be the problem? The Real problem was not the reboot or the SQL Server configuration. A week before this issue I was testing the SSL validation and session handoff on a new .NET App. I needed an SSL Certificate on my dev box. To do this so I installed a local SSL Certificate using SelfSSL.EXE from Microsoft. The reason this made no immediate change is that SQL Server, both 2000 and 2005, process the SSL on instance load so since I had not restarted the SQL Servers they didn’t use the new SSL. After the reboot they tried to use the new SSL and failed. Funny thing, this was not in the LOG of SQL. It said SSL loaded successfully. The SQL log was the first place I started looking for a resolution. When I noticed the SSL was loaded correctly I then realized I had made the SSL changed a week before. It seems that the SSL loaded fine but once it tried to use it in a connection the SSL would not work in SQL. Now the fix. We need to remove the SSL. To do this go to “RUN”. Type “MMC” then click “FILE” > “Add/Remove” Snap in. Select “Certificates” > Select “Computer account”. And then select “Local computer”. Then Click “OK” Once back
-
Now before you think you know the issue please read. The Error. “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.) (type SqlException)" Two days of scratching my head and searching and I could not find a single answer to this error that worked. The reason this was such a pain is everything was working great until I rebooted the machine. After that SQL 2005 could not connect. I also noticed my SQL 2000 instance could not connect either. I mean not a single device could connect. The servers loaded without error. I could restart services just fine but then I noticed that SQL Agent could not connect either. Connecting with integrated security or even the SA login failed. The most common issue for this is found at MSDN http://msdn2.microsoft.com/en-us/library/aa952081.aspx [^]. The funny thing is everyone on the net would say the same thing and say I just configured my server wrong. But this was not the issue. In my experience things do not just stop working or should I say in most cases. How could a simple reboot be the problem? The Real problem was not the reboot or the SQL Server configuration. A week before this issue I was testing the SSL validation and session handoff on a new .NET App. I needed an SSL Certificate on my dev box. To do this so I installed a local SSL Certificate using SelfSSL.EXE from Microsoft. The reason this made no immediate change is that SQL Server, both 2000 and 2005, process the SSL on instance load so since I had not restarted the SQL Servers they didn’t use the new SSL. After the reboot they tried to use the new SSL and failed. Funny thing, this was not in the LOG of SQL. It said SSL loaded successfully. The SQL log was the first place I started looking for a resolution. When I noticed the SSL was loaded correctly I then realized I had made the SSL changed a week before. It seems that the SSL loaded fine but once it tried to use it in a connection the SSL would not work in SQL. Now the fix. We need to remove the SSL. To do this go to “RUN”. Type “MMC” then click “FILE” > “Add/Remove” Snap in. Select “Certificates” > Select “Computer account”. And then select “Local computer”. Then Click “OK” Once back
Hmmm, interesting...
"I guess it's what separates the professionals from the drag and drop, girly wirly, namby pamby, wishy washy, can't code for crap types." - Pete O'Hanlon
-
Hmmm, interesting...
"I guess it's what separates the professionals from the drag and drop, girly wirly, namby pamby, wishy washy, can't code for crap types." - Pete O'Hanlon
This was driving me nuts - thanks for posting this! We created the cert for IIS and it affects SQL - not exactly ideal...
-
Now before you think you know the issue please read. The Error. “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.) (type SqlException)" Two days of scratching my head and searching and I could not find a single answer to this error that worked. The reason this was such a pain is everything was working great until I rebooted the machine. After that SQL 2005 could not connect. I also noticed my SQL 2000 instance could not connect either. I mean not a single device could connect. The servers loaded without error. I could restart services just fine but then I noticed that SQL Agent could not connect either. Connecting with integrated security or even the SA login failed. The most common issue for this is found at MSDN http://msdn2.microsoft.com/en-us/library/aa952081.aspx [^]. The funny thing is everyone on the net would say the same thing and say I just configured my server wrong. But this was not the issue. In my experience things do not just stop working or should I say in most cases. How could a simple reboot be the problem? The Real problem was not the reboot or the SQL Server configuration. A week before this issue I was testing the SSL validation and session handoff on a new .NET App. I needed an SSL Certificate on my dev box. To do this so I installed a local SSL Certificate using SelfSSL.EXE from Microsoft. The reason this made no immediate change is that SQL Server, both 2000 and 2005, process the SSL on instance load so since I had not restarted the SQL Servers they didn’t use the new SSL. After the reboot they tried to use the new SSL and failed. Funny thing, this was not in the LOG of SQL. It said SSL loaded successfully. The SQL log was the first place I started looking for a resolution. When I noticed the SSL was loaded correctly I then realized I had made the SSL changed a week before. It seems that the SSL loaded fine but once it tried to use it in a connection the SSL would not work in SQL. Now the fix. We need to remove the SSL. To do this go to “RUN”. Type “MMC” then click “FILE” > “Add/Remove” Snap in. Select “Certificates” > Select “Computer account”. And then select “Local computer”. Then Click “OK” Once back
-
Now before you think you know the issue please read. The Error. “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.) (type SqlException)" Two days of scratching my head and searching and I could not find a single answer to this error that worked. The reason this was such a pain is everything was working great until I rebooted the machine. After that SQL 2005 could not connect. I also noticed my SQL 2000 instance could not connect either. I mean not a single device could connect. The servers loaded without error. I could restart services just fine but then I noticed that SQL Agent could not connect either. Connecting with integrated security or even the SA login failed. The most common issue for this is found at MSDN http://msdn2.microsoft.com/en-us/library/aa952081.aspx [^]. The funny thing is everyone on the net would say the same thing and say I just configured my server wrong. But this was not the issue. In my experience things do not just stop working or should I say in most cases. How could a simple reboot be the problem? The Real problem was not the reboot or the SQL Server configuration. A week before this issue I was testing the SSL validation and session handoff on a new .NET App. I needed an SSL Certificate on my dev box. To do this so I installed a local SSL Certificate using SelfSSL.EXE from Microsoft. The reason this made no immediate change is that SQL Server, both 2000 and 2005, process the SSL on instance load so since I had not restarted the SQL Servers they didn’t use the new SSL. After the reboot they tried to use the new SSL and failed. Funny thing, this was not in the LOG of SQL. It said SSL loaded successfully. The SQL log was the first place I started looking for a resolution. When I noticed the SSL was loaded correctly I then realized I had made the SSL changed a week before. It seems that the SSL loaded fine but once it tried to use it in a connection the SSL would not work in SQL. Now the fix. We need to remove the SSL. To do this go to “RUN”. Type “MMC” then click “FILE” > “Add/Remove” Snap in. Select “Certificates” > Select “Computer account”. And then select “Local computer”. Then Click “OK” Once back
Thank you very Much, I tried to add selfSLL to IIS, then I can't connect to sql server. “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.) (type SqlException)" Your instruction solve my problem.
Karay AKAR - Yapar