The "The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly" saga… Part 2

We’ve looked into this in much detail… this is a continuation of a previous blog entry

If you are having similar issues, it worth looking at:

We’ve done all of the above…. hopefully today we’ll do a test and check to see if it has been resolved

SpittingCAML




You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

2 Responses to “The "The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly" saga… Part 2”

  1. SpittingCAML Says:

    This information is also useful if you find you are suffering from lots of Performance Monitoring issues other than MSMQ. Please note however that the KB article that this information is from was written for Windows 2000 Server, so may not help.

    To resolve this problem, run the following commands at a command prompt in the %SystemRoot%\System32 folder to unload and reload the IIS performance dynamic-link libraries (DLLs). After you run these commands, the warning messages are not logged:

    unlodctr w3svc
    unlodctr msftpsvc
    unlodctr asp
    unlodctr inetinfo
    lodctr w3ctrs.ini
    lodctr ftpctrs.ini
    lodctr axperf.ini
    lodctr infoctrs.ini

    After you run these commands, you must restart your computer for the changes to take effect.

    This information from Microsoft KB 267831

    SpittingCAML

  2. SpittingCAML Says:

    … also, check out: Event ID number 2003 is logged in the Application log after you install Windows Server 2003 Service Pack 2

Leave a Reply