none
Ошибка при старте службы Data Protection Manager (DPM) RRS feed

  • Вопрос

  • Добрый день, коллеги. После очередного перезапуска сервера, не стартует служба Data Protection Manager (DPM). Перезагрузки не помогли.  Выдает ошибку:

    Log Name:      Application
    Source:        MSDPM
    Date:          10/12/2015 8:31:52 AM
    Event ID:      976
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      HYPERV.lan.net
    Description:
    The description for Event ID 976 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    
    If the event originated on another computer, the display information had to be saved with the event.
    
    The following information was included with the event: 
    
    The DPM job failed because it could not contact the DPM engine.
    
    Problem Details:
    <JobTriggerFailed><__System><ID>9</ID><Seq>0</Seq><TimeCreated>10/12/2015 5:31:52 AM</TimeCreated><Source>TriggerJob.cs</Source><Line>172</Line><HasError>True</HasError></__System><Tags><JobSchedule /></Tags></JobTriggerFailed>
    
    
    the message resource is present but the message is not found in the string/message table
    
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSDPM" />
        <EventID Qualifiers="0">976</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2015-10-12T05:31:52.000000000Z" />
        <EventRecordID>907050</EventRecordID>
        <Channel>Application</Channel>
        <Computer>HYPERV.lan.net</Computer>
        <Security />
      </System>
      <EventData>
        <Data>The DPM job failed because it could not contact the DPM engine.
    
    Problem Details:
    &lt;JobTriggerFailed&gt;&lt;__System&gt;&lt;ID&gt;9&lt;/ID&gt;&lt;Seq&gt;0&lt;/Seq&gt;&lt;TimeCreated&gt;10/12/2015 5:31:52 AM&lt;/TimeCreated&gt;&lt;Source&gt;TriggerJob.cs&lt;/Source&gt;&lt;Line&gt;172&lt;/Line&gt;&lt;HasError&gt;True&lt;/HasError&gt;&lt;/__System&gt;&lt;Tags&gt;&lt;JobSchedule /&gt;&lt;/Tags&gt;&lt;/JobTriggerFailed&gt;
    </Data>
        <Binary>3C004A006F00620054007200690067006700650072004600610069006C00650064003E003C005F005F00530079007300740065006D003E003C00490044003E0039003C002F00490044003E003C005300650071003E0030003C002F005300650071003E003C00540069006D00650043007200650061007400650064003E00310030002F00310032002F003200300031003500200035003A00330031003A0035003200200041004D003C002F00540069006D00650043007200650061007400650064003E003C0053006F0075007200630065003E0054007200690067006700650072004A006F0062002E00630073003C002F0053006F0075007200630065003E003C004C0069006E0065003E003100370032003C002F004C0069006E0065003E003C004800610073004500720072006F0072003E0054007200750065003C002F004800610073004500720072006F0072003E003C002F005F005F00530079007300740065006D003E003C0054006100670073003E003C004A006F0062005300630068006500640075006C00650020002F003E003C002F0054006100670073003E003C002F004A006F00620054007200690067006700650072004600610069006C00650064003E00</Binary>
      </EventData>
    </Event>



    12 октября 2015 г. 6:02

Ответы

  • Решил проблему. Помог вот этот совет:

    1) Apply the ServicesPipeTimeout registry setting: This registry setting helps avoid failures when installing DPM and DPM updates or after moving to a new network with more latency.

        Launch Registry Editor (regedit) and navigate to the following key:
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
        Click the Edit menu and select New and DWORD (32-bit) Value
        Type ServicesPipeTimeout (case-sensitive) for the name and press Enter
        Right-click the ServicesPipeTimeout DWORD entry that you created and click Modify
        Select Decimal
        Type 300000 in the Value data field and click OK
        Restart the computer


    2) After restarting the server, then I ran the following command to cleanup the DMP database.

    Выполнить => cmd

        dpmsync -sync




    12 октября 2015 г. 8:07