• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 877
  • Last Modified:

Windows updates KB958644/KB948109 (critical security updates) + SQL Server 2005 error 53

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 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
wdelaney05
Asked:
wdelaney05
1 Solution
 
wdelaney05Author Commented:
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

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now