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.
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.
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
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.
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
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.
After you install the hotfix, you must changethe 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:
Start SQL Server Enterprise Manager.
Expand the SQL Server Group, and then click your SQL Server name.
Right-click your SQL Server name, and then click Properties.
In the SQL Server Properties (Configure) - SQL Server Name dialog box, click the General tab.
On the General tab, click Startup Parameters.
In the Startup Parameters - SQL Server Name dialog box, type -T3614 in the Parameter text box.
Click Add, and then click OK.
In the SQL Server Properties (Configure) - <SQL Server Name> dialog box, click OK.
Restart the SQL Server service for the new startup parameter to take effect.
Note Do not use the DBCC TRACEONTransact-SQL statement as an alternative method to set the startup parameter because the effect of the DBCC TRACEON Transact-SQL statement maybe 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.
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