none
Microsoft Azure Recovery Services Management Agent service terminated unexpectedly

    Question

  • Using the Azure Recovery Services Management Agent to connect SCDPM to Azure Recovery Services Vault for replicating backup data, but the recovery services agent keeps crashing every 5 minutes. I"ve tried uninstalling/reinstalling, verified I have latest version of the agent downloaded from the Azure mgmt portal, not sure what the problem is, thoughts? It generates three error events in the windows log each time it crashes (details below).

    Log Name:      System
    Source:        Service Control Manager
    Date:          6/28/2018 9:33:08 AM
    Event ID:      7031
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:     
    Description:
    The Microsoft Azure Recovery Services Management Agent service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 300000 milliseconds: Restart the service.

    Log Name:      Application
    Source:        Application Error
    Date:          6/28/2018 9:33:08 AM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:     
    Description:
    Faulting application name: OBRecoveryServicesManagementAgent.exe, version: 2.0.9118.0, time stamp: 0x5ab8ef90
    Faulting module name: TraceProvider.dll, version: 2.0.9118.0, time stamp: 0x5ab8efd6
    Exception code: 0xc0000005
    Fault offset: 0x00000000000063a1
    Faulting process id: 0x16e4
    Faulting application start time: 0x01d40ee48ab9f210
    Faulting application path: C:\Program Files\Microsoft Azure Recovery Services Agent\bin\OBRecoveryServicesManagementAgent.exe
    Faulting module path: C:\Program Files\Microsoft Azure Recovery Services Agent\bin\TraceProvider.dll
    Report Id: cac8d9f4-7ad7-11e8-80c5-842b2b6def83
    Faulting package full name:
    Faulting package-relative application ID:

    Log Name:      Application
    Source:        .NET Runtime
    Date:          6/28/2018 9:33:08 AM
    Event ID:      1026
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:     
    Description:
    Application: OBRecoveryServicesManagementAgent.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.AccessViolationException
       at <Module>.CTraceProvider.TraceToErrorFile(CTraceProvider*, DLS_TRACE_EVENT*)
       at Microsoft.Internal.EnterpriseStorage.Dls.Trace.TraceProvider.Trace(Microsoft.Internal.EnterpriseStorage.Dls.Trace.TraceFlag, System.String, Int32, System.Guid*, Boolean, System.String, System.Object[])
       at Microsoft.Internal.EnterpriseStorage.Dls.Trace.TraceProvider._TraceMessage(Microsoft.Internal.EnterpriseStorage.Dls.Trace.TraceFlag, System.String, Int32, System.String, System.Object[])
       at Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.OMCommon.DpmServerFactory.GetServer(System.String, System.ComponentModel.AsyncOperation, Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.OMCommon.DpmServerScope)
       at Microsoft.Internal.EnterpriseStorage.Dls.UI.Cmdlet.Common.ConnectDpmServer.ProcessRecord()
       at System.Management.Automation.CommandProcessor.ProcessRecord()
       at System.Management.Automation.CommandProcessorBase.DoExecute()
       at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(System.Object, System.Collections.Hashtable, Boolean)
       at System.Management.Automation.PipelineOps.InvokePipeline(System.Object, Boolean, System.Management.Automation.CommandParameterInternal[][], System.Management.Automation.Language.CommandBaseAst[], System.Management.Automation.CommandRedirection[][], System.Management.Automation.Language.FunctionContext)
       at System.Management.Automation.Interpreter.ActionCallInstruction`6[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.Boolean, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Run(System.Management.Automation.Interpreter.InterpretedFrame)
       at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(System.Management.Automation.Interpreter.InterpretedFrame)
       at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(System.Management.Automation.Interpreter.InterpretedFrame)
       at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(System.Management.Automation.Interpreter.InterpretedFrame)
       at System.Management.Automation.Interpreter.Interpreter.Run(System.Management.Automation.Interpreter.InterpretedFrame)
       at System.Management.Automation.Interpreter.LightLambda.RunVoid1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.__Canon)
       at System.Management.Automation.DlrScriptCommandProcessor.RunClause(System.Action`1<System.Management.Automation.Language.FunctionContext>, System.Object, System.Object)
       at System.Management.Automation.DlrScriptCommandProcessor.Complete()
       at System.Management.Automation.CommandProcessorBase.DoComplete()
       at System.Management.Automation.Internal.PipelineProcessor.DoCompleteCore(System.Management.Automation.CommandProcessorBase)
       at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(System.Object, System.Collections.Hashtable, Boolean)
       at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
       at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()
       at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
       at System.Threading.ThreadHelper.ThreadStart()


    Shaun

    Thursday, June 28, 2018 2:20 PM

All replies

  • I have the same issue as you do.  Heard anything, or figured it out?

    Tuesday, July 3, 2018 6:17 PM
  • Hi

    I'm also getting this issue, do you manage to find a resolution to the issue.

    I have found if you stop the Microsoft Azure Recovery Service Agent and then start the Microsoft Azure Recovery Service Management Agent, then restart the Microsoft Azure Recovery Service Agent, the Microsoft Azure Recovery Service Management Agent will stay running.

    It does not fix my issue for long and i am still having issues getting my recovery points to sync to Azure, as I get an warning message in the CBEngineCurr.Errlog.

    WARNING    cbpVersion 2.0.9118.0 , latestVersion 2.0.9109.0

    Thanks

    

    Tuesday, July 24, 2018 6:56 AM
  • Same problem here.

    3 x Errors every 5 minutes

    1. Application error
    Faulting application name: OBRecoveryServicesManagementAgent.exe, version: 2.0.9127.0, time stamp: 0x5b6221b9
    Faulting module name: TraceProvider.dll, version: 2.0.9127.0, time stamp: 0x5b6221eb
    Exception code: 0xc0000005
    Fault offset: 0x00000000000063a1
    Faulting process id: 0x17d8

    2. .NET Runtime error

    Application: OBRecoveryServicesManagementAgent.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.AccessViolationException

    3. Service Control Manager

    The Microsoft Azure Recovery Services Management Agent service terminated unexpectedly. 

    Any updates? Any Ideas?
    Thanks in advance.

    Monday, August 13, 2018 9:09 AM
  • Hi,

    I confirm that this sequence does make a difference. I managed to go 10 minutes so far and it did not crash.

    Clearly it's not a solution (and it will break at the first restart), but it is a marked improvement!

    thanks

    Thursday, September 6, 2018 3:46 PM