none
Assistance with MSDPM error 945

    Frage

  • Hello,

    Last week, we built a new bare-metal server, hosting DPM 1801, with only a handful of protection groups/members. Every night, at midnight, we receive the following error:

    Unable to connect to the DPM database because of a general database failure.  Make sure that SQL Server is running and that it is configured correctly.  
    Problem Details:<FatalServiceError>
    	<__System>
    		<ID>19</ID>
    		<Seq>8765</Seq>
    		<TimeCreated>6/4/2018 7:00:05 AM</TimeCreated>
    		<Source>DpmThreadPool.cs</Source>
    		<Line>163</Line>
    		<HasError>True</HasError>
    	</__System>
    	<ExceptionType>SqlException</ExceptionType>
    	<ExceptionMessage>Violation of PRIMARY KEY constraint 'PK_tbl_SM_Disk_Usage_Trend'. Cannot insert duplicate key in object 'dbo.tbl_SM_Disk_Usage_Trend'. The duplicate key value is (727b4c80-ee5e-41ed-bd18-5b98ad93123d, 6289e98c-8f05-4e2d-b308-073df8e90f65).The statement has been terminated.</ExceptionMessage>
    	<ExceptionDetails>System.Data.SqlClient.SqlException (0x80131904): Violation of PRIMARY KEY constraint 'PK_tbl_SM_Disk_Usage_Trend'. Cannot insert duplicate key in object 'dbo.tbl_SM_Disk_Usage_Trend'. The duplicate key value is (727b4c80-ee5e-41ed-bd18-5b98ad93123d, 6289e98c-8f05-4e2d-b308-073df8e90f65).The statement has been terminated.   at Microsoft.Internal.EnterpriseStorage.Dls.SummaryManager.SummaryManagerMachine.OnStart(ErrorInfo&amp; eInfo)   at Microsoft.Internal.EnterpriseStorage.Dls.TaskExecutor.SimpleStateMachine.Start(Message msg)   at Microsoft.Internal.EnterpriseStorage.Dls.TaskExecutor.Fsm.Transition.Execute(Message msg)   at Microsoft.Internal.EnterpriseStorage.Dls.TaskExecutor.Fsm.Engine.ChangeState(Message msg)   at Microsoft.Internal.EnterpriseStorage.Dls.TaskExecutor.TaskInstance.Process(Object dummy)   at Microsoft.Internal.EnterpriseStorage.Dls.TaskExecutor.FsmThreadFunction.Function(Object taskThreadContextObj)   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()   at System.Threading.ThreadPoolWorkQueue.Dispatch()ClientConnectionId:af7601e9-6435-4843-9648-866fb2ca51b8Error Number:2627,State:1,Class:14</ExceptionDetails>
    </FatalServiceError>

    This error causes the DPM service to terminate, which subsequently caused our midnight backups to fail. Any assistance on this issue would be greatly appreciated.

    Server information:

    • O/S: Windows Server 2016 Build 14393.2273
    • SQL version: SQL 2016 SP2
    • DPM version: DPM 1801

    Thank you,

    Mathew


    Montag, 4. Juni 2018 15:05

Alle Antworten

  • Hi!

    Is your DPM server joined in a domain?

    If yes, there might be some registry keys that are incorrectly formatted using UPN syntax.

    The registry keys are found in here:

    HKLM\software\microsoft\microsoft dpm\setup


    Make sure that the registry keys above have the values in the format of domain\username and not username@domain.com.


    Registry Keys:

    • SqlAgentAccoutName 
    • SchedulerJobOwnerName

    See example of how it should look like below:

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com  LinkedIn:   

    Montag, 4. Juni 2018 22:36
  • Thank you for your reply, Leon.

    Unfortunately, the two Registry Keys have the correct domain\username information.

    It should be noted that the back up jobs resume at their next run time (01:00), without issue. So, I'm guessing there is a kind of clean up occurring at midnight, which is failing - causing the error.

    There is some kind of referential integrity error when adding/removing entries in: 'dbo.tbl_SM_Disk_Usage_Trend'

    Error 1: Violation of PRIMARY KEY constraint 'PK_tbl_SM_Disk_Usage_Trend'. Cannot insert duplicate key in object 'dbo.tbl_SM_Disk_Usage_Trend'.

    I do not want to modify the SQL database manually, without guidance first. 

    Thank you,

    Mathew

    Montag, 4. Juni 2018 23:41
  • try moving your SQL server to it own box.  I was having similar issues and thats what the MS tech has me do, might work for you.  
    Montag, 18. Juni 2018 20:21
  • As mentioned above, you could give it a shot to backup your database and restore it on another server.

    The steps on how to do it can be found in the link below:

    https://docs.microsoft.com/en-us/system-center/dpm/upgrade-dpm?view=sc-dpm-1801


    Blog: https://thesystemcenterblog.com  LinkedIn:   

    Montag, 18. Juni 2018 23:12