Solved

SQL Server 2005 error 53 possibly due to Windows Server updates

Posted on 2008-10-27
2
1,064 Views
Last Modified: 2012-05-05
I am no longer to connect remotely to our SQL Server database after the important updated KB948109 and/or KB958644 were installed over the weekend.  In the SQL Server Surface Area Configuration Tool, I am was allowing for Remote Connections via TCP/IP.  This morning, everything was working as usual, and then all of a sudden it stopped allowing remote connections to the database.

Our .NET web app couldn't connect until I increased the remote connections setting to allow both TCP/IP and Named Pipes to remotely connect.  However, I still cannot connect remotely via Management Studio, from a .NET Windows application that uses a connection string to connect to the database, or from another application that uses ODBC to connect to the database.  I attempted to install the patches, but the problem is still occurring.  We are using SQL Server 2005 SP2, which is installed on a Windows Server 2008 SP1 box.

Any thoughts on if/how these patches are causing the issue, and what the appropriate response is to get my connections working again?
0
Comment
Question by:wdelaney05
2 Comments
 

Accepted Solution

by:
wdelaney05 earned 0 total points
ID: 22816191
For us,
Here's what it was due to:
http://support.microsoft.com/kb/914277


You want to look specifically at the firewall section, at least, thats what gave us problems:


Create an exception for SQL Server 2005 in Windows Firewall
To create an exception for SQL Server 2005 in Windows Firewall, follow these steps:
1.      In Windows Firewall, click the Exceptions tab, and then click Add Program.
2.      In the Add a Program window, click Browse.
3.      Click the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe executable program, click Open, and then click OK.

Note The path may be different depending on where SQL Server 2005 is installed. MSSQL.1 is a placeholder for the instance ID that you obtained in step 3 of the previous procedure.
4.      Repeat steps 1 through 3 for each instance of SQL Server 2005 that needs an exception.
0
 

Expert Comment

by:PaulMdx
ID: 23093429
I have the same issue as the OP.  Both named pipes and TCP connectivity is enabled and Windows Firewall is disabled.  Any further suggestions?  Thanks.
0

Featured Post

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Scenerio: You have a server running Server 2003 and have applied a retail pack of Terminal Server Licenses.  You want to change servers or your server has crashed and you need to reapply the Terminal Server Licenses. When you enter the 16-digit lic…
Introduction: When running hybrid database environments, you often need to query some data from a remote db of any type, while being connected to your MS SQL Server database. Problems start when you try to combine that with some "user input" pass…
In an interesting question (https://www.experts-exchange.com/questions/29008360/) here at Experts Exchange, a member asked how to split a single image into multiple images. The primary usage for this is to place many photographs on a flatbed scanner…

829 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question