locked
DPM 2012 Agent installation failure *Possible Bug* RRS feed

  • Question

  • Hello everyone,

    I may have discovered a new bug and I considered to share. We have 1 DPM 2012 server meeting all the standard requirements for deployment. Agent installations can proceed to all machines except certain Windows XP SP3 machines and the error log has been similar for all of them, please take a look:

    ******************************************************************************************************************************************

    The description for Event ID 997 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: 

    A non-fatal failure instance has been detected for process 'msdpm'. This will be reported to Microsoft.  

    Problem Details:
    <FatalServiceError><__System><ID>19</ID><Seq>10704</Seq><TimeCreated>17/05/2012 5:51:44 PM</TimeCreated><Source>DpmThreadPool.cs</Source><Line>163</Line><HasError>True</HasError></__System><ExceptionType>DlsException</ExceptionType><ExceptionMessage>MSDPM AgentInstallationFailure Code:[AMRemoteACPreInstallError], DetailedCode:[0], DetailedErrorCode:[], DetailedSource:[None],  DlsErrorCode:[346]</ExceptionMessage><ExceptionDetails>Microsoft.Internal.EnterpriseStorage.Dls.Utils.DlsException: MSDPM AgentInstallationFailure Code:[AMRemoteACPreInstallError], DetailedCode:[0], DetailedErrorCode:[], DetailedSource:[None],  DlsErrorCode:[346] ---&gt; System.OverflowException: Length of the access control list exceed the allowed maximum.
       at System.Security.AccessControl.RawAcl.InsertAce(Int32 index, GenericAce ace)
       at Microsoft.Internal.EnterpriseStorage.Dls.AgentManager.Win32.LocalGroup.Win32LocalGroup.AddComputerToComSecurity(FqMachineName server, FqMachineName computerName)
       at Microsoft.Internal.EnterpriseStorage.Dls.AgentManager.ACInstallMachine.JustEnableRemoteDcom(Message msg)
       at Microsoft.Internal.EnterpriseStorage.Dls.AgentManager.AMFsm.Impersonating(Message msg, Action action)
       at Microsoft.Internal.EnterpriseStorage.Dls.AgentManager.ACInstallMachine.EnableRemoteDcom(Message msg)
       --- End of inner exception stack trace ---
       at Microsoft.Internal.EnterpriseStorage.Dls.AgentManager.AMErrorHandler.InvokeWatson(DlsException amException, Guid jobId)
    *** Mojito error was: AMRemoteACPreInstallError; 0; None</ExceptionDetails></FatalServiceError>


    the message resource is present but the message is not found in the string/message table

    *******************************************************************************************************************************************

    Seems to be a programming issue.... can anyone shed some light from the DPM development team?



    • Edited by Abdul Khans Friday, May 18, 2012 6:21 PM upgraded to dpm 2012
    Thursday, May 17, 2012 6:44 PM

Answers

  • well since nobody posted an answer. I had to open a support call with Microsoft.

    It was found that on Win XP SP3 machines, the DCOM was 'restrictive'. I had to:

    1) Open DCOM properties via 'dcomcnfg' in command prompt.

    2) Goto Computers and then click on 'Properties' for the computer

    3) Under the 'COM Security' Tab, click Edit Limits for Activation Permission:

    Everyone, Anonymous Logon and SYSTEM user accounts must have Local and Remote Access permissions

    4) Similarly click Edit Limits for Launch and Activation Permissions:

    Everyone, Anonymous Logon and SYSTEM user accounts must have Local Launch, Remote Launch, Local Activation and Remote Activation all set to allow.

    This seemed to have resolved the issue. I was able to push agents onto these machines after a restart.

    • Marked as answer by Abdul Khans Saturday, May 26, 2012 3:51 PM
    Saturday, May 26, 2012 3:51 PM

All replies

  • well since nobody posted an answer. I had to open a support call with Microsoft.

    It was found that on Win XP SP3 machines, the DCOM was 'restrictive'. I had to:

    1) Open DCOM properties via 'dcomcnfg' in command prompt.

    2) Goto Computers and then click on 'Properties' for the computer

    3) Under the 'COM Security' Tab, click Edit Limits for Activation Permission:

    Everyone, Anonymous Logon and SYSTEM user accounts must have Local and Remote Access permissions

    4) Similarly click Edit Limits for Launch and Activation Permissions:

    Everyone, Anonymous Logon and SYSTEM user accounts must have Local Launch, Remote Launch, Local Activation and Remote Activation all set to allow.

    This seemed to have resolved the issue. I was able to push agents onto these machines after a restart.

    • Marked as answer by Abdul Khans Saturday, May 26, 2012 3:51 PM
    Saturday, May 26, 2012 3:51 PM
  • Thank you very much for sharing your experience!

    It's sad that I've found this thread only 3 years later :)

    Monday, September 14, 2015 6:52 AM