Microsoft KB Archive/170394
Article ID: 170394
Article Last Modified on 2/14/2005
- Microsoft SQL Server 6.5 Standard Edition
This article was previously published under Q170394
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
Microsoft SQL Server version 6.5 performance counters do not appear if you do not have Microsoft Windows NT administrative access to the target computer that is running Windows NT Server 4.0 or if you do not have other access that gives you READ permission to the registry of the target computer.
This problem does not occur with SQL Server version 6.0, Windows NT Server 3.51, or Windows NT Workstation 4.0.
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To work around this problem, use Regedit.exe to grant READ access to the following key of the target computer:
Grant 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.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
You 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. However, by default, you may not see any Windows NT counters.
To see SQL Server 6.5 performance counters, you must use Regedit.exe to grant READ access to the key that is mentioned in the "Workaround" section.
Additional query words: perfmon
Keywords: kbbug kbinterop kbenv KB170394