Discussion:
"An existing connection was forcibly closed by the remote host" (RESOLVED)
(too old to reply)
Steve Harclerode
2008-09-24 19:05:32 UTC
Permalink
When I came in to work today, I booted up a dev web server that also has SQL
Server 2005 running on it. When I tried to connect to the main server
instance via Management Studio, I saw the following message:

TITLE: Connect to Server
------------------------------

Cannot connect to EBI-W2003E-BASE.

------------------------------
ADDITIONAL INFORMATION:

A connection was successfully established with the server, but then an error
occurred during the pre-login handshake. (provider: TCP Provider, error: 0 -
An existing connection was forcibly closed by the remote host.) (Microsoft
SQL Server, Error: 10054)

For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10054&LinkId=20476

------------------------------
BUTTONS:

OK
------------------------------

After I made several different attempts to resolve the error, my co-worker
noticed that a Windows update had been installed the night before: KB 948496

After uninstalling the KB, the issue went away. I'm posting this so that
maybe others won't have to go through a morning like I just did.


Steve
--
My BizTalk blog:
http://stevestechnotes.blogspot.com/
Steve Harclerode
2008-09-24 19:30:20 UTC
Permalink
I was able to connect once, but now I'm getting the same error message
again. Any ideas? I tried
http://support.microsoft.com/?kbid=919710
but the registry key specified in the article is actually blank when I run
regedit. I have another box where SQL works okay, and the registry key looks
the same on that box.

Aargh.
- Steve
Post by Steve Harclerode
When I came in to work today, I booted up a dev web server that also has
SQL Server 2005 running on it. When I tried to connect to the main server
TITLE: Connect to Server
------------------------------
Cannot connect to EBI-W2003E-BASE.
------------------------------
A connection was successfully established with the server, but then an
error occurred during the pre-login handshake. (provider: TCP Provider,
error: 0 - An existing connection was forcibly closed by the remote host.)
(Microsoft SQL Server, Error: 10054)
Raman Gosala
2008-09-25 15:16:02 UTC
Permalink
Steve,

Here you go..,
http://support.microsoft.com/?kbid=942861

This article was helpful for me to resolve the issue.

~Raman Gosala
Post by Steve Harclerode
I was able to connect once, but now I'm getting the same error message
again. Any ideas? I tried
http://support.microsoft.com/?kbid=919710
but the registry key specified in the article is actually blank when I run
regedit. I have another box where SQL works okay, and the registry key looks
the same on that box.
Aargh.
- Steve
Post by Steve Harclerode
When I came in to work today, I booted up a dev web server that also has
SQL Server 2005 running on it. When I tried to connect to the main server
TITLE: Connect to Server
------------------------------
Cannot connect to EBI-W2003E-BASE.
------------------------------
A connection was successfully established with the server, but then an
error occurred during the pre-login handshake. (provider: TCP Provider,
error: 0 - An existing connection was forcibly closed by the remote host.)
(Microsoft SQL Server, Error: 10054)
Loading...