Failure installing MP 2.1.5.440-x64

From the logs we can see that the F5 Management Pack Data Source is crashing on startup, inside the SCOM Health Service / Monitoring Host. You would also probably see an error event ID 4000 in the Operations Manager event log as well, signaling this crash. As a result, the F5 Monitoring Service is stopping during startup, upon attempting to connect to the Data Source.

 

 

Now, the Data Source apparently is crashing because insufficient permissions while trying to open the F5 Monitoring Log. This operation involves reading the Event Log info from the local registry. While this attempt is being made, the security permissions are being audited (by the local system) and another failure happens while trying to open the Security log, to audit the security permission event. This operation is again compromised, apparently for the same security reasons (our logs shows that the 'Security' event log is missing). So clearly we have a permission issue here.

 

 

- What is the account running the SCOM Health Service (i.e. System Center Management)? Is it different from LocalSystem?

 

- Is it possible that you may have tracing enabled on your Data Source? This would be true, if you see a F5Networks.DataSource.dll.config file in your F5 Management Pack deployment folder. I hope it's not there, but if you have such a configuration file, I would recommend deleting it.

 

- Is your SCOM environment distributed, with one Root Management Server and one or more management servers? I assume (from the current setup.log that we have from you) that it's only one Root Management Server. Correct me if I'm wrong.

 

 

Let me know the answers to all these questions, and we'll further investigate.

 

 

Thank you.

 

Julian