"Performance Monitor Shared Memory Setup Failed: -1"

FIX: "Performance Monitor Shared Memory Setup Failed: -1" Error Message When You Start SQL Server

SYMPTOMS

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.

Additionally, if you query the sysprocesses table in the master database, the value of the waittype column and the waittime column is always zero for all system process IDs (SPIDs). The value of the waittype column and the waittime column may remain at zero, even if you query the sysprocesses table several times.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem described in this article. Only apply it to systems that are experiencing this specific problem. This fix may receive additional testing to further ensure product quality. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next SQL Server 2000 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

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 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.