Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: You may receive error messages when you try to log in to an instance of SQL Server 2005 and SQL Server handles many concurrent connections

FIX: You may receive error messages when you try to log in to an instance of SQL Server 2005 and SQL Server handles many concurrent connections

View products that this article applies to.

Bug #: 50001317 (SQL Hotfix)
VSTS bug number: 262044

↑ Back to the top

Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.

↑ Back to the top

Summary

This article describes the following about this hotfix release:
  • The issues that are fixed by the hotfix package
  • The prerequisites for installing the hotfix package
  • Information about whether you must restart the computer after you install the hotfix package
  • Information about whether the hotfix package is replaced by any other hotfix package
  • Information about whether you must make any registry changes
  • The files that are contained in the hotfix package

↑ Back to the top

Symptoms

When you log in to an instance of SQL Server 2005, error messages that resemble the following are logged in the SQL Server Errorlog file:
Error message 1
2007-03-27 12:01:28.45 Logon Error: 18456, Severity: 14, State: 23.

Error message 2
2007-03-27 12:01:28.45 Logon Login failed for user LoginName'. [CLIENT: IPAddress]
Additionally, error messages that resemble the following may be logged in the SQL Server Errorlog file if an existing connection is reused in the connection pool:
2007-04-23 13:18:09.380 spid4371 Error: 18056, Severity: 20, State: 29.

2007-04-23 13:18:09.380 spid4371 The client was unable to reuse a session with SPID SPID, which had been reset for connection pooling. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.

When this problem occurs, you may also experience the following symptoms:
  • High CPU usage occurs.
  • The Microsoft Windows operating system frequently performs context switches.
This problem occurs when SQL Server handles many concurrent connections on a computer that has many processors installed. Additionally, a time-out may occur when you run a query.

↑ Back to the top

Cause

This problem occurs because memory allocation contention causes a slowdown on the login process or the query execution process.

↑ Back to the top

Resolution

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have SQL Server 2005 Service Pack 2 (SP2) installed to apply this hotfix.

For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

913089 How to obtain the latest service pack for SQL Server 2005

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
SQL Server 2005 32-bit version
File nameFile versionFile sizeDateTimePlatform
Microsoft.sqlserver.maintenanceplantasks.dll9.0.3171.0296,30421-May-200720:12x86
Msmdlocal.dll9.0.3171.015,943,53621-May-200720:12x86
Mssqlsystemresource.ldfNot applicable524,28821-May-200717:23Not applicable
Mssqlsystemresource.mdfNot applicable40,173,56821-May-200717:23Not applicable
Rdistcom.dll2005.90.3171.0644,46421-May-200720:12x86
Sqlaccess.dll2005.90.3171.0350,57621-May-200720:12x86
Sqlservr.exe2005.90.3171.029,190,00021-May-200720:12x86
Sysdbupg.sqlNot applicable510,62210-May-200715:40Not applicable
SQL Server 2005 x64-based version
File nameFile versionFile sizeDateTimePlatform
Microsoft.sqlserver.maintenanceplantasks.dll9.0.3171.0296,30421-May-200720:12x86
Msmdlocal.dll9.0.3171.015,943,53621-May-200720:12x86
Mssqlsystemresource.ldfNot applicable524,28821-May-200717:23Not applicable
Mssqlsystemresource.mdfNot applicable40,173,56821-May-200717:23Not applicable
Rdistcom.dll2005.90.3171.0828,27222-May-200708:15x64
Sqlaccess.dll2005.90.3171.0357,74422-May-200708:15x86
Sqlservr.exe2005.90.3171.039,538,54422-May-200708:15x64
Sysdbupg.sqlNot applicable510,62210-May-200715:40Not applicable

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

Error 18056 is a generic error that occurs during the login process when connection pooling is enabled. However, factors such as delayed authentication or server performance issue may also cause this error. If you continue to have problems after you have installed this hotfix, troubleshoot the issue from an authentication and performance perspective.


For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499 New naming schema for Microsoft SQL Server software update packages

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top

Keywords: kb, kbautohotfix, kbsql2005engine, kbexpertiseadvanced, kbfix, kbpubtypekc, kbqfe, kbhotfixserver

↑ Back to the top

Article Info
Article ID : 937745
Revision : 1
Created on : 1/7/2017
Published on : 6/21/2014
Exists online : False
Views : 612