Sql Server 2005 - error occurred during the pre-lo

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2005 Forums

SQL Server Administration (2005)

Sql Server 2005 - error occurred during the pre-lo

Author

Topic

poratips
Posting Yak Master

105 Posts

Posted - 2013-05-22 : 17:48:05

Hi,
I am having following error:
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 didn't work.
2) I also tried Surface Area configuration for services & connections ==> Remote Connections > Selected Using both TCP/IP and Named pipes & Restart SQL Server & SQL Server Browser service.

Appreciate your help!

Thanks,

poratips
Posting Yak Master

105 Posts

Posted - 2013-05-23 : 17:33:18

Hello,
I have done so far following:
1) SQL Server service is up and running
2)
Run “sqlcmd -L” ==> Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

>osql -L
==> Servers:
Loal
MTDB

Servers:
— NONE –

>sqlcmd -L

Servers: MTDB

2) Enabled TCP/IP in SQL Server Configuration

3) All Firewall are off

4) Enabled Remote Connection

5) Enabled SQL Server Browser Service

poratips
Posting Yak Master

105 Posts

Posted - 2013-05-27 : 19:54:01

Hi,
I tried many other steps but none of the works, any other ideas?
When I m trying to restart the Sql Agent but it starts and stops immediately, any help?

chadmat
The Chadinator

1974 Posts

Posted - 2013-05-27 : 20:19:04

Do you see this message in your errorlog? "The certificate was successfully loaded for encryption".

Make sure there are no expired certificates in the MMC certificates snap in, if there are, delete them.

-Chad

poratips
Posting Yak Master

105 Posts

Posted - 2013-05-28 : 13:21:50

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

Thank for your help!

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources