Forum Discussion

Jeff_Jezek_4399's avatar
Jeff_Jezek_4399
Icon for Nimbostratus rankNimbostratus
Jan 25, 2011

Service not running after 2.1.5.440 upgrade

Hi,   This morning I upgraded our MP 2.1.3.217 to 2.1.5.440 and have run into a few issues. We have one RMS and one MS. Upgrade was run on both with same results.     1) At the end of th...
management
microsoft
scom
Julian_Balog_34's avatar
Julian_Balog_34
Historic F5 Account
Jan 25, 2011
Thanks for the quick feedback Jeff.

 

 

Now that you mentioned the override management pack depending on the F5 Management Pack, first thought that comes to my mind is the possibility of failed F5 MP workflows that could make the Health Service eventually discard the F5 data sources. The Operations Manager event log will possibly tell us more. Can you please zip it to managementpack(at)f5(dot)com? And while we're analyzing the log, could you also temporarily remove the override pack (and re-import later), if that's an option, to see if the problem persist?

 

 

On a side note, the post that you referred to as possibly pointing to a similar behavior ("F5 monitoring agent not stable after upgrading MP to 2.1.5.440 x64") had the SCOM Health Service crashing intermittently, with error event IDs 4000, preceded by event ID 33333 (data access error). The crash is apparently being induced by workflows run by other management packs. The F5 Management Pack workflows were exposing the problem more noticeably and within a shorter time span.

 

 

Send us please the Operations Manager event log and we'll take it from there.

 

 

Thank you!

 

Julian