Steve Harclerode
2008-09-24 19:05:32 UTC
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
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/
My BizTalk blog:
http://stevestechnotes.blogspot.com/