Microsoft KB Archive/812915

From BetaArchive Wiki

Article ID: 812915

Article Last Modified on 9/27/2005


  • Microsoft SQL Server 2000 Service Pack 3

BUG#: 363762 (SHILOH_bugs)


When you run System Monitor from the Performance console on a computer that is running SQL Server with Service Pack 3 (SP3) and you restart SQL Server without closing the Performance console, the following message is logged in the SQL Server error log:

Performance monitor shared memory setup failed: -1

You may notice that SQL Server-related objects do not appear in the Performance object list.

When this error occurs, SQL Server disables the collection of all performance counter data. If you query the sysprocesses table in the master database, the value of the waittype column and of the waittime column is always zero for all system process IDs (SPIDs). The value of the waittype column and of the waittime column may remain at zero, even if you query the sysprocesses table several times. Other commands that return performance information, such as querying the sysperfinfo virtual table or running the DBCC SQLPERF(WAITSTATS) command, will either return empty results sets or return results that indicate no waits or wait time occurred.


Service pack information

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional 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

Note Turn off the monitor programs that are running on your computer and restart the SQL Server service before you install this hotfix. The monitor programs may cause a shared memory segment that was created before the installation of the hotfix to be left open with the corresponding Access Control Lists (ACL), even after you install the hotfix on your computer.

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
   26-Feb-2003  01:41  2000.80.777.0     29,244 bytes  Dbmslpcn.dll 
   08-Feb-2003  03:44                   786,432 bytes  Distmdl.ldf 
   08-Feb-2003  03:44                 2,359,296 bytes  Distmdl.mdf 
   29-Jan-2003  23:55                       180 bytes  Drop_repl_hotfix.sql 
   31-Jan-2003  22:32  2000.80.763.0  1,557,052 bytes  Dtsui.dll
   30-Jan-2003  03:18                   746,470 bytes  Instdist.sql 
   29-Jan-2003  23:55                     1,402 bytes  Inst_repl_hotfix.sql 
   08-Feb-2003  04:40  2000.80.765.0     90,692 bytes  Msgprox.dll 
   08-Feb-2003  01:53                 1,065,895 bytes  Replmerg.sql 
   08-Feb-2003  04:40  2000.80.765.0    221,768 bytes  Replprov.dll 
   08-Feb-2003  04:40  2000.80.765.0    307,784 bytes  Replrec.dll
   30-Jan-2003  03:18                 1,084,318 bytes  Replsys.sql
   27-Feb-2003  23:34  2000.80.778.0    176,696 bytes  Sqlmap70.dll 
   08-Feb-2003  04:40  2000.80.765.0     57,920 bytes  Sqlrepss.dll 
   03-Mar-2003  17:15  2000.80.780.0  7,516,241 bytes  Sqlservr.exe 
   08-Feb-2003  04:40  2000.80.765.0     45,644 bytes  Sqlvdi.dll 
   26-Feb-2003  01:41  2000.80.777.0     29,244 bytes  Ssmslpcn.dll
   26-Feb-2003  01:41  2000.80.777.0     82,492 bytes  Ssnetlib.dll 
   27-Feb-2003  23:34  2000.80.778.0     98,872 bytes  Xpweb70.dll 

Note Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.


To work around this problem, close the Performance console before you restart SQL Server.


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.


To access the Performance object list, follow these steps:

  1. In the Performance console, expand Performance Logs and Alerts.
  2. Click Counter Logs, and then in the detail pane, double-click an item.
  3. In the dialog box that opens, click Add Counters.

In the Add Counters dialog box, you see the Performance object list.

Keywords: kberrmsg kbbug kbqfe kbsqlserv2000presp4fix kbperfmon kbhotfixserver KB812915