Results 1 to 2 of 2
  1. #1
    Join Date
    Aug 2006

    Unanswered: Snapshot Agent Retried and Failed

    Hello, need some guidance.

    I noticed that my snapshot agent never got moving at all and has been failing. It keeps on generating errors in the System Log with every retry...

    The server {08B0B2D9-3FB3-11D3-A4DE-00C04F610189} did not register with DCOM within the required timeout.

    and this

    SubSystem Message - Job 'mws-cpmorder-CPmOrder_Mobile-2' (0x669FF0D471C2A54FA11F764B1E3B0DFD), step 2 - Server execution failed

    in the application log.

    Any help is appreciated.


  2. #2
    Join Date
    Jan 2006
    I have got something on internet....

    Microsoft Knowledge Base wrote:

    DCOM Clients Cannot Create Objects

    View products that this article applies to.
    This article was previously published under Q187146
    IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

    256986 Description of the Microsoft Windows Registry


    Distributed Component Object Model (DCOM) client programs that run inside Terminal Server sessions other than the console cannot create objects of classes implemented inside DCOM servers running as Terminal Server services.

    You may also receive occurrences of event ID 10010 from DCOM in the Event Viewer with the following description:

    The server <clsid> did not register with DCOM within the required timeout.


    You may also receive the following error message:
    CoGetClassObject failed - Server Execution failed CO_E_SERVER_EXEC_FAILURE 0x80080005


    This behavior is because those object classes are considered as user globals by DCOM and Terminal Server.

    However, DCOM and Terminal Server provide the ability to register DCOM classes as system globals. But, in the case of classes implemented in services, they should be considered as system globals, unless they had been explicitly registered as user globals.


    WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

    To explicitly register a DCOM class as a system global, use the following steps:

    1. If it does not exist, create the following registry key:
    HKLM\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\CLSID

    2. Create a subkey with {CLSID} as its name, where the CLSID is the class identifier of the DCOM class that is to be a system global. For example, a subkey would be:


    3. Under the above subkey, create fSystemGlobalClass as the value name with a REG_DWORD type and set its value data to 1.

    Or, you can upgrade to Microsoft Windows 2000 Server with Terminal Services, which does not have the same restriction.


    Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.


    To reproduce this, use the DCOM sample named "ATLDRAW" provided with the ActiveX Template Library (ATL).
    Rajesh Patel

    Everybody says - mistake is the first step of success, but it's not true. The correction of the mistake is the first step of success.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts