Pre Login HAndShake Error in Sql Server - 2005 SSMS

Question

Pre Login HAndShake Error in Sql Server - 2005 SSMS

poratips

Hall of Fame

Points: 3994
More actions
May 22, 2013 at 2:33 pm

#277801

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.) ((Microsoft SQL Server, Error: 233)
I tried to Force Protocol Encryption, checked other Network protocol settings but did't work.
Appreciate your help!
Thanks,

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply

Orlando Colamatteo SSC Guru Points: 182276 More actions · Answer 1

From the provider error I am assuming you are trying to connect to a local instance. Please confirm.

Also, you posted in a 2008 forum but are saying 2005 SSMS. Please confirm the version of SSMS and the version of the server you're trying to connect to.

Are you trying to use a SQL Login or a Windows User to connect? If the former, make sure you have Mixed Mode Authentication enabled.

There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato

poratips Hall of Fame Points: 3994 More actions · Answer 2

Thanks,

Sorry as I have posted in a 2008 forum but we have Sql Server 2005 and 2005 SSMS.

I have tried both Sql server and Windows.

I couldn't login so unable to check any other things except I have mentioned.

osql -L

==> Servers:

Local

MTDB

Servers:

— NONE –

>sqlcmd -L

Servers: MTDB

2) Enabled TCP/IP in SQL Server Configuration

3) All Firewall are off

4) Enable Remote Connection

5) SQL Server Browser Service is enabled

6) Created exception of sqlbrowser.exe in Firewall

7) No Alias!!!

Orlando Colamatteo SSC Guru Points: 182276 More actions · Answer 3

osql was deprecated in SQL 2005 so I would recommend to stop using it. sqlcmd is the replacement for it.

Are you trying to connect to a local or remote instance? Try enabling Named Pipes too, just as a test, and then try connecting again.

There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato

poratips Hall of Fame Points: 3994 More actions · Answer 4

Thanks again.

I have already enabled - named pipes too, I was just checking osql -L and sqlcmd -L to see.

poratips Hall of Fame Points: 3994 More actions · Answer 5

Hi,

I am also using local instance which ones on VM.

I have also moved TCP before named pipes in the protocol order list.

When I am starting up Sql Agent from Sql Server Configuration manager, it's throwing an error:

The Request Failed or the Service Didn't respond in a timely manner, consult the event log.

I checked the Eventlog in Event Viewer and Sql Server Agent Error is: Sql Server Agent couldn't be started (reason: Unable to connect to Server local; Sql Server Agent can't Start)

I am also seeing other errors for Source - crypt32

Failed auto update retrieval of third party root list sequence number from http://www.download.windowupdate.com/msdownlod/update/v3/static/trustedr/authrootseq.txt> with error: This network connection does not exist.

Thanks

poratips Hall of Fame Points: 3994 More actions · Answer 6

Hi,

I have tried many tips but none of the helping, any idea?

Orlando Colamatteo SSC Guru Points: 182276 More actions · Answer 7

Could be lots of things. Try some of the basic troubleshooting articles, see if you can narrow it down.

http://blogs.msdn.com/b/sql_protocols/archive/2008/04/30/steps-to-troubleshoot-connectivity-issues.aspx

There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato

poratips Hall of Fame Points: 3994 More actions · Answer 8

It was security certificate issue, so it was fixed after renaming.

Thank for your help!

Orlando Colamatteo SSC Guru Points: 182276 More actions · Answer 9

Great news. There a lot of these connectivity issues but not a lot of solutions that detail renaming a security certificate. It might be extremely helpful to others that find this thread if you could detail exactly what you did to fix the issue.

There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato

poratips Hall of Fame Points: 3994 More actions · Answer 10

I did following after goggling and reading some topics but finally certificate renaming works.

1) Check all services

2)Enabled TCP/IP in SQL Server Configuration

3) All Firewall are off

4) Enable Remote Connection

5) SQL Server Browser Service is enabled

6) Created exception of sqlbrowser.exe in Firewall

7) Protocol Encryption set up off, checked other Network protocol settings but didn't work.

8) I also tried Surface Area configuration for services & connections

9) moved TCP before named pipes in the protocol order

Orlando Colamatteo SSC Guru Points: 182276 More actions · Answer 11

Renaming what certificate? Can you list the steps?

There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato