This troubleshooting information provides information about common issues that are encountered in IBM® Sterling Control Center Monitor and their solutions.
The following table provides solutions to common IBM Sterling Control Center Monitor system issues:
|Queued Activity Monitor does not show the current executing Process.
|Alerts for SLC events do not show in Alerts Monitor.
|Cannot log on using HTTPS.
|Verify that you are logging on with the host name used to set up the HTTPS connection.
|One ore more IBM Sterling Control Center Monitor functions are not visible.
|Your IBM Sterling Control Center Monitor role does not have permission to perform the functions in question. Your system administrator can change your role if necessary.
|IBM Sterling Control Center Monitor does not recognize daylight savings time change.
|IBM Sterling Control Center Monitor ignores certain Sterling Connect:Direct commands.
|Suspending a Process results in a blank screen followed by a CNCD017E Suspend process failed message.
|Window text is not clear in UNIX X Window System environment.
|This problem is related to how a UNIX X Window System environment handles font display. Refer to your UNIX documentation to resolve display problems.
|In monitoring FTP servers, the servers appear to go off and back online continuously.
|This situation occurs when multiple IBM Sterling Control Center Monitor engines monitor an FTP server through the same agent. If more than one engine is monitoring an FTP server, make sure that each engine uses its own FTP agent.
|IBM Sterling Control Center Monitor cannot connect to databases after a database is restarted.
|Restart your IBM Sterling Control Center Monitor engine. If you restart a database, a restart of your IBM Sterling Control Center Monitor engine is required.
|FASP statistics are not displayed when a Sterling Connect:Direct server that uses FASP is monitored.
|In server settings, ensure that the Do not collect process step statistics option is not checked.
|IBM Sterling Control Center Monitor cannot monitor file transfers from W3C FTP servers.
|In the IBM Sterling Control Center Monitor console, set the time zone for the monitored W3C FTP servers to the same as the time stamp in the W3C FTP server log through .
|IBM Sterling Control Center Monitor cannot connect to IBM Sterling Connect:Direct for Microsoft Windows Version 126.96.36.199 with the TLS or SSL connection type.
|Upgrade your IBM Sterling Connect:Direct for Microsoft Windows server to version 188.8.131.52_iFix020 or later.
|Information about certificate authentication to IBM Sterling Connect:Direct was not translated.
|Use the English version of the topic Authenticate IBM Control Center Monitor to IBM Sterling Connect:Direct with a certificate.
|Information about monitoring IBM Transformation Extender Advanced (ITXA) as a dynamically discovered server type was not translated.
|Use the English version of the topic What's new.
|The AIX 631 Installer installation encounters missing OS