FIX: SQL Server 2000 may not start if many users try to log in to SQL Server when SQL Server is trying to start

Article translations Article translations
Article ID: 834798 - View products that this article applies to.
BUG #: 470852 (SQL Server 8.0)

Microsoft distributes SQL Server 2000 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the software updates that were included with the previous SQL Server 2000 software update.
Expand all | Collapse all

On This Page

SYMPTOMS

If many users try to log in when SQL Server 2000 is trying to start, SQL Server 2000 may not start. You may also see error messages that are similar to the following in the SQL Server error log:

2003-12-16 13:58:01.11 spid5 Clearing tempdb database.
2003-12-16 13:58:01.11 spid5 Could not create worker thread.
2003-12-16 13:58:01.25 spid5 Could not find database ID 2. Database may not be activated yet or may be in transition.


One example of too many users trying to log on is Web applications that are running on many computers in a Web farm to connect to SQL Server.

RESOLUTION

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

Hotfix information

The English version of this fix has the file attributes (or later) 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  05:15  2000.80.818.0      78,400  Console.exe      
   27-Oct-2003  14:51  2000.80.873.0     315,968  Custtask.dll     
   02-Oct-2003  07:29  2000.80.867.0      33,340  Dbmslpcn.dll     
   24-Apr-2003  12:42                    786,432  Distmdl.ldf
   24-Apr-2003  12:42                  2,359,296  Distmdl.mdf
   29-Jan-2003  12:25                        180  Drop_repl_hotfix.sql
   11-Sep-2003  13:56  2000.80.859.0   1,905,216  Dtspkg.dll       
   26-Aug-2003  06:46  2000.80.854.0     528,960  Dtspump.dll      
   23-Jun-2003  09:10  2000.80.837.0   1,557,052  Dtsui.dll        
   23-Jun-2003  09:10  2000.80.837.0     639,552  Dtswiz.dll       
   23-Apr-2003  13:21                    747,927  Instdist.sql
   10-Oct-2003  05:22                    745,961  Instmsdb.sql
   02-May-2003  12:26                      1,581  Inst_repl_hotfix.sql
   07-Feb-2003  17:10  2000.80.765.0      90,692  Msgprox.dll      
   31-Mar-2003  12:37                      1,873  Odsole.sql
   04-Apr-2003  12:16  2000.80.800.0      62,024  Odsole70.dll     
   07-May-2003  07:11  2000.80.819.0      25,144  Opends60.dll     
   02-Apr-2003  08:18  2000.80.796.0      57,904  Osql.exe         
   02-Apr-2003  09:45  2000.80.797.0     279,104  Pfutil80.dll     
   04-Aug-2003  04:47                    550,780  Procsyst.sql
   11-Sep-2003  11:07                     12,305  Qfe469315.sql
   22-May-2003  09:27                     19,195  Qfe469571.sql
   19-Jan-2004  11:15                  1,090,380  Replmerg.sql
   05-Sep-2003  17:48  2000.80.858.0     221,768  Replprov.dll     
   15-Jan-2004  11:54  2000.80.908.0     307,784  Replrec.dll      
   15-Jan-2004  11:43  2000.80.908.0     159,813  Replres.rll
   05-Sep-2003  10:30                  1,087,150  Replsys.sql
   13-Aug-2003  02:58                    986,603  Repltran.sql
   02-Jan-2004  06:12  2000.80.904.0     287,304  Rinitcom.dll     
   21-Oct-2003  10:38  2000.80.871.0      57,916  Semnt.dll        
   29-Jul-2003  06:43  2000.80.819.0     492,096  Semobj.dll       
   31-May-2003  04:57  2000.80.818.0     172,032  Semobj.rll
   02-Jan-2004  06:12  2000.80.904.0      53,832  Snapshot.exe     
   09-Dec-2003  06:37                    117,834  Sp3_serv_uni.sql
   15-Jan-2004  11:53  2000.80.908.0      28,672  Sqlagent.dll     
   15-Jan-2004  11:54  2000.80.908.0     311,872  Sqlagent.exe     
   07-Jan-2004  09:08  2000.80.905.0     126,976  Sqlakw32.dll     
   31-May-2003  11:31  2000.80.818.0   4,215,360  Sqldmo.dll       
   07-Apr-2003  04:14                     25,172  Sqldumper.exe    
   19-Mar-2003  04:50  2000.80.789.0      28,672  Sqlevn70.rll
   26-Sep-2003  15:12  2000.80.865.0     180,792  Sqlmap70.dll     
   02-Sep-2003  13:26  2000.80.857.0     188,992  Sqlmmc.dll       
   02-Sep-2003  09:33  2000.80.857.0     479,232  Sqlmmc.rll
   21-Oct-2003  10:38  2000.80.871.0     401,984  Sqlqry.dll       
   07-Feb-2003  17:10  2000.80.765.0      57,920  Sqlrepss.dll     
   23-Jan-2004  12:29  2000.80.910.0   7,610,449  Sqlservr.exe     
   25-Jul-2003  08:14  2000.80.845.0     590,396  Sqlsort.dll      
   07-Feb-2003  17:10  2000.80.765.0      45,644  Sqlvdi.dll       
   23-Jan-2004  12:29  2000.80.910.0     106,588  Sqsrvres.dll     
   02-Oct-2003  07:29  2000.80.867.0      33,340  Ssmslpcn.dll     
   31-May-2003  11:31  2000.80.818.0      82,492  Ssnetlib.dll     
   31-May-2003  11:31  2000.80.818.0      25,148  Ssnmpn70.dll     
   27-Oct-2003  14:51  2000.80.873.0     123,456  Stardds.dll      
   31-May-2003  11:31  2000.80.818.0     158,240  Svrnetcn.dll     
   31-May-2003  05:29  2000.80.818.0      76,416  Svrnetcn.exe     
   30-Apr-2003  10:22  2000.80.816.0      45,132  Ums.dll          
   01-Jul-2003  10:49  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.

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

After you install the hotfix, you must change the startup behavior of SQL Server so that the server-side Net-Library is initialized after the tempdb database starts. You can change the startup behavior of SQL Server by enabling SQL Server trace flag 3614. To enable trace flag 3614 and to make sure that the trace flag is set whenever SQL Server starts, add trace flag 3614 as a SQL Server startup parameter.

Note Trace Flag 3614 is required regardless of whether you have the SQL Server 2000 post-Service Pack 3 hotfix installed or you have SQL Server 2000 Service Pack 4 installed.

To add trace flag 3614 as a SQL Server startup parameter, follow these steps:
  1. Start SQL Server Enterprise Manager.
  2. Expand the SQL Server Group, and then click your SQL Server name.
  3. Right-click your SQL Server name, and then click Properties.
  4. In the SQL Server Properties (Configure) - SQL Server Name dialog box, click the General tab.
  5. On the General tab, click Startup Parameters.
  6. In the Startup Parameters - SQL Server Name dialog box, type -T3614 in the Parameter text box.
  7. Click Add, and then click OK.
  8. In the SQL Server Properties (Configure) - <SQL Server Name> dialog box, click OK.
  9. Restart the SQL Server service for the new startup parameter to take effect.
Note Do not use the DBCC TRACEON Transact-SQL statement as an alternative method to set the startup parameter because the effect of the DBCC TRACEON Transact-SQL statement may be lost when SQL Server is shut down. Therefore, the trace flag may not be enabled during the SQL Server startup.

After you install the hotfix and you enable trace flag 3614, the startup sequence of SQL Server 2000 will be slightly different. The server side Net-Library will be initialized after the tempdb database is ready.

Note You may notice messages that are similar to the following in the SQL Server error log. These messages indicate that the server-side Net-Library (the Ssnetlib.dll file) is initialized after the tempdb database starts.

2004-02-09 10:37:46.86 spid3 Server name is 'ASQLSERVER'.
2004-02-09 10:37:46.86 spid8 Starting up database 'msdb'.
2004-02-09 10:37:46.86 spid10 Starting up database 'Northwind'.
2004-02-09 10:37:48.09 spid5 Clearing tempdb database.
2004-02-09 10:37:48.49 spid11 Starting up database 'pubs'.
2004-02-09 10:37:50.10 spid5 Starting up database 'tempdb'.
2004-02-09 10:37:50.70 server Using 'SSNETLIB.DLL' version '8.0.766'.
2004-02-09 10:37:50.75 server SQL server listening on 192.168.0.77: 1433.

REFERENCES

For more information about software updates, 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 product updates, tools, and add-ons

Properties

Article ID: 834798 - Last Review: November 2, 2007 - Revision: 4.2
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
Keywords: 
kbhotfixserver kbqfe kbuser kblogin kbservice kbserver kbdatabase kbsqlserv2000presp4fix kbfix kbbug KB834798

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