Forum Discussion
Randy_18074
Nimbostratus
NimbostratusDevice Statistics Processing Failure
Hello,
We are running SCOM 2007 SP1, after I installed the F5 Mangement pack I keep getting this one error from the mangement pack! Anyone else see this error? We have 4 F5 Devices and all of them are reporting this error.
Date and Time: 5/11/2009 2:50:41 PM
Log Name: F5 Monitoring Log
Source: F5 Events
Event Number: 806
Level: 2
Logging Computer: SERVERSCOM99
User: N/A
Description:
Unable to process device [F5 Device [14.4.230.213]] statistics due to data failure: The PerformanceDataSourceConnector connection to Operations Manager Health Service host SERVERSCOM99 could not be established: Failed to connect to an IPC Port: The system cannot find the file specified. : SERVERSCOM99
Event Data:
- The error shows that for some reason the F5 Management Pack service could not [temporarily] communicate with the SCOM Health Service (OpsMgr Health Service). To be able to better diagnose the problem I would recommend restarting the OpsMgr Health Service, followed by re-starting the F5 Monitoring Service, and if the problem persist, please attach a copy of the "trace.log" file that is in your %Program Files%\F5 Networks\Management Pack\Logs directory. This will provide us with more information to help troubleshoot your situation.
Also, could you please specify more information about the environment you're testing with? If it's a distributed management server environment, we'd like to know the basic topology involved (RMS, MS, SQL-Server). On the management server host, where you discovered the devices (and running the F5 Monitoring Service) you can run a system information utility (Click here) that would provide us even more information for troubleshooting (please attach the output file to this post). 
Ben_Newport_102Had this exact error in setting this up on Win2k8 server running SCOM R2. The issue we had is that the Health Service was not able to start under the specified ID. Once that was corrected though we still couldn't start the F5 service. To correct that we ran a repair option on the F5 Management pack and then started and that seems to of fixed the issue.
