Error message
Connection denied. Systemwalker Operation Manager server is not activated or port number is incorrect. |
Applicable versions and levels
Windows versions: V5.0L10 or later
Solaris versions: 5.0 or later
Linux versions: 5.2, V10.0L10 or later
Linux for Itanium versions: V12.0L10 or later
HP-UX versions: 5.1 or later
AIX versions: 5.1 or later
DS versions: V20L10
Action 1
Cause
The Jobscheduler service does not receive requests from the Systemwalker Operation Manager client until its startup is complete.
Possible causes of the Jobscheduler service startup to take a while are as follows:
There are many files in the Jobscheduler database directory (Jobscheduler checks the privileges when it starts)
There is an extremely large amount of schedule information (schedule processing takes a while)
Action method
Wait for a while, and then select Jobscheduler again in the Systemwalker Operation Manager client.
Description
Point
How to check that the Jobscheduler initialization processing is complete
Jobscheduler records the message shown below to the SYSLOG/event log at the point when the initialization processing for the server startup is complete. By checking the message that was recorded to the SYSLOG/event log, the completion of the initialization processing can be checked.
UNIX versions
MpJobsch: INFO: 0272: The jobscheduler daemon has been started.
Remarks. It is necessary to configure the settings so that user.info information is recorded in /etc/syslog.conf.
Windows versions
MpJobsch: INFO:1308: Systemwalker MpJobsch has started normally.
Action 2 [UNIX versions]
Points to check
Is the message queue depleted?
Refer to "Action 16" in "4.2.2 A Job Net or Job does not Start at the Intended Time" for information on the cause and action method.
Action 3
Points to check
Is the jobschprint command output stopped by the more command?
Refer to "Action 9" in "4.2.2 A Job Net or Job does not Start at the Intended Time" for information on the cause and action method.
Action 4
Points to check
Is the starting and closing of job nets or jobs concentrated within a short period of time?
Refer to "Action 4" in "4.2.18 Job Nets are Not Completed" for information on the cause and action method.
Action 5
Points to check
In the following version levels, was a policy distributed with a different continuous execution mode?
Windows versions: V5.0L10 to V5.0L30
Solaris versions: 5.0 to 5.2
HP-UX versions: 5.1
AIX versions: 5.1
Action method
Change the continuous execution mode of the policy extraction source, and then extract (extract the startup parameter)/distribute the policy again.
