Fix: The DPM console crashes and logs Event ID 945 when making any changes - The Official System Center Data Protection Manager Team Blog - Site Home - TechNet Blogs

Fix: The DPM console crashes and logs Event ID 945 when making any changes

Fix: The DPM console crashes and logs Event ID 945 when making any changes

  • Comments 10
  • Likes

imageHi everyone, Marc Reynolds here. I have seen some issues recently where the System Center Data Protection Manager Admin Console crashes and logs an Event ID 945 any time any changes were made.   The information below describes the issue, how to identify it and how you can easily resolve it.


The DPM console crashes when you try to make any change in DPM (e.g. adding a protection group, installing an agent, modifying disk allocation). MSDPM logs error 945 in the Application Event log showing the exception "Cannot insert the value NULL into column 'owner_sid', table 'msdb.dbo.sysjobs'; column does not allow nulls. INSERT fails."

Log Name: Application
Source: MSDPM
Date: 1/4/2012 1:21:11 AM
Event ID: 945
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: <dpm server name>

The description for Event ID 945 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:
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>7119</Seq><TimeCreated>1/4/2012 7:21:11 AM</TimeCreated><Source>DpmThreadPool.cs</Source><Line>163</Line><HasError>True</HasError></__System><ExceptionType>SqlException</ExceptionType><ExceptionMessage>Cannot insert the value NULL into column 'owner_sid', table 'msdb.dbo.sysjobs'; column does not allow nulls. INSERT fails.
The statement has been terminated.</ExceptionMessage><ExceptionDetails>System.Data.SqlClient.SqlException: Cannot insert the value NULL into column 'owner_sid', table 'msdb.dbo.sysjobs'; column does not allow nulls. INSERT fails.
The statement has been terminated.

at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.Internal.EnterpriseStorage.Dls.DB.SqlRetryCommand.ExecuteNonQuery()
at Microsoft.Internal.EnterpriseStorage.Dls.Scheduler.SqlAgentHelper.AddJob(String jobName, String jobOwner, String categoryName)
at Microsoft.Internal.EnterpriseStorage.Dls.Scheduler.SqlAgentHelper.RegisterSchedule(Schedule schedule)
at Microsoft.Internal.EnterpriseStorage.Dls.Scheduler.ConsistencyCheckHelper.PerformDBOperation()
at Microsoft.Internal.EnterpriseStorage.Dls.Scheduler.CommandHelper.Execute(SqlContext sqlContext)
at Microsoft.Internal.EnterpriseStorage.Dls.Scheduler.ConsistencyCheckHelper.Execute()
at Microsoft.Internal.EnterpriseStorage.Dls.Scheduler.SchedulerImpl.CheckDlsSchedules(Hashtable dlsSchedules, Hashtable sqlSchedules, ConsistencyCheckHelper consistencyCheckHelper)
at Microsoft.Internal.EnterpriseStorage.Dls.Scheduler.SchedulerImpl.ConsistencyCheck()
at Microsoft.Internal.EnterpriseStorage.Dls.Intent.IMCatalogDB.Rollback()
at Microsoft.Internal.EnterpriseStorage.Dls.Intent.IT.ProtectedGroupTranslator.TranslateGroup(IMCatalogType IMCatalogXmlPassed)
at Microsoft.Internal.EnterpriseStorage.Dls.Engine.CIntentServices.ConfigureProtectedGroup(UInt16* bstrIMCatalogXml)
at Microsoft.Internal.EnterpriseStorage.Dls.Engine.CCoreServices.ConfigureProtectedGroup(CCoreServices* , UInt16* bstrIMCatalogXml, tagSAFEARRAY** exceptionResult)</ExceptionDetails></FatalServiceError>


The registry keys for the SqlAgentAccoutName and SchedulerJobOwnerName are incorrectly formatted using UPN syntax.


Change the following registry values from the format to domain\username:

Path: HKLM\software\microsoft\microsoft dpm\setup

Keys: SchedulerJobOwnerName and SqlAgentAccountName

Marc Reynolds | Senior Support Escalation Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog:
AVIcode Team blog:
ConfigMgr Support Team blog:
DPM Team blog:
MED-V Team blog:
OOB Support Team blog:
Opalis Team blog:
Orchestrator Support Team blog:
OpsMgr Support Team blog:
SCMDM Support Team blog:
SCVMM Team blog:
Server App-V Team blog:
Service Manager Team blog:
System Center Essentials Team blog:
WSUS Support Team blog:

The Forefront Server Protection blog:
The Forefront Identity Manager blog :
The Forefront TMG blog:
The Forefront UAG blog:

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Hi Marc,

    Thanks for sharing this. I remember having this same issue a few months back and we dug and dug to trace the issue.  Was this issue becoming more common?

    Where is this upn format comin from?  Any ideas?

  • I just wanted to drop a note thanking you for this post. I had this problem and your post was the at the top of the list on Google.

    Thanks much!

  • See comments in this thread:

    This is not the fix you are looking for...

  • Just wanted to thanks you .... my 8 hours of troubleshooting session ends on this article. !

  • Thank you!!! It's December and we just ran into the same issue. How has Microsoft not resolved this?

  • One of the scenario could be this :

  • Thank you so much for this fix.

  • Dpm 2012 R2 fresh installation with update 4 and got the same error.
    Thank you so much!!

  • Excellent! fixed my issue with DPM 2012 R2 and SQL

  • Brilliant... thanks a lot