BUG: SQL Server Perf. Counters Don't Work on WinNT Server 4.0Last reviewed: July 14, 1997Article ID: Q170394 |
The information in this article applies to:
SYMPTOMSSQL Server version 6.5 performance counters do not appear if you don't have Windows NT administrative access (or other access giving READ permission to the registry) to the Windows NT Server 4.0 target computer. This problem does not occur with SQL Server version 6.0, Windows NT Server 3.51, or Windows NT Workstation 4.0.
WORKAROUNDTo work around this problem, use Regedit.exe to grant READ access to the following key of the target machine:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServerGrant this to those wanting SQL counter access. As when granting any NT access permission, you can grant based on an individual user or a group.
STATUSMicrosoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. We are researching this problem, and will post new information here in the Microsoft Knowledge Base as it becomes available.
MORE INFORMATIONYou can see this problem by starting Performance Monitor on a client computer running Windows NT 4.0 (on which you do not have Windows NT administrator access to the target) and pointing it to a Windows NT Server 4.0 computer on which SQL Server 6.5 is running. By default, you may not even see Windows NT counters unless you have performed the steps listed in the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q158438 TITLE : Enabling Non-Admin Users to Remotely Monitor with PERFMONThe steps in this article involve using Regedit.exe to grant access to certain registry keys on the target computer. If these steps are followed, you will see Windows NT counters but not SQL Server counters. To also see SQL Server 6.5 performance counters, you must similarly use Regedit.exe to grant READ access to the key listed in the WORKAROUND section above. |
Keywords : kbbug6.50 kbenv kbinterop SSrvGen SSrvMon
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |