Product Connector subscription failed to update.
Hello I've faced this issue for the first time in our SCOM setup. The recent changes done on the setup are 1) Imported two custom management packs which contain unit monitors to monitor some services. These have registry based discovery probe configured and are targeting specific servers. 2) HP and IBM management packs - rules and monitors severity overrided to warning - Out of these on some rules and monitors the severity changed to critical. Other than the above two there aren't any changes to the infrastructure. The problem started when the RMS started showing greyed out and we cleared the RMS cache because just restarting the system center management service on it wasn't helping. Our setup contains seamless connectors installed to forward scom alerts to another application. We are also using the seamless heartbeat management pack which creates and event on SCOM MS's and those events are picked up and sent to the connector. A separate subscription is used to handle these heartbeat events. When the RMS was healthy again the alert flow was not resuming and we tried to update the connector subscription just to reapply the settings (Have seen before this step helping out). But this time we got the following error and the update failed with below error.. ****************************************************************************************************** Application: System Center Operations Manager 2007 R2 Application Version: 6.1.7221.81 Severity: Error Message: System.InvalidOperationException: The connector subscription could not be updated. See inner exception for details. ---> System.ArgumentException: The notification subscription was invalid for insert. See inner exception for details. ---> : Database error. [MPInfra_p_ManagementPackInstall] failed with exception: Database error. [MPInfra_p_ManagementPackInstall] failed with exception: ManagementPack cannot be updated because ProductConnectorSubscription51f64e76_1dd9_415d_8857_2f31dffdc2ef has been modified more recently. --- End of inner exception stack trace --- at Microsoft.EnterpriseManagement.ConnectorFramework.MonitoringConnector.UpsertConnectorSubscription(MonitoringConnectorSubscription connectorSubscription, ManagementGroup managementGroup, Boolean isUpdate) at Microsoft.EnterpriseManagement.ConnectorFramework.MonitoringConnectorSubscription.Update() --- End of inner exception stack trace --- at Microsoft.EnterpriseManagement.ConnectorFramework.MonitoringConnectorSubscription.Update() at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.Administration.ProductConnectors.SubscriptionProgress.<>c__DisplayClass4.<BackgroundWorkerDoWork>b__1(Object , ConsoleJobEventArgs ) at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(IComponent component, EventHandler`1 job, Object sender, ConsoleJobEventArgs args) System.ArgumentException: The notification subscription was invalid for insert. See inner exception for details. ---> : Database error. [MPInfra_p_ManagementPackInstall] failed with exception: Database error. [MPInfra_p_ManagementPackInstall] failed with exception: ManagementPack cannot be updated because ProductConnectorSubscription51f64e76_1dd9_415d_8857_2f31dffdc2ef has been modified more recently. --- End of inner exception stack trace --- at Microsoft.EnterpriseManagement.ConnectorFramework.MonitoringConnector.UpsertConnectorSubscription(MonitoringConnectorSubscription connectorSubscription, ManagementGroup managementGroup, Boolean isUpdate) at Microsoft.EnterpriseManagement.ConnectorFramework.MonitoringConnectorSubscription.Update() : Database error. [MPInfra_p_ManagementPackInstall] failed with exception: Database error. [MPInfra_p_ManagementPackInstall] failed with exception: ManagementPack cannot be updated because ProductConnectorSubscription51f64e76_1dd9_415d_8857_2f31dffdc2ef has been modified more recently. ****************************************************************************************************** Any ideas ? Adhokd
April 30th, 2012 1:41am

Hi, Firstly, please ensure the management server is not in maintenance mode. On the management server, please try restarting the following services and see how it works: System Center Management service System Center Management Configuration service System Center Data Access service If the issue persists, please check the Event Log on the management server and see if there are any other related errors; if so, please let us know the details. Hope this helps. Thanks. Nicholas Li TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
April 30th, 2012 11:46pm

Hi, Thanks for replying. The connector update was done after restarting the RMS services. I tried to check the events related but couldn't find any events which could specify any issue with the connector. Whichever events (warning or critical) I found after the incident were related to RMS performance (writing data to DW) etc. The connector is working fine. We only re-apply settings if the RMS fail and it comes back online after cache is cleared because we have seen earlier that after RMS recovers the automatic alert flow to the connector stops for longer period. When we run the connector subscription wizard again then the alert flow comes back to normal. I'm not 100% sure but this also seems to be related to performance of RMS as the number of agents in our management group is almost 5200. Are there any other things which I need to check related to connector. Are there any connector log files which we can check? Adhok
May 7th, 2012 7:50am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics