FIX: Delayed domain authentication may cause SQL Server to stop responding

Article translations Article translations
Article ID: 820788 - View products that this article applies to.
BUG #: 200031 (SQLBUG_70)
BUG #: 235386 (SHILOH_BUGS)
Expand all | Collapse all

On This Page

SYMPTOMS

If domain authentication takes a long time to occur while Microsoft SQL Server is processing a Microsoft Windows NT authenticated login request, other users who have already successfully logged in to SQL Server may be affected. Periodic pauses may occur when the users are running queries, or in extreme cases, the SQL Server service may stop responding. This problem occurs only if a network problem or a domain controller problem causes the authentication request to take much longer than expected.

RESOLUTION

SQL Server 2000 service pack information

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 How to obtain the latest SQL Server 2000 service pack

SQL Server 2000 hotfix information

A hotfix for this problem is available for both SQL Server 2000 and SQL Server 7.0. The root cause of this problem is an extremely slow domain authentication request. The hotfix prevents delayed login processing for one user from slowing down other users who have already been authenticated. This hotfix does not prevent slower login times or login timeouts if authentication is too slow.

Note This hotfix (build 839) is intended to be applied on a computer that is running SQL Server 2000 Service Pack 3 (SP3) or a hotfix that is based on SQL Server 2000 SP3.

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 tool in Control Panel.
   Date         Time   Version        Size       File name
   ------------------------------------------------------------------
   31-May-2003  18:45  2000.80.818.0     78,400  Console.exe
   25-Jun-2003  01:01  2000.80.818.0     33,340  Dbmslpcn.dll
   25-Apr-2003  02:12                   786,432  Distmdl.ldf
   25-Apr-2003  02:12                 2,359,296  Distmdl.mdf
   30-Jan-2003  01:55                       180  Drop_repl_hotfix.sql
   23-Jun-2003  22:40  2000.80.837.0  1,557,052  Dtsui.dll
   23-Jun-2003  22:40  2000.80.837.0    639,552  Dtswiz.dll
   24-Apr-2003  02:51                   747,927  Instdist.sql
   03-May-2003  01:56                     1,581  Inst_repl_hotfix.sql
   08-Feb-2003  06:40  2000.80.765.0     90,692  Msgprox.dll
   01-Apr-2003  02:07                     1,873  Odsole.sql
   05-Apr-2003  01:46  2000.80.800.0     62,024  Odsole70.dll
   07-May-2003  20:41  2000.80.819.0     25,144  Opends60.dll
   02-Apr-2003  21:48  2000.80.796.0     57,904  Osql.exe
   02-Apr-2003  23:15  2000.80.797.0    279,104  Pfutil80.dll
   22-May-2003  22:57                    19,195  Qfe469571.sql
   12-Jun-2003  16:37                 1,083,989  Replmerg.sql
   04-Apr-2003  21:53  2000.80.798.0    221,768  Replprov.dll
   08-Feb-2003  06:40  2000.80.765.0    307,784  Replrec.dll
   05-May-2003  00:05                 1,085,874  Replsys.sql
   01-Jun-2003  01:01  2000.80.818.0    492,096  Semobj.dll
   31-May-2003  18:27  2000.80.818.0    172,032  Semobj.rll
   29-May-2003  00:29                   115,944  Sp3_serv_uni.sql
   01-Jun-2003  01:01  2000.80.818.0  4,215,360  Sqldmo.dll
   07-Apr-2003  17:44                    25,172  Sqldumper.exe
   19-Mar-2003  18:20  2000.80.789.0     28,672  Sqlevn70.rll
   02-Jul-2003  00:18  2000.80.834.0    180,736  Sqlmap70.dll
   08-Feb-2003  06:40  2000.80.765.0     57,920  Sqlrepss.dll
   23-Jun-2003  22:40  2000.80.837.0  7,553,105  Sqlservr.exe
   08-Feb-2003  06:40  2000.80.765.0     45,644  Sqlvdi.dll
   25-Jun-2003  01:01  2000.80.818.0     33,340  Ssmslpcn.dll
   01-Jun-2003  01:01  2000.80.818.0     82,492  Ssnetlib.dll
   01-Jun-2003  01:01  2000.80.818.0     25,148  Ssnmpn70.dll
   01-Jun-2003  01:01  2000.80.818.0    158,240  Svrnetcn.dll
   31-May-2003  18:59  2000.80.818.0     76,416  Svrnetcn.exe
   30-Apr-2003  23:52  2000.80.816.0     45,132  Ums.dll
   02-Jul-2003  00:19  2000.80.834.0     98,816  Xpweb70.dll
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

SQL Server 7.0 hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Note This hotfix (build 1092) is intended to be applied on a computer that is running SQL Server 7.0 Service Pack 4 or a hotfix that is based on SQL Server 7.0 SP4.

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 tool in Control Panel.
   Date         Time   Version            Size    File name
   -----------------------------------------------------------------
   04-Oct-2002  23:59  7.00.1081          28,944  Dbmssocn.dll     
   06-Sep-2002  23:55  7.00.1077          53,520  Distrib.exe      
   06-Sep-2002  23:55  7.00.1077          98,576  Logread.exe      
   05-May-2003  18:34                     54,904  Opends60.dbg
   05-May-2003  18:34  7.00.1093         155,920  Opends60.dll     
   06-Sep-2002  23:56  7.00.1077         250,128  Rdistcom.dll     
   06-Sep-2002  23:55  7.00.1077          82,192  Replmerg.exe     
   06-Sep-2002  23:56  7.00.1077          78,096  Replres.dll      
   17-Sep-2002  22:52                      7,941  Securityhotfix.sql
   15-Jan-2003  23:31  7.00.1085         413,696  Semsys.dll       
   15-Jan-2003  20:14  7.00.1085         114,688  Semsys.rll
   06-Sep-2002  23:56  7.00.1077         160,016  Snapshot.exe     
   08-Feb-2003  00:49                     63,834  Sp4_serv_uni.sql
   15-Jan-2003  01:33  7.00.1085         344,064  Sqlagent.exe     
   06-Sep-2002  23:55  7.00.1077          45,056  Sqlcmdss.dll     
   21-Feb-2003  19:51  7.00.1088          81,920  Sqlmap70.dll     
   25-Apr-2003  20:22  7.00.1092       5,062,928  Sqlservr.exe     
   04-Oct-2002  23:59  7.00.1081          45,328  Ssmsso70.dll     
   17-Dec-2002  01:36  7.00.1083          24,848  Ssnmpn70.dll     
   26-Sep-2002  20:30                     28,408  Ums.dbg
   26-Sep-2002  20:27  7.00.1079          57,616  Ums.dll          
   25-Feb-2003  02:40  7.00.1088         151,552  Xpweb70.dll
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

WORKAROUND

Note that the hotfix discussed in this article will only partially ease the effects of the problem. With the hotfix, a delayed authentication request will not cause a SQL Server scheduler to stop responding. However, a delayed authentication request will still cause a SQL Server worker thread to stop responding. Even with the hotfix installed, the delayed authentication request may still cause problems such as logon time-outs. If all available worker threads have stopped responding while waiting for a domain controller, the computer that is running SQL Server will still be unresponsive. This problem occurs because of unusually slow domain authentication requests. Therefore, you can avoid this problem by addressing the root cause of the domain authentication performance problem. You can switch to a network library other than TCP/IP, such as Named Pipes, to work around the problem. You can use Client Network Utility to select a preferred network library on a client computer.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.

MORE INFORMATION

For more information, 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

Properties

Article ID: 820788 - Last Review: November 27, 2007 - Revision: 9.7
APPLIES TO
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Personal Edition
  • Microsoft SQL Server 2000, Workgroup Edition
  • Microsoft SQL Server 2000 Desktop Engine (Windows)
  • Microsoft SQL Server 2000 Enterprise Edition 64-bit
  • Microsoft SQL Server 7.0 Standard Edition
Keywords: 
kbproductlink kbhotfixserver kbqfe kbqfe kbsqlserv2000presp4fix kbsqlserv700presp5fix kbfix kbbug KB820788

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com