Solved

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

Posted on 2008-10-27
1
865 Views
Last Modified: 2013-11-10
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
Comment
Question by:wdelaney05
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 

Accepted Solution

by:
wdelaney05 earned 0 total points
ID: 22816198
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

2017 Webroot Threat Report

MSPs: Get the facts you need to protect your clients.
The 2017 Webroot Threat Report provides a uniquely insightful global view into the analysis and discoveries made by the Webroot® Threat Intelligence Platform to provide insights on key trends and risks as seen by our users.

Question has a verified solution.

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

Use this article to create a batch file to backup a Microsoft SQL Server database to a Windows folder.  The folder can be on the local hard drive or on a network share.  This batch file will query the SQL server to get the current date & time and wi…
Join Greg Farro and Ethan Banks from Packet Pushers (http://packetpushers.net/podcast/podcasts/pq-show-93-smart-network-monitoring-paessler-sponsored/) and Greg Ross from Paessler (https://www.paessler.com/prtg) for a discussion about smart network …
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …

617 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