Failed to save the Notification Subscribe: The operation for this recipient could not be completed.

Question

When configuring Notification Subscribe on SCOM 2019, I get Failed to save the Notification Subscribe: The operation for this recipient could not be completed.

Note: The following information was gathered when the operation was attempted. The information may appear cryptic but provides context for the error. The application will continue to run.

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 error. MPInfra_p_ManagementPackInstall failed with exception:
[SQL Error Code: -2146232060][MP ID: dcfdedc4-68bd-42b4-1e9a-ba94b1577732][MP Version: 10.19.10050.0][MP PKT: ] Procedure or function p_MPImportXML has too many arguments specified.
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 error. MPInfra_p_ManagementPackInstall failed with exception:
[SQL Error Code: -2146232060][MP ID: dcfdedc4-68bd-42b4-1e9a-ba94b1577732][MP Version: 10.19.10050.0][MP PKT: ] Procedure or function p_MPImportXML has too many arguments specified.

What could be the problem?

Answer 1

@Chicagotech.net , Research and find a similar issue. It mentioned that this can be caused by the following reasons:

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.

We can try the solutions in the following link to see if our issue can be fixed:
https://social.technet.microsoft.com/wiki/contents/articles/51244.scom-troubleshooting-notification-subscriber-addition-modification-error-the-operation-for-the-recipient-could-not-be-completed.aspx

However, if the issue still persists, we can consider rerunning the update-rollup_mom_db.sql in the OperationsManager Database. The SQL script will be located at C:\Program Files\Microsoft System Center\Operations Manager\Server\SQL Script for Update Rollups
Note: Please do database backup before we do any action.

Hope it can help.

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Thank you. Will post back

Answer 3

Hi Chrystal,

I can't follow this step: Restart the SCOM Services SDK, Config, Health service on all the Management servers and this should fix the issue. Where is these services located. I don't see them under Services.

Answer 4

OK, I find

OpsMgr – RTM/SP1 OpsMgr R2
OpsMgr SDK Service System Center Data Access
OpsMgr Health Service System Center Management
OpsMgr Config Service System Center Management Configuration

After restarting these services, I still have the same problem. The problem is I can't rename the Health Service State becasue it is in use even I have stopped those services.