|
SiteScope does not have the appropriate permissions to access the machine on which the Mercury Business Availability Center Admin Server is installed.
|
If this is the case, SiteScope shows error statuses for all monitors that are reporting on the operating system of the Mercury Business Availability Center machine. Check the user access permissions that have been granted to the SiteScope account on the remote server. SiteScope requires remote registry permissions to be able to monitor server statistics. Try connecting to the remote machine using Perfmon.
|
|
A Business Process Monitor is not sending data.
|
Check why the Business Process Monitor is not working. Possible causes: the Business Process Monitor machine is down or a process is stuck; there are network problems so the Business Process Monitor cannot connect to the Mercury Business Availability Center Core Server; the Mercury Business Availability Center loaders are failing to insert the data into the profile database; the Mercury Business Availability Center management database is down; the profile database is down.
|
|
The Last Reported Data Time monitor has an error among its components.
|
The Last Reported Data Time monitor is different from other monitors because it checks a complete, round-trip process, and not one specific component of a process. It may be that at some point in the round trip a problem was found: try and isolate the problem by looking at a Mercury Business Availability Center Core Server monitor.
|
|
The monitor name: File-Age <sample type> Buffers Read on $TOPAZ_HOST_NAME$ indicates an error. Note: <sample type> can be one of the following: Transaction, SiteScope, WebTrace, EMS, J2EE.
|
This problem may indicate that the Mercury Business Availability Center loaders are failing to insert the data collection samples into the profile database.
SiteScope checks the time that the Read directory in each loader was last modified, and uses predefined thresholds for this monitor:
If the time since the loader was last modified is more than 4 minutes, SiteScope issues a warning.
If the time since the loader was last modified is more than 8 minutes, SiteScope issues an error.
If you know that the interval at which the relevant data collectors report data to Mercury Business Availability Center is higher than these thresholds, you should change the threshold for warnings and errors in these monitors.
|