Share via

System Center data protection manager 2022 after update Rollup 2 crashes ID917

Alex_Nick 81 Reputation points
2023-11-20T16:17:52.0566667+00:00

Hello everyone, I ran into such a problem, after the update Rollup 2 for Microsoft System Center data protection manager 2022 stopped working correctly, after a minute this error appears in the console and tasks are not executed

addition 1

As I noticed, if there are no active tasks, the crash does not occur

as soon as any job starts executing, this failure 917 occurs immediately

User's image

How can all this be fixed now?

User's image

User's image

Hi, please help me solve this problem, thank you

@Leon Laude

@Sujay Jagadish Desai

@Ingo Dettmar

@Jose E MB Vink

@XinGuo-MSFT

@Limitless Technology

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,754 questions
Azure Backup
Azure Backup
An Azure backup service that provides built-in management at scale.
1,264 questions
Microsoft System Center
Microsoft System Center
A suite of Microsoft systems management products that offer solutions for managing datacenter resources, private clouds, and client devices.
989 questions
Accepted answer
  1. Amardeep Saini 1,175 Reputation points Microsoft Employee
    2023-11-21T08:35:41.0233333+00:00

    @Alex_Nick - I have checked the logs which you have shared with us and here is the analyzes for it.

    2C8C 1198 11/20 22:31:38.527 23 EmIntegration.cs(1800000) NORMAL DpmTimer: Setting Interval to {0}

    2C8C 2BC8 11/20 22:31:38.590 07 NotificationManager.cs(47) NORMAL Sending Mail using AuthType = WindowsAuthType

    2C8C 2BC8 11/20 22:31:40.722 07 Mailer.cs(134) NORMAL About to send mail 2

    2C8C 2BC8 11/20 22:31:40.738 07 NotificationManager.cs(87) WARNING Exception : System.Security.SecurityException: Requested registry access is not allowed.

    2C8C 2BC8 11/20 22:31:40.738 07 NotificationManager.cs(87) WARNING at System.ThrowHelper.ThrowSecurityException(ExceptionResource resource)

    2C8C 2BC8 11/20 22:31:40.738 07 NotificationManager.cs(87) WARNING at Microsoft.Win32.RegistryKey.OpenSubKey(String name, Boolean writable)

    2C8C 2BC8 11/20 22:31:40.738 07 NotificationManager.cs(87) WARNING at Microsoft.Internal.EnterpriseStorage.Dls.NotificationManager.NotificationManager.GetSmtpAuthType()

    2C8C 2BC8 11/20 22:31:40.738 07 NotificationManager.cs(87) WARNING The Zone of the assembly that failed was:

    2C8C 2BC8 11/20 22:31:40.738 07 NotificationManager.cs(87) WARNING MyComputer

    2C8C 2BC8 11/20 22:31:40.753 68 DpmThreadPool.cs(122) WARNING Caught unhandled exception : System.Security.SecurityException: Requested registry access is not allowed.

    2C8C 2BC8 11/20 22:31:40.753 68 DpmThreadPool.cs(122) WARNING at Microsoft.Internal.EnterpriseStorage.Dls.NotificationManager.NotificationManager.GetSmtpAuthType()

    2C8C 2BC8 11/20 22:31:40.753 68 DpmThreadPool.cs(122) WARNING at Microsoft.Internal.EnterpriseStorage.Dls.NotificationManager.Mailer.Send(String to, String from, String subject, String body, String mailServerName, UInt16 port, String username, String password)

    2C8C 2BC8 11/20 22:31:40.753 68 DpmThreadPool.cs(122) WARNING at Microsoft.Internal.EnterpriseStorage.Dls.NotificationManager.Mailer.Send(String to, String subject, String body)

    2C8C 2BC8 11/20 22:31:40.753 68 DpmThreadPool.cs(122) WARNING at Microsoft.Internal.EnterpriseStorage.Dls.NotificationManager.NotificationSubscription.SendNotificationWorker(Object param)

    2C8C 2BC8 11/20 22:31:40.753 68 DpmThreadPool.cs(122) WARNING at Microsoft.Internal.EnterpriseStorage.Dls.EngineUICommon.DpmThreadPool.Function(Object state)

    2C8C 2BC8 11/20 22:31:40.753 68 DpmThreadPool.cs(122) WARNING at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

    2C8C 2BC8 11/20 22:31:40.753 68 DpmThreadPool.cs(122) WARNING at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

    2C8C 2BC8 11/20 22:31:40.753 68 DpmThreadPool.cs(122) WARNING at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()

    2C8C 2BC8 11/20 22:31:40.753 68 DpmThreadPool.cs(122) WARNING at System.Threading.ThreadPoolWorkQueue.Dispatch()

    2C8C 2BC8 11/20 22:31:40.753 68 DpmThreadPool.cs(122) WARNING The Zone of the assembly that failed was:

    So, seems it is the permission issue with the registry on DPM server. I would request you to please go to below mentioned registry path and check if you have the required permission on it or not.

    User's image

    This should resolve the issue for you. If the suggestions were helpful, click “Accept Answer” and Up-Vote. Feel free to reach out to us if you've additional questions in this regard.

    2 people found this answer helpful.
    0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. XinGuo-MSFT 18,081 Reputation points
    2023-11-21T01:59:18.72+00:00

    Hi,

    Since it was the MSDPM service that crashed, the next step is to take a look at the corresponding DPM error log. The default location for these DPM error logs is similar to C:\Program Files\Microsoft System Center 2012\DPM\DPM\Temp\.

    The crash event is recorded at the very end of the file and shows you more details.

    Here is a same problem for your reference.

    DPM Service not running/Event ID:999

  2. Soorya R 0 Reputation points Microsoft Employee
    2023-11-21T05:18:06.2433333+00:00

    Hi Alex,

    I am Soorya from the DPM product team. Do you have a support case open/can create a support case for this issue with Microsoft?

    If not, please reach out to me at sooryar [at] microsoft [dot] com for us to get more details and help debug this issue.

    Regards,
    Soorya

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.