Module C:\Windows\CCM\StatusAgentProxy.dll failed to register. HRESULT -2147010895 Problem installing sccm 2012 client

Hi,
I am getting the following error, detailed in the client.msi.log, when trying to install the SCCM 2012 SP1 client on windows 2008 R2 servers.Why StatusAgentProxy.dll fails to register.
<![LOG[MSI: Action 22:08:03: RegisterTypeLibraries. Registering type libraries]LOG]!><time="22:08:03.092-330" date="12-18-2013" component="ccmsetup" context="" type="0" thread="8096" file="msiutil.cpp:314">
<![LOG[MSI: Action 22:08:03: SelfRegModules. Registering modules]LOG]!><time="22:08:03.827-330" date="12-18-2013" component="ccmsetup" context="" type="0" thread="8096" file="msiutil.cpp:314">
<![LOG[MSI: Module C:\Windows\CCM\StatusAgentProxy.dll failed to register.  HRESULT -2147010895.  Contact your support personnel.]LOG]!><time="22:08:03.889-330" date="12-18-2013" component="ccmsetup"
context="" type="3" thread="8096" file="msiutil.cpp:300">
<![LOG[MSI: Action 22:08:03: Rollback. Rolling back action:]LOG]!><time="22:08:03.952-330" date="12-18-2013" component="ccmsetup" context="" type="0" thread="8096" file="msiutil.cpp:314">
<![LOG[File C:\Windows\ccmsetup\{59A0EA77-D28C-4286-83A6-04BB57B9CDD6}\client.msi installation failed. Error text:
ExitCode: 1603
Action: SelfRegModules.
ErrorMessages:
Module C:\Windows\CCM\StatusAgentProxy.dll failed to register.  HRESULT -2147010895.  Contact your support personnel.
I've already checked this forum but nothing helped .
Please provide a valid action plan to resolve this issue.
I'd highly appreciate any help.
Thanks and regards
Arsalan

Hi,
Restart those server might be helpful.
After installing the Client manually, you could check the registration of statusagentproxy.dll in that log.
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

  • DTSAGENT.DLL failed to register when trying to install CRRuntime_32bit_13_0_7

    Hello together,
    maybe some can help me with an installing issue with CRRuntime_32bit_13_0_7.
    When i try to run the setup i get the error:
    Error 1904. Module C:\Program Files\SAP BusinessObjects\Crystal
    Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\dtsagent.dll failed to register.
    HRESULT -1073741819. Contact your support personnel.
    I found something following the link: http://scn.sap.com/thread/1948999 but it didn´t really fix my problem. I think it´s a problem with the constellation of McAfee that is also using the dtsagent.dll
    I welcome each comment, feedback and each suggestion which could help me to fix this problem.
    Thanks
    Chris

    Hi Chris,
    This issue has been discussed many times before. Please use the top right corner search box.
    I searched for "error, 1904, install, crystal, visual studio" keywords and here are the results.
    http://search.sap.com/ui/scn#query=error%2C+1904%2C+install%2C+crystal%2C+visual+studio&startindex=1&filter=scm_a_site%28scm_v_Site11%29&filter=scm_a_modDate%28*%29&timeScope=all
    - Bhushan
    Senior Engineer
    SAP Active Global Support
    Follow us on Twitter
    Got Enhancement ideas? Try the SAP Idea Place
    Getting started and moving ahead with Crystal Reports .NET applications.

  • DPM 2012 R2 long backup to tape job randomly fail after installing SCCM 2012 Client

    Hello,
    I'm managing a two nodes 2012 R2 file server cluster that contains a 16To CSV. I'm using DPM 2012 R2 to backup this entire shared volume directly to LTO 4 tapes, the job last about 55h.
    Since SCCM 2012 client has been installed(I don't manage it), the tape jobs are failing ramdomly after several hours with the error:
    Type: Tape backup
    Status: Failed
    Description: The DPM service was unable to communicate with the protection agent on serverX.xxxx.xxx . (ID 52 Details: The semaphore timeout period has expired (0x80070079))
     More information
    End time: 19/07/2014 03:11:06
    Start time: 18/07/2014 22:00:00
    Time elapsed: 05:11:05
    Data transferred: 768 289,56 MB
    Cluster node serverX.xxxx.xxx
    Source details: G:\
    Protection group members: 1
     Details
    Protection group: File Server Tape Protection
    Library: Quantum PX500 Series Medium Changer
    Tape Label (Barcode): File Server Tape Protection-00000230 (000043L4)
    If I uninstall SCCM 2012 client, no more issue, backups succeed. I've asked our SCCM team, no specific task has been scheduled or deployed in SCCM.
    I can't see anything abnormal in logs.
    Any idea?

    I have disabled "Configuration Manager Maintenance" and I have also tried to set the registry value HKLM\Software\Microsoft\CCM\CcmEval\NotifyOnly to TRUE and still the same issue.
    I can't find any correlated errors in the Windows event logs, task scheduler history neither in the DPM logs.
    I've increased the log level of DPM by following the following procedure
    http://blogs.msdn.com/b/george_bethanis/archive/2013/11/04/how-to-collect-dpm-verbose-logs.aspx
    Now i'm suspecting the maintenance job of Windows 2012 R2, i'll try to disabled this task. But the fact is that I don't have this backup issue if SCCM 2012 client is not installed.
    I'm waiting for next logs and will keep you informed

  • Problem Installing SCCM 2012 R2 client on Windows Thin PC 7 (Windows Embedded)

    Hi, I'm trying to install SCCM 2012 R2 client on Windows thin pc 7
    I check the ccmsetup.log and it returned this:
    Failed to get list of protected volume: List pointer is NULL (3)
    ccmsetup 07/08/2014 08:06:26''
    2040 (0x07F8)
    DetectEWF failed with 0x80070003. ccmsetup
    07/08/2014 08:06:26'' 2040 (0x07F8)
    DetectWindowsEmbeddedWF failed with 0x80070003.
    ccmsetup 07/08/2014 08:06:26''
    2040 (0x07F8)
    A Fallback Status Point has not been specified.  Message with STATEID='304' will not be sent.
    ccmsetup 07/08/2014 08:06:26''
    2040 (0x07F8)
    Cannot install over embedded OS with WF enabled on the system drive.
    ccmsetup 07/08/2014 08:06:26''
    2040 (0x07F8)
    CcmSetup failed with error code 0x80004005 ccmsetup
    07/08/2014 08:06:26'' 1960 (0x07A8)
    Can somebody help me?
    Thanks
    Renzo
    PD: Sorry for my bad English

    Cannot install over embedded OS with WF enabled on the system drive.
    You have to disable write filters on that device first.
    Torsten Meringer | http://www.mssccmfaq.de

  • Client installation: MsiHandler.dll failed to register. HRESULT -2147024769

    Due to a company merger, I had to move approx 200 clients from a SCCM 2012 R2 site to a SCCM 2012 SP1 site. I did this by uninstalling all clients, uninstalling the SCCM 2012 R2 site, cleaned up, set up boundaries and AD publishing on the SCCM 2012 SP1 site,
     then changing the SCCM SUP GPO to point to the new SUP.
    Almost all clients successfully installed the agent and assigned to the new site , expect for 4.
    I have tried:
    ccmclean.exe
    http://sccmclictr.codeplex.com/ (Reset DCOM permissions, Register common DLL's, Reset WMI Repository, Repair Agent)
    None of these helped
    ccmsetup.log
    <![LOG[MSI: Module C:\Windows\CCM\MsiHandler.dll failed to register.  HRESULT -2147024769.  Contact your support personnel.]LOG]!><time="12:34:13.529-60" date="11-26-2013" component="ccmsetup" context=""
    type="3" thread="3852" file="msiutil.cpp:300">
    <![LOG[MSI: Action 12:34:13: Rollback. Rolling back action:]LOG]!><time="12:34:13.639-60" date="11-26-2013" component="ccmsetup" context="" type="0" thread="3852" file="msiutil.cpp:314">
    <![LOG[File C:\Windows\ccmsetup\{59A0EA77-D28C-4286-83A6-04BB57B9CDD6}\client.msi installation failed. Error text: ExitCode: 1603
    Action: SelfRegModules.
    ErrorMessages:
    Module C:\Windows\CCM\MsiHandler.dll failed to register.  HRESULT -2147024769.  Contact your support personnel.
    ]LOG]!><time="12:34:18.014-60" date="11-26-2013" component="ccmsetup" context="" type="3" thread="3852" file="msiutil.cpp:872">
    client.msi.log
    CustomAction +MsiHandler_dll.EDFC37A5_EC0F_4170_9D99_8A7F441C1017 returned actual error code -2147024769 (note this may not be 100% accurate if translation happened inside sandbox)
    MSI (s) (E0:48) [12:34:13:529]: Product: Configuration Manager Client -- Error 1904. Module C:\Windows\CCM\MsiHandler.dll failed to register.  HRESULT -2147024769.  Contact your support personnel.
    Error 1904. Module C:\Windows\CCM\MsiHandler.dll failed to register.  HRESULT -2147024769.  Contact your support personnel.

    Hi Jason,
    Thank you for your reply.
    Correction, there are 3 affected systems. One is a Windows Server 2003 SP2 32-bit, the last two are Windows Server 2008 R2 SP1. All three have the same error.
    The msihandler.dll is extracted from the client.msi during installation to the C:\windows\ccm folder. When the installation fails, it rolls back and deletes the CCM folder. But I was able to get a copy of the msihandler.dll file, and tried registering it
    manually, which failed with a general error that the specified module could not be found. I also copied the file from a working system, but it still failed.
    The Windows app event log reflects the same error during MSI installation as the log files.
    The systems does have SCEP from the previous SCCM site installed and running. I uninstalled it on of the the VMs and rebootet, but SCCM client installation still fails with the same error.

  • SCCM 2012 Client.msi Fails

    I am able to install the SCCM client on many machines, but two machines are failing.  First I looked in ccmsetup.log:
    <![LOG[File C:\Windows\ccmsetup\{59A0EA77-D28C-4286-83A6-04BB57B9CDD6}\client.msi installation failed. Error text: ExitCode: 1603
    Action:
    ErrorMessages:
    ]LOG]!><time="16:25:20.476+00" date="03-16-2013" component="ccmsetup" context="" type="3" thread="1512" file="msiutil.cpp:860">
    <![LOG[Next retry in 120 minute(s)...]LOG]!><time="16:25:20.507+00" date="03-16-2013" component="ccmsetup" context="" type="0" thread="1512" file="ccmsetup.cpp:7554">
    Then i looked at client.msi.log for more detail, and searced for "return value 3".  This log file is hug so i included an excerpt from it.  Let me know where to look in the log file for more descriptive text.
    [15:43:48] Automatic Delayed Start configuration is enabled for CCMEXEC
    MSI (s) (70:64) [15:43:48:682]: Executing op: CustomActionSchedule(Action=CcmRegisterWinTaskRollback,ActionType=3329,Source=BinaryData,Target=CcmRegisterWinTaskRollback,)
    MSI (s) (70:64) [15:43:48:697]: Executing op: ActionStart(Name=CcmRegisterWinTask,Description=Registers tasks with Windows Task Scheduler.,)
    MSI (s) (70:64) [15:43:48:697]: Executing op: CustomActionSchedule(Action=CcmRegisterWinTask,ActionType=3073,Source=BinaryData,Target=CcmRegisterWinTask,)
    MSI (s) (70:64) [15:43:48:697]: Creating MSIHANDLE (24379) of type 790536 for thread 1892
    MSI (s) (70:10) [15:43:48:697]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI6477.tmp, Entrypoint: CcmRegisterWinTask
    MSI (s) (70!24) [15:43:48:713]: Creating MSIHANDLE (24380) of type 790531 for thread 3620
    MSI (s) (70!24) [15:43:48:713]: Closing MSIHANDLE (24380) of type 790531 for thread 3620
    [15:43:48] Registering windows task 'Configuration Manager Idle Detection'
    MSI (s) (70:10) [15:43:48:713]: Closing MSIHANDLE (24379) of type 790536 for thread 1892
    CustomAction CcmRegisterWinTask returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    MSI (s) (70:64) [15:43:48:760]: User policy value 'DisableRollback' is 0
    MSI (s) (70:64) [15:43:48:760]: Machine policy value 'DisableRollback' is 0
    Action ended 15:43:48: InstallFinalize. Return value 3.
    MSI (s) (70:64) [15:43:48:838]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1114668398,LangId=1033,Platform=589824,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
    MSI (s) (70:64) [15:43:48:838]: Executing op: DialogInfo(Type=0,Argument=1033)
    MSI (s) (70:64) [15:43:48:838]: Executing op: DialogInfo(Type=1,Argument=Configuration Manager Client)
    MSI (s) (70:64) [15:43:48:838]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
    MSI (s) (70:64) [15:43:48:838]: Executing op: ActionStart(Name=CcmRegisterWinTask,Description=Registers tasks with Windows Task Scheduler.,)
    MSI (s) (70:64) [15:43:48:838]: Executing op: ProductInfo(ProductKey={D6804B3A-BFEC-4AB4-BFA5-FD9BECC80630},ProductName=Configuration Manager Client,PackageName=client.msi,Language=1033,Version=83893884,Assignment=1,ObsoleteArg=0,,,PackageCode={59A0EA77-D28C-4286-83A6-04BB57B9CDD6},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)
    MSI (s) (70:64) [15:43:48:838]: Executing op: ActionStart(Name=CcmRegisterWinTaskRollback,Description=Rolls back the changes made by CcmRegisterWinTask.,)
    MSI (s) (70:64) [15:43:48:838]: Executing op: CustomActionRollback(Action=CcmRegisterWinTaskRollback,ActionType=3329,Source=BinaryData,Target=CcmRegisterWinTaskRollback,)
    MSI (s) (70:64) [15:43:48:838]: Creating MSIHANDLE (24381) of type 790536 for thread 1892
    MSI (s) (70:8C) [15:43:48:838]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI6504.tmp, Entrypoint: CcmRegisterWinTaskRollback
    MSI (s) (70!DC) [15:43:48:853]: Creating MSIHANDLE (24382) of type 790531 for thread 3548
    MSI (s) (70!DC) [15:43:48:853]: Closing MSIHANDLE (24382) of type 790531 for thread 3548
    MSI (s) (70:8C) [15:43:48:853]: Closing MSIHANDLE (24381) of type 790536 for thread 1892
    [15:43:48] Removing windows task 'Configuration Manager Idle Detection'
    From successfully installation i typically see folders created in C:\Windows\CCM\* but in this particular case there are only a couple .tmp files and other misc.  Where should i look next?  I have tried ccmsetup.exe /uninstall and then ccmsetup.exe
    /mp:<machine> SMSSITECODE=<code> /noservice and also with /service.
    I have tried winmgmt /resetrepository
    I have checked that BITS service is running.
    What else should i look for?
    thanks

    Did someone able to find the root cause of it and able to it resolve it, i'm currently facing the same issue:
    Error 1904. Module C:\Windows\CCM\DCMADQueryProvider.dll failed to register.
    HRESULT -2147024703. Contact your support personnel"
    This error is not
    restricted to any 1 dll but it's random like DCMADQueryProvider.dll,
    statusagent.dll, ccmcore.dll
    •I'm getting this error while installing
    SCCM 2012 client.
    Steps i tried:
    1.I did try manually registering
    oringinally but when the client fails to install, it removes all the source
    files including the ccmcore.dll. So, ccmcore.dll doesn't reside on the system
    after failing to install the client or at least not that I can see.
    2. I
    have tried timing it just right so that my "regsvr32 ccmcore.dll" is run during
    the install process while the file is in the CCM folder but that didnt work
    either.
    3. I had manually created the directory CCM\x64\ccmcore.dll and
    copied the file from a working client and try to register but it gave me an
    error " Failed to load .dll"
    4. i have tried uninstalling the client from
    ccmclean and tried to reinstall it but still it fails.
    Currently not sure what is wrong with the client install, so still
    investigating the issue, please help if someone was able to solve the issue.
    There are some
    articles out there which points to resolving this issue by registering
    ATL.dll.
    However, in this
    case ATL.dll has been registered only 1 times using regsvr32.exe (system32 and
    syswow64 folders).
    Based on procmon :
    HKCR\Wow6432Node\CLSID\{44EC053A-400F-11D0-9DCD-00A0C90391D3}\InprocServer32\
    While installing, it was looking for ATL.DLL and found the location from
    registry as "“%systemroot%\system32\atl.dll”

  • Getting "querypanel.dll failed to register" on Windows 7 32 bit machine

    Trying to move from CR 2008 SP2 to CR 2008 SP3.
    For the CR 2008 SP2 version of our application, which runs our Crystal .rpt files, we used Visual Studio 2005.  we then created a Visual Studio .msi file, using the merge module (CRRuntime_12_2), to install this application on a target machine that had .NET Framework 2.0 and VC++ Redistributable 2005 SP1 installed. If these two latter prerequisites were not installed, our install would fail because the CEReportSource.dll could not be registered.
    After installing CR SP3 on my development machine, we created a new Visual Studio project, again using Visual Studio 2005. I used CRRuntime_12_3 as the merge module and everything else was the same.
    I was getting this same error message "CEReportSource.dll failed to register" when I attempt to install the SP3 version of the app on the very same machine on which I previously successfully installed the SP2 version. I found an answer in these forums to install Microsoft Visual C++ 2005 SP1 update. Even this did not help. When I installed  MS VC++  2008 Redistributable - x86 9.0.30729.17, finally the problem of "CEReportSource.dll failed to register"  went away on XP and Vista machines.
    Now I am trying to install my program on Windos 7 32 bit machine and I get "querypanel.dll failed to register".
    Q1. By installing S VC++  2008 Redistributable - x86 9.0.30729.17, the problem of "CEReportSource.dll failed to register" did not occur. Is this the right thing to do. I am not sure why VC++ 2005 SP1 did not fix the issue.
    Q2.What do we need in order to prevent "querypanel.dll failed to register" error on Windows 7 32 bit machine.
    Thanks for your time.

    Moved to .NET SDK forum.
    Search here, lots of info on distribution. Likely caused by MS updated the C++ runtime to include security updates. Go to MS's site and download the latest C++ distribution package with enhanced security.
    If you use the CR MSI package rather than the Merge Modules it should work.
    Thank you
    Don
    Edited by: Don Williams on Nov 9, 2010 2:16 PM

  • Open Procedure for service "BITS" in DLL "C:\Windows\system32\bitsperf.dll" failed

    This error is occurring on my Windows Server 2008R2 server with SQL 2008R2 installed.  I have found lots of "help" but none of it works...
    The Open Procedure for service "BITS" in DLL "C:\Windows\system32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
    The "help" I have found...
    http://technet.microsoft.com/en-us/library/cc774913(WS.10).aspx
    http://support.microsoft.com/kb/300956 

    I was able to re-install BITS.  The BITS error seems to have gone away, but this error is now showing...
    The object length of an object returned by Extensible Counter DLL "C:\Windows\system32\wbem\wmiaprpl.dll" for the "WmiApRpl" service was not correct. The sum of the object lengths returned did not match the size of the buffer returned.  The performance
    data returned by the counter DLL will not be returned in the Perf Data Block. The first four bytes (DWORD) of the Data section contains the count of objects.
    Help?

  • Importent6.dll fails to register on WTS (Citrix & Windows 2003 64bit)

    Hi,
    I am trying to install the BOE XI 3.1 client tools on a 64bit Windows 2003 R2 SP2 machine (used as Windows Terminal Server) and I get the message that importent6.dll and exportSDK.dll fail to register during the installation.
    Did anyone of you out there had a similar problem so far? Due to the error I cannot get the import wizard installed.
    Additionally it would be interesting to know if it is possible to use the import wizard XI 3.1  as a terminal server application in a WTS (64bit) environment.
    Regards,
    Stratos

    Hi,
    with regards to the "(x86)" folder i would not recommend installing the BOE Client Tools into that folder. Please create a own Folder (you can for sure do this on drive D:) and install it into the folder. You could create a "Program Files" folder instead of installing it into the "Program Files (x86)" Folder.
    About the Errormessage of your .dll`s please check SAP Note - 1205687
    https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361706E6F7465735F6E756D6265723D3132303536383726
    About Windows7. Windows7 is only supported since SP3. Please use the SP3 Fill Build setup routine for the BOE Clients for installing on Windows7.
    Regards
    -Seb.

  • How do I fix this error: Module C:\Program Files\Bonjour\mdnsNSP.dll failed to register. HRESULT -2147024769. Contact your support personnel.

    I am trying to install iTunes, and get this error: "Module C:\Program Files\Bonjour\mdnsNSP.dll failed to register. HRESULT -2147024769. Contact your support personnel."
    Any ideas on how to fix this error, or get the install to comlete?

    *complete...

  • The Open Procedure for service "WDSTFTP" in DLL "C:\Windows\system32\wdstftp.dll" failed. WDS not PXE booting!

    This morning came in to find clients were not getting there bootfiles through PXE. I checked the logs to find the following events related to WDS.
    The Open Procedure for service "WDSTFTP" in DLL "C:\Windows\system32\wdstftp.dll" failed
    The Open Procedure for service "WDSServer" in DLL "C:\Windows\system32\wdssrv.dll" failed
    The Open Procedure for service "WDSMC" in DLL "C:\Windows\system32\wdsmc.dll" failed
    Has anyone seen this or have a link to a resolution?
    tconners

    Hotfix loaded but didn't help.
    Found a few articles referring to rebuilding the perf counter library. I ran "lodctr /R" failed first time then worked the second time. I believe the errors:
    The Open Procedure for service "WDSTFTP" in DLL "C:\Windows\system32\wdstftp.dll" failed
    The Open Procedure for service "WDSServer" in DLL "C:\Windows\system32\wdssrv.dll" failed
    The Open Procedure for service "WDSMC" in DLL "C:\Windows\system32\wdsmc.dll" failed
    Are gone but PXE boot still fails.
    Do you think I might have to uninstall WDS and reinstall? "Using SCCM console to just remove PXE"
    tconners

  • C:\Windows\system32\bitsperf.dll" failed

    Log Name:      Application
    Source:        Microsoft-Windows-Perflib
    Date:          10/23/2013 4:36:55 AM
    Event ID:      1008
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      xxxxxxxxxxx
    Description:
    The Open Procedure for service "BITS" in DLL "C:\Windows\system32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Perflib" Guid="{13B197BD-7CEE-4B4E-8DD0-59314CE374CE}" EventSourceName="Perflib" />
        <EventID Qualifiers="49152">1008</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2013-10-23T02:36:55.000Z" />
        <EventRecordID>355461</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>Application</Channel>
        <Computer>SWAMR0041.INDUSTRIE.AMMANN.INTRA</Computer>
        <Security />
      </System>
      <UserData>
        <EventXML xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="Perflib">
          <param1>BITS</param1>
          <param2>C:\Windows\system32\bitsperf.dll</param2>
          <binaryDataSize>8</binaryDataSize>
          <binaryData>0200000000000000</binaryData>
        </EventXML>
      </UserData>
    </Event>
    Tried to rebuild the counters 
    1. lodctr bitsperf.dll
    2. lodctr \R
    3. lodctr /e:bitsperf.dll
    After performing the above still getting the issue.
    Microsoft Provided steps are confusing.
    Can any one provide me the detailed steps to resolve the issue ?
    Shashidhar N Bharadwaj

    I actually ran into this issue myself and I found this to be my fix.
    "Unable to add these counters:
    \Memory\Available MBytes
    \Memory\% Committed Bytes In Use
    \Memory\Cache Faults/sec
    \Memory\Cache Faults/sec
    \PhysicalDisk(*)\%Idle Time
    \PhysicalDisk(*)\Avg. Disk Queue Length
    \Network Interface(*)\Bytes Total/sec"
    after that I checked my Test Server and saw the same error in Windows Server 2012. I searched and found a lot of info
    about this error in earlier version of Windows but not for Server 2012 and therefore decided to write a wiki about it. It is my first English wiki and I want to write this wiki for other people who may have similar problem because Ed Price suggested us:
    Below are some steps to be followed.
    Steps:
    We have to rebuild Performance Counters with LODCTR from an elevated command prompt.
    1. Launch Command Prompt as Administrator (right click Runs As Administrator).
    2. Drop into the C:\WINDOWS\System32 directory by typing CD\ then CD Windows\System32
    3. To rebuild your resource counters type the following command:
    lodctr /r
    This will rebuild your counter values and may take a few moments so please be patient.
    4. If you wish to query the counters to make sure they were correctly set, use:
    lodctr /q
    This will give you something like the following:
    Performance Counter ID Queries [PERFLIB]:
        Base Index: 0x00000737 (1847)
        Last Counter Text ID: 0x000031D2 (12754)
        Last Help Text ID: 0x000031D3 (12755)
    [.NET CLR Data] Performance Counters (Enabled)
        DLL Name: %systemroot%\system32\netfxperf.dll
        Open Procedure: OpenPerformanceData
        Collect Procedure: CollectPerformanceData
        Close Procedure: ClosePerformanceData
    [.NET CLR Networking] Performance Counters (Enabled)
        DLL Name: %systemroot%\system32\netfxperf.dll
        Open Procedure: OpenPerformanceData
        Collect Procedure: CollectPerformanceData
        Close Procedure: ClosePerformanceData
    and etc
    5.Now reopen the Performance Monitor and check it. You will see that the error was fixed.
    Note 1:
    In the query if you have provider name that is Disabled, Use this Cmdlet to enable it.
    lodctr /e:<provider name>
    for example (think in above query Performance Counters is disable ) :
    lodctr /e:Performance Counters
    Note 2:
    If you perform this step and it doesn't work, please see the event log and search for if there is Event ID = 3006 in it? if yes, 
    please go to registry and change Disable Performance Counters from "1" to "0".
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib
    Hope this is helpful. 

  • Explorer.exe Application Error - Faulting module name: Windows.UI.Xaml.dll

    We are having a problem with one of our Windows 2012 R2 Terminal Server. The server keeps maxing out CPU to 100% the only way to resolve the issue is by restarting the guest OS. When I have been trying to troubleshoot the issue. I have noticed the following
    error is appearing in the event log. I have tried various research online but have been unable to find a resolution to the issue.  Anyone have any ideas?
    Faulting application name: explorer.exe, version: 6.3.9600.17415, time stamp: 0x54503a3a
    Faulting module name: Windows.UI.Xaml.dll, version: 6.3.9600.17415, time stamp: 0x54504b1a
    Exception code: 0xc000027b
    Fault offset: 0x0000000000982bea
    Faulting process id: 0xd44
    Faulting application start time: 0x01d0526d40641d26
    Faulting application path: C:\Windows\explorer.exe
    Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
    Report Id: 80a05322-be60-11e4-80db-005056bd0cad
    Faulting package full name:
    Faulting package-relative application ID:

    Hi,
    Please test the issue in Clean Boot first. For the detailed steps, please refer to the following Microsoft KB article:
    How to perform a clean boot in Windows
    http://support.microsoft.com/kb/929135
    Also seems you should try to uninstall IE and install it again but before that you can run command type:
    SFC /SCANNOW and let the system to scan your DLL files and repair them, then reinstall the new IE.
    For general reference, windows.UI.xmal.dll can handle several file in background process. For more detail refer
    this article.
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • CR for VS2010 deployment - crtslv.dll failed to register

    I'm still having problems with packaging up the CR for VS2010 library with our applications installation.
    I'm using InstallShield 2011 for the installation setup.
    I've included the CRRuntime_13_0.msm file. (That is the only MSM file I included, are the others needed also?)
    I've included the Microsoft Visual C++ 2005 SP1 Redistributable Package (x86 and the x64 versions.)
    I have tried to do a test install on both a 64bit and a 32bit Windows 7 computer and it keeps giving me the crtslv.dll failed to register error on both computers.
    Error 1904.Module C:\Program Files\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86\crtslv.dll failed to register.  HRESULT -2147010895.  Contact your support personnel.
    I thought it might just be due to the 32 bit MSM causing the problem on the 64bit computer, but I can't even get it to install on a 32bit computer. (On the 32bit computer install, I even removed the x64 bit version of the MS C++ 2005 Redistributable from the installation setup just to make sure it wasn't causing a problem).
    I have even tried having my Install Shield setup 'Chain' the CRRuntime_32bit_13_0.msi file to my main installation (not using the Merge module). Even when that runs, it produces the same crtslv.dll failed to register again.
    BUT, if I run the CRRuntime_32bit_13_0.msi manually on the computer it installs correctly. (I even tried using the same /qf parameters that InstallShield is using on it and it also worked OK that way.)  So I can't figure out how to get it to run in conjunction with my InstallShield installation.
    Can anyone give me any suggestions?
    Mike...

    I finally got past this issue and got things to install, with a few hackish work-arounds.
    First the CR13 msm redistributable appears to requre the 32 bit version of "Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security" that you'll read about in every post.  On 64 bit machines I found that even when it was installed,I would still get a crtslv.dll failed to register message, followed several other dlls not registering.  Once I installed the 32 bit version on the 64 bit OS, the crystal 13 redistibutable installed fine everytime.  I did this on several 64 bit VMs all running Server 2003,XP, and Windows 7.  It ran fine every time.
    The problem you'll face is how do you install the 32 bit version of this ATL security pack on a 64 bit machine.  You may be able to download and run the 32 bit version from Microsoft's site with the link Ludek has posted.  That wouldn't work for me because I had to distribute it with my software so I used the prerequisite available for InstallShield.  The prereq however is designed to only run on 32 bit machines, so I edited it in InstallShield and modifed the conditions to allow it to run on both 32 & 64 bit operating systems. 
    The next problem encountered is that this 32 bit prereq getting installed on a 64 bit machine will result in an error being returned that the installation appears to have failed.  Well it is a 32 bit installation not intended for a 64 bit OS and we're not supposed to do that.  I did say hackish work-around.  The 32 & 64 bit files are installed to different directories and the 64 bit version does not get overwritten.   If you check the event viewer you'll see a message logged in that the installation of the ATL prereq completed sucessfully.  So I modified the behavior of the prereq in InstallShield to "continue the setup if the condition still indicates it is required after completion".  Now it runs without error and everything for Crystal installs sucessfully.
    The final problem was also with the pre-requisite.  The code determines if it is already installed by looking for the file:
    [WindowsFolder]\WinSxS\x86_Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_8.0.50727.4053_x-ww_473666fd\ATL80.dll
    I found on some machines it was previousy installed to:
    [WindowsFolder]\WinSxS\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.4053_none_d1c738ec43578ea1\
    This results in the prereq being required every time because the file it's checkig for is not found.  Furthermore, it fails every time, most likely because it's alreday installed and not supposed to be installed again.  So once again, I modified the prereq conditios in InstallShield and made it look for the file in both locations to determine if it was installed.
    I haven't seen any problems since with either the Crystal runtime or the ATL update.  Happy day.
    The part I stll don't understand is that SAP says they can't distribute the ATL update in their MSM because of licensing issues, but we can sell our software and distribute it freely.  Microsoft even create the prereq so that we could distribute it freely.  So why can't SAP distribute the required files for their runtime?  A lot of people on these threads have wasted a lot of time and money on this issue.  Ludek provides great support but maybe this issue needs to be investigated further by development.

  • [Forum FAQ] Management Point fails after installing SCCM 2012 SP1

    Symptom:
    The Management Point might fail to be installed after you install SCCM 2012 sp1 on Windows Server 2012, either fresh install or others.
    You might see some errors in mpMSI.log like listed below.
    “Setup was unable to compile the file CcmExec_Global.mof”
    “The error code is 80041002”
    Cause:
    Reinstall Management Point cannot work. This is because CCM Namespace remains in WMI which prevents SCCM from installing MP. You need clear CCM Namespace from WMI.
    Resolution:
    1. Uninstall Management Point from the console, then wait for the uninstallation to finish in MPSetup.log.
    2. Open Wbemtest -> Connect to root -> Click Enum Classes and choose Recursive -> Double click _NAMESPACE in Query Result dialog -> Click Instances -> Delete  _NAMESPACE.Name=”ccm”
    3. Install Management Point.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    Symptom:
    The Management Point might fail to be installed after you install SCCM 2012 sp1 on Windows Server 2012, either fresh install or others.
    You might see some errors in mpMSI.log like listed below.
    “Setup was unable to compile the file CcmExec_Global.mof”
    “The error code is 80041002”
    Cause:
    Reinstall Management Point cannot work. This is because CCM Namespace remains in WMI which prevents SCCM from installing MP. You need clear CCM Namespace from WMI.
    Resolution:
    1. Uninstall Management Point from the console, then wait for the uninstallation to finish in MPSetup.log.
    2. Open Wbemtest -> Connect to root -> Click Enum Classes and choose Recursive -> Double click _NAMESPACE in Query Result dialog -> Click Instances -> Delete  _NAMESPACE.Name=”ccm”
    3. Install Management Point.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Maybe you are looking for

  • Void Methods and Value Returning Methods in Java

    Hello, I'm new here so please let me know if I overstep any of the rules or expectations. I merely want to learn more about Java Programming efficiently, and easily. I can ask and discuss these topics with my online prof, but she doesn't have much ti

  • Table for inspection plan

    hi all , what are the tables related to  inspection plan in QM Module regards

  • Working with 32 bit color HDRs in Lightroom

    The feature of being able to work with 32 bit color Tiff files in Lightroom is awesome and wonderful.  However, I note that when I do not follow the recommended workflow of bringing the 32 bit file directly back into Lightroom to work on it - working

  • Load Balancer cookie

    Hey, A question about Sun Portal Server 6 2004Q2: Is there a cookie that can be used by load balancers for sticky session in Portal? If so, how is it configured?

  • 11I.OWF.G: WORKFLOW DIAGRAM EXPEDITE BUTTON

    제품: AOL 작성날짜 : 2005-11-30 11I.OWF.G: WORKFLOW DIAGRAM EXPEDITE BUTTON ============================================= PURPOSE Explanation OWF.G Roll Up Patch 7 (patch 3868138.) 이상을 적용 하시면 Expedite Button은 더 이상 사용하실 수 없다고 합니다. 사용자들이 이 Expedite Button을 이