Microsoft KB Archive/228804

{|
 * width="100%"|

-

The information in this article applies to:


 * Microsoft SQL Server version 7.0
 * Microsoft SQL Server, Enterprise Edition, version 7.0

-

SYMPTOMS
SQL Server Performance Monitor counters for the Virtual Server are not present when SQL Server 7.0 is set up with an active or passive virtual SQL Server configuration and the passive node has control of the resources. However, when the active node has control of the resources, the SQL counters are available.

WORKAROUND
Follow the steps listed below so the SQL Performance Monitor counters will be available for the virtual server regardless of which node controls the resources:

 Copy the file sqlctr70.dll from the \Winnt\System32 directory on the active node to the \Winnt\System32 directory on the passive node. Confirm that the passive node has control of the SQL Server resource. If the active node has control when running the command in the next step the following error occurs:  On the passive node, run the following from a command prompt to update the registry with the SQL Server counters:  lodctr \\ \\ \ \mssql7\binn\sqlctr.ini For example: lodctr \\VSSQL1 \\VSSQL1\H$\MSSQL7\BINN\sqlctr.ini

NOTE: You must use the virtual server name, not the node name, in the preceding command because sqlctr70.dll is loaded from the following registry key on the passive node:  Take the SQL Server resource offline and then bring it online again to load the SQL Server counter dll, sqlctr70.dll.

MORE INFORMATION
IMPORTANT: Before you set up clustering, you should confirm that the SQL Server Performance Monitor counters are present. If not, see the following Microsoft Knowledge Base article:

"Q196657 PRB: 'Event ID (1001) in Source (SQLCTR70) Could Not Be Found'" When SQL Server Clustering is enabled, you should connect to the Virtual Server Name, not the node name, to view the SQL Performance Monitor Counters for the clustered server. Additional query words:

Keywords         : kbSQLServ700 Version          : winnt:7.0 Platform         : winnt Issue type       : kbbug
 * }