none
DPM 2010 Protection Group for Windows XP DCOM error RRS feed

  • Question

  • I have Windows 2008 R2 server with DPM 2010 backing up server and workstations. When backing up Windows XP laptops, I get a DCOM error on the server every 30 minutes after and laptop is removed from the network until it returns.

     

    Is there any known issues with DPM 2010 backing up Windows XP?

    Log Name:      System

    Source:        Microsoft-Windows-DistributedCOM

    Date:          3/21/2011 9:23:19 AM

    Event ID:      10009

    Task Category: None

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:      XXX.XXX.XXX.net

    Description:

    DCOM was unable to communicate with the computer XXX.XXX.XXX.net using any of the configured protocols.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />

        <EventID Qualifiers="49152">10009</EventID>

        <Version>0</Version>

        <Level>2</Level>

        <Task>0</Task>

        <Opcode>0</Opcode>

        <Keywords>0x80000000000000</Keywords>

        <TimeCreated SystemTime="2011-03-21T16:23:19.000000000Z" />

        <EventRecordID>44419</EventRecordID>

        <Correlation />

        <Execution ProcessID="0" ThreadID="0" />

        <Channel>System</Channel>

        <Computer>server.XXX.XXX..net</Computer>

        <Security />

      </System>

      <EventData>

        <Data Name="param1">XXX.XXX.XXX.net</Data>

        <Binary>3C5265636F726423313A20436F6D70757465723D286E756C6C293B5069643D3734303B332F32312F323031312031363A32333A31393A3233393B5374617475733D313732323B47656E636F6D703D323B4465746C6F633D313731303B466C6167733D303B506172616D733D313B7B506172616D23303A307D3E3C5265636F726423323A20436F6D70757465723D286E756C6C293B5069643D3734303B332F32312F323031312031363A32333A31393A3233393B5374617475733D313732323B47656E636F6D703D31383B4465746C6F633D313434323B466C6167733D303B506172616D733D313B7B506172616D23303A50524F423337313931302E70726F626174696F6E2E736163636F756E74792E6E65747D3E3C5265636F726423333A20436F6D70757465723D286E756C6C293B5069643D3734303B332F32312F323031312031363A32333A31393A3233393B5374617475733D313732323B47656E636F6D703D31383B4465746C6F633D3332333B466C6167733D303B506172616D733D303B3E3C5265636F726423343A20436F6D70757465723D286E756C6C293B5069643D3734303B332F32312F323031312031363A32333A31393A3233393B5374617475733D313233373B47656E636F6D703D31383B4465746C6F633D3331333B466C6167733D303B506172616D733D303B3E3C5265636F726423353A20436F6D70757465723D286E756C6C293B5069643D3734303B332F32312F323031312031363A32333A31393A3233393B5374617475733D31303036303B47656E636F6D703D31383B4465746C6F633D3331313B466C6167733D303B506172616D733D333B7B506172616D23303A3133357D7B506172616D23313A307D7B506172616D23323A3078633138313065306130303030303030307D3E3C5265636F726423363A20436F6D70757465723D286E756C6C293B5069643D3734303B332F32312F323031312031363A32333A31393A3233393B5374617475733D31303036303B47656E636F6D703D31383B4465746C6F633D3331383B466C6167733D303B506172616D733D303B3E</Binary>

      </EventData>

    </Eve

    Monday, March 21, 2011 5:34 PM

Answers

  • Another thought, have you protected these XP laptops using the Client Protection feature or did you protect them as servers? If you protected them using the Servers option when you created the protection group then DPM will probe the protected servers every 30 minutes andif it cannot contact them it will log the DCOM evnt you are seeing.

     

    Marc

    Friday, July 15, 2011 2:48 PM
    Moderator

All replies

  •  

    I have Windows 2008 R2 server with DPM 2010 backing up server and workstations. When backing up Windows XP laptops, I get a DCOM error on the server every 30 minutes after and laptop is removed from the network until it returns.

     

     

    Is there any known issues with DPM 2010 backing up Windows XP?

    Log Name: System

    Source: Microsoft-Windows-DistributedCOM

    Date: 3/21/2011 9:23:19 AM

    Event ID: 10009

    Task Category: None

    Level: Error

    Keywords: Classic

    User: N/A

    Computer: XXX.XXX.XXX.net

    Description:

    DCOM was unable to communicate with the computer XXX.XXX.XXX.net using any of the configured protocols.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

    <System>

    <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />

    <EventID Qualifiers="49152">10009</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2011-03-21T16:23:19.000000000Z" />

    <EventRecordID>44419</EventRecordID>

    <Correlation />

    <Execution ProcessID="0" ThreadID="0" />

    <Channel>System</Channel>

    <Computer>server.XXX.XXX..net</Computer>

    <Security />

    </System>

    <EventData>

    <Data Name="param1">XXX.XXX.XXX.net</Data>

    <Binary>3C5265636F726423313A20436F6D70757465723D286E756C6C293B5069643D3734303B332F32312F323031312031363A32333A31393A3233393B5374617475733D313732323B47656E636F6D703D323B4465746C6F633D313731303B466C6167733D303B506172616D733D313B7B506172616D23303A307D3E3C5265636F726423323A20436F6D70757465723D286E756C6C293B5069643D3734303B332F32312F323031312031363A32333A31393A3233393B5374617475733D313732323B47656E636F6D703D31383B4465746C6F633D313434323B466C6167733D303B506172616D733D313B7B506172616D23303A50524F423337313931302E70726F626174696F6E2E736163636F756E74792E6E65747D3E3C5265636F726423333A20436F6D70757465723D286E756C6C293B5069643D3734303B332F32312F323031312031363A32333A31393A3233393B5374617475733D313732323B47656E636F6D703D31383B4465746C6F633D3332333B466C6167733D303B506172616D733D303B3E3C5265636F726423343A20436F6D70757465723D286E756C6C293B5069643D3734303B332F32312F323031312031363A32333A31393A3233393B5374617475733D313233373B47656E636F6D703D31383B4465746C6F633D3331333B466C6167733D303B506172616D733D303B3E3C5265636F726423353A20436F6D70757465723D286E756C6C293B5069643D3734303B332F32312F323031312031363A32333A31393A3233393B5374617475733D31303036303B47656E636F6D703D31383B4465746C6F633D3331313B466C6167733D303B506172616D733D333B7B506172616D23303A3133357D7B506172616D23313A307D7B506172616D23323A3078633138313065306130303030303030307D3E3C5265636F726423363A20436F6D70757465723D286E756C6C293B5069643D3734303B332F32312F323031312031363A32333A31393A3233393B5374617475733D31303036303B47656E636F6D703D31383B4465746C6F633D3331383B466C6167733D303B506172616D733D303B3E</Binary>

    </EventData>

    </Eve

    Monday, March 21, 2011 7:25 PM
  • Hey does any one else have problems backing up XP laptops and getting this error?
    Monday, March 28, 2011 3:51 PM
  • Hi Paul,

    it looks to me that this is a connection issue. any firewalls active? how is the client connected? everything should work fine on XP (sp2 and later)

    kind regards,

    Alex Smits

    Wednesday, April 6, 2011 7:24 PM
  • Thanks Alex,

    This is in a corporate environment so all firewalls are off. These are Windows XP w/ SP3 laptops on the corprat network connected with CAT5. The errors only happen on the DPM 2010 server when the computer are taken off the network.

    Thank you for any help you can give on this.

    Paul Sjoberg

    Thursday, April 7, 2011 3:34 PM
  • Paul,

    Were you able to resolve this or does the issue still occur? The DCOM error looks like what you would see when the DPM server probes for a protected SERVER and cannot reach it. With client protection I don't think that DPM does these probes since the client may or may not be connected to the network at anytime.

     

    Thanks,

    Marc

    Friday, July 15, 2011 2:38 PM
    Moderator
  • Another thought, have you protected these XP laptops using the Client Protection feature or did you protect them as servers? If you protected them using the Servers option when you created the protection group then DPM will probe the protected servers every 30 minutes andif it cannot contact them it will log the DCOM evnt you are seeing.

     

    Marc

    Friday, July 15, 2011 2:48 PM
    Moderator