FUJITSU
Contents
Expand/Collapse this branch (Collapse Contents)
Title Page
Preface
Chapter 1  Troubleshooting Flow
Expand/Collapse contents list Chapter 2  Common Troubleshooting
Expand/Collapse contents list 2.1  Problems with Installation
2.1.1  Silent Installation Fails [UNIX Versions]
2.1.2  Message "The InstallShield engine (iKernel.exe) could not be launched. Access is denied." is Output during Startup of the Installer and Installation Ends Abnormally
2.1.3  Systemwalker Operation Manager Error Messages are Displayed in an Environment in Which Networker, etc., Coexist
2.1.4  Authentication of the Startup Account Fails When Installing the Software in an Environment Configured as a Backup Domain Controller of Active Directory
2.1.5  The Service or Daemon Fails to Stop and Installation Fails
2.1.6  Message "00872:Failed in installation process. " is Displayed When Installation is 99% Complete
2.1.7  The Warning Message "The Web Link function will be installed. However, Setup will not be performed because IIS is not installed. " is Displayed during Installation [Windows Versions]
2.1.8  The System is Installed in English (ASCII) even though the System Encoding is Japanese [UNIX Versions]
2.1.9  00103 Error Message is Output and Installation Cannot be Completed
2.1.10  The Message "Web server setup failed." is Displayed
Expand/Collapse contents list 2.2  Problems with Processes
2.2.1  A Process Error is Displayed
2.2.2  A Process Error is Displayed during Check of the Process Running Status
2.2.3  Message "failed to obtain the monitored processes" is Displayed
2.2.4  Message "skipped monitoring, because of resource lack." Is Displayed
2.2.5  A KERNEL32.DLL Initialization Error Occurs, Preventing the Systemwalker Operation Manager Process From Starting Up [Windows Versions]
2.2.6  Unable to Collect IPC Resources [UNIX Versions]
2.2.7  Message "Connection Failed or Server Process is Down" is Output in an Environment in Which Systemwalker Operation Manager Coexists With the Operation Management Server of Systemwalker Centric Manager
2.2.8  Standard Output or Standard Error Cannot be Used Inside the Shell (mppmonsnd.sh) of the User Customization of Process Monitoring Function [UNIX Versions]
2.2.9  CPU Usage is High for the f3crheeg and f3crhesv Processes [Windows Versions]
2.2.10  Message "AP:F3CVSERV:Warning:3001:The time-out interval elapsed.(detail)" Is Displayed
2.2.11  A java.exe Process Error is Displayed during Check of the Process Running Status [Windows Versions]
Expand/Collapse contents list 2.3  Problems with Starting or Stopping
2.3.1  Unable to Start Systemwalker Operation Manager Services [Windows Versions]
2.3.2  The F3CVSERV Service is Set to be Started Manually but is not Started during the Product Startup [Windows Versions]
2.3.3  Cluster Failover Takes Time or a Process Accessing Files Under /var/spool/mjes is Detected during Cluster Failover [UNIX Versions]
2.3.4  "MpAuditLogO: ERROR: 1: The audit log was not able to be initialized. The log is not output to the operation after this." is Output to the Event Log during a System Reboot or Shutdown [Windows Versions]
2.3.5  If the Systemwalker Operation Manager Start Command (soperationmgr) is Executed via cron, Subsequent Start Commands Fail [UNIX Versions]
Expand/Collapse contents list 2.4  Problems with Systemwalker Operation Manager Infrastructure
2.4.1  Error Messages Output By Systemwalker Operation Manager Infrastructure
2.4.2  The Message " Failed to send the start parameters. Code=0xXXXXXXXX" (XXXXXXXX Represents a Code) is Displayed on the Environment Setup Client [UNIX Versions]
2.4.3  Unable to Log In to the Server From a Systemwalker Operation Manager Client or Environment Setup Client [UNIX Versions]
2.4.4  A jmnetsv Daemon Error Occurs, Preventing Systemwalker Operation Manager From Starting Up [UNIX Versions]
2.4.5  The mpjmsrv Process Crashes After Login From Systemwalker Operation Manager Client [UNIX Versions]
2.4.6  The Error Message "MpJmSrv: ERROR: 0028: socket() Address family not supported by protocol" is Output by the Systemwalker Operation Manager Infrastructure [UNIX Versions]
Expand/Collapse contents list 2.5  Problems with Access Rights
2.5.1  If Connecting as a User Other than Superuser, the Project is not Displayed Even if the Access Rights have been Set [UNIX Versions]
2.5.2  If Connecting as a Domain Account, the Project is not Displayed When Jobscheduler is Selected in the Job Selection Window Even if the Access Rights have been Set [Windows Versions]
2.5.3  Message "Incorrect user name or password. " is Displayed, Projects cannot be Created or Deleted, and the Owner Cannot be Changed
2.5.4  Message "Could not get user definition information. " Is Displayed When Trying to Set the Project Access Rights in the Cluster System
2.5.5  Message "Could not get domain name list.(0:0) " Is Displayed When the Project Access Rights are Set [Windows Versions]
2.5.6  If Connecting as a General User, the Project is not Displayed Even if the Access Rights have been Set [Windows Versions]
2.5.7  Projects With Access Rights are not Displayed on the Client [UNIX Versions]
2.5.8  "Could not get domain name list.(0:0) (For Window) "
2.5.9  If Failover is Performed in the Cluster System, the Information of Operation Manager Users That Should have been Registered is Restored [UNIX Versions]
Expand/Collapse contents list 2.6  Problems with Policy
2.6.1  Policy Distribution is not Implemented Correctly [UNIX Versions]
2.6.2  The Message "Policy distribution is not allowed because destination server policy information is not applied. " is Output and Policies Cannot be Distributed
2.6.3  Failover Occurs When Policies are Distributed in the Cluster Environment [UNIX Versions]
2.6.4  The Message "Policy distribution is not allowed because destination server type is different." is Output and Policies Cannot be Distributed
Expand/Collapse contents list 2.7  Problems with Utility Commands
2.7.1  An Abnormal Completion Message is Output With the Completion Code 7 Even When a Service is Started Normally Using the Service Start Command (f3crhsst.exe) [Windows Versions]
Expand/Collapse contents list 2.8  Problems with Backup, Restore or Migration
2.8.1  Backup or Restore Commands do not Run Normally if Executed by a Shell Script [UNIX Versions]
2.8.2  Backup in Silent Mode Fails
2.8.3  Message "MpJobsch: ERROR: 7300 func=JOBSCH_dbfile_open:CreateFile()" Is Displayed [Windows Versions]
2.8.4  The jobschmsgevent Command Does not Run Normally when the Schedule Server is Migrated [Solaris Versions]
Expand/Collapse contents list 2.9  Problems with the Maintenance Information Collection Tool
2.9.1  An Application Error Occurs for MsInfo32 if the Maintenance Information Collection Tool is Started From Jobscheduler [Windows Versions]
Expand/Collapse contents list 2.10  Problems with Other Products
2.10.1  Systemwalker Operation Manager Provisioning Fails When Using ServerView Resource Coordinator (*1) Provisioning
2.10.2  After the Password Change Command (pwchangeo.exe) is Executed, Error Message "Failed to change the password." Is Displayed and the Systemwalker Centric Manager Service Fails to Start Up [Windows Versions]
Expand/Collapse contents list 2.11  Problems with the Client
2.11.1  The Message "Failure in writing audit log." is Displayed
2.11.2  The Message "Run-time error '429': ActiveX component can't create object." is Displayed [Windows Versions]
Expand/Collapse contents list 2.12  Problems with the Web Console
2.12.1  Information is not Displayed during Operation of the Web Console
2.12.2  When Login window will be displayed, Web site: "Internet Explorer cannot display the webpage" is viewed.
2.12.3  The pop-up message is displayed during Operation of the Web Console
2.12.4  "INVALIDSESSION:" appears immediately after logging in to the web console
Expand/Collapse contents list Chapter 3  Troubleshooting Calendar/Power Control
Expand/Collapse contents list 3.1  Power off is Not Operating Correctly
3.1.1  PowerChutePLUS (APC product) Connects but only Shutdown is Performed, with no Power off [Windows Version]
3.1.2  The Power Goes off at the Day Change Time
3.1.3  The Power Control Schedule has been Set, however, a Power off and Reboot are Not Performed [Windows Version]
3.1.4  A System Reboot or Shutdown Occurs at an Unexpected Time
Expand/Collapse contents list 3.2  Power Control does Not Operate Normally
3.2.1  Shutdown is Performed before Completion of Commands Executed at the Completion of Operation during Shutdown Monitoring
3.2.2  When Trying to Restart Multiple Servers using Batch Power Control, One or More Servers do Not Restart
3.2.3  Cannot Power on
Expand/Collapse contents list 3.3  Automatic Reflection Function for Calendar Information does Not Work during Cluster Operation
3.3.1  The Calendar Automatic Reflection Setup was Completed but the Calendar Information is not Reflected Automatically
Expand/Collapse contents list Chapter 4  Troubleshooting Jobscheduler
Expand/Collapse contents list 4.1  Groups are Not Operating as Expected
4.1.1  A Job Net Starts even though the Preceding Job Net has not Been Executed
4.1.2  Immediately after Completion of a Group, the Same Group is Continuously Started
4.1.3  Job Nets Cannot be Added to a Group
4.1.4  The Scheduled Startup Day of a Group Awaiting Execution becomes the Next Scheduled Startup Day when the Server is Restarted
4.1.5  The Scheduled Start Time is not Displayed for Groups and Job Nets in a Group
4.1.6  Job Nets in a Group Start up even if the Execution Conditions are not Met
4.1.7  Even though the Preceding Job Net of the Job Nets in the Group Ended Normally, the Succeeding Job Net does not Start Instantly
4.1.8  One of the Job Nets in the Group was not Started on the Current Day, or a Job Net not Scheduled to be Started was Started
4.1.9  When the Job Net was Disabled, the Succeeding Job Net Started even though a Message Event was not Generated
4.1.10  The Group Ends Abnormally with Code 239
4.1.11  The Group does not Start
4.1.12  Startup Days of Job Nets in the Group were Changed, however the Change was not Reflected in the Scheduled Start Time
4.1.13  The Group Started after the Confirm Operation
4.1.14  Even though the Day Change Time is Reached, the Group does not Change to the "Waiting" Status
4.1.15  A Job Net in the Group Started on an Unscheduled Day
4.1.16  A Job Net in the Group did not Start on Startup Days
4.1.17  Even though the Preceding Job Net of the Job Nets in the Group was Disabled, the Succeeding Job Net does not Start
Expand/Collapse contents list 4.2  The Job Net Behavior is Abnormal
4.2.1  A Job Net Started at an Unexpected Time
4.2.2  A Job Net or Job does not Start at the Intended Time
4.2.3  A Job Net that Waits for a Message Event and a Startup Time is Started at an Unintended Time
4.2.4  A Job Net that Waits for Message Events and the Execution Time is not Started, even if a Message Event was Generated and the Execution Time was Exceeded
4.2.5  Job Nets that should Start when Multiple Message Events are Generated Started, even though Not All Multiple Message Events were Generated
4.2.6  A Job Net that should have Started Starts Again
4.2.7  Even though the Job Net should not Start on the Current Day because of the Invalid period setting on the Startup days tab (V13.4.0 or later) or Operation period tab (V13.3.1 or earlier) in the Job Net Properties window, it does Start
4.2.8  Even though a Holiday was set in the Calendar, the Job Net is Started when a Message is Generated
4.2.9  Even though a Message Event was Generated, the Job Net does not Start
4.2.10  Even though a Message Event was not Generated, the Job Net Starts
4.2.11  There is no Job Net Schedule, so the Job Net is not Started
4.2.12  The Job Net is Refused, and does not Start
4.2.13  The Job Net Starts at a Time that is not in Sync with the Registered Scheduled Start Time
4.2.14  The Job Net Starts One Day Later than the Registered Startup Day
4.2.15  A Job Net for which it was not the Startup Day was Scheduled, or Started
4.2.16  If a Failover has occurred on a Cluster Operation Server, an Unintended Job Net is Started
4.2.17  The Job Net that Ended Abnormally Yesterday still has the "Abended" Status Today
4.2.18  Job Nets are Not Completed
4.2.19  After the Day Change Time, a Job Net not Scheduled to Start Today Changed Status to the "Waiting" Status
4.2.20  The Startup Delay Exit Started at an Unintended Time
4.2.21  The Job Execution Control Attribute/Interstage Attribute Job are Running, but the Job Net Ends Abnormally
4.2.22  The Execution Result is not Displayed on the Previous log tab in the Monitor - Job window, or in the Job Output Info window
4.2.23  The Startup Day Information set in the Startup Days window or the Application Plan window is not Reflected
4.2.24  Even though a Specific Day is Set as an Unscheduled Day in the Schedule Pattern, it is still a Startup Day
4.2.25  Cannot Copy the Job Net
4.2.26  In a Cluster Operation, even though the Holiday Calendar was Changed, the Change is not Reflected in the Startup Day
Expand/Collapse contents list 4.3  The Job Behavior is Abnormal
4.3.1  I do not Understand the Meaning of the Job Completion Code
4.3.2  Although the Job Flow Execution Proceeds in the Monitor Job Net window, when the Job Execution Result is Checked, it seems that the Job has not been Started
4.3.3  The Job Net is Executing, but the Job in the Job Net is not Executed
4.3.4  If the Restart Operation is Performed for a Job Net that Ended Abnormally, the Top Job will be Executed
4.3.5  The Job Execution History "skipped" is Displayed in the Job Execution History
4.3.6  All Jobs in the Job Net have the "Waiting" Status
4.3.7  The Job Net has a Job that Changed from "Disabled" or "Paused" to the "Waiting" Status
4.3.8  Even though File Transfer is not Complete, chkfile.exe, chkfile.sh, or jobschchkfile Ends
4.3.9  The Job does not Start. Alternatively, even though the Job has actually Ended, it does not change to the "Ended" Status for Some Time
4.3.10  Even though the Job Net or Group has the "Waiting" Status, the Job has the "Ended" Status
4.3.11  The Job does not End [UNIX Versions]
4.3.12  The Job does not Operate Normally [UNIX Versions]
4.3.13  Even though the Parameters field was specified in the Add/Change - Job window, not all Parameters are Passed to the Command
Expand/Collapse contents list 4.4  The Group/Job Net/Job Behavior is Abnormal
4.4.1  A Paused Group/Job Net/Job Was Started after having changed to the "Continue" Status
4.4.2  When Jobscheduler Starts, the Group/Job Net/Job Ends Abnormally with Completion Code 239
4.4.3  The Group/Job Net does not Start after the Year Changes
Expand/Collapse contents list 4.5  The Gantt Chart Display is Abnormal
4.5.1  "Disabled" is Displayed in the Gantt Chart for a Job Net for which the Disable Operation has not been Performed
4.5.2  The Job Net Execution History is not Displayed in the Gantt Chart
4.5.3  After the Waiting Job Net, a Short Band that Indicates Completed (or Abended, Canceled, or Pseudo-normal Completed) is Displayed
Expand/Collapse contents list 4.6  The Multi-server Monitoring window Display is Abnormal
4.6.1  The Multi-server Monitoring window Cannot be Displayed
4.6.2  When the Host is Selected, "Connection not possible" is Displayed and Monitoring is Not Possible
4.6.3  When the Host is Selected, "Access denied" is Displayed and Monitoring is Not Possible
Expand/Collapse contents list 4.7  The Sample Source Behavior is Abnormal
4.7.1  The Sample Source abendrerun.c was Used in a Cluster System, but there are Job Nets that Cannot Restart
Expand/Collapse contents list 4.8  The Termination Processing Job Net Behavior is Abnormal [Windows Versions]
4.8.1  When the Termination Processing Job Net is Started, it does not Start even when the Next Execution Time Arrives
4.8.2  Job Net End Processing is not possible using the End Processing Exit
4.8.3  Even if the Termination Processing Job Net is Completed, the Server does not Reboot/Shut Down
Expand/Collapse contents list 4.9  The Jobscheduler Command or API Behavior is Abnormal
4.9.1  The Error Message "Systemwalker MpJobsch is being started" [Windows Versions]/"The daemon is being started" [UNIX Versions] is Output, and the Command cannot be Executed
4.9.2  The Error Message "Systemwalker MpJobsch is not started" [Windows Versions]/" The daemon was not started." [UNIX Versions] is Output, and the Command cannot be Executed
4.9.3  The Error Message "The LANG value is different" is Output [UNIX Versions]
4.9.4  An Error Message is Output, and the Command cannot be Executed [Windows Versions]
4.9.5  The Jobscheduler Command/API Called from the User Application does not Work Normally
4.9.6  When you try to Obtain the Schedule Content using the jobschprint Command, an Error Message is Output
4.9.7  The Calendar was Changed using the jobschsethol Command, but All Holidays outside the Part that was Changed Disappear
4.9.8  The Jobscheduler API Returns with Return Code 4
4.9.9  The Error Message "The job net is being saved or controlled" is Displayed
4.9.10  It takes a while to Execute the Jobscheduler Command, API or Web API
4.9.11  A Message Event that was already Registered cannot be Deleted using the jobschsetnet -nche Command
4.9.12  The Characters in the Job Status Field are Garbled using the jobschprint -p Command
4.9.13  A New Job Net cannot be Created/an Existing Job Net cannot be Changed using the jobschsetnet Command if there is no Execution Condition
4.9.14  When the Job Net/Group is Registered using the jobschsetnet/jobschsetgrp Command Based on the Information that was Extracted using the jobschprint Command, Position Information about the Job is not Inherited
Expand/Collapse contents list 4.10  A Message Event is not Generated by the jobschmsgevent Command
4.10.1  A Message Event is not Generated
4.10.2  The Error Message "RegisterEventSource() 5: Access denied" is Output [Windows Versions]
4.10.3  The Error Message "RegisterEventSource() 1722:RPC server is not available" is Output [Windows Versions]
4.10.4  The Error Message "ReportEvent() 997:Redundant I/O process" is Output [Windows Versions]
4.10.5  The Message "MpJobsch: ERROR: 0309: Usage: jobschmsgevent event_name[:project_name[/job_net_name] [message_text]] [-h host_name] [-t:INFO | -t:WARN | -t:ERROR]" is Output when the jobschmsgevent Command is Executed from a Schedule Job [UNIX Versions]
Expand/Collapse contents list 4.11  The Message Event is not Recognized by the Job Net
4.11.1  Message Events Generated for Job Nets using the jobschmsgevent command are not Recognized
Expand/Collapse contents list 4.12  Cannot Reference the Job Properties
4.12.1  When the Job Properties are Referenced in the Monitor Job Net window, "system error" is Displayed [UNIX Versions]
4.12.2  The Message "Failure in allocating information storage area." is Output
4.12.3  About One Minute is Required to Display the Properties of the Jobs in the Job Net
4.12.4  The Message "Resource with identifier '0' not found 0" is Output
4.12.5  The Message "Disconnected because an invalid socket ID was specified." is Output
Expand/Collapse contents list 4.13  The Jobscheduler Behavior is Abnormal
4.13.1  After the System Time is Changed, the Job Net Does not Start on Schedule
4.13.2  After the System Time is Changed, the History Information cannot be Displayed Correctly
4.13.3  Many file name job name.oxxxx, job name.exxxx (xxxx is the job number) are Generated in the Home Directory [UNIX Versions]
4.13.4  The Jobscheduler Server Processing Hangs up [UNIX Versions]
4.13.5  No Response when OK is Selected in the Host connection specification Dialog Box
4.13.6  A Failover Occurs while the Cluster System is Running, and the Message "Specified host not found." is Displayed
4.13.7  Many Jobs that Wait for File have been Registered, so the CPU Load is High [UNIX Versions]
4.13.8  The xxxxxxxx.exe application could not be initialized correctly. (xxxxxxxx is one of tskgrsrv, tskelsrv, tskwnsrv, tskbasrv, tskussrv, or tskevsrv) [Windows Versions]
4.13.9  It takes a While until Jobscheduler Starts
4.13.10  The Job Net Operation Takes a While
4.13.11  The CPU Usage of the Process "tskussrv"/"tskgrsrv" is High [UNIX Versions]
4.13.12  When SHUTDOWN.EXE is Executed, the Job Net Completion Code is 239 [Windows Versions]
4.13.13  Cannot Perform the Operation for the Job Net that Corresponds to the Completed exit or Abended exit
4.13.14  Cannot Start the Jobscheduler Service [Windows Versions]
4.13.15  Cannot Start the Jobscheduler Daemon [UNIX Versions]
4.13.16  "MpJobsch: ERROR: 0063: the daemon already started" is Output, and the Jobscheduler Daemon cannot Start [UNIX Versions]
4.13.17  Illegal Information is Displayed in the Job Execution History (Output Information) [UNIX Versions]
4.13.18  Even though Abended (*1) is selected on the Event output tab in the Define Jobscheduler Startup Parameters window, this is not Output to the Event Log/SYSLOG when the Job Status has the "Closed" status (Completion Code: 239)
4.13.19  After the Restore, when Jobscheduler is Started the Group/Job Net/Job Ends Abnormally with Completion Code 239
4.13.20  The Jobscheduler Service does not Start [Windows Versions]
4.13.21  There is a Large Number of Files in /var/tmp [UNIX Versions]
4.13.22  The Startup Delay Exit is Started at the Scheduled Start Time of a Disabled Job Net
4.13.23  The Jobscheduler Daemon/Service is not Running
4.13.24  Even though the job net Started, Completed, or Ended Pseudo-normally, these Messages are not Output to the Event Log/SYSLOG
4.13.25  Controlling the desired status (Watching delay of job / job net) Function is not Working as Expected
4.13.26  Even though the Events Set in the Message table Were Generated, the Job Net does not Start [Windows Versions]
Expand/Collapse contents list 4.14  Error Message Notifications are Received from Jobscheduler
4.14.1  The Warning Error Message "The size of log information has exceeded the maximum value" is Output
4.14.2  A Jobscheduler Error Message is Displayed in the Event Log [Windows Versions]/SYSLOG [UNIX Versions]
4.14.3  The Error Message "iconv() ..." is Displayed, as in "iconv() Illegal byte sequence", and "iconv() Invalid Argument" [UNIX Versions]
4.14.4  The Error Message "Process cannot access the file" is Output [Windows Versions]
4.14.5  The Error Message "Failure in accessing project DB" is Output
4.14.6  The Error Message "Failure in accessing project DB." is Output [Windows Versions]
4.14.7  The Error Message "jobsch: ERROR: read() Connection timed out" or "Socket function error occurred" is Output
4.14.8  When Jobscheduler is Selected from the Systemwalker Operation Manager Client, an Error Message is Output to the Event Log [Windows Versions]
4.14.9  The Message "Failure in opening DB." is Output
4.14.10  An Error Message is Displayed immediately after Day Change Time
4.14.11  The Message "MpJobsch: Error :6052: Invalid format" is Output when Using the jobschprint Command to Obtain Job Schedule Information
4.14.12  The Message "MpJobsch: ERROR: msgrcv() Invalid argument" or "MpJobsch: ERROR: msgrcv() Identifier removed" is Output [UNIX Versions]
4.14.13  The Message "0330:The job net has abnormal ended.CODE=XXX", or "330 The job net has ended abnormally. Job net comment=XXXX Job net name=YYYY Code=CCCC Project name=ZZZZ" is Output
4.14.14  The Message "ERROR: 1000002: Check if the Systemwalker Operation Manager process (tskmnsrv) is running properly." is Output [UNIX Versions]
4.14.15  The Message "Failure in host information acquisition in the monitor authorization host file." is Displayed
4.14.16  The Error Messages "write() File too large" and "The daemon failed to write job net output information" are Displayed [UNIX Versions]
4.14.17  Even though the Jobscheduler Daemon has Stopped, the Error Message "Jobscheduler daemon is started. The jobschconvert command cannot be used" is Displayed [UNIX Versions]
4.14.18  The Error Message "MpJobsch: ERROR: read() Bad file number" is Displayed [UNIX Versions]
4.14.19  The Message "AP:MpJobsch: ERROR: 6305: Service: Write message failed at client (message queue)" is Displayed during Service Stop Processing [Windows Versions]
4.14.20  The Message "MpJobsch: ERROR: msgget() No space left on device" is Output to SYSLOG during Startup of Jobscheduler [UNIX Versions]
4.14.21  The Message "Error /opt/FJSVJOBSC/etc/rc3.d/start_jobs daemon did not started..." is Output and Jobscheduler is Unable to Start [UNIX Versions]
4.14.22  The Error Message "Calendar information not found" is Displayed
4.14.23  A Jobscheduler Error Message is Displayed during Startup of the Cluster System [UNIX Versions]
4.14.24  The Error Message "ReadFile() 6: Invalid handle" is Output [Windows Versions]
4.14.25  The Message "MpJobsch: ERROR: 0189: XXXXX YYYYYY Failure in job net generation" is Output to SYSLOG [UNIX Versions]
4.14.26  The Error Message "The requested operation cannot be performed on a file with a user-mapped section open" is Output [Windows Versions]
4.14.27  The Message "MpJobsch: ERROR: 0412: bind() Address already in use" is Output to SYSLOG [UNIX Versions]
4.14.28  The Error Messages "7022:Erroneous record exists in job net information of XXXX" and "7300:func=JOBSCH_dbfile_read:ReadFile() 170: The requested resource is in use" are Displayed [Windows Versions]
4.14.29  The Error Messages "7000:func=jobschsetnet:ftruncate() No error" and "6007: Systemwalker MpJobsch failed to write job net information" are Displayed [Windows Versions]
4.14.30  The Warning Message "Systemwalker MpJobsch failed to set policy information" is Output
4.14.31  The Error Message "7300: Service :func=GetEventLog:ReadEventLog() 1500: The event log file is corrupt" is Output [Windows Versions]
4.14.32  The Error Message "getpwnam() No such file or directory" is Output [UNIX Versions]
4.14.33  The Message "MpJobsch Event ID: 7012 Detail:Past EventLog record is trapped" is Output to the Event Log [Windows Versions]
4.14.34  The Message "0017: The jobscheduler failed to attach shared memory" is Displayed after Executing a Jobscheduler Command [UNIX Versions]
4.14.35  The Message "MpJobsch: ERROR: 0412: shmget() No space left on device" is Output to SYSLOG [UNIX Versions]
4.14.36  The Error Message "The requested resource is in use" is Output [Windows Versions]
4.14.37  The Error Message "shmget() Invalid argument", "shmget() No space left on device" or "0009: The jobscheduler failed to create shared memory" is Output [UNIX Versions]
4.14.38  The Start Delayed Message is Displayed at the Scheduled Start Time of a Disabled Job Net
4.14.39  If the jobschmsgevent Command is Executed in the Subsystem Environment, "The daemon was not started" is Output [UNIX Versions]
4.14.40  "func=JOBSCH_dbfile_open:CreateFile() 32: Process cannot access the file. "MpJobsch: ERROR: 7300 func=JOBSCH_dbfile_open:CreateFile() 32" is Output to the Event Log during Execution of Job Nets and Jobs [Windows Versions]
4.14.41  The Message "MpJobsch: ERROR: open() too many open files" is Output to SYSLOG [UNIX Versions]
4.14.42  The Message "MpJobsch: ERROR: 0422: Failed to convert the standard output or the standard error code for the job. The job result file contains illegal characters" is Output [UNIX Versions]
4.14.43  The Error Messages "write() No space left on device" and "The daemon failed to write job net output information" are Output [UNIX Versions]
4.14.44  The Error Message "MpJobsch: ERROR: 0412: socket() Address family not supported by protocol" is Output [UNIX Versions]
4.14.45  The Error Messages "5: Access denied." and "MpJobsch: ERROR: 6208: Systemwalker MpJobsch failed to read log information." are Output to the Event Log by Jobscheduler [Windows Versions]
Expand/Collapse contents list 4.15  The Job Outputs a Code and Ends Abnormally
4.15.1  The Job Outputs a Code and Ends Abnormally. Alternatively, the Job Outputs a Message and Ends Abnormally
Expand/Collapse contents list 4.16  The Systemwalker Operation Manager Client Behavior is Abnormal
4.16.1  After a Job such As Calendar or Jobscheduler is Selected, or the Connection Destination Host is Selected, in the Job Selection window, the Pop-up "A connection timeout occurred." is Displayed
4.16.2  When Jobscheduler is Selected in the Client, some of the Server Information is not Displayed
4.16.3  The Client Response is Slow/Does not Return
4.16.4  "Run-time error '6': Overflow" is Displayed
4.16.5  The Systemwalker Operation Manager Client Function Displays the Pop-up "Run-time error", and may End Abnormally (Error Code Undefined)
4.16.6  The Message " Run-time error '339':Component 'comct232.ocx' or one of its dependencies not correctly registered: a file is missing or invalid" is Displayed
4.16.7  If Jobscheduler is Selected in the Systemwalker Operation Manager Client Immediately after the Jobscheduler Service is Started, " Connection denied. Systemwalker Operation Manager server is not activated or port number is incorrect." is Output
4.16.8  The Gantt chart Switches at a Different Time to the Day Change Time
4.16.9  "Systemwalker Operation Manager" Remains Displayed in the Main Window
4.16.10  Even though this is a Subsystem Operation, the Subsystem is not Displayed in the Systemwalker Operation Manager Client Job Tree
4.16.11  The Message " Run-time error '35602':key not unique in collection." is Displayed when Jobscheduler is Opened
4.16.12  The Message "Protocol data cannot be received. " is Displayed on the Client
4.16.13  "Monitoring server is down due to an internal error. The client will exit." is Displayed in the Multi-server Monitoring Client
4.16.14  "No buffer area. (1113)" is Displayed
4.16.15  The Job Output Info (Previous log of the job) is not Displayed [UNIX Versions]
4.16.16  An Error Occurs when the Operation Manager Client Starts, and the User Name and Password are Specified to Connect [Windows Versions]
4.16.17  It takes a while to display the Job History window
4.16.18  The Pop-up Message "A connection timeout occurred." is Displayed
4.16.19  The Pop-up Message " Job Output Info can not be displayed because it failed in the character-code conversion." is Displayed
4.16.20  "Connecting with Jobscheduler ..." Remains Displayed
4.16.21  The Message " Connection denied. Systemwalker Operation Manager server is not activated or port number is incorrect." is Displayed when the Systemwalker Operation Manager Client is Started up
4.16.22  "Could not get user name list." or "Could not get group name list." is Displayed on the Set Permissions window
Expand/Collapse contents list 4.17  "Link to Systemwalker Centric Manager" is Abnormal
4.17.1  The "Link to Systemwalker Centric Manager" function does not Work
4.17.2  A Message is Notified to Systemwalker Centric Manager in Duplicate
4.17.3  A Message is not Notified to Systemwalker Centric Manager [UNIX Versions]
Expand/Collapse contents list 4.18  Import/Export of Job Net Definitions is Operating Abnormally
4.18.1  Importing is not Possible if a Parent Job Net is Specified for Another base job net in the Child Job Net Startup Days Settings
Expand/Collapse contents list Chapter 5  Troubleshooting Job Execution Control
Expand/Collapse contents list 5.1  The Job Execution Result is Abnormal
5.1.1  I do not Understand the Meaning of the Job Completion Code
5.1.2  Even if the Job Completion Code is 256 or more, "255" is Displayed as the Code in the Previous log tab of the Monitor - Job window
5.1.3  The Job Completion Code is Always 0 [Windows versions]
5.1.4  The Job Completion Code is Always 0 [UNIX versions]
5.1.5  The COBOL Application Completion Code is Abnormal
5.1.6  The stty or eucset Error is Output to the Output Result [UNIX versions]
5.1.7  The Rights are Insufficient, so the Job Does Not Operate Normally [Windows versions]
5.1.8  The Environment Variables are Insufficient, so the Job Does Not Operate Normally [Windows versions]
5.1.9  After Systemwalker Operation Manager is Restarted, the Job Behavior Changes [UNIX versions]
5.1.10  Job behavior differs from previous
Expand/Collapse contents list 5.2  The Job Ends Abnormally
5.2.1  The Job Outputs a Code and Ends Abnormally. Alternatively, the Job Outputs an Error Message and Ends Abnormally
5.2.2  When Antivirus Software is used, the Job Ends Abnormally [Windows versions]
5.2.3  The Job Ends Abnormally with Code 1 [UNIX versions]
5.2.4  The Job Ends Abnormally with Code 137, 138, or 139 [UNIX versions]
5.2.5  The Job Ends Abnormally with Code 239
5.2.6  The Job Ends Abnormally with Code 243
5.2.7  The Job Ends Abnormally with Code 250 (1)
5.2.8  The Job Ends Abnormally with Code 250 (2)
5.2.9  The Job Ends Abnormally with Code 253
5.2.10  The Job Ends Abnormally with Code 201 - 256
5.2.11  The Job Ends Abnormally with Code 0x40000913 [Windows versions]
5.2.12  The Job Ends Abnormally with Code 0x40000913 [UNIX versions]
5.2.13  The Job Ends Abnormally with Code 0x40000999, or if 'Job' or 'Queue' is Selected in the Job Selection window, Error Message:MJS819E is Output
5.2.14  The Job Ends Abnormally with Exception Code 0xC0000005, 0xe06d7363 [Windows versions]
5.2.15  The Job Ends Abnormally with Exception Code 0xC0000135 [Windows versions]
5.2.16  The Job Ends Abnormally with Exception Code 0xC0000142 [Windows versions]
5.2.17  The Job Ends Abnormally with Exception Code 0x40000999 [Windows versions]
5.2.18  The Job Ends Abnormally (with Other Code)
5.2.19  The Jobs Outputs an Error Message and Ends Abnormally [UNIX versions]
5.2.20  The Network Job that Shuts Down or Reboots Another Server Ends Abnormally
5.2.21  Even if the Continuous Execution Mode is Enabled, if the Execution Server has Shut Down (Failover), the Network Job that is being Executed Ends Abnormally
5.2.22  The Job that Uses Shared Memory Ends Abnormally [UNIX versions]
5.2.23  64-bit/32-bit Application Jobs End Abnormally when they are Executed [Windows Versions]
Expand/Collapse contents list 5.3  The Job is not Executed
5.3.1  The Job is not Executed [UNIX versions]
5.3.2  Failed to Execute the Network Job (Error Message:MJS881S is Output)
5.3.3  Failed to Execute the Network Job (Error Message:MJS844E is Output)
5.3.4  Failed to Execute the Network Job (Error Message:MJS819E is Output)
5.3.5  Failed to Execute the Network Job (Error Message:MJS830E is Output)
5.3.6  Failed to Execute the Network Job (Error Message:MJS876E is Output)
5.3.7  The Job is not Executed, and a Delay Occurs
5.3.8  After JCL is Executed, the "Insufficient space for file name.line=nnn. job not queued." Error Message is Output, and the JCL Does Not Start
5.3.9  The Network Job that was Running Does Not Run After the Version Upgrade
5.3.10  An Error Occurs when the Policy Distribution Job is Executed
Expand/Collapse contents list 5.4  The Job Does Not Operate Normally
5.4.1  The Job Does Not Operate Normally [Windows versions]
5.4.2  The Job Does Not Operate Normally [UNIX versions]
5.4.3  The Job (Arcserve, COBOL, PowerSORT, SymfoWARE, and Others) Does Not Operate Normally [Windows versions]
5.4.4  The Job was not Executed in the Directory Specified in Directory in the Standard information Tab of the Add/Change - Job Window
5.4.5  The Job Does Not End (1)
5.4.6  The Job Does Not End (2) [Windows versions]
5.4.7  The Job Does Not End (3) [Windows versions]
5.4.8  The Job Does Not End (4) [UNIX versions]
5.4.9  The Network Job Takes a While to End
5.4.10  A Job that was being Executed before the System Failure Waits to be Executed, but is not Executed even if the System is Restarted
5.4.11  The Application cannot Reference the Network Drive [Windows versions]
5.4.12  The Job That Accesses RDBMS via ODBC Does Not Operate Normally [Windows versions]
5.4.13  The Network Job Starts in Duplicate, and Seems to be Executing Even Though the Job has Actually Ended, or Outputs Error Message: MJS881S and then Ends Abnormally
5.4.14  The Command Name cannot be Referenced from the Script File [UNIX versions]
5.4.15  The Network Job Ends Before the Estimated End Time
5.4.16  The Job is Delayed and not Started, or the Start is Delayed
5.4.17  A Network Job from a Windows Server to a UNIX Server is Executed with Administrator Rights by a General User who is the Owner
5.4.18  Unintended Permissions were Set for the File or Directory Created in the Job [UNIX versions]
5.4.19  If the Schedule Server is in a Cluster Configuration, the Network Job Ends Before the Estimated End Time
5.4.20  If the Schedule Server is in a Cluster Configuration, it Takes a While until the Network Job Ends
5.4.21  The Job That Handles Microsoft Office Products (such as Excel or Access) Does Not Operate Normally [Windows versions]
Expand/Collapse contents list 5.5  The Job Execution Control Behavior is Abnormal
5.5.1  The Content Defined in Define Operating Information is not Reflected
5.5.2  The CPU Usage Time of mjsini.exe Increases [Windows versions]
5.5.3  The "/etc/security/limits.conf" Value is not Reflected in the Systemwalker Operation Manager Job [UNIX versions]
5.5.4  A Job List File (job name.|job number) is Created Unwillingly
5.5.5  The Job Cannot be Canceled
5.5.6  Nothing is Displayed in the View Queue Status/Operate Window if Queue is Selected in the Job Selection Window [UNIX versions]
Expand/Collapse contents list 5.6  An Error Message is Notified from Job Execution Control
5.6.1  Error Message "MpMjes: WARNING: 10113: mjsnetsv : TCP port number does not exist." is Output [UNIX versions]
5.6.2  "MpMjes: ERROR: 10091 [UNIX versions] or 1011 [Windows versions]: The continuous execution modes of each server are not unified." is Output
5.6.3  When Job or Queue was Selected in the Job Selection Window, or, the qstat Command is Executed, "Unable to get queue information." is Output [Windows versions]
5.6.4  When Job or Queue was Selected in the Job Selection Window, Error Message:MJS876E is Output [UNIX versions]
5.6.5  When the qjstat Command is Executed, "System error occurred. function: FindFirstFile() code: -1" is Output, or, when the qstat Command is Executed, "Unable to get system information." is Output [UNIX versions]
5.6.6  When the qjstat Command is Executed, "System error occurred. function: readjobinfo()" is Output, or, when the qstat Command is Executed, "Unable to get queue information." or "Unable to get job information." is Output [UNIX versions]
5.6.7  "Failure in receiving parameter information file. " is Displayed in the Client
5.6.8  When the Job Execution Control Daemon Starts, the Error Message "MpMjes: ERROR: 10063: mjsdaemon : The environment of the sub-system number does not exist." is Output [UNIX versions]
5.6.9  "MpMjes: mjsrjob : job information file read error." is Output [UNIX versions]
5.6.10  Error Message "MpMjes: F3CUB_LOG_PIPE write system error occurred." is Output [UNIX versions]
5.6.11  If Job is Selected in the Job Selection Window, a Message is Output and Information in the View Job Status/Operate Window Cannot be Referenced [UNIX versions]
Expand/Collapse contents list Chapter 6  Troubleshooting Services/Applications
Expand/Collapse contents list 6.1  Problems during Service/Application Execution
6.1.1  An Error Message is Displayed even though the Service/Application Starts Normally [Windows Versions]
Expand/Collapse contents list Chapter 7  Troubleshooting Event Monitoring and Action Control [Windows Versions]
Expand/Collapse contents list 7.1  The Action Execution is Abnormal
7.1.1  The Action is not Executed (General)
7.1.2  The Action is not Executed (Application Execution)
7.1.3  The Action is not Executed (Pager Notification/Short Mail)
7.1.4  The Action is not Executed (Pop-up)
7.1.5  The Action is not Executed (Mail)
7.1.6  The Action is not Executed (Audio Notification)
7.1.7  An Unintended Action is Executed
7.1.8  A Large Number of Actions is Executed
7.1.9  The Audio Notification Action Does not Stop
7.1.10  The Pop-up Message is Delayed
7.1.11  It Takes a While to Execute the Action after the Event has Occurred
7.1.12  Strings, such as %HOST, are not Substituted
7.1.13  Japanese Characters in the Email Sender Field are Garbled
Expand/Collapse contents list 7.2  The Behavior of the Action Control Window is Abnormal
7.2.1  Cannot Start the Action Control Window
7.2.2  Cannot Delete the Email Action that is Executing
Expand/Collapse contents list 7.3  The Event Monitoring Behavior is Abnormal
7.3.1  "Past event has been retrieved." is Output Frequently
Expand/Collapse contents list 7.4  The Behavior of the Monitored Event Table Window is Abnormal
7.4.1  Cannot Start the Monitored Event Table Window
Expand/Collapse contents list 7.5  The Behavior of the Monitored Log File Setup Window is Abnormal
7.5.1  Cannot Start the Monitored Log File Setup Window
Expand/Collapse contents list 7.6  An Error Message is Notified from Event Monitoring
7.6.1  "MpAosfB: ERROR: 1052: Failed to write to the event log location file." or "MpAosfB: ERROR: 7011: Error occurred in system function. Calling source: f3crheeg System function name: CopyFile() Reason: xxxx" is Output to the Event Log
Expand/Collapse contents list Chapter 8  Troubleshooting Task Link
Expand/Collapse contents list 8.1  The File Control Behavior is Abnormal
8.1.1  Compression Using the File Compression/Expansion Commands (fprssvr/fprscli) Fails
8.1.2  Connection to the Shared Directory from the File Transfer Command (FCOPYSVR.EXE)/File Operation Command (FCTRLSVR.EXE) Fails [Windows Versions]
Expand/Collapse contents list 8.2  The Application Startup Behavior is Abnormal
8.2.1  When the Client Application Startup is Executed by the execacli Command, "0x13A" is Returned
8.2.2  The Application Cannot be Started Using the execacli Application Startup Command
Expand/Collapse contents list 8.3  The Client Power Control Behavior is Abnormal
8.3.1  Remotely Powering On the Client Using the poncli Command Fails
8.3.2  Remotely Powering Down the Client Using the poffcli Command Fails
8.3.3  After Remotely Powering Down the Client, "Active Desktop Repair" Starts when the Client Starts
8.3.4  The poffcli Command Ends Normally, but the Client Machine does not Shut Down
Expand/Collapse contents list 8.4  The Client Task Link Engine Behavior is Abnormal
8.4.1  An Error Occurs when the Client Task Link Engine is Started
Expand/Collapse contents list 8.5  The Task Link Command Behavior is Abnormal
8.5.1  The Client Task Link Command Registered in the Job Net keeps Running
8.5.2  "0xb007(0x410e): The Task Link Engine process startup request was not accepted." is Displayed
Expand/Collapse contents list 8.6  The Task Link Service (Systemwalker MpNjsosv) Behavior is Abnormal
8.6.1  10307:Failed to receive the request of server search in the thread of server search. is Displayed [Windows Versions]
Expand/Collapse contents list Chapter 9  Troubleshooting Schedule Distribution/Master Schedule Management Functions
9.1  Creation of Schedule Information Fails
9.2  A Schedule by Dates Project that has Exceeded the Number of Stored Generations of Schedule Information is Not Deleted
9.3  Because of Manual Startup, the Job Net that should have Completed is Scheduled and then Restarted
Expand/Collapse contents list 9.4  A Message Event is Not Generated by the jobschmsgeventex Command
9.4.1  A Message Event is Not Generated
Expand/Collapse contents list Appendix A  Maintenance Information Collection Tool
Expand/Collapse contents list A.1  Usage Method
A.1.1  Windows Versions
A.1.2  UNIX Versions
Expand/Collapse contents list A.2  If the Maintenance Information Could not be Collected
A.2.1  Windows Versions
A.2.2  UNIX Versions
Expand/Collapse contents list Appendix B  How to Check the Process Running Status
B.1  Checking the Process Running Status
Expand/Collapse contents list B.2  Process Names
B.2.1  Process Names [Windows Versions]
B.2.2  Process Names [UNIX Versions]
Expand/Collapse contents list Appendix C  Conventions Used in This Document and Trademarks
C.1  Abbreviations and Generic Terms Used
C.2  Trademarks

Top