My fear is that SCOM may miss a bunch of issues due to some internal failure ... any health check advice?
Nile From: [email protected] [mailto:[email protected]] On Behalf Of Gilmanov, Nile Sent: Friday, September 26, 2014 9:10 AM To: [email protected] Subject: [msmom] Dealing with Network Outages So I noticed that Operations Manager's ability to bounce back from network blips needs a little help. A couple of times now I noticed that I stop getting alerts because it looks like ExecuteScalar cannot bounce back from a network outage. Any advice on how to deal with that? Seems like one needs a monitoring solution for the monitoring solution. Thanks, Nile Alert: Alert subscription data source module encountered errors while running Source: All Management Servers Resource Pool Path: Not Present Last modified by: System Last modified time: 9/26/2014 8:58:40 AM Alert description: Alert subscription data source module encountered errors while running: Alert subscription data source module was unable to find alerts that match the subscription because of database errors. The following error(s) were encountered: Exception Message: ExecuteScalar requires an open and available Connection. The connection's current state is closed. One or more workflows were affected by this. Workflow name: Subscription936a7d4f_1ce4_4ce0_a786_52994858d052 Instance name: Alert Notification Subscription Server Instance ID: {E07E3FAB-53BC-BC14-1634-5A6E949F9230}
