Paul Galvin's (old) SharePoint space [SharePoint

Just another WordPress.com site

Event ID 1023: “Windows cannot load extensible counter DLL MSSCNTRS”

UPDATE (04/08/08): I seem to have solved this problem.  From the command line, I ran "c:\windows\system32\lodctr /R" as per an entry talking about InstallShield problems and that appears to have solved it for me.

I have noticed that lately, my desktop/server fan never turns off.  I know it used to turn off.  I took a moment to check it out noticed that the a VMware process was running a consistent 20% utilization on one of the CPU’s.  I checked the event log and saw these errors in the application log happening dozens of times per minute:

Windows cannot load extensible counter DLL UGatherer, the first DWORD in data section is the Windows error code.

Windows cannot load extensible counter DLL UGTHRSVC, the first DWORD in data section is the Windows error code.

Windows cannot load extensible counter DLL MSSCNTRS, the first DWORD in data section is the Windows error code.

If I drill into the details of one of those messages, I get this:

Source: Perflib

Type: Error

Category: None

Event ID 1023

I did some research and there was some indication it could be a permission problem in terms of access to the DLLs in question.  I played around with that stuff but could not affect things in a positive way so I gave up on that.

VMware had been nagging me about performing an update for quite some time, so I jotted down the version I had installed (apparently "1.0.1 build 29996") and did the update.  This upgraded me to v1.04.  Sadly, it did not fix the issue.

I can stop the insane number of messages going to my application log if I shut down a service named "VMware Authorization Service".  This prevents me from using the VMware software, so … not such a great option. 

The host operating system is Windows XP 64 bit. 

I don’t think this has always happened, but I don’t recall any particular event that might have led to it.

This is why I hate computers.

</end>

Technorati Tags:

Advertisements

4 responses to “Event ID 1023: “Windows cannot load extensible counter DLL MSSCNTRS”

  1. Steve March 4, 2008 at 9:32 am

    I have the same problem on an SBS Server with VMPlayer.  It happened with VMWare Server too.

  2. Daryl March 31, 2008 at 8:04 am

    I have been having the same issue on my SBS Server. However, I do not have VMware installed. I would love to get to the bottom of this.

  3. Daryl April 4, 2008 at 11:41 am

    Have a look at this link: http://support.microsoft.com/default.aspx?scid=kb;EN-US;300956 That seems to have fixed the problem for me. However, be very careful, backup your registry first and read the instructions twice. It is a very involved time consuming process.

  4. Alex September 15, 2009 at 5:25 pm

    These are components of the Windows Desktop Search…. here is some helpful info. Easiest thing to do is uninstall and reinstall… or you can try the things listed in the links below.http://blogs.microsoft.nl/blogs/tonykrijnen/archive/2007/01/26/9958.aspxI have already re-registered the msscntrs.dll—————————————————————–http://www-01.ibm.com/support/docview.wss?uid=swg21390900This link suggests that it may be WDS causing the issue——————————————————————https://www.eventid.net/displayqueue.asp?eventid=1023Except from above link"Event ID: 1023 Event Source: Perflib Event Type: Error Event Description: Windows cannot load extensible counter DLL MSSCNTRS the first DWORD in data section is the Windows error code.Windows cannot load extensible counter DLL UGatherer the first DWORD in data section is the Windows error code.Windows cannot load extensible counter DLL UGTHRSVC the first DWORD in data section is the Windows error code. Comment: It only happened after updating our exchange server (Hub and CAS) with windows update. We noticed that windows search was installed along with the updates.Uninstalling windows Search V4.0 solved the issue. "—————————————————————–http://support.microsoft.com/default.aspx?scid=kb;EN-US;300956This link will tell you how to rebuild the performance library… but before you go that far… run findstr drivername .ini and see what shows up on the list…. exampleC:\\WINDOWS\\system32>findstr drivername *.iniesentprf.ini:drivername=ESENTiasperf.ini:drivername=IASmqperf.ini:drivername=MSMQmsdtcprf.ini:drivername=MSDTCntdsctrs.ini:drivername=NTDSntfrscon.ini:drivername=FileReplicaConnntfrsrep.ini:drivername=FileReplicaSetperfci.ini:drivername=ContentIndexperffilt.ini:drivername=ContentFilterperfwci.ini:drivername=ISAPISearchpschdprf.ini:drivername=PSchedrasctrs.ini:drivername=RemoteAccesstslabels.ini:drivername=TermServiceAs you can see… this box did not show the perf counters loaded so the rebuild is not needed… only to run lodctr gthrctr.ini and lodctr gsrvctr.ini.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: