Forum Discussion

Zimpaya_101559's avatar
Zimpaya_101559
Icon for Nimbostratus rankNimbostratus
May 16, 2012

F5 Management Pack version 3.1 fails with the Datasource and Condition Detection....

Hello,

 

 

the F5 Management Pack version 3.1 fails on SCOM 2007 R2 CU5 with following error message:

 

 

 

<05-16-2012 10:58:49> FatalError: The DataSource and ConditionDetection modules required for the F5 Monitoring Service to run could not be loaded by Operations Manager monitoring host. Check the Operations Manager Event Log for errors and manually start the F5 Monitoring Service once any issues have been resolved.

 

 

this is my error messsage

 

 

In event viewer, F5 Monitoring Service service can not start and fails with error:

 

 

"The F5 Monitoring Service service terminated with the following error:

 

There are no more files."

 

 

I installed it on the Root MS. The service account is Domain Admin, DB owner and SQL admin.

 

 

Thanks,

 

 

Nicolas

 

 

  • The errrors in the logs point to the following error (Failed to connect to an IPC Port: The system cannot find the file specified. )

     

     

    Global Error: 0 : [5/16/2012 1:03:55 PM]Unhandled global exception: F5Networks.F5Exception: Unable to connect to data source: The PerformanceDataSourceConnector connection to Operations Manager Health Service host HealthService could not be established: Failed to connect to an IPC Port: The system cannot find the file specified. : HealthService ---> F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionFailedException: The PerformanceDataSourceConnector connection to Operations Manager Health Service host HealthService could not be established: Failed to connect to an IPC Port: The system cannot find the file specified. : HealthService ---> System.Runtime.Remoting.RemotingException: Failed to connect to an IPC Port: The system cannot find the file specified.

     

     

    Which file is he looking at?

     

     

    any clues?

     

     

    Thanks
  • We are seeing the exact same error with the same versions of software. Did you get anywhere with this? We saw the same error a long time ago with a different version of the management pack, but that was due to Service Broker not being enabled on the OperationsManager DB. We double-checked that, and it is enabled, but we are still seeing this error. Our service account is similar to yours, plenty of permissions, but no joy.

     

     

    This seems like it could be a bug in the Management Pack, since none the usual fixes seem to help. Anyone have any ideas?
  • Soooo, "Repair" doesn't fix the issue, clearing out the OpsMgr cache and re-starting everything doesn't help, and I can't Uninstall the management pack due to a 1608 msi error.
  • It certainly appears to be a permissions/access issue. I installed with a low privileged account and another low one for the service account and got the same error. I reinstalled using Repair option as an elevated (not quite Domain Admin) account with the low privileged account and everything is running with no errors.