That's a known issue with SQL Server 2000. Basically you had something trying to look at the perfmon counters the last time the SQL Server was restarted. This prevented the SQL Server from correctly registering the performance counters with the perfmon api. The only solution is to close/stop what ever software is monitoring the counters and restart the SQL Server instance. After the SQL Server instance has been restarted you can then start up the monitoring software which looks at the counters.
Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.