User troubleshooting

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:

Issue Solution
Queued Activity Monitor does not show the current executing Process.
  • If you are running processes with numerous copy steps, IBM Sterling Control Center Monitor may not show the current status. This situation occurs due to the large number of statistics records generated. You can disable collecting Sterling Connect:Direct® step statistics.
  • Fast-running processes can complete before they are shown in the Queued Activity Monitor.
  • Sterling Connect:Enterprise® and FTP processes are never shown in the Queued Activity Monitor because information about those Processes is not known until the Process completes.
  • Set a lower Monitor Rest Time setting in the Server Properties page.
Alerts for SLC events do not show in Alerts Monitor.
  • Verify that a rule is configured properly to generate an alert from an event.
  • Verify that the rule and SLC are enabled and correct.
  • Workflow SLC alerts can be seen only in an alerts monitor opened on IBM Sterling Control Center Monitor not on an individually managed server.
  • Verify that alert is not restricted to a data visibility group for which the user has no authority.
  • Verify that rule is not restricted to a data visibility group that does not have visibility of the events.
  • SLCs with wildcard server expressions can generate alerts for events that did not occur. As a result, you can see these types of alerts only in an alerts monitor opened on IBM Sterling Control Center Monitor. You cannot see these alerts on an individually managed server.
  • Verify the Severity Level of the Alert being generated. Level 0 Alerts do not appear in the Active Alerts Monitor, but are automatically moved to the Handled Alerts Monitor by the Rule Service. You can change the Alert level for an event by editing the Rule.
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.
  • Verify that the time zone supports daylight savings time in the server definition or in the time preferences.
  • If you use UTC time for IBM Sterling Control Center Monitor time displays, you must manually adjust the UTC time to daylight savings time. UTC time never changes for daylight savings time.
IBM Sterling Control Center Monitor ignores certain Sterling Connect:Direct commands.
  • Verify that IBM Sterling Control Center Monitor is logging the appropriate statistics records.
  • Use the Server Properties window to verify that the user ID that accesses the Sterling Connect:Direct server has the authorization required to issue the commands.
Suspending a Process results in a blank screen followed by a CNCD017E Suspend process failed message.
  • The Process completed.
  • Fast-running Processes can complete and others can begin to run before the Completed Activity Monitor is updated.
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 Server Properties > Settings.
IBM Sterling Control Center Monitor cannot connect to IBM Sterling Connect:Direct for Microsoft Windows Version 4.7.0.0 with the TLS or SSL connection type. Upgrade your IBM Sterling Connect:Direct for Microsoft Windows server to version 4.7.0.3_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 libraries

Error detail: </tmp/install.dir.17563914/AIX/resource/jre/lib/default/libjvm.so> - reason: < 0509-022 Cannot load module /tmp/install.dir.17563914/AIX/resource/jre/lib/default/libjvm.so. 0509-150 Dependent module libc+.a(shr_64.o) could not be loaded. 0509-022 Cannot load module libc+.a(shr_64.o). 0509-026 System error: A file or directory in the path name does not exist.
  • Install the required compatible packages libc++.rte