Share via

SCOM Troubleshooting: Notification subscriber addition / Modification Error - The operation for the recipient could not be completed.

  • Article

Issue:

When you save an email subscriber post editing an existing one or creating a new one in SCOM you may see the below error:

Message: The operation for the recipient could not be completed. See inner exception for details.

Date: 2/20/2018 4:05:00 PM

Application: Operations Manager

Application Version: 7.1.10226.1177

Severity: Error

Message: The operation for the recipient could not be completed. See inner exception for details.

System.ArgumentException: The operation for the recipient could not be completed. See inner exception for details. ---> Microsoft.EnterpriseManagement.Common.ManagementPackException: Database error. MPInfra_p_ManagementPackInstall failed with exception:

Database concurrency error. MPInfra_p_ManagementPackInstall failed due to a concurrency situation with exception:

ManagementPack cannot be updated because Microsoft.SystemCenter.Notification.Recipients has been modified more recently.

Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 1, current count = 0.

   at Microsoft.EnterpriseManagement.Common.Internal.ServiceProxy.HandleFault(String methodName, Message message)

   at Microsoft.EnterpriseManagement.Common.Internal.MonitoringNotificationServiceProxy.UpsertNotificationRecipient(Guid recipientId, String name, String schedulesAndDevicesXml, Boolean isUpdate)

   at Microsoft.EnterpriseManagement.MonitoringNotificationManagement.InsertNotificationRecipient(NotificationRecipient notificationRecipient)

   --- End of inner exception stack trace ---

   at Microsoft.EnterpriseManagement.MonitoringNotificationManagement.InsertNotificationRecipient(NotificationRecipient notificationRecipient)

   at Microsoft.EnterpriseManagement.Mom.Internal.UI.Notification.RecipientCompletionPage.CommitChanges(Object sender, DoWorkEventArgs e)

: Database error. MPInfra_p_ManagementPackInstall failed with exception:

Database concurrency error. MPInfra_p_ManagementPackInstall failed due to a concurrency situation with exception:

ManagementPack cannot be updated because Microsoft.SystemCenter.Notification.Recipients has been modified more recently.

Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 1, current count = 0.

Cause

There may be few reasons for this error:

  1.  SQL Server used by SCOM is overloaded.
  2.  SQL transactions stuck in the SQL end due to deadlock issues due to SQL performance.
  3. Management Servers having corrupt cache.

Solution

  1. Restart the SCOM Services SDK, Config, Health service on all the Management servers and this should fix the issue.

  2. If the issue still exists, stop the SDK, Config, Health service and then rename the "Health Service State" folder to "Health Service State.old" on all the management servers located by default in 

    C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server

    If you are not sure of the above location then use the below PowerShell command on the management server to find the SCOM installation location:

    (Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup").InstallDirectory

  3. If the above steps do not work, then after performing step 2, do not start the SCOM services. Just restart the SQL Services on the SQL Server. When the SQL Services are up and running then start the SCOM Services SDK, Config, Health services.