ID رویداد 1023: “ویندوز می تواند MSSCNTRS DLL ضد توسعه را بار نیست”

تکمیلی (04/08/08): I seem to have solved this problem. From the command line, I ran "c:\WINDOWS SYSTEM32 lodctr / R" در صحبت کردن در مورد مشکلات InstallShield یا ورود و که به نظر می رسد که آن را برای من حل شده.

من متوجه شدم که به تازگی, 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.

ویندوز می تواند MSSCNTRS DLL ضد توسعه را بار نیست, the first DWORD in data section is the Windows error code.

If I drill into the details of one of those messages, من این را دریافت کنید:

منبع: Perflib

نوع: خطا

دسته: هیچ یک

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. متاسفانه, 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, پس … not such a great option.

The host operating system is Windows XP 64 ذره.

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.

</پایان>

برچسب ها:

4 دیدگاه در "ID رویداد 1023: “ویندوز می تواند MSSCNTRS DLL ضد توسعه را بار نیست”

  1. Alex Jackson

    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.aspx

    I have already re-registered the msscntrs.dll
    —————————————————————–

    http://www-01.ibm.com/support/docview.wss?uid=swg21390900

    This link suggests that it may be WDS causing the issue
    ——————————————————————

    https://www.eventid.net/displayqueue.asp?eventid=1023

    Except from above link

    "Event ID: 1023
    Event Source: Perflib
    Event Type: خطا
    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;300956

    This 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…. example

    C:\WINDOWS\system32>findstr drivername *.ini
    esentprf.ini:drivername=ESENT
    iasperf.ini:drivername=IAS
    mqperf.ini:drivername=MSMQ
    msdtcprf.ini:drivername=MSDTC
    ntdsctrs.ini:drivername=NTDS
    ntfrscon.ini:drivername=FileReplicaConn
    ntfrsrep.ini:drivername=FileReplicaSet
    perfci.ini:drivername=ContentIndex
    perffilt.ini:drivername=ContentFilter
    perfwci.ini:drivername=ISAPISearch
    pschdprf.ini:drivername=PSched
    rasctrs.ini:drivername=RemoteAccess
    tslabels.ini:drivername=TermService

    همانطور که می بینید… 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.

    پاسخ

پاسخ

آدرس ایمیل شما منتشر نخواهد شد. بخشهای موردنیاز علامتگذاری شدهاند *