Upload
others
View
0
Download
0
Embed Size (px)
Citation preview
B1X1-0118-05ENZ0(00)April 2014
Windows/Linux
Systemwalker Runbook Automation
Message Guide
Preface
Purpose of This Document
This document describes the messages of Systemwalker Runbook Automation V15.1.3.
Intended Readers
This document is intended for people who operate and manage systems using Systemwalker Runbook Automation.
This document assumes that readers already have a general understanding of basic operating system and GUI operations as well as basicknowledge of ITIL (R).
Abbreviations and Generic Terms Used
- The term "Windows(R) 8.1" refers to the following products:
- Windows(R) 8.1 Pro(x86)
- Windows(R) 8.1 Enterprise(x86)
- Windows(R) 8.1 Pro(x64)
- Windows(R) 8.1 Enterprise(x64)
- The term "Windows(R) 8" refers to the following products:
- Windows(R) 8 Pro(x86)
- Windows(R) 8 Enterprise(x86)
- Windows(R) 8 Pro(x64)
- Windows(R) 8 Enterprise(x64)
- The term "Windows(R) 7" refers to the following products:
- Windows(R) 7 Home Premium(x86)
- Windows(R) 7 Professional(x86)
- Windows(R) 7 Ultimate(x86)
- Windows(R) 7 Enterprise(x86)
- Windows(R) 7 Home Premium(x64)
- Windows(R) 7 Professional(x64)
- Windows(R) 7 Ultimate(x64)
- Windows(R) 7 Enterprise(x64)
- The term "Windows Vista (R)" refers to the following products:
- Windows Vista(R) Home Basic(x86)
- Windows Vista(R) Home Premium(x86)
- Windows Vista(R) Business(x86)
- Windows Vista(R) Ultimate(x86)
- Windows Vista(R) Enterprise(x86)
- Windows Vista(R) Business(x64)
- Windows Vista(R) Ultimate(x64)
- i -
- The term "Windows(R) XP" refers to the following products:
- Microsoft(R) Windows(R) XP Professional x64 Edition
- Microsoft(R) Windows(R) XP Professional
- Microsoft(R) Windows(R) XP Home Edition
- The term "Windows Server 2012" refers to the following products:
- Microsoft(R) Windows Server(R) 2012 R2 Standard(x64)
- Microsoft(R) Windows Server(R) 2012 R2 Datacenter(x64)
- Microsoft(R) Windows Server(R) 2012 Standard(x64)
- Microsoft(R) Windows Server(R) 2012 Datacenter(x64)
- The term "Windows Server 2008" refers to the following products:
- Microsoft(R) Windows Server(R) 2008 R2 Standard(x64)
- Microsoft(R) Windows Server(R) 2008 R2 Enterprise(x64)
- Microsoft(R) Windows Server(R) 2008 R2 Datacenter(x64)
- Microsoft(R) Windows Server(R) 2008 Standard(x86)
- Microsoft(R) Windows Server(R) 2008 Enterprise(x86)
- Microsoft(R) Windows Server(R) 2008 Standard(x64)
- Microsoft(R) Windows Server(R) 2008 Enterprise(x64)
- Microsoft(R) Windows Server(R) 2008 Datacenter(x64)
- Microsoft(R) Windows Server(R) 2008 Standard without Hyper-V(x86)
- Microsoft(R) Windows Server(R) 2008 Enterprise without Hyper-V(x86)
- Microsoft(R) Windows Server(R) 2008 Datacenter without Hyper-V(x64)
- The term "Windows Server 2003" refers to the following products:
- Microsoft(R) Windows Server(R) 2003, Standard Edition
- Microsoft(R) Windows Server(R) 2003, Enterprise Edition
- Microsoft(R) Windows Server(R) 2003, Standard x64 Edition
- Microsoft(R) Windows Server(R) 2003, Enterprise x64 Edition
- Microsoft(R) Windows Server(R) 2003 R2, Standard Edition
- Microsoft(R) Windows Server(R) 2003 R2, Enterprise Edition
- Microsoft(R) Windows Server(R) 2003 R2, Standard x64 Edition
- Microsoft(R) Windows Server(R) 2003 R2, Enterprise x64 Edition
- Windows Internet Explorer (R) is referred to as Internet Explorer.
- The Oracle Solaris Operating System may be referred to as Solaris, Solaris Operating System or Solaris OS.
- Microsoft (R) Cluster Server and Microsoft (R) Cluster Service are referred to as MSCS.
- The versions of Systemwalker Runbook Automation that run on Windows systems are referred to as the Windows version.
- The versions of Systemwalker Runbook Automation that run on Linux systems are referred to as the Linux version.
- ii -
Export Restriction
If this document is to be exported or provided overseas, it is necessary to check Foreign Exchange and Foreign Trade Law, and take thenecessary procedure according to these laws.
Trademarks
ITIL(R) is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in theUS Patent and Trademark Office.
Linux is a registered trademark of Linus Torvalds.
Microsoft, Windows, Windows Server, and Microsoft Cluster Service are either registered trademarks or trademarks of MicrosoftCorporation in the United States and/or other countries.
Netscape, Netscape Navigator, Netscape Communicator, "N" logo, and the steering wheel logo are registered trademarks of NetscapeCommunications Corporation in the United States and other countries.
Red Hat and all Red Hat-based trademarks and logos are trademarks or registered trademarks of Red Hat, Inc. in the United States andother countries.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
UNIX is a registered trademark of The Open Group in the United States and other countries.
VMware, the VMware "boxes" logo and design, Virtual SMP and VMotion are registered trademarks or trademarks of VMware, Inc. inthe United States and/or other jurisdictions.
Other company names and product names are trademarks or registered trademarks of respective companies.
The company names, system names, product names and other proprietary names that appear in this document are not always accompaniedby trademark symbols ((TM) or (R)).
This guide uses screenshots in accordance with Microsoft Corporation's guidelines.
February 2014
Revision history
March 2012: First edition
July 2012: Second edition
September 2012: Third edition
February 2013: Fourth edition
April 2014: Fifth edition
Copyright 2010-2014 FUJITSU LIMITED
- iii -
ContentsChapter 1 Overview..................................................................................................................................................................1
1.1 Message Overview...............................................................................................................................................................................11.2 Message Format...................................................................................................................................................................................11.3 Message Information in this Manual...................................................................................................................................................2
Chapter 2 Messages with Labels.............................................................................................................................................42.1 Messages Starting with FCMDB.........................................................................................................................................................42.2 Messages Starting with FJSVlnkbs....................................................................................................................................................132.3 Messages Starting with FSP_FJSVCIR_CIRINST...........................................................................................................................152.4 Messages Starting with FSP_SW/RB-A_BASE................................................................................................................................172.5 Messages Starting with SHN.............................................................................................................................................................772.6 Messages Starting with SHS..............................................................................................................................................................832.7 Messages Starting with MpJobsch...................................................................................................................................................151
Chapter 3 Messages without Labels....................................................................................................................................1523.1 Messages Relating to Installation and Uninstallation......................................................................................................................1523.2 Messages Relating to Setup and Setup Cancellation.......................................................................................................................1703.3 Messages Relating to Starting and Stopping...................................................................................................................................1863.4 Messages Relating to Execution Status Confirmation.....................................................................................................................2013.5 Messages Relating to Backup and Restore......................................................................................................................................2043.6 Messages Relating to Changes in the Host Name/IP Address.........................................................................................................2193.7 Messages Relating to the Server Account Management Function..................................................................................................2253.8 Messages Relating to the IPMI Information Account Management Function................................................................................2283.9 Messages Relating to Data Collection.............................................................................................................................................2303.10 Messages Relating to Registering/Changing Password.................................................................................................................2323.11 Messages Relating to Communications Infrastructure Commands...............................................................................................2353.12 Messages Relating to start history of Schedule Definition............................................................................................................2373.13 Messages Relating to the Interstage Single Sign-On.....................................................................................................................238
3.13.1 ssoclsetup Command Messages..............................................................................................................................................2383.13.2 ssoclunsetup Command Messages..........................................................................................................................................2453.13.3 ssoclservicectl Command Messages.......................................................................................................................................2483.13.4 ssoclbackup Command Messages...........................................................................................................................................2503.13.5 ssoclrestore Command Messages...........................................................................................................................................256
3.14 Messages Relating to Systemwalker Runbook Automation Studio Maintenance Commands.....................................................2623.14.1 swrbaexport Settings Export Command.................................................................................................................................2623.14.2 swrbaimport Settings Import Command.................................................................................................................................2633.14.3 swrbacolinf Collecting Maintenance Information Command................................................................................................263
3.15 Messages Relating to QuickForm UI Components.......................................................................................................................2643.16 Messages Relating to the REST Interface.....................................................................................................................................266
3.16.1 Response messages.................................................................................................................................................................2663.17 Messages Displayed in the Custom Messages Dialog Box...........................................................................................................273
- iv -
Chapter 1 OverviewThis chapter explains the messages output by Systemwalker Runbook Automation.
1.1 Message OverviewThe messages output by Systemwalker Runbook Automation include the following:
- Messages output to Event Log on Windows operating system
- Messages output to syslog on UNIX.
- Standard messages output as responses to commands or procedure results.
- Pop-up messages displayed as part of the procedure for windows.
For details on messages output to event log or syslog, refer to "Chapter 2 Messages with Labels".
For details on messages with labels output to the standard output or pop-up windows, refer to "Chapter 2 Messages with Labels".
For details on messages without labels output to the standard output or pop-up windows, refer to "Chapter 3 Messages without Labels".
1.2 Message FormatThis section describes the format of the messages output by Systemwalker Runbook Automation.
Message format
Messages output to the event log or to syslog use the format below:
<label>: <error type>: <message number>: <message text>
<label>: <error type>: <[message number]>: <message text>
Standard and pop-up messages use one of the following formats:
<label>: <message number>: <message text>
<label>: <message text>
<error type>: <message number>: <message text>
<error type>: <message text>
<message number>: <message text>
<message text>
The <label>, <error type>, and <message number> elements are separated by a colon (:) and a space.
Message elements and their meanings
<label>
Identifies the program that output the message.
For messages output to Windows event log, the label format is "AP: <source name>".For messages output to syslog, the label format is "UX: <source name>".The descriptions in this manual do not include the "AP" and "UX" prefixes.
<error type>
Indicates the message type - it corresponds to the "Type" column in the event log.
- 1 -
The list below describes the meaning of the possible values of this element:
- INFO
The procedure has finished and no particular action is required.
- WARNING
A problem has occurred - perform the "Action method" listed in this manual for the message.
- ERROR
A problem has occurred - perform the "Action method" listed in this manual for the message.
<message number>
Message unique identifier - it corresponds to the "Event ID" in the event log.
Use message numbers to find message descriptions in this manual.
<message text>
Information about the status of the system or system errors.
1.3 Message Information in this ManualThis section describes how messages are documented in this manual.
<message text>
Lists the message text (the "AP" and "UX" prefixes will not be displayed in this document).
This document explains the messages that are common to each platform. Accordingly, messages output on each platform may be different.For this reason, the symbol that appears at the start of the message text is used to identify the platform.
Symbol: None
CRF: ERROR: fsv00001: Memory Allocation failed.
- The same message is output in Windows, Linux, and Solaris.
Symbol: [Windows]
[Windows]FSP_FJSVCIR_CIRINST: ERROR: 104: CIRINST104: Failed to copy CIR files.
- This message is output in Windows.
Symbol: [Linux]
[Linux][0001]Parameter error : <option>
- This message is output in Linux.
Symbol: [Solaris]
[Linux][Solaris]FSP_FJSVCIR_CIRINST: ERROR: 104: CIRINST104: Failed to copy CIR installer files.
- 2 -
- This message is also output in Solaris.
Description
Explains the meaning or the cause of the message.
Parameters
Describes the message's parameters (indicated by "%1" or "%2") - omitted for messages without parameters.
System processing
Describes how the system works when the message is displayed.
Cause
Describes the reason why the message is displayed.
Action method
Describe the action to be taken (if applicable).
- 3 -
Chapter 2 Messages with Labels
2.1 Messages Starting with FCMDB FCMDB: INFO: [10001] %1 has started. Description
The %1 service has started successfully.
Parameters
%1: Service name
FCMDB: INFO: [10002] %1 has started. Database update check time: %2 Description
The %1 service has started successfully.
Parameters
%1: Service name
%2: The timestamp of the database update checks (in hh:mm format, separated by commas ",")
FCMDB: INFO: [10003] %1 has stopped. Description
The %1 service has stopped successfully.
Parameters
%1: Service name
FCMDB: INFO: [10004] Update check processing has started.'%1' Description
The database update check held by existing products has started.
Parameters
%1: Service name
FCMDB: INFO: [10005] Update check processing has completed.'%1' Description
Update check procedure has completed successfully.
Parameters
%1: Service name
FCMDB: INFO: [10006] The database has started in recovery mode. Description
The data store has started in recovery mode.
- 4 -
FCMDB: INFO: [10007] Update check processing is being suppressed. Processing has been terminated.'%1' Description
Update check processing of the database belonging to the existing product has been suppressed, therefore processing has beenterminated.
Parameters
%1: Service name
FCMDB: WARNING: [30001] Settings file '%1' is invalid. Processing will continue. (%2) Description
A settings file contains an illegal entry, but processing will continue.
Parameters
%1: Settings file name (file path)
%2: Detailed reason, etc.
Action method
Check the file again to verify if the settings have been changed. Contact Fujitsu technical support if the problem cannot be resolved.
FCMDB: WARNING: [30002] A linked product is not running. (%1) Description
It was not possible to collect data for a linked product because the linked product is not running.
Parameters
%1: Service name where the problem occurred
Action method
Either start the linked product in question, or delete the service where the problem is occurring.
FCMDB: WARNING: [30003] There is at least one node from which IT resource data was not collectedsuccessfully. Description
Data collection failed in one or more nodes.
System processing
The system continues collecting data after recording the error node information into the error log.
Cause
The following are the possible causes:
- The node is not running.
- SSH connection failed.
- Failed to run the data collection program.
- 5 -
Action method
Refer to the following file to eliminate the cause of the failure.
Windows
FJSVcmdba\var\mdr_inv\errorinfo.csv
Linux
/var/opt/FJSVcmdba/etc/mdr_inv/errorinfo.csv
Error log File Format
ID Address Code Message Error description
INITIALIZATION
<none> 000 It failed. Failed to initialize. The process will abort.
Action: Contact Fujitsu technical support.
[group:<group name>] 001 The group is notdefined.
The group is not defined. Group data collection willabort.
Action: Define the group in mdr_inv.properties.
<none> 002 Networks to becollected are notdefined.
The network for data collection is not specified.Data collection for the network to which the nodebelongs will continue.
Action: Specify a network in mdr_inv.properties.
[networkaddress:<network address>sysname:<systemname>]
003 The local systemname is contradicted.
The local system name conflicts. Processing willcontinue without a local system name.
Action: Update the local system name inmdr_inv.properties.
<none> 999 system error. Failed to initialize.
Action: Contact Fujitsu technical support.
PREPARATION
<none> 200 It failed in thepreparationprocessing.
Failed to prepare transaction file creation. Theprocess will abort.
Action: Contact Fujitsu technical support.
[networkaddress:<network address>]
201 There is no nodeinformation on thenetwork.
Node data was not found because node detection isnot performed or failed. Data collection for thisnetwork will not be performed.
Action: Perform the node detection for thisnetwork.
<none> 202 There is no nodeinformation.
Node data is not found. The process will abort.
Action: Refer to the preceding log contents andtake appropriate actions.
<none> 999 system error. Failed to prepare transaction file creation.
Action: Contact Fujitsu technical support.
CREATION
<none> 600 It failed. Failed to prepare transaction file creation. Theprocess will abort.
Action: Contact Fujitsu technical support.
<none> 999 system error. Failed to prepare transaction file creation.
Action: Contact Fujitsu technical support.
TERMINATION
<none> 700 It failed. Failed to close the file. The process will abort.
Action: Contact Fujitsu technical support.
- 6 -
ID Address Code Message Error description
<none> 999 system error. Failed to create a transaction.
Action: Contact Fujitsu technical support.
NODE <none> 100 It failed. Failed to detect a node. The process will abort.
Action: Contact Fujitsu technical support.
<none> 999 system error. Failed to detect a node.
Action: Contact Fujitsu technical support.
[group:<group name>subnetMask:<subnetmask>]
101 An illegal value isdefined in the subnetmask.
An invalid value is specified for the subnet mask.The process for the group, which uses thedefinition, will be skipped.
Action: Fix the value defined for <groupname>.mdbad.inventory.network.subnetmask inmdr_inv.properties.
[group:<group name>networkaddress:<network address>subnetMask:<subnetmask>]
102 An illegal value isdefined in thenetwork address.
An invalid value is specified for the networkaddress. The process for the network, which usesthe definition, will be skipped.
Action: Fix the value defined for <groupname>.mdbad.inventory.network.address inmdr_inv.properties.
<none> 103 There is no definitionto detect the node.
No definition is specified. The process will abort.
Action: Refer to the preceding log contents andtake appropriate actions.
[networkaddress:<network address>]
104 The node detectioncommand failed.
The node detection command failed. The datacollection for this network will abort.
Action: Contact Fujitsu technical support.
[networkaddress:<network address>]
105 Detection failure. Failed to detect a node. The data collection for thisnetwork will abort.
Action: Contact Fujitsu technical support.
[networkaddress:<network address>]
106 The node detectionresult is illegal.
The result of node detection is invalid. The datacollection for this network will abort.
Action: Contact Fujitsu technical support.
[networkaddress:<network address>]
107 Node informationwas not able to beacquired.
Unable to collect information for a node. The datacollection for this network will abort.
Action: Contact Fujitsu technical support.
COLLECTION
[IPaddress:<IPaddress>networkaddress:<network address>]
300 It failed. Failed to collect data. The process will continue.
Action: Refer to the preceding log contents andtake appropriate actions.
[IPaddress:<IPaddress>networkaddress:<network address>]
301 It failed in theacquisition of theXML document.(Node detection)
Failed to load XML document for detecting nodes.The process will continue.
Action: Contact Fujitsu technical support.
[IPaddress:<IPaddress>networkaddress:<network address>]
302 It was not possible toconnect it.
Connection failure. The process will continue.
Action: Configure the network environment toenable communication using SSH or Linkexpress.
- 7 -
ID Address Code Message Error description
[IPaddress:<IPaddress>networkaddress:<network address>]
303 There is nodocument.
The document containing data collection resultsdoes not exist. The process will continue.
Action: Contact Fujitsu technical support.
[IPaddress:<IPaddress>networkaddress:<network address>]
304 It failed in makingthe history.
Failed to create an archive log. The process willcontinue. Note that the next data collection will notwork unless this problem is resolved.
Action: Contact Fujitsu technical support.
DEPLOY
[IPaddress:<IPaddress>networkaddress:<network address>]
400 It failed. Failed to deploy the data collection program. Theprocess will continue.
Action: Refer to the preceding log contents andtake appropriate actions.
[IPaddress:<IPaddress>networkaddress:<network address>]
999 system error. Failed to deploy the data collection program.
Action: Contact Fujitsu technical support.
OPERATION
[IPaddress:<IPaddress>networkaddress:<network address>]
500 It failed. Failed to run the data collection program. Theprocess will continue.
Action: Refer to the preceding log contents andtake appropriate actions.
[IPaddress:<IPaddress>networkaddress:<network address>]
999 system error. Failed to run the data collection program.
Action: Contact Fujitsu technical support.
Error log File Sample
2011/01/01 04:30:09.434,START
2011/01/01 04:30:27.792,NODE,[networkAddress: 192.0.2.10],105,Detection failure.
2011/01/01 04:30:27.805,NODE,,202,There is no node information.
2011/01/01 04:30:27.809,PREPARATION,,200,It failed in the preparation processing.
2011/01/01 04:30:28.079,COLLECTION,[IPaddress: 192.0.2.20 networkaddress: 192.0.2.30],302,It was not possible toconnect it.
2011/01/01 04:30:28.083,COLLECTION,[IPaddress: 192.0.2.40 networkaddress: 192.0.2.50],302,It was not possible toconnect it.
2011/01/01 20:04:28.147,END
Eliminate the cause of the failure and run the data collection process again, or collect data at the next scheduled node discovery process.
FCMDB: WARNING: [30004] There is at least one network in which the node detection process failed. Description
Node detection failed in one or more networks.
System processing
The system writes the network where the node detection failed to the error log file, and data collection continues with the other network.Data collection will end if no further network exists for this purpose.
- 8 -
Cause
The possible cause is as follows:
- Invalid value was specified for the subnet mask or network address.
Action method
Refer to the following file to eliminate the cause of the failure.
Windows:
FJSVcmdba\var\mdr_inv\errorinfo.csv
Linux:
/var/opt/FJSVcmdba/etc/mdr_inv/errorinfo.csv
See
For details on the file format, refer to the "Error log File Format".
Eliminate the cause of the failure and run the data collection process again, or collect data at the next scheduled node discovery process.
FCMDB: WARNING: [30005] There is at least one node in which the IT resource data collection programwas not deployed successfully. Description
The deployment of data collection program failed in one or more nodes.
System processing
The system writes the node where the data collection program deployment failed to the error log, and deployment and data collectioncontinue with the other node.
Causes
The possible causes are as follow:
- SSH connection failed
- File transfer failed
- Insufficient disk space
- Insufficient memory
Action method
Refer to the following file to eliminate the cause of the failure.
Windows:
FJSVcmdba\var\mdr_inv\errorinfo.csv
Linux:
/var/opt/FJSVcmdba/etc/mdr_inv/errorinfo.csv
See
For details on the file format, refer to the "Error log File Format".
Eliminate the cause of the failure and run the data collection process again, or collect data at the next scheduled node discovery process.
- 9 -
FCMDB: WARNING: [30006] There is at least one node in which the IT resource data collection programwas not executed successfully. Description
The execution of data collection program failed in one or more nodes.
System processing
The system writes the node where the data collection program failed to the error log, and data collection continues with the other node.
Cause
The possible causes are as follow:
- Insufficient disk space
- Insufficient memory
Action method
Refer to the following file to eliminate the cause of the failure.
Windows:
FJSVcmdba\var\mdr_inv\errorinfo.csv
Linux:
/var/opt/FJSVcmdba/etc/mdr_inv/errorinfo.csv
See
For details on the file format, refer to the "Error log File Format".
Resolve the cause, and then run the IT resource data collection again, or collect IT resource data at the next scheduled discovery process.
FCMDB: ERROR: [60001] %1 failed to start. (%2) Description
An error has occurred during the startup procedure for the %1 service.
Parameters
%1: Service name
%2: Detailed reason, etc.
Action method
Refer to the detailed reason. Also, refer to any other messages that have been output. Contact Fujitsu technical support if the problemcannot be resolved.
FCMDB: ERROR: [60002] Failed to read file '%1'. (%2) Description
Reading a file has failed.
Parameters
%1: File name (file path)
%2: Detailed reason, etc.
- 10 -
Action method
Contact Fujitsu technical support if the file exists and there are no problems with access privileges.
FCMDB: ERROR: [60003] Failed to write file '%1'. (%2) Description
Writing to a file has failed.
Parameters
%1: File name (file path)
%2: Detailed reason, etc.
Action method
Contact Fujitsu technical support if there are no problems with file access privileges or disk space.
FCMDB: ERROR: [60004] Failed to create file or directory '%1'.(%2) Description
Creating a file or directory has failed.
Parameters
%1: Name of the file (file path) or directory (directory path)
%2: Detailed reason, etc.
Action method
Contact Fujitsu technical support if there are no problems with access privileges or disk space.
FCMDB: ERROR: [60005] Settings file '%1' is invalid. (%2) Description
A settings file contains an illegal entry.
Parameters
%1: Name of the settings file (file path)
%2: Detailed reason, etc.
Action method
Check the file again to verify if the settings have been changed. Contact Fujitsu technical support if the problem cannot be resolved.
FCMDB: ERROR: [60006] Schema file '%1' is invalid. (%2) Description
The content of a schema file (*.xsd) is invalid.
The schema file might have been changed.
Parameters
%1: Name of the schema file (file path)
%2: Detailed reason, etc.
- 11 -
Action method
Replace the schema file with the original one if it has been updated unexpectedly.
If the original schema file cannot be found, then install the package again.
FCMDB: ERROR: [60007] Update check processing has failed. '%1' (%2) Description
An error has occurred during update check procedure.
Parameters
%1: Service name
%2: Detailed reason, etc.
Cause
The possible causes are as follow:
- The Management Server is not running.
- The Systemwalker Runbook Automation is not running on the Management Server.
- The communications infrastructure is not running on the Management Server.
- The linked products are not running.
- One of the following configuration files contains an error:
- Agent linkage definition.
- Data collection definition.
- Schedule Definition file
- Insufficient disk space.
- Insufficient memory.
Action method
Take the following actions, and start record collection again.
- Start the Management Server.
- Start Systemwalker Runbook Automation using the swrba start command on the Management Server.
- Start the communications infrastructure using the swncctrl start command on the Management Server.
- Refer to the Systemwalker Runbook Automation Reference Guide and update the definition files.
- Delete unnecessary files to free disk space.
- Increase memory size.
FCMDB: ERROR: [60008] Failed to execute an event action. (%1) Description
An error has occurred during the execution procedure for an event (exit function).
Parameters
%1: Detailed reason, etc.
- 12 -
Action method
If the command for the event action has been edited, check the settings. Also, check the existence of the command. Contact Fujitsutechnical support if the problem cannot be resolved.
FCMDB: ERROR: [60013] A linked product is not installed. (%1) Description
It was not possible to collect data for a linked product because the linked product is not running.
Parameters
%1: Name of the service where the problem occurred
Action method
Either install the linked product in question, or delete the service where the problem is occurring.
2.2 Messages Starting with FJSVlnkbsThis chapter explains messages output by File Transfer library.
FJSVlnkbs: INFO: 00001: File Transfer library has started. Description
File Transfer library has started.
System Processing
File Transfer library has started.
FJSVlnkbs: INFO: 00002: File Transfer library has stopped. Description
File Transfer library has stopped.
System Processing
File Transfer library has stopped.
FJSVlnkbs: ERROR: 00003: File Transfer library has failed to start.(code=%s) Description
Failed to start File Transfer library.
Parameters
%s: return code
System Processing
Starting File Transfer library is cancelled.
Cause
Possible causes are listed below.
- Insufficient disk space
- Insufficient system parameters[Linux] [Solaris]
- Other system errors
- 13 -
Action method
If return code is 8, check the following.
- Check if there is enough disk space in the disk where the product installation directory is.
- Check if system parameters are enough.
For system parameters, see Pre-installation Tasks in the Systemwalker Runbook Automation Installation Guide.
If return code is not 8, or neither of the above applies, contact Fujitsu technical support.
FJSVlnkbs: ERROR: 00004: File Transfer library has failed to stop.(code=%s) Description
Failed to stop File Transfer library.
Parameters
%s: return code
System Processing
Stopping processing of File Transfer library is cancelled.
Cause
Possible causes are listed below.
- Insufficient disk space
- Insufficient system parameters[Linux] [Solaris]
- Other system errors
Action method
If return code is 8, check the following.
- Check if there is enough disk space in the disk where the product installation directory is.
- Check if system parameters are enough.
For system parameters, see "Pre-installation Tasks" in the Systemwalker Runbook Automation Installation Guide.
If return code is not 8, or neither of the above applies, contact Fujitsu technical support.
FJSVlnkbs: INFO: 00005: File Transfer library has already started. Description
File Transfer library has already started.
System Action
Because File Transfer library has already started, starting processing is cancelled.
FJSVlnkbs: INFO: 00006: File Transfer library has already stopped. Description
File Transfer library has already stopped.
System Action
Because File Transfer library has already stopped, starting processing is cancelled.
- 14 -
2.3 Messages Starting with FSP_FJSVCIR_CIRINSTThis section describes messages output by FJSVcir.
FSP_FJSVCIR_CIRINST: ERROR: 101: CIRINST101: Administrator privilege is required. Description
The user does not have administrator privileges
Action method
Login with administrator privileges and run the command again.
FSP_FJSVCIR_CIRINST: ERROR: 102: CIRINST102: Failed to create %s Description
Failed to create a directory during the installation.
Parameters
%s: Directory name
Action method
Creating the directory might have failed for some reason. Run the installer again, or run cirinst command again. If the problem persists,check the system log.
FSP_FJSVCIR_CIRINST: ERROR: 103: CIRINST103: It is required at least %dMB Description
Insufficient disk space (at least 150 MB required).
Parameters
%d: Disk spaces
Action method
Confirm that the system has sufficient disk spaces
[Windows] FSP_FJSVCIR_CIRINST: ERROR: 104: CIRINST104: Failed to copy CIR files.[Linux][Solaris]FSP_FJSVCIR_CIRINST: ERROR: 104: CIRINST104: Failed to copy CIR installer files. Description
Failed to copy files required for the installation.
Action method
Copying the files failed for some reason. Run the installer again, or run cirinst command again. If the problem persists, check thesystem log.
FSP_FJSVCIR_CIRINST: ERROR: 105: CIRINST105: Failed to copy JRE. Description
Failed to copy JRE required for installation.
- 15 -
Action method
Copying the files failed for some reason. Run the installer again, or run cirinst command again. If the problem persists, check thesystem log.
FSP_FJSVCIR_CIRINST: ERROR: 106: CIRINST106: Failed to copy CIR files. Description
Failed to copy files during the installation.
Action method
Copying the files failed for some reason. Run the installer again, or run cirinst command again. If the problem persists, check thesystem log.
FSP_FJSVCIR_CIRINST: ERROR: 107: CIRINST107: Invalid option. Description
An invalid option was specified.
Action method
Specify a valid option. [-c]: Command interface
FSP_FJSVCIR_CIRINST: ERROR: 108: CIRINST108: JRE which should be deployed is not bundled. Description
An appropriate JRE for this system is not bundled.
Action method
Confirm that the product supports the platform.
FSP_FJSVCIR_CIRINST: ERROR: 109: CIRINST109: Unsupported OS. Description
Unsupported operating system.
Action method
Confirm that the product supports the operating system.
[Linux]
If the product supports the operating system, there may be insufficient redhat-lsb packages. Check whether the redhat-lsb packagesare in the system. If they are not, add them then re-execute the installer.
[Linux]FSP_FJSVCIR_CIRINST: ERROR: 185: CIRINST185: lsb_release was not found. Please install thepackage below.- redhat-lsb Description
lsb_release command was not found.
Action method
Add redhat-lsb package and then execute install again.
- 16 -
FSP_FJSVCIR_CIRINST: ERROR: 186: CIRINST186: lsb_release was not found. Description
lsb_release command was not found.
Action method
Add relevant package and then execute install again.
FSP_FJSVCIR_CIRINST: ERROR: 201: CIRINST201: Administrator privilege is required. Description
The user does not have administrator privileges
Action method
Login with administrator privileges and run the command again.
FSP_FJSVCIR_CIRINST: ERROR: 203: CIRINST203: Failed to delete files. Description
Failed to delete FJSVcir files.
Action method
Deleting the files failed for some reason. Run cirremove command again. If the problem persists, check the system log.
FSP_FJSVCIR_CIRINST: ERROR: 205: CIRINST205: Invalid option. Description
Invalid option is specified.
Action method
No option is supported. Retry without any options.
2.4 Messages Starting with FSP_SW/RB-A_BASE FSP_SW/RB-A_BASE: ERROR: 00001: A management server has already been setup. Unable to run thecommand. Description
A management server has already been setup. Unable to run the command.
System processing
Automated Operation Process is interrupted. 202 Return Values of operation component is output.
Cause
The possible causes are as follow:
- If the message is displayed while running swrba_getmanagerhostinfo command:
- The management server environment is already setup.
- A repository is defined in the Interstage Directory Service.
- 17 -
- If the message is displayed while deploying L-Server:
- An attempt was made to create L-Server without running swrba_getmanagerhostinfo command.
- Management server might have been setup after running swrba_getmanagerhostinfo command, and then trying to create L-Server.
Action method
Take the following actions:
- If the message is displayed while running swrba_getmanagerhostinfo command:
If the management server is already setup, cancel to setup it. Delete any repositories in the Interstage Directory Service on themanagement server (for details, refer to Interstage Application Server manuals).
- If the message is displayed while deploying L-Server:
Create the L-Server again. But before that, run the swrba_getmanagerhostinfo command to save host information. Do not startInterstage or setup the management server while creating L-Server. For details, refer to Systemwalker Configuration Managermanuals.
FSP_SW/RB-A_BASE: ERROR: 00002: Unable to run the command because Interstage is running. Description
Unable to run the command, because Interstage is running.
System processing
Processing is interrupted.
Cause
Unable to run the command, because Interstage is running.
Action method
Confirm the Interstage status using isstat command - if Interstage is running, then terminate it by issuing the isstop -f command (fordetails on these commands, refer to Interstage Application Server Reference Manual (Command Edition)).
If the message is displayed while deploying L-Server, then it has been created incorrectly and must be created again. But before that,run the swrba_getmanagerhostinfo command to save host information. Do not start Interstage or setup the Management Server, whilecreating L-Server. Refer to Systemwalker Software Configuration Manager manuals for details.
FSP_SW/RB-A_BASE: ERROR: 00003: Invalid options or arguments are specified. Command name=%1 Description
Unable to run the command because invalid options or arguments were found.
Parameters
%1: Command name
System processing
Processing is interrupted.
Cause
Unable to run the command because invalid options or arguments were found.
Action method
For details on command options and arguments, refer to Systemwalker Runbook Automation Reference Guide.
- 18 -
FSP_SW/RB-A_BASE: ERROR: 00004: I-O error occurred. Detail=%1 Description
An I/O error occurred.
Parameters
%1: Error detail
System processing
Processing is interrupted.
Cause
An I/O error occurred.
Action method
Eliminate the cause of the problem and run the command again.
FSP_SW/RB-A_BASE: ERROR: 00005: Interstage Directory Service repository has already created.Unable to run the command. Description
Unable to run the command - Interstage Directory Service repository has already been created.
System processing
Processing is interrupted.
Cause
A repository is created in the Interstage Directory Service.
Action method
Delete the repository for Interstage Directory Service.
FSP_SW/RB-A_BASE: ERROR: 00006: Interstage Application Service configuration file (http.conf) doesnot exist. Description
http.conf does not exist.
System processing
Processing is interrupted.
Cause
Systemwalker Runbook Automation installation directory might be corrupt.
Action method
Install Systemwalker Runbook Automation again.
FSP_SW/RB-A_BASE: ERROR: 00007: Failed to edit Interstage Application Server configuration file(http.conf). Description
Failed to edit http.conf.
- 19 -
System processing
Processing is interrupted.
Cause
The following are the possible causes:
- Insufficient access permission.
- Insufficient memory.
- I-O error.
Action method
- Confirm that the administrator privilege was granted to access Systemwalker Runbook Automation installation directory.
- Confirm that I/O error does not occur - if it does, reinstall Systemwalker Runbook Automation.
- Confirm that sufficient memory size was allocated.
FSP_SW/RB-A_BASE: ERROR: 00008: Command for creating L-Server does not exist. Description
A command file for creating L-Server does not exist.
System processing
Processing is interrupted.
Cause
Unable to run the command because a command file, which is required for creating L-Server, does not exist.
Action method
Refer to Systemwalker Software Configuration Manager manuals, copy then required command, and run the operation again.
FSP_SW/RB-A_BASE: ERROR: 00009: Failed to run the command. Detail=%s Description
Failed to run the command.
Parameters
%1: Error detail
System processing
Processing is interrupted.
Cause
Failed to run the command.
Action method
Eliminate the cause of the failure and run the command again.
FSP_SW/RB-A_BASE: ERROR: 00010: Insufficient privilege to run the command. Description
Insufficient privileges to run the command.
- 20 -
System processing
Processing is interrupted.
Cause
Insufficient privileges to run the command.
Action method
Run the command again using superuser account.
FSP_SW/RB-A_BASE: ERROR: 00011: Unable to run the command because the linked server/relay serverhas already been setup. Description
Unable to run the command because the linked server/relay server has already been setup.
System processing
Processing is interrupted.
Cause
Unable to run the command because the linked server/relay server has already been setup.
L-Server creation might have been started without cancelling linked server/relay server setup.
Action method
Create the L-Server again. But before that, run a setup cancellation for linked server and relay server. Refer to Systemwalker SoftwareConfiguration Manager manuals for details.
FSP_SW/RB-A_BASE: ERROR: 00012: swrba_getmanagerhostinfo is not completed. Description
Unable to update Management Server host information because swrba_getmanagerhostinfo command has not completed.
System processing
Processing is interrupted.
Cause
L-Server creation might be started without completing swrba_getmanagerhostinfo command.
Action method
Create the L-Server again. But before that, run swrba_getmanagerhostinfo command to save host information. Refer to SystemwalkerSoftware Configuration Manager manuals for details.
FSP_SW/RB-A_BASE: ERROR: 00013: Incorrect environment variable. environment variable=%1 value=%2 Description
Unable to run the command because there is an error in the environment variable.
Parameters
%1: Environment variable name that contains an error
%2: Environment variable value
- 21 -
System processing
Processing is interrupted.
Cause
Unable to run the command because there is an error in the environment variable.
Action method
There might be a problem in the environment where L-Server is deployed. Refer to Systemwalker Software Configuration Managermanuals, and confirm the environment where L-Server is deployed.
FSP_SW/RB-A_BASE: INFO: 00014: Command has been completed. Description
The command has been completed.
Action method
This message informs the progress. No action is required.
FSP_SW/RB-A_BASE: INFO: 00406: Starting Systemwalker Runbook Automation. Description
Systemwalker Runbook Automation is starting up.
Action method
This message informs the progress. No action is required.
FSP_SW/RB-A_BASE: INFO: 00407: Systemwalker Runbook Automation has started. Description
Systemwalker Runbook Automation has started normally.
Action method
This message informs the progress. No action is required.
FSP_SW/RB-A_BASE: ERROR: 00416: Failed to start Systemwalker Runbook Automation. Description
Starting Systemwalker Runbook Automation has failed.
Action method
- Check the system log (event log for Windows) and resolve any errors that appear before this message.
- If Interstage service is not running, then start it.
- If memory size is insufficient, then increase it.
- if disk space is insufficient, then increase it.
- Ensure that the system parameter is specified correctly.
If the problem persists, collect investigation data using the iscollectinfo command, and contact Fujitsu technical support.
FSP_SW/RB-A_BASE: INFO: 00426: Systemwalker Runbook Automation is closing down.
- 22 -
Description
Systemwalker Runbook Automation close down process has started.
Action method
This message informs the progress. No action is required.
FSP_SW/RB-A_BASE: INFO: 00427: Systemwalker Runbook Automation has terminated normally. Description
Systemwalker Runbook Automation has terminated normally.
Action method
This message informs the progress. No action is required.
FSP_SW/RB-A_BASE: ERROR: 00436: Terminating Systemwalker Runbook Automation has failed. Description
Terminating Systemwalker Runbook Automation has failed.
Action method
- Check the system log (event log for Windows) and resolve any errors that appear before this message.
- Sufficient memory size could not be allocated because of the system load. Wait until the system load becomes low, and retrytermination.
If the problem persists, collect investigation data using the iscollectinfo command, and contact Fujitsu technical support.
FSP_SW/RB-A_BASE: ERROR: 00451: Interstage is not started, Systemwalker Runbook Automationcannot be started. Description
Because Interstage is not started, Systemwalker Runbook Automation cannot be started.
Cause
After OS is started, starting Interstage cannot be checked.
Action Method
Check the following.
- Because starting Interstage may have failed, check the error message output before and take the appropriate action.
- Starting Interstage has been delayed. After Interstage is started, start Systemwalker Runbook Automation by swrba_start command.
FSP_SW/RB-A_BASE: ERROR: 00452: The LDAP server is not started, Systemwalker RunbookAutomation cannot be started. Description
Because the LDAP server is not started, Systemwalker Runbook Automation cannot be started.
Cause
After the operating system is started, LDAP server start cannot be checked.
Action method
Check the following:
- 23 -
- LDAP server start might have failed. Refer to the LDAP server error messages and take the appropriate action.
- Access to LDAP might have failed. Check if the LDAP server has started.
- LDAP server start is delayed. After the LDAP server starts, use the swrba_start command to start Systemwalker RunbookAutomation.
FSP_SW/RB-A_BASE: ERRROR: 00453: Systemwalker Runbook Automation cannot be started because%1 has not been started. Description
%1 has not started, therefore Systemwalker Runbook Automation cannot be started.
Parameters
%1: Service that has not started
Cause
Whether or not %1 had started could not be checked after the operating system started.
Action method
Check the following:
- If "Interstage Java EE DAS" is displayed in %1, the Interstage Java EE DAS service may have failed to start. Refer to the errormessage output immediately before, then take action. Alternatively, there may have been a delay in the start of the Interstage JavaEE DAS service. After the Interstage Java EE DAS service has started, use the swrba_start command to start SystemwalkerRunbook Automation.
- If "Interstage Java EE Node Agent" is displayed in %1, the Interstage Java EE Node Agent service may have failed to start. Referto the error message output immediately before, then take action. Alternatively, there may have been a delay in the start of theInterstage Java EE Node Agent service. After the Interstage Java EE Node Agent service has started, use the swrba_start commandto start Systemwalker Runbook Automation.
- If "Message Broker" is displayed in %1, the message broker may have failed to start. Refer to the error message output immediatelybefore, then take action. Alternatively, there may have been a delay in the start of the message broker. After the message brokerhas started, use the swrba_start command to start Systemwalker Runbook Automation.
FSP_SW/RB-A_BASE: ERROR: 00460: The start processing for monitoring file transfer infrastructure hasfailed. Detail=%1 Description
An error occurred when file transfer infrastructure started, therefore processing could not start. Take action based on the message.
Parameters
%1: Error detail
System processing
Processing is interrupted.
Cause
The following are the possible causes:
- File transfer infrastructure has not started, or an error occurred in file transfer infrastructure.
- Insufficient memory.
- I/O error.
- 24 -
Action method
- If an error has occurred in file transfer infrastructure, take action according to the message output by it, then start file transferinfrastructure.
- Confirm that the administrator privilege was granted to access Windows version Systemwalker Runbook Automation installationdirectory.
- Confirm that I/O error does not occur - if it does, reinstall Systemwalker Runbook Automation.
- Confirm that sufficient memory size was allocated.
If the problem persists, collect investigation data using the iscollectinfo command, and contact Fujitsu technical support.
FSP_SW/RB-A_BASE: ERROR: 00461: Monitoring process %1 has finished. Description
The file transfer infrastructure process has finished.
Parameters
%1: Error detail
System processing
Processing is finished.
Cause
An error occurred in the file transfer infrastructure or it has finished.
Action method
Check the system log (event log for Windows) and resolve any errors that appear before this message.
If an error has occurred in file transfer infrastructure, take action according to the message output by it, then start file transferinfrastructure.
If the problem persists, collect investigation data using the iscollectinfo command, and contact Fujitsu technical support.
FSP_SW/RB-A_BASE: ERROR: 00462: Error has occurred in the monitoring process of file transferinfrastructure. Detail=%1 Description
An error has occurred in the file transfer infrastructure monitoring.
Parameters
%1: Error detail
System processing
Processing is finished.
Cause
File transfer infrastructure monitoring failed.
Action method
If an error has occurred in file transfer infrastructure, take action according to the message output by it, then start file transferinfrastructure.
Additionally, Confirm that sufficient memory size was allocated.
If the problem persists, collect investigation data using the iscollectinfo command, and contact Fujitsu technical support.
- 25 -
FSP_SW/RB-A_BASE: INFO: 00601: Starting %2 for %1. Description
This is an informational message on starting backup or restore.
Parameters
%1: Target of the backup/restore:
- Systemwalker Runbook Automation
- Process Management Database
- File(s)
- CMDB manager
- Interstage Business Process Manager
- Systemwalker Runbook Automation to the restoration target Management Server
- Systemwalker Runbook Automation on the restoration target Management Server
- Restoration target directory
- Scheduling
%2: Process type:
- Backup
- Restore
- Environment build
- Environment deletion
- Initialization
Action method
This message informs the progress. No action is required.
FSP_SW/RB-A_BASE: INFO: 00602: %2 for %1 has been completed. Description
This is an informational message on completing backup or restore.
Parameters
%1: Target of the backup/restore:
- Systemwalker Runbook Automation
- Process Management Database
- File(s)
- CMDB manager
- Interstage Business Process Manager
- Systemwalker Runbook Automation to the restoration target Management Server
- Systemwalker Runbook Automation on the restoration target Management Server
- Restoration target directory
- Scheduling
%2: Process type:
- 26 -
- Backup
- Restore
- Environment build
- Environment deletion
- Initialization
Action method
This message informs the progress. No action is required.
FSP_SW/RB-A_BASE: ERROR: 00611: An error occurred during %2 for %1. (Detail: %3) Description
This is an error message used for backup or restore.
Parameters
%1: Target of the backup/restore:
- Systemwalker Runbook Automation
- Process Management Database
- File(s)
- CMDB manager
- Backup environment
- Restore environment
- Interstage Business Process Manager
- Systemwalker Runbook Automation to the restoration target Management Server
- Systemwalker Runbook Automation on the restoration target Management Server
- Restoration target directory
- Scheduling
%2: Process type:
- Backup
- Restore
- Initial status check
- Checking process
- Environment build
- Environment deletion
- Initialization
%3: Error detail
- One of the "messages without labels" appears.
See
Refer to "Chapter 3 Messages without Labels".
- 27 -
Action method
Refer to the error detail and take the appropriate action.
FSP_SW/RB-A_BASE:INFO: 02000:%1 is starting. Option:%2 Description
The command is starting...
Parameters
%1: Command name
%2: Option name
System processing
The process has completed.
FSP_SW/RB-A_BASE:INFO: 02001: %1 has finished. Option: %2 Code: %3 Description
The command has finished.
Parameters
%1: Command name
%2: Option name
%3: Return code
System processing
The process has been finished.
FSP_SW/RB-A_BASE:ERROR: 02002: %1 has terminated abnormally. Option: %2 Code: %3 Description
An error occurred while running the command.
Parameters
%1: Command name
%2: Option name
%3: Return code
System processing
Processing is interrupted.
Action method
Check the error details and take the appropriate action.
FSP_SW/RB-A_BASE:ERROR: 02003:The specified process definition has already been registered.Process definition name: %1 Description
The specified process definition has already registered.
- 28 -
Parameters
%1: Process definition name
System processing
Abort the new registration for the defined process.
Cause
The process definition has already registered.
Action method
Register a process that has not been registered yet.
FSP_SW/RB-A_BASE:ERROR: 02004: The specified definition file is invalid. Command: %1 Option: %2Definition file name: %3 Description
The content of the definition file is invalid.
Parameters
%1: Command name
%2: Option name
%3: Definition file name
System processing
Processing is interrupted.
Cause
The content of the definition file is invalid.
Action method
Specify a valid definition file and run the command again.
FSP_SW/RB-A_BASE:ERROR: 02005: The process definition for the specified version does not exist.Command: %1 Option: %2 Process definition name: %3 Description
The process definition for the specified version does not exist..
Parameters
%1: Command name
%2: Option name
%3: Process definition name
System processing
The system cancels the start process.
Cause
The specified version of the process definition does not exist.
Action method
Specify an existing version of the process definition.
- 29 -
FSP_SW/RB-A_BASE:ERROR: 02006: The specified user ID or password is incorrect. Command: %1Option: %2 user: %3 Description
Login failed because an incorrect user ID or password has been entered.
Parameters
%1: Command name
%2: Option name
%3: User ID
System processing
Processing is interrupted.
Cause
The user ID or the password is incorrect.
Action method
Specify a valid user ID and password.
FSP_SW/RB-A_BASE: ERROR: 02007:Do not have the privileges required to execute %1. Command: %1Option: %2 user: %3 Description
The user ID does not have sufficient privileges to run the operation.
Parameters
%1: Command name
%2: Option name
%3: User ID
System processing
Processing is interrupted.
Cause
The specified user does not have sufficient privileges.
Action method
Specify a user ID that has sufficient privileges.
FSP_SW/RB-A_BASE: ERROR: 02008:The specified directory does not exist. Command: %1 Option: %2Directory: %3 Description
The specified directory does not exist.
Parameters
%1: Command name
%2: Option name
%3: Directory
- 30 -
System processing
Processing is interrupted.
Cause
The specified directory does not exist.
FSP_SW/RB-A_BASE: ERROR: 02009:The specified file does not exist. Command: %1 Option: %2 Filename: %3 Description
The specified file does not exist.
Parameters
%1: Command name
%2: Option name
%3: File name
System processing
Processing is interrupted.
Cause
The specified file does not exist.
FSP_SW/RB-A_BASE: ERROR: 02010: An internal error occurred. Command: %1 Option: %2 Code: %3 Description
An internal error has occurred.
Parameters
%1: Command name
%2: Option name
%3: Return code
System processing
Processing is interrupted.
Cause
An internal error has occurred.
Action method
Contact Fujitsu technical support.
System Administrator action
Contact Fujitsu technical support.
FSP_SW/RB-A_BASE: ERROR: 02011:The parameter is invalid. Usage: %1 Description
An invalid parameter was specified.
- 31 -
Parameters
%1: Usage
System processing
Processing is interrupted.
Cause
An invalid parameter was specified.
Action method
Specify the correct parameter.
System Administrator action
None.
FSP_SW/RB-A_BASE: ERROR: 02012: Failed to connect to BPM. Description
Connecting to BPM has failed.
System processing
Processing is interrupted.
Cause
Connecting to BPM has failed.
Action method
Ensure that Systemwalker Runbook Automation is running.
If the message appears while Systemwalker Runbook Automation is running correctly, contact Fujitsu technical support.
System Administrator action
Contact Fujitsu technical support.
FSP_SW/RB-A_BASE: ERROR: 02013: The specified automated operation process group definition hasalready been registered. Automated operation process group name: %1 Description
The group definition has already been already registered.
Parameters
%1: Automated Operation Process Group definition name
System processing
Processing is interrupted.
Cause
The specified group definition has already been registered.
Action method
Specify an group definition that has not been registered yet.
- 32 -
FSP_SW/RB-A_BASE: ERROR: 02014:The specified parameter file does not exist. Command: %1 Option:%2 Parameter file name: %3 Description
The specified parameter file does not exist.
Parameters
%1: Command name
%2: Option name
%3: Parameter file name
System processing
Processing is interrupted.
Cause
The specified parameter file does not exist.
Action method
No action is required.
FSP_SW/RB-A_BASE: ERROR: 02015:The file character code is invalid. File: %1 Description
The file uses an invalid encoding.
Parameters
%1: File name
System processing
Processing is interrupted.
Cause
The file does not use UTF-8 encoding.
Action method
Specify a file that uses UTF-8 encoding.
FSP_SW/RB-A_BASE: ERROR: 02016:The specified automated operation process group definition doesnot exist. Automated operation process group name: %1 Description
The specified Automated Operation Process Group definition does not exist.
Parameters
%1: Automated Operation Process Group name
System processing
Processing is interrupted.
Cause
The specified Automated Operation Process Group definition does not exist.
- 33 -
Action method
Specify a group that has already been defined.
FSP_SW/RB-A_BASE: ERROR: 02017: The parameter is invalid. Parameter name: %1 Parameter content:%2 Description
An invalid parameter was specified.
Parameters
%1: Parameter name
%2: Parameter content
System processing
Processing is interrupted.
Cause
The specified parameter is invalid.
Action method
Specify a valid parameter and run the process again.
System Administrator action
None.
FSP_SW/RB-A_BASE: ERROR: 02018:Failed to create the specified directory. Directory: %1 Description
Failed to create the specified directory..
Parameters
%1: Directory
System processing
Processing is interrupted.
Cause
Unable to create the specified directory.
Action method
Ensure that the user has sufficient privileges to create the directory and that there is sufficient disk space.
If no problem is detected, contact Fujitsu technical support.
FSP_SW/RB-A_BASE: ERROR: 02019:The specified process definition does not exist. Process definitionname: %1 Description
The specified process definition does not exist.
Parameters
%1: Process definition name
- 34 -
System processing
Processing is interrupted.
Cause
The specified process definition does not exist.
Action method
Specify a process that has already been defined and can be run by the user.
FSP_SW/RB-A_BASE: ERROR: 02020:The specified automated operation process group does not exist.Automated operation process group name: %1 Description
The Automated Operation Process Group does not exist.
Parameters
%1: Automated Operation Process Group name
System processing
Processing is interrupted.
Cause
The Automated Operation Process Group does not exist.
Action method
Specify a process group that has already been defined.
System Administrator action
None.
FSP_SW/RB-A_BASE: ERROR: 02021: The UDA specified in parameter file does not exist in the processdefinition. Parameter file: %1 Description
The UDA, which is specified in the parameter file, does not exist in the process definition.
Parameters
%1: Parameter file
System processing
Processing is interrupted.
Cause
The UDA, which is specified in the parameter file, does not exist in the process definition.
Action method
Update the process definition to specify the UDA.
FSP_SW/RB-A_BASE: ERROR: 02022:Failed to read the specified file. File: %1 Description
Reading the file has failed.
- 35 -
Parameters
%1: File name
System processing
Processing is interrupted.
Cause
Reading the file has failed.
Action method
Ensure that the file access permission.
FSP_SW/RB-A_BASE: ERROR: 02023 : Failed to register the specified process definition. Processdefinition name: %1 Description
Process definition registration has failed.
Parameters
%1: Process definition name
System processing
Processing is interrupted.
Cause
The reason for failure is described in the message displayed before this one.
Action method
Refer to the message displayed before this one and take the appropriate action.
FSP_SW/RB-A_BASE: ERROR: 02024:The parameter file syntax is invalid. Parameter file: %1 Description
The file format is invalid - "=" is missing between the UDA key and value described in the parameter file.
Parameters
%1: Parameter file name
System processing
Processing is interrupted.
Cause
"=" is missing between the UDA key and value described in the parameter file.
Action method
Correct the file.
FSP_SW/RB-A_BASE: ERROR: 02025:The specified extension is invalid. File:%1 Description
The specified extension is invalid.
- 36 -
Parameters
Specify parameter in message text.
%1:File name
System processing
Processing is interrupted.
Cause
The specified extension is invalid.
Action method
Specify correct extension file.
- If register and update automated operation group , specify extension bar file.
- If register and update process definition, specify extension xpdl file.
FSP_SW/RB-A_BASE: ERROR: 02026:Failed to obtain the specified process instance information.Process instance ID: %1 Description
Failed to obtain the specified process instance information.
Parameters
%1: Process instance ID
System processing
Processing is interrupted.
Cause
Failed to obtain the specified process instance information.
Action method
If the Systemwalker Runbook Automation Management Server is not running, then start it. Otherwise, collect investigation data usingthe iscollectinfo command, and contact Fujitsu technical support.
FSP_SW/RB-A_BASE: ERROR: 02027: The status of specified automated operation process group isDELETED or OFFLINE. Automated operation process group ID:%1 Description
The status of specified Automated Operation Process Group does not exist or is OFFLINE.
Parameters
Specify parameter in message text.
%1: Automated Operation Process Group ID
System processing
Processing is interrupted.
Cause
The status of specified Automated Operation Process Group does not exist or is OFFLINE.
- 37 -
Action method
Specify automated operation process ID as ONLINE state.
FSP_SW/RB-A_BASE: ERROR: 02028: The specified process instance ID format is invalid. Processinstance ID: %1 Description
The specified process instance ID format is invalid.
Parameters
%1: Process instance ID
System processing
Processing is interrupted.
Cause
The specified process instance ID string type is invalid, or ID value exceed a certain maximum value
Action method
Specify a valid process instance ID.
FSP_SW/RB-A_BASE: ERROR: 02029: Failed to obtain owner group. File: %1 Description
Failed to obtain an owner group.
Parameters
%1: File name
System processing
Processing is interrupted.
Cause
Failed to obtain an owner group.
Action method
No action is required.
FSP_SW/RB-A_BASE: ERROR: 02030: Failed to upload the specified BAR file. BAR file: %1 Description
BAR file upload has failed.
Parameters
%1: BAR file name
System processing
Processing is interrupted.
Cause
BAR file upload has failed.
- 38 -
User action
The file is invalid.
Disk space might be insufficient.
Ensure that the file has access permission.
FSP_SW/RB-A_BASE: ERROR: 02031:Failed to update the attribute file of the automated operationprocess group. Automated operation process group name: %1 Description
Failed to update the attribute file of the Automated Operation Process Group.
Parameters
%1: Automated Operation Process Group name
System processing
Processing is interrupted.
Cause
The reason for update attribute of Automated Operation Process Group failure is described in the message displayed before this one.
Action method
Refer to the message displayed before this one and take the appropriate action.
FSP_SW/RB-A_BASE: ERROR: 02032: Failed to extract the specified BAR file. BAR file: %1 Description
Failed to extract the specified BAR file.
Parameters
%1: BAR file name
System processing
Processing is interrupted.
Cause
The BAR file is invalid.
Disk space might be insufficient.
Ensure that the access permission of BAR file.
Action method
Specify correct BAR file and re-execute.
Confirm disk space and access permission.
FSP_SW/RB-A_BASE: ERROR: 02033:Failed to update the specified automated operation process group.Automated operation process group name: %1 Description
Failed to update the Automated Operation Process Group.
Parameters
%1: Automated Operation Process Group name
- 39 -
System processing
Processing is interrupted.
Cause
The reason for failure to update specified Automated Operation Process Group is described in the message displayed before this one.
Action method
Refer to the message displayed before this one and take the appropriate action.
FSP_SW/RB-A_BASE: ERROR: 02034: Failed to delete process instance. Process instance ID: %1 Description
Failed to delete the process instance.
Parameters
1%: Process instance ID
System processing
Processing is interrupted.
Cause
The process instance is in use.
Action method
Wait until deleting the process instance becomes possible, and retry.
FSP_SW/RB-A_BASE: ERROR: 02035: The specified version process definition has already been deleted.Process definition name: %1 Version: %2 Parameters
1%: Process definition name
2%: Version
System processing
Processing is interrupted.
Cause
The specified version process definition has already been deleted.
Action method
Specify an existing version of the process definition.
FSP_SW/RB-A_BASE: ERROR: 02036:The specified version process definition has already beenpublished. Process definition name: %1 Version: %2 Description
The specified version process definition has already been published. .
Parameters
1%: Process definition name
2%: Version
- 40 -
System processing
Processing is interrupted.
Cause
The specified version process definition has already been published.
Action method
Specify a process definition which is in Draft state.
FSP_SW/RB-A_BASE: ERROR: 02037: The specified version process definition does not exist. Processdefinition name: %1 Version: %2 Description
The specified version process definition does not exist.
Parameters
1%: Process definition name
2%: Version
System processing
Processing is interrupted.
Cause
The specified version process definition does not exist
Action method
Confirm as below.
- If permission for process definition starting is correct.
- If process definition no exist.
FSP_SW/RB-A_BASE: ERROR: 02038: The specified automated operation process group ID format isinvalid. Automated operation process group ID:%1 Description
The specified Automated Operation Process Group ID format is invalid.
Parameters
1%: Process definition name
System processing
Processing is interrupted.
Cause
The specified Automated Operation Process Group ID is invalid format.
Action method
Specify correct process group ID.
FSP_SW/RB-A_BASE: ERROR: 02039:The specified process definition UDA type is not STRING. Processdefinition name:%1
- 41 -
Description
The specified process definition UDA type is not STRING.
Parameters
1%: Process definition name
System processing
Processing is interrupted.
Cause
The specified process definition UDA type is not STRING.
Action method
Specify process definition in UDA type process definition
FSP_SW/RB-A_BASE:INFO: 02040: The event notify command has completed normally. Description
The command has completed.
System processing
The command has completed.
FSP_SW/RB-A_BASE:ERROR: 02041: The event notify command has terminated abnormally. Description
An error occurred while running the command.
System processing
Processing is interrupted.
Action method
Check the error details and take the appropriate action.
FSP_SW/RB-A_BASE:ERROR: 02042: The specified %1 has exceeded the maximum length. %1: %2 Description
The option value exceeds the maximum length.
Parameters
%1: Option name
%2: Option value
System processing
Processing is interrupted.
Cause
The option value exceeds the maximum length.
Action method
Confirm the maximum length for the option.
msgID length: 1 to 250
- 42 -
host length: 1 to 250
comment length: 1 to 300
FSP_SW/RB-A_BASE:ERROR: 02043: User %1 has not be able to start process instance by processdefinition (Name= %2, Version= %3). Process instance is able to start by only published or draft statusof process definition. Description
Not start specified process definition.
Parameters
%1: User who execute command.
%2: Process definition name
%3: version
System processing
Processing is interrupted.
Cause
Specified process definition status is release or draft..
Action method
Specify process definition status as draft or published
FSP_SW/RB-A_BASE:ERROR: 02044: User %1 is not an owner of process definition, so user %1 has notbe able to start process instance by process definition (Name=%2, Version= %3, Owner= %4). Description
Failed to start process definition.
Parameters
%1: User who execute command.
%2: Process definition name
%3: version
%4: Process definition owner
System processing
Processing is interrupted.
Cause
User specified parameter is not process definition owner.
Action method
Specify process definition owner as parameter.
FSP_SW/RB-A_BASE:ERROR: 02045: The published or draft status of process definition does not exist.Process definition name: %1 Description
The published or draft status of process definition does not exist.
- 43 -
Parameters
%1: Process definition name
System processing
Processing is interrupted.
Cause
The published or draft status of process definition does not exist.
Action method
Specify the published or draft status of process definition.
FSP_SW/RB-A_BASE:ERROR: 02046: User %1 is not an owner of process definition, so user %1 has notbe able to start process instance by process definition. Process definition name: %2 Description
Failed to start process instance
Parameters
%1 User who execute command
%2: Process definition name
System processing
Processing is interrupted.
Cause
The user who executes command is not owner of process definition.
Action method
Specify the process definition owned by user who execute command
FSP_SW/RB-A_BASE: ERROR: 02047: The command is already running. Description
The swrba_audit command is already running.
System processing
Processing is interrupted.
Cause
Multiple instances of the swrba audit command cannot be executed.
Action method
Wait for the command to finish and re-execute.
System Administrator action
None.
FSP_SW/RB-A_BASE: ERROR: 02048: Failed to manipulate the audit information file. File: %1
- 44 -
Description
The monitoring information file operation failed and monitoring information can not be output.
Parameters
%1: File name
System processing
Processing is interrupted.
Cause
The file operation failed.
Action method
Check the file privileges.
System Administrator action
None.
FSP_SW/RB-A_BASE: ERROR: 02049: Failed to obtain the date and time when the previous search wasexecuted. Description
Failed to obtain the date/time of the previous search.
System processing
Processing is interrupted.
Cause
Failed to load the file in which the date/time of the previous command execution is recorded.
Action method
Check the file privileges.
System Administrator action
Contact Fujitsu technical support.
FSP_SW/RB-A_BASE: ERROR: 02050: Failed to obtain audit information for the process instance. Description
Failed to get the process instance audit information.
System processing
Processing is interrupted.
Cause
Failed to get the process instance audit information.
Action method
None.
System Administrator action
Contact Fujitsu technical support.
- 45 -
FSP_SW/RB-A_BASE: ERROR: 02051: Failed to save the date and time when the command was executed. Description
Failed to save the date/time for when the command was executed.
System processing
Processing is interrupted.
Cause
The write to file operation failed.
Action method
Check the file privileges.
System Administrator action
Contact Fujitsu technical support.
FSP_SW/RB-A_BASE: INFO: 02052: There are no target process instances. Description
There was no output target process instance.
System processing
No process instance audit information is output to the process instance audit information file.
Additionally, if there is no process instance audit information file, a process instance audit information file will not be created.
Cause
This is a progress message.
Action method
This is a progress message. No action is required.
FSP_SW/RB-A_BASE: INFO: 02053:You do not have permission to start the specified ProcessDefinition. Description
Specified user does not have permission to start process instance from the specified Process Definition.
Parameters
1%: The user who started process instance
2%: Process definition name
System processing
Processing is interrupted.
Cause
Specified user do not have permission to start process instance from the specified Process Definition.
Action method
Specify a user who has permission to start process definition as a start user, and execute the command again.
- 46 -
FSP_SW/RB-A_BASE: ERROR: 03001: Failed to open message catalog. : PROCESSID=%d1 ACTIVITYID=%d2 DETAIL=%s3 Description
Failed to open a message catalog.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Error detail
System processing
Changes the Automated Operation Process to aborted status. 202 Return Values of operation component is output.
Action method
There is something wrong with Management Server environment.
Collect investigation data using the iscollectinfo command, and contact Fujitsu technical support.
FSP_SW/RB-A_BASE: ERROR: 03002: Message ID does not exist. : PROCESSID=%d1 ACTIVITYID=%d2MSGID=%d3 Description
The message is not found.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%d3: Message ID
System processing
Changes the Automated Operation Process to aborted status. 202 Return Values of operation component is output.
Action method
There is something wrong with Management Server environment.
Collect investigation data using the iscollectinfo command, and contact Fujitsu technical support.
FSP_SW/RB-A_BASE: ERROR: 03003: Failed to output message. : PROCESSID=%d1 ACTIVITYID=%d2MSGID=%d3 DETAIL=%s4 Description
Failed to output a message.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%d3: Message ID
%s4: Error detail
- 47 -
System processing
Changes the Automated Operation Process to aborted status. 202 Return Values of operation component is output.
Action method
There is something wrong with Management Server environment.
Collect investigation data using the iscollectinfo command, and contact Fujitsu technical support.
FSP_SW/RB-A_BASE: ERROR: 03004: System error. : PROCESSID=%d1 ACTIVITYID=%d2 DETAIL=%s3 Description
An internal error has occurred.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Error detail
System processing
Changes the Automated Operation Process to aborted status. 202 Return Values of operation component is output.
Action method
There is something wrong with Management Server environment.
Collect investigation data using the iscollectinfo command, and contact Fujitsu technical support.
FSP_SW/RB-A_BASE: ERROR: 03005: Failed to access workflow control server. : PROCESSID=%d1ACTIVITYID=%d2 DETAIL=%s3 Description
An error has occurred on the Management Server.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Error detail
System processing
Changes the Automated Operation Process to aborted status. 202 or 203 Return Values of operation component is output.
If this message is output because of insufficient virtual memory, the Automated Operation Process may continue processing, and avalue other than 202 or 203 may be output as the operation component return value.
Action method
- Interstage Business Process Manager service may be stopped. Execute swrba_start command. For the detail of swrba_startcommand, Refer to Systemwalker Runbook Automation Reference Guide.
- The virtual memory of the Management Server may be insufficient. Check that sufficient capacity has been reserved on the diskallocated for virtual memory.
If virtual memory is insufficient, the following message may be output to the event log or system log:
ISJEE: WARNING: ISJEE_OM3204: Alert monitoring function was detected the alert. CLUSTER={0} INSTANCE={1}MESSAGE={2}
Refer to the error detail (%s3) and eliminate the cause of the failure.
- 48 -
If the error cause could not be determined, collect investigation data using the iscollectinfo command, and contact Fujitsu technicalsupport.
FSP_SW/RB-A_BASE: ERROR: 03006: Failed to access runbook automation server. : PROCESSID=%d1ACTIVITYID=%d2 DETAIL=%s3 Description
An error has occurred on the Management Server.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Error detail
System processing
Changes the Automated Operation Process to aborted status. 202 or 203 Return Values of operation component is output.
Action method
There is something wrong with Management Server environment.
Collect investigation data using the iscollectinfo command, and contact Fujitsu technical support.
FSP_SW/RB-A_BASE: WARNING: 03007: The content of the operation component executionconfiguration file is incorrect. : PROCESSID=%d1 ACTIVITYID=%d2 FILE=%s3 KEY=%s4 VALUE=%s5 Description
An invalid value was specified in the operation component execution configuration file.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Configuration file name
%s4: Key name
%s5: Specified value
System processing
Automated Operation Process continues using a default value.
Action method
Update the key's value.
FSP_SW/RB-A_BASE: ERROR: 03008: Failed to access CMDB. : PROCESSID=%d1 ACTIVITYID=%d2HOST=%s3 DETAIL=%s4 Description
Failed to access CMDB.
Parameters
%d1: Process Instance ID
%d2: Activity ID
- 49 -
%s3: Host name
%s4: Error detail
System processing
Changes the Automated Operation Process to aborted status. 202 Return Values of operation component is output.
Action method
- CMDB service may be stopped.Execute swrba_start command. For the detail of swrba_start command, Refer to Systemwalker Runbook Automation ReferenceGuide.
- If the name of the host executing the operation component is stated in "hostname" of that operation component and " The CMDBis in an ambiguous state. There are too many LogicalServers. " is output in the detailed error messages, it is possible that multiplelogical nodes with the same host name are registered in the Configuration Management Database (CMDB).Delete the logical node information for the same host name from the Configuration Management Database (CMDB). Alternatively,enter the IP address on which the operation component is executed into the "hostname" of the operation component. Refer to theSystemwalker Runbook Automation Operation Guide for information on deleting the configuration information.
Refer to the error detail (%s4) and eliminate the cause of the failure.
If the error cause could not be determined, collect investigation data using the iscollectinfo command, and contact Fujitsu technicalsupport.
FSP_SW/RB-A_BASE: ERROR: 03009: Failed to request operation parts execution. : PROCESSID=%d1ACTIVITYID=%d2 DETAIL=%s3 Description
Requesting operation component execution has failed.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Error detail
System processing
Changes the Automated Operation Process to error status. 202 Return Values of operation component is output.
Action method
An error might have occurred in the connection to the message broker.
If "MQJMSRA" or "IJMQ" is included in the error detail, refer to Interstage Application Server Messages.
If the error cause could not be determined, collect investigation data using the iscollectinfo command, and contact Fujitsu technicalsupport.
FSP_SW/RB-A_BASE: ERROR: 03010: Cannot find specified UDA/SLIP element. : PROCESSID=%d1ACTIVITYID=%d2 kind=%s3 NAME=%s4 ASSIGN=%s5 Description
The UDA or form element does not exist.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Parameter kind
- 50 -
- uda: UDA
%s4: Parameter name for the operation component
%s5: Destination name
System processing
Changes the Automated Operation Process to error status. 202 Return Values of operation component is output.
Action method
In process definition, UDA which specified Parameter for the operation component not exist.
Update the process definition to fix the parameter specified for the operation component.
FSP_SW/RB-A_BASE: ERROR: 03011: Cannot find specified operation parts. : PROCESSID=%d1ACTIVITYID=%d2 NAME=%s3 Description
The operation component cannot be found.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: operation component name
System processing
Changes the Automated Operation Process to error status. 202 Return Values of operation component is output.
Action method
Operation components which using in Automated operation Process does not regist in Management Server. If this message is outputin self-made operation components, register the operation components.
If this message is output in provided operation components, collect investigation data using the iscollectinfo command, and contactFujitsu technical support.
FSP_SW/RB-A_BASE: ERROR: 03012: Cannot set data because data is exceeds the limit. : PROCESSID=%d1 ACTIVITYID=%d2 NAME=%s3 NOW=%d4 LIMIT=%d5 Description
The data length exceeds the limit defined for the operation component parameter.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Parameter name for the operation component
%d4: Current data value
%d5: Maximum value
System processing
Changes the Automated Operation Process to error status. 205 or 206 Return Values of operation component is output.
Action method
The string data length exceeds the limit defined for the operation component parameter.
- 51 -
Update the process definition to correct the parameter specified for the operation component.
FSP_SW/RB-A_BASE: ERROR: 03013: I/O error. : PROCESSID=%d1 ACTIVITYID=%d2 PATH=%s3DETAIL=%s4 Description
An I/O error occurred.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: operation component name
%s4: Error detail
System processing
Changes the Automated Operation Process to aborted status. 202 or 203 Return Values of operation component is output.
Action method
Refer to the error detail (%s4) and eliminate the cause of the failure.
If the error cause could not be determined, collect investigation data using the iscollectinfo command, and contact Fujitsu technicalsupport.
FSP_SW/RB-A_BASE: ERROR: 03014: Failed to execute operation parts. : PROCESSID=%d1ACTIVITYID=%d2 NAME=%s3 DETAIL=%s4 Description
Failed to run the operation component.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: operation component name
%s4: Error detail
System processing
Changes the Automated Operation Process to aborted status. 202 or 203 Return Values of Operation component is output.
Action method
Refer to the error detail (%s4) and eliminate the cause of the failure.
If the error cause could not be determined, collect investigation data using the iscollectinfo command, and contact Fujitsu technicalsupport.
FSP_SW/RB-A_BASE: ERROR: 03015: Error on operation parts execution. : PROCESSID=%d1ACTIVITYID=%d2 NAME=%s3 DETAIL=%s4 Description
An error occurred while running the operation component.
Parameters
%d1: Process Instance ID
- 52 -
%d2: Activity ID
%s3: operation component name
%s4: Error detail
System processing
Changes the Automated Operation Process to aborted status. 202 Return Values of operation component is output.
Action method
Refer to the error detail (%s4) and eliminate the cause of the failure.
If the error cause could not be determined, collect investigation data using the iscollectinfo command, and contact Fujitsu technicalsupport.
FSP_SW/RB-A_BASE: WARNING: 03016: Failed to backup result of operation parts. : PROCESSID=%d1ACTIVITYID=%d2 DETAIL=%s3 Description
Failed to backup the result of the operation component.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Error detail
System processing
Automated operation Processing continues.
Action method
Refer to the error detail (%s3) and eliminate the cause of the failure.
If the error cause could not be determined, collect investigation data using the iscollectinfo command, and contact Fujitsu technicalsupport.
FSP_SW/RB-A_BASE: WARNING: 03017: Operation parts execution is timeout. : PROCESSID=%d1ACTIVITYID=%d2 NAME=%s3 Description
Timeout occurred while running the operation component.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: operation component name
System processing
Automated Operation Process continues. 201 Return Values of operation component is output.
Action method
The Business Server or the network might be overloaded.
Modify the timeout value specified for the operation components parameter.
- 53 -
FSP_SW/RB-A_BASE: WARNING: 03018: Retry count exceeded limit the number of operation parts run. :PROCESSID=%d1 ACTIVITYID=%d2 NAME=%s3 COUNT=%d4 Description
The retry limit for operations parts run was exceeded.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: operation component name
%d4: Retry count
System processing
Automated Operation Process continues. From 161 to 170 Return Values of operation component is output
Action method
The Business Server or the network might be overloaded.
Modify the maximum retry count specified for the operation parts parameter.
FSP_SW/RB-A_BASE: ERROR: 03019: Failed to decrypt password. : PROCESSID=%d1 ACTIVITYID=%d2 Description
Password decryption has failed.
Parameters
%d1: Process Instance ID
%d2: Activity ID
System processing
Changes the Automated Operation Process to aborted status. 202 or 203 Return Values of Operation component is output.
Action method
Collect investigation data using the iscollectinfo command, and contact Fujitsu technical support.
FSP_SW/RB-A_BASE: ERROR: 03020: Failed to convert the operation component input informationvariable parameter. : PROCESSID=%d1 ACTIVITYID=%d2 NAME=%s3 VALUE=%s4 DETAIL=%s5 Description
Failed to replace the specified variable parameter.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Parameter name for the operation component
%s4: Parameter value for the operation component
%s5: Detailed information
System processing
Changes the Automated Operation Process to error status. 205 Return Values of operation component is output.
- 54 -
Action method
Update the process definition to correct the parameter specified for the operation component.
FSP_SW/RB-A_BASE: ERROR: 03021: A mandatory parameter for the operation component input hasnot been specified. : PROCESSID=%d1 ACTIVITYID=%d2 NAME=%s3 Description
The required parameter for the operation component was not specified.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Parameter name for the operation component
System processing
Changes the Automated Operation Process to error status. 205 Return Values of operation component is output.
Action method
The required parameter for the operation component was not specified.
Update the process definition to correct the parameter specified for the operation component.
FSP_SW/RB-A_BASE: ERROR: 03022: The operation component input parameter types do not match. :PROCESSID=%d1 ACTIVITYID=%d2 NAME=%s3 DETAIL=%s4 Description
Parameter type for the operation component is inconsistent.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Parameter name for the operation component
%s4: Detailed information
System processing
Changes the Automated Operation Process to error status. 205 or 206 Return Values of operation component is output.
Action method
The UDA type specified in I/O information of Operation component is incorrect.
Update the process definition to correct the parameter specified for the operation parts.
FSP_SW/RB-A_BASE: ERROR: 03023: Cannot find operation component execution setup file. :PROCESSID=%d1 ACTIVITYID=%d2 PATH=%s3 Description
The operation component configuration file is not found.
Parameters
%d1: Process Instance ID
%d2: Activity ID
- 55 -
%s3: operation component configuration file
System processing
Changes the Automated Operation Process to aborted status. 204 Return Values of operation component is output.
Action method
Ensure that the operation component configuration file (rb.xml or pl.xml) exists.
Contact Fujitsu technical support, when:
- This message appears but the operation component configuration file exists.
- The operation component configuration file does not exist.
FSP_SW/RB-A_BASE: ERROR: 03024: The operation component execution setup file format isincorrect. : PROCESSID=%d1 ACTIVITYID=%d2 DETAIL=%s3 Description
There is an error in the operation component configuration file.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Detailed information
System processing
Changes the Automated Operation Process to aborted status. 204 Return Values of operation component is output.
Action method
The format of the operation component configuration file is incorrect.
Modify the operation component configuration file by referring to detail information specified %s3
FSP_SW/RB-A_BASE: ERROR: 03025: Cannot find the file that executes the operation component. :PROCESSID=%d1 ACTIVITYID=%d2 PATH=%s3 Description
The executable file, which runs the operation component, cannot be found.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Path of the executable file that runs the operation component
System processing
Changes the Automated Operation Process to aborted status. 204 Return Values of operation component is output.
Action method
The format of the operation component configuration file is incorrect.
Ensure that the executable command specified in command tag of operation component configuration file exists.
- 56 -
FSP_SW/RB-A_BASE: ERROR: 03026: The execution command specified in the operation componentexecution setup file has exceeded its length limit. : PROCESSID=%d1 ACTIVITYID=%d2 DETAIL=%s3 Description
The command tag size limit was exceeded.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Detailed information
System processing
Changes the Automated Operation Process to aborted status. 204 Return Values of operation component is output.
Action method
The format of the operation component configuration file is incorrect.
Correct the string specified in the command tag in the operation component configuration file.
FSP_SW/RB-A_BASE: ERROR: 03027: Control characters have been used in the execution command inthe operation component execution setup file. : PROCESSID=%d1 ACTIVITYID=%d2 DETAIL=%s3 Description
A control character was used in the tag value.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Detailed information
System processing
Changes the Automated Operation Process to aborted status. 204 Return Values of operation component is output.
Action method
The format of the operation component configuration file is incorrect.
Ensure that the value specified in the tag in the operation component configuration file does not contain control characters.
FSP_SW/RB-A_BASE: ERROR: 03028: The execution command path in the operation componentexecution setup file does not exist. : PROCESSID=%d1 ACTIVITYID=%d2 DETAIL=%s3 Description
The executable program path does not exist.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Detailed information
System processing
Changes the Automated Operation Process to aborted status. 204 Return Values of operation component is output.
- 57 -
Action method
The format of the operation component configuration file is incorrect.
Ensure that the path specified in the tag in the operation component configuration file exists.
FSP_SW/RB-A_BASE: ERROR: 03029: The working directory path in the operation component executionsetup file does not exist. : PROCESSID=%d1 ACTIVITYID=%d2 DETAIL=%s3 Description
The directory specified in the tag does not exist.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Detailed information
System processing
Changes the Automated Operation Process to aborted status. 204 Return Values of operation component is output.
Action method
The format of the operation component configuration file is incorrect.
Ensure that the path specified in the tag in the operation component absolute path name.
FSP_SW/RB-A_BASE: ERROR: 03030: The working directory in the operation component executionsetup file does not exist. : PROCESSID=%d1 ACTIVITYID=%d2 DETAIL=%s3 Description
The directory specified in the tag does not exist.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Detailed information
System processing
Changes the Automated Operation Process to aborted status. 204 Return Values of operation component is output.
Action method
The format of the operation component configuration file is incorrect.
Ensure that the path specified in the tag in the operation component configuration file exists.
FSP_SW/RB-A_BASE: ERROR: 03031: The working directory in the operation component executionsetup file has exceeded its length limit. : PROCESSID=%d1 ACTIVITYID=%d2 DETAIL=%s3 Description
The directory name exceeds the size limit.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Detailed information
- 58 -
System processing
Changes the Automated Operation Process to aborted status. 204 Return Values of operation component is output.
Action method
The format of the operation component configuration file is incorrect.
Ensure that the value specified in the tag in the operation component configuration file has a valid length.
FSP_SW/RB-A_BASE: ERROR: 03032: Control characters have been used in the working directory in theoperation component execution setup file. : PROCESSID=%d1 ACTIVITYID=%d2 DETAIL=%s3 Description
A control character was used in the tag value.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Detailed information
System processing
Changes the Automated Operation Process to aborted status. 204 Return Values of operation component is output.
Action method
The format of the operation component configuration file is incorrect.
Ensure that the value specified in the tag in the operation component configuration file does not contain control characters.
FSP_SW/RB-A_BASE: ERROR: 03033: Control characters have been used in the parameter in theoperation component execution setup file. : PROCESSID=%d1 ACTIVITYID=%d2 DETAIL=%s3 Description
A control character was used in the tag value.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Detailed information
System processing
Changes the Automated Operation Process to aborted status. 204 Return Values of operation component is output.
Action method
The format of the operation component configuration file is incorrect.
Ensure that the value specified in the tag in the operation component configuration file does not contain control characters.
FSP_SW/RB-A_BASE: ERROR: 03034: Total size of parameters specified in the operation componentexecution setup file has exceeded its limit. : PROCESSID=%d1 ACTIVITYID=%d2 DETAIL=%s3 Description
The number of characters specified in the parameter has exceeded the maximum length that can be specified.
- 59 -
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Detailed information
System processing
Changes the Automated Operation Process to aborted status. 204 Return Values of operation component is output.
Action method
The format of the operation component configuration file is incorrect.
Ensure that the value specified in the tag in the operation component configuration file has a valid length.
FSP_SW/RB-A_BASE: ERROR: 03035: The environment variable name specified in the operationcomponent execution setup file has exceeded its length limit. : PROCESSID=%d1 ACTIVITYID=%d2DETAIL=%s3 Description
The environment variable exceeds the size limit.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Detailed information
System processing
Changes the Automated Operation Process to aborted status. 204 Return Values of operation component is output.
Action method
The format of the operation component configuration file is incorrect.
Ensure that the value specified in the environment tag in the operation component configuration file has a valid length.
FSP_SW/RB-A_BASE: ERROR: 03036: The environment variable name specified in the operationcomponent execution setup file is incorrect. : PROCESSID=%d1 ACTIVITYID=%d2 DETAIL=%s3 Description
There is an error in the environment variable.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Detailed information
System processing
Changes the Automated Operation Process to aborted status. 204 Return Values of operation components is output.
Action method
The format of the operation component configuration file is incorrect.
Ensure that a valid environment variable is specified in the environment tag in the operation component configuration file.
- 60 -
FSP_SW/RB-A_BASE: ERROR: 03037: Control characters have been used in the environment variablename in the operation component execution setup file. : PROCESSID=%d1 ACTIVITYID=%d2 DETAIL=%s3 Description
A control character was used in the environment variable name.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Detailed information
System processing
Changes the Automated Operation Process to aborted status. 204 Return Values of operation components is output.
Action method
The format of the operation component configuration file is incorrect.
Ensure that the environment variable's name specified in the environment tag in the operation component configuration file does notcontain control characters.
FSP_SW/RB-A_BASE: ERROR: 03038: Control characters have been used in the environment variablevalue in the operation component execution setup file. : PROCESSID=%d1 ACTIVITYID=%d2 DETAIL=%s3 Description
A control character was used in the environment variable value.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Detailed information
System processing
Changes the Automated Operation Process to aborted status. 204 Return Values of operation component is output.
Action method
The format of the operation component configuration file is incorrect.
Ensure that the environment variable's value specified in the environment tag in the operation component configuration file does notcontain control characters.
FSP_SW/RB-A_BASE: ERROR: 03039: Total size of environment variable values in the operationcomponent execution setup file has exceeded its limit. : PROCESSID=%d1 ACTIVITYID=%d2 DETAIL=%s3 Description
The environment variable's value exceeds the size limit.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Detailed information
- 61 -
System processing
Changes the Automated Operation Process to aborted status. 204 Return Values of operation component is output.
Action method
The format of the operation component configuration file is incorrect.
Ensure that the environment variable's value specified in the environment tag in the operation component configuration file has a validlength.
FSP_SW/RB-A_BASE: ERROR: 03040: The environment variable value (path) in the operation componentexecution setup file has exceeded its length limit. : PROCESSID=%d1 ACTIVITYID=%d2 DETAIL=%s3 Description
The path specified in the environment variable exceeds the size limit.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Detailed information
System processing
Changes the Automated Operation Process to aborted status. 204 Return Values of operation component is output.
Action method
The format of the operation component configuration file is incorrect.
Ensure that the path specified in the environment tag in the operation component configuration file has a valid length.
FSP_SW/RB-A_BASE: ERROR: 03041: Total size of environment variable name and value in the operationcomponent execution setup file has exceeded its limit. : PROCESSID=%d1 ACTIVITYID=%d2 DETAIL=%s3 Description
The environment variable name plus its value exceeds the size limit.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Detailed information
System processing
Changes the Automated Operation Process to aborted status. 204 Return Values of operation components is output.
Action method
The format of the operation component configuration file is incorrect.
Ensure that the environment variable's name plus its value specified in the environment tag in the operation component configurationfile has a valid length.
FSP_SW/RB-A_BASE: ERROR: 03042: The environment variable name in the operation componentexecution setup file is duplicated. : PROCESSID=%d1 ACTIVITYID=%d2 DETAIL=%s3
- 62 -
Description
A duplicate environment variable is specified.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Detailed information
System processing
Changes the Automated Operation Process to aborted status. 204 Return Values of operation component is output.
Action method
The format of the operation component configuration file is incorrect.
Ensure that the environment variable specified in the environment tag in the operation component configuration file is not duplicated.
FSP_SW/RB-A_BASE: ERROR: 03043: The environment variable in the operation component executionsetup file contains a circular reference. : PROCESSID=%d1 ACTIVITYID=%d2 DETAIL=%s3 Description
The environment variable creates a circular reference.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Detailed information
System processing
Changes the Automated Operation Process to aborted status. 204 Return Values of operation component is output.
Action method
The format of the operation component configuration file is incorrect.
Ensure that the environment variable specified in the environment tag in the operation component configuration file does not create acircular reference.
FSP_SW/RB-A_BASE: WARNING: 03044: Failed to record the execution status of the operation activity. :PROCESSID=%d1 ACTIVITYID=%d2 DETAIL=%s3 Description
Failed to record the operation component runtime log.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: Detailed information
System processing
Automated Operation Process continues.
- 63 -
Action method
Confirm the operation component execution result, collect investigation data using the iscollectinfo command, and contact Fujitsutechnical support.
Note that the operation component execution result can be displayed in the Web Console by selecting Process Management >Process, then selecting the automated operation process in the list and then selecting BPMN tab.
FSP_SW/RB-A_BASE: WARNING: 03045: Failed to read the operation component executionconfiguration file. : PROCESSID=%d1 ACTIVITYID=%d2 FILE=%s3 DETAIL=%s4 Description
Failed to load the operation component execution configuration file.
Parameters
%d1: Process Instance ID
%d2: Activity ID
%s3: File name
%s4: Detailed information
System processing
Automated Operation Process continues using a default value.
Action method
Ensure that the operation component execution configuration file (opecnfig.properties) exists.
Contact Fujitsu technical support, when:
- This message appears but the operation component execution configuration file exists.
- The operation component execution configuration file does not exist.
FSP_SW/RB-A_BASE: ERROR: 03046: The operation component node could not be resumed. :PROCESSID=%d1 ACTIVITYID=%d2 Description
Failed to recover operation component node.
Parameters
%d1: Process Instance ID
%d2: Activity ID
System processing
Changes the Automated Operation Process to aborted status. 208 Return Values of operation component is output.
Automated Operation Process may not be done normally.
Action method
If Automated Operation Process is done normally, restart Automated Operation Process again.
FSP_SW/RB-A_BASE: ERROR: 03047: The number of values specified for a parameter in an operationcomponent has exceeded the maximum limit. : PROCESSID=%d1 ACTIVITYID=%d2 NAME=%s3 NOW=%d4 LIMIT=%d5
- 64 -
Description
Multiple parameters were specified for the operation component, and one of the input parameters input has exceeded the upper limitthat can be specified.
Parameters
%d1: Process instance ID
%d2: Activity ID
%s3: Name of the operation component input parameter
%d4: Current value
%d5: Limit
System processing
Changes the Automated Operation Process to error status. 205 or 206 is output as the operation component return value.
Action method
The parameters specified in the operation component have exceeded the maximum number of characters that can be specified.
Review the process definition, and check that the number of parameters specified has not exceeded the upper limit that can be specified.
FSP_SW/RB-A_BASE: ERROR: 03048: The format for specifying multiple values for a parameter in anoperation component is invalid. : PROCESSID=%d1 ACTIVITYID=%d2 NAME=%s3 Description
The input format of one of the parameters that was specified for the operation component is invalid.
Parameters
%d1: Process instance ID
%d2: Activity ID
%s3: Name of the operation component input parameter
System processing
Changes the Automated Operation Process to error status. 205 or 206 is output as the operation component return value.
Action method
The input format of one of the parameters that was specified for the operation component is invalid.
Review the process definition, and confirm whether the parameter follows the constraint that must be followed when multiple inputparameters are specified.
FSP_SW/RB-A_BASE: ERROR: 03049: The number of parameters specified for a parameter in anoperation component is invalid. : PROCESSID=%d1 ACTIVITYID=%d2 NAME=%s3 Description
The number of parameters specified for the operation component is incorrect.
Parameters
%d1: Process instance ID
%d2: Activity ID
%s3: Name of the operation component input parameter
- 65 -
System processing
Changes the Automated Operation Process to error status. 205 or 206 is output as the operation component return value.
Action method
The number of parameters specified for the operation component is incorrect.
Review the process definition, and confirm whether the parameter follows the constraint that must be followed when multiple inputparameters are specified.
FSP_SW/RB-A_BASE: INFO: 03050: Execution of the operation component is about to start. :PROCESSID=%d1 ACTIVITYID=%d2 NAME=%s3 Description
Operation component execution has started.
Parameters
%d1: Process instance ID
%d2: Activity ID
%s3: operation component name
System processing
Starts operation component execution.
Cause
This is a progress message.
Action method
This is a progress message. No action is required.
FSP_SW/RB-A_BASE: INFO: 03051: Execution of the operation component has finished. : PROCESSID=%d1 ACTIVITYID=%d2 NAME=%s3 Description
Operation component execution has ended.
Parameters
%d1: Process instance ID
%d2: Activity ID
%s3: operation component name
System processing
Ends operation component execution.
Cause
This is a progress message.
Action method
This is a progress message. No action is required.
FSP_SW/RB-A_BASE: INFO: 03052: Filtering is about to start. : PROCESSID=%d1 ACTIVITYID=%d2NAME=%s3 FILTER=%s4
- 66 -
Description
Filtering of the operation component execution results has started.
Parameters
%d1: Process instance ID
%d2: Activity ID
%s3: operation component name
%s4: Filter definition
System processing
Starts filtering processing.
Cause
This is a progress message.
Action method
This is a progress message. No action is required.
FSP_SW/RB-A_BASE: INFO: 03053: Filtering has finished. : PROCESSID=%d1 ACTIVITYID=%d2 NAME=%s3 FILTER=%s4 Description
Filtering of the operation component execution results has been completed.
Parameters
%d1: Process instance ID
%d2: Activity ID
%s3: operation component name
%s4: Filter definition
System processing
Ends filtering processing.
Cause
This is a progress message.
Action method
This is a progress message. No action is required.
FSP_SW/RB-A_BASE: ERROR: 03054: Filtering failed. : PROCESSID=%d1 ACTIVITYID=%d2 NAME=%s3OUTPUT=%s4 FILTER=%s5 DETAIL=%s6 Description
Filtering of the operation component execution results has failed.
Parameters
%d1: Process instance ID
%d2: Activity ID
%s3: operation component name
%s4: Filter output destination
%s5: Filter definition
- 67 -
%s6: Detailed information
System processing
Changes the Automated operation Process to error status.
The operation component output results are not filtered.
Cause
Filtering processing ended abnormally.
Action method
Refer to the detailed information shown in %s6 and remove the cause of the error.
FSP_SW/RB-A_BASE: ERROR: 03055: The volume of data stored in the execution results has exceededthe upper limit: PROCESSID=%d1 ACTIVITYID=%d2 NAME=%s3 RESULT=%s4 Description
The volume of data stored in the execution result has exceeded the upper limit.
Parameters
%d1: Process instance ID
%d2: Activity ID
%s3: operation component name
%s4: Name of execution result
System processing
Changes the Automated Operation Process to error status.
Cause
The volume of data stored in the execution result has exceeded the upper limit, therefore the Automated Operation Process is changedto error status.
Action method
Reduce the volume of data that is output from the operation component.
FSP_SW/RB-A_BASE: ERROR: 03056: The input parameter for the operation component contains a linefeed.: PROCESSID=%d1 ACTIVITYID=%d2 NAME=%s3 Description
A parameter specified in the operation component contains a line feed.
Parameters
%d1: Process instance ID
%d2: Activity ID
%s3: Operation component parameter name
System processing
Changes the Automated Operation Process to error status.
Cause
The string that was specified contains a line feed, even though it cannot be used in this parameter.
- 68 -
Action method
Review the process definition and check whether the parameter that was specified contains a line feed.
Additionally, check whether a line feed can be used in this parameter.
FSP_SW/RB-A_BASE: INFO: 04001: swrba_schedule_exit:SUCCESS[%1](AppId:%2 PdName:%3ProcessID:%4 ) Description
Command has been finished normally.
Parameters
%1: Return code
%2: Automated Operation Process Group ID
%3: Process definition name
%4: Process ID
System processing
Processing has been finished normally.
Action method
This is passing message. You do not need to action.
FSP_SW/RB-A_BASE: ERROR: 04002: swrba_schedule_exit:FAILURE[1]:Parameter error.Usage:swrba_schedule_exit -appid AutomatedOperationProcessGroupID -sdnameScheduleDefinitionName Description
Parameter error.
System processing
Abort processing
Action method
Check specified parameter.
FSP_SW/RB-A_BASE: ERROR: 04003: swrba_schedule_exit:FAILURE[3]:Check specified processdefinition.(AppId:%1 PdName:%2) Description
Process definition for started object does not exist.
Parameters
%1: Specified Automated Operation Process Group ID
%2: Specified Process definition name
System processing
Abort processing
Causes
- The process definition specified as a stated object does not exist.
- Specified process group is not ONLINE.
- 69 -
Action method
Specify process definition of version which existed.
FSP_SW/RB-A_BASE: ERROR: 04004: swrba_schedule_exit:FAILURE[5]:Check the executionprivileges.(AppId:%1 PdName:%2 UserId:%3) Description
No authority to execute specified option.
Parameters
%1: Automated Operation Process Group ID
%2: Specified Process definition name
%3: User ID
System processing
Abort to execute command
Causes
No authority to execute specified user in user.
Specified process definition is draft status.
Action method
Specify user having authority.
Start by user who have process definition owner authority.
FSP_SW/RB-A_BASE: ERROR: 04005: swrba_schedule_exit:FAILURE[%1]:Internal error.(AppId:%2SdName:%3 Datail:%4) Description
Internal error occurred.
Parameters
%1: Return code
%2: Automated Operation Process Group ID
%3: Schedule Definition name
%4: Detailed error information
System processing
Abort to execute command.
Causes
Internal error occurred.
Action method
Contact Fujitsu technical support.
FSP_SW/RB-A_BASE: ERROR: 04006: swrba_schedule_exit:FAILURE[2]:Failed to connect to BPM. Description
Failed to connect with BPM
- 70 -
System processing
Abort to execute command.
Causes
Failed to connect with BPM.
Action method
Confirm that Systemwalker Runbook Automation has been started.
If Systemwalker Runbook Automation has been started and this message is output, Contact Fujitsu technical support.
FSP_SW/RB-A_BASE: ERROR: 04007: swrba_schedule_exit:FAILURE[2]: The UDA specified in theschedule definition file does not exist in the process definition. PdName: %1 SdName: %2 Description
Failed to set UDA
Parameters
%1: Process definition name
%2: Schedule Definition name
System processing
Abort to execute command
Causes
UDA key set in Schedule Definition does not set in process definition.
Action method
Modify UDA key set in Schedule Definition, or set UDA key in process definition.
FSP_SW/RB-A_BASE: ERROR: 04101: Failed to start automated operation process by scheduling. Description
Failed to execute automated operation process in the following started.
- Auto execution according to Schedule Definition
- Start directory from Schedule Definition list
- Start directory from process status
System processing
This automated operation process does not been executed.
Causes
It seems to be insufficient resources of operating system. Check message in event log or system log, and confirm that caused messageshas been output.
Action method
After deleting error cause, restart Schedule Definition list or restart from process status window.
If there is no causes, collect investigation data using the iscollectinfo command, and contact Fujitsu technical support.
FSP_SW/RB-A_BASE: INFO: 04200: Schedule Definition/Schedule Pattern export is about to start. Description
Export of a Schedule Definition or a Schedule Pattern is starting.
- 71 -
System processing
Starts command processing.
Cause
This is a progress message.
Action method
This is a progress message. No action is required.
FSP_SW/RB-A_BASE: INFO: 04201: Schedule Definition/Schedule Pattern import is about to start. Description
Import of a Schedule Definition or a Schedule Pattern is starting.
System processing
Starts command processing.
Cause
This is a progress message.
Action method
This is a progress message. No action is required.
FSP_SW/RB-A_BASE: INFO: 04202: Schedule Definition/Schedule Pattern export has finished. Description
Export of a Schedule Definition or a Schedule Pattern has completed.
System processing
Ends command processing.
Cause
This is a progress message.
Action method
This is a progress message. No action is required.
FSP_SW/RB-A_BASE: INFO: 04203: Schedule Definition/Schedule Pattern import has finished. Description
Import of a Schedule Definition or a Schedule Pattern has completed.
System processing
Ends command processing.
Cause
This is a progress message.
Action method
This is a progress message. No action is required.
FSP_SW/RB-A_BASE: ERROR: 04204: The option/operand specified in the command is invalid. Description
The option or operand specified in the command is invalid.
- 72 -
System processing
Interrupts command processing.
Cause
The option or operand specified in the command is invalid.
Action method
Refer to the Systemwalker Runbook Automation Reference Guide and specify the correct option or operand in the command.
FSP_SW/RB-A_BASE: ERROR: 04205: The specified process group does not exist. Process group ID:%1 Description
Command processing failed because the specified process group does not exist.
Parameters
%1: Process group ID
System processing
Interrupts command processing.
Cause
The process group does not exist.
Action method
Check the process group name specified in the command. If the process group name is incorrect, specify the correct process groupname and then execute the command again.
FSP_SW/RB-A_BASE: INFO: 04206: The Schedule Definition/Schedule Pattern was exported. Processgroup ID:%1 Number exported:%2 Description
The Schedule Definition or Schedule Pattern was exported.
Parameters
%1: Process group ID
%2: Number of exported Schedule Definitions or Schedule Patterns
System processing
Continues command processing.
Cause
This is a progress message.
Action method
This is a progress message. No action is required.
FSP_SW/RB-A_BASE: INFO: 04207: The Schedule Definition/Schedule Pattern was imported. Processgroup ID:%1 Number imported:%2 Description
The Schedule Definition or Schedule Pattern was imported.
Parameters
%1: Process group ID
- 73 -
%2: Number of imported Schedule Definitions or Schedule Patterns
System processing
Continues command processing.
Cause
This is a progress message.
Action method
This is a progress message. No action is required.
FSP_SW/RB-A_BASE: ERROR: 04208: Failed to export the Schedule Definition. Process group ID:%1Schedule Definition:%2 Detail:%3 Description
Schedule Definition export failed.
Parameters
%1: Process group ID
%2: Schedule Definition name
%3: Detailed message
System processing
Interrupts export of the Schedule Definition displayed in the parameter.
Cause
The cause of the error is displayed in the detailed message.
Action method
Refer to the error displayed in the detailed message and remove the cause of the error, and then execute the command again.
FSP_SW/RB-A_BASE: ERROR: 04209: Failed to export the Schedule Pattern. Process group ID:%1Schedule Pattern:%2 Detail:%3 Description
Schedule Pattern export failed.
Parameters
%1: Process group ID
%2: Schedule Pattern name
%3: Detailed message
System processing
Interrupts export of the Schedule Pattern displayed in the parameter.
Cause
The cause of the error is displayed in the detailed message.
Action method
Refer to the error displayed in the detailed message and remove the cause of the error, and then execute the command again.
FSP_SW/RB-A_BASE: ERROR: 04210: Failed to export the Schedule Definition/Schedule Pattern. Detail:%1
- 74 -
Description
Schedule Definition or Schedule Pattern export failed.
Parameters
%1: Detailed message
System processing
Interrupts export of the Schedule Definition or Schedule Pattern.
Cause
The cause of the error is displayed in the detailed message.
Action method
Refer to the error displayed in the detailed message and remove the cause of the error, and then execute the command again.
FSP_SW/RB-A_BASE: ERROR: 04211: Failed to import the Schedule Definition. Process group ID:%1Schedule Definition:%2 Detail:%3 Description
Schedule Definition import failed.
Parameters
%1: Process group ID
%2: Schedule Definition name
%3: Detailed message
System processing
Interrupts import of the Schedule Definition displayed in the parameter.
Cause
The cause of the error is displayed in the detailed message.
Action method
Refer to the error displayed in the detailed message and remove the cause of the error, and then execute the command again.
FSP_SW/RB-A_BASE: ERROR: 04212: Failed to import the Schedule Pattern. Process group ID:%1Schedule Pattern:%2 Detail:%3 Description
Schedule Pattern import failed.
Parameters
%1: Process group ID
%2: Schedule Pattern name
%3: Detailed message
System processing
Interrupts import of the Schedule Pattern displayed in the parameter.
Cause
The cause of the error is displayed in the detailed message.
- 75 -
Action method
Refer to the error displayed in the detailed message and remove the cause of the error, and then execute the command again.
FSP_SW/RB-A_BASE: ERROR: 04213: Failed to import the Schedule Definition/Schedule Pattern. Detail:%1 Description
Schedule Definition or Schedule Pattern import failed.
Parameters
%1: Detailed message
System processing
Interrupts import of the Schedule Definition or Schedule Pattern.
Cause
The cause of the error is displayed in the detailed message.
Action method
Refer to the error displayed in the detailed message and remove the cause of the error, and then execute the command again.
FSP_SW/RB-A_BASE: INFO: 04214: The Schedule Definition was exported. Process Group ID: %1Schedule Definition: %2 Description
The Schedule Definition was exported.
Parameters
%1: Process group ID
%2: Schedule Definition name
System processing
Ends command processing.
Cause
This is a progress message.
Action method
This is a progress message. No action is required.
FSP_SW/RB-A_BASE: INFO: 04215: The Schedule Pattern was exported. Process Group ID: %1 SchedulePattern: %2 Description
The Schedule Pattern was exported.
Parameters
%1: Process group ID
%2: Schedule Pattern name
System processing
Ends command processing.
- 76 -
Cause
This is a progress message.
Action method
This is a progress message. No action is required.
2.5 Messages Starting with SHNThis section describes messages output by Shunsaku.
SHN: INFO: shn01100i: Initializing... (s*) [t*] Description
Startup process has started.
Parameters
s*: Process name
t*: Director ID
SHN: INFO: shn01106i: Director waiting for connection to searcher. (s*) [t*] Description
The director is waiting for connection to searcher.
Parameters
s*: Process name
t*: Director ID
SHN: INFO: shn01107i: Connected to searcher. (s*,d*) (t*) [u*] Description
Connecting with searcher has been completed.
Parameters
s*: Hostname or IP address where searcher will be deployed
d*: Port number with which searcher receive a request from director
t*: Process name
u*: Director ID
SHN: INFO: shn01108i: Number of searcher connections has reached the maximum. d* (s*) [t*] Description
The number of searcher connection has reached the maximum.
Parameters
d*: Number of searcher
s*: Process name
t*: Director ID
- 77 -
SHN: INFO: shn01109i: Initialization complete. (s*) [t*] Description
Startup process has been completed.
Parameters
s*: Process name
t*: Director ID
SHN: INFO: shn01200i: Ending program... (s*) [t*] Description
Close down process has started.
Parameters
s*: Process name
t*: Director ID
SHN: INFO: shn01202i: Program ended. (s*) [t*] Description
Close down process has been completed.
Parameters
s*: Process name
t*: Director ID
SHN: INFO: shn01300i: Deleting director data... (s*) [t*] Description
Deleting director data has started.
Parameters
s*: Process name
t*: Director ID
SHN: INFO: shn01301i: Clear all data command sent to searcher. (s*) [t*] Description
Sending a batch delete request to searcher.
Parameters
s*: Process name
t*: Director ID
SHN: INFO: shn01302i: Deletion of director data complete. (s*) [t*] Description
Deleting director data has been completed.
- 78 -
Parameters
s*: Process name
t*: Director ID
SHN: ERROR: shn02000e: Communication error. 's*' (t* d*) (u*) [v*] Description
Error occurred in communication processing.
Parameters
s*: Process type (start/search/entry)
t*: Hostname or IP address deployed searcher
d*: Port number which searcher received from request of director
u*: Process name
v*: Director ID
Action method
If this message output when Systemwalker Runbook Automation has been stopped, you do not need to do action.
Otherwise, Restart Systemwalker Runbook Automation.
SHN: INFO: shn03100i: Initializing... (s*) [t*] Description
Startup process has started.
Parameters
s*: Process name
t*: Searcher ID
SHN: INFO: shn03101i: Deletion request of search data received from director. (s*) [t*] Description
Received a search data deletion request from director.
Parameters
s*: Process name
t*: Searcher ID
System processing
Starts deleting search data.
SHN: INFO: shn03102i: Initialization complete. (s*) [t*] Description
Startup process has been completed.
Parameters
s*: Process name
- 79 -
t*: Searcher ID
SHN: INFO: shn03104i: Search port connection success. (s*,d*) (t*) [u*] Description
Connecting with the port for searching director has been completed.
Parameters
s*: Director host name
d*: Port number for searching director
t*: Process name
u*: Searcher ID
SHN: INFO: shn03105i: Entry port connection success. (s*,d*) (t*) [u*] Description
Connecting with the port for updating director has been completed.
Parameters
s*: Director host name
d*: Port number for updating director
t*: Process name
u*: Searcher ID
SHN: INFO: shn03200i: Ending program... (s*) [t*] Description
Close down process has started.
Parameters
s*: Process name
t*: Searcher ID
SHN: INFO: shn03201i: Program ended. (s*) [t*] Description
Close down process has been completed.
Parameters
s*: Process name
t*: Searcher ID
SHN: INFO: shn03300i: Delete request received from director. (s*) [t*] Description
Received a batch delete request from director.
- 80 -
Parameters
s*: Process name
t*: Searcher ID
SHN: ERROR: shn04000e: Communication error. 's*' (t*,d*) (u*) [v*] Description
Error occurred in communication processing.
Parameters
s*: Process type (start/search/entry)
t*: Director hostname
d*: Director search/Update port number
u*: Process name
v*: Searcher ID
Action method
If this message output when Systemwalker Runbook Automation has been stopped, you do not need to do action.
Otherwise, Restart Systemwalker Runbook Automation.
SHN: INFO: shn06009i: Conductor has been activated. [s*] Description
Conductor startup process has been completed.
Parameters
s*: Conductor ID
SHN: INFO: shn06010i: Conductor has been halted. [s*] Description
Conductor close down process has been completed.
Parameters
s*: Conductor ID
SHN: INFO: shn07001i: Initializing sorter. (s*) [t*] Description
Sorter startup process has started.
Parameters
s*: Process name
t*: Sorter ID
SHN: INFO: shn07002i: Sorter initialization has been completed. (s*) [t*] Description
Sorter startup process has been completed.
- 81 -
Parameters
s*: Process name
t*: Sorter ID
SHN: INFO: shn07003i: Ending program... (s*) [t*] Description
Close down process has started.
Parameters
s*: Process name
t*: sorter ID
SHN: INFO: shn07004i: Program ended. (s*) [t*] Description
Close down process has been completed.
Parameters
s*: Process name
t*: sorter ID
SHN: ERROR: shn07017e: A communications error has occurred. (d*) (s*) [t*] Description
Error occurred in communication processing.
Parameters
d*: Port number which received from sort request of conductor
s*: Process name
t*: Sorter ID
Action method
If this message output when Systemwalker Runbook Automation has been stopped, you do not need to do action. Otherwise, RestartSystemwalker Runbook Automation
SHN: INFO: shn30024i: Log file has been switched. type=s* (t*) [u*] Description
The log file has been switched.
Parameters
s*: Log type
performance: Performance log
process: Activity log
t*: Process name
u*: ID
- 82 -
2.6 Messages Starting with SHS SHS: INFO: ihs00001: HTTP Server started. [%s1] Description
The Web server was started.
Parameters
%s1: Web server name
System processing
The Web server was started.
Action method
No action required.
SHS: INFO: ihs00002: HTTP Server stopped. [%s1] Description
The Web server was stopped.
Parameters
%s1: Web server name
System processing
The Web server was stopped.
Action method
No action required.
SHS: INFO: ihs00003: HTTP Server restarted. [%s1] Description
The Web server was restarted.
Parameters
%s1: Web server name
System processing
The Web server was restarted.
Action method
No action required.
SHS: ERROR: ihs00004: Pre-configuration failed [%s1] Description
An error has occurred with initialization pre-processing.
Parameters
%s1: Web server name
- 83 -
System processing
Web server program execution processing is canceled.
Cause
An error has occurred with initialization pre-processing.
Action method
Refer to the message that was output at the same time, and eliminate the cause of the error.
SHS: ERROR: ihs00005: Unable to open logs [%s1] Description
An error has occurred with log initialization processing.
Parameters
%s1: Web server name
System processing
Web server program execution processing is canceled.
Cause
An error has occurred with log initialization processing.
Action method
Refer to the message that was output at the same time, and eliminate the cause of the error.
SHS: ERROR: ihs00006: Configuration Failed [%s1] Description
An error has occurred with initialization processing.
Parameters
%s1: Web server name
System processing
Web server program execution processing is canceled.
Cause
An error has occurred with initialization processing.
Action method
Refer to the message that was output at the same time, and eliminate the cause of the error.
SHS: ERROR: ihs00007: Ouch! Out of memory in ap_setup_prelinked_modules()! Description
Failed to get memory.
System processing
Web server program execution processing is canceled.
- 84 -
Cause
There is insufficient memory.
Action method
Secure the memory capacity that is required for running the Web server, for example by closing unnecessary programs.
SHS: ERROR: ihs00008: %s1: module "%s2" is not compatible with this version of Apache (found %s3,need %s4). [%s5] Description
An internal error occurred.
Parameters
%s1: Web server program name%s2: Plug-in module name%s3: Plug-in module major version%s4: Web server program major version%s5: Web server name
System processing
Web server program execution processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00009: %s1: module "%s2" could not be loaded, because the dynamic module limit wasreached. Please increase DYNAMIC_MODULE_LIMIT and recompile. [%s3] Description
An internal error occurred.
Parameters
%s1: Web server program name%s2: Plug-in module name%s3: Web server name
System processing
Web server program execution processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00010: Syntax error in -C/-c directive: %s1 [%s2] Description
An internal error occurred.
- 85 -
Parameters
%s1: Syntax error content%s2: Web server name
System processing
A system error might have occurred.
Cause
There is an error with the syntax of the directive that was specified in the -C or -c option.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00011: %s1: could not open document config file %s2 [%s3] Description
An internal error occurred.
Parameters
%s1: Web server program name%s2: Environment definition file path%s3: Web server name
System processing
Web server program execution processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00012: Syntax error on line %s1 of %s2: %s3 [%s4] Description
An internal error occurred.
Parameters
%s1: Environment definition file line number%s2: Environment definition file path%s3: Syntax error content%s4: Web server name
System processing
Web server program execution processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
- 86 -
SHS: ERROR: ihs00013: (%s1)%s2: Invalid config file path %s3 [%s4] Description
An internal error occurred.
Parameters
%s1: Error number%s2: Error details content%s3: Environment definition file name%s4: Web server name
System processing
Web server program execution processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00014: (%s1)%s2: alloc_listener: failed to set up sockaddr for %s3 [%s4] Description
An internal error occurred.
Parameters
%s1: Error number%s2: Error details content%s3: Host name%s4: Web server name
System processing
Web server program execution processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00015: (%s1)%s2: alloc_listener: failed to get a socket for %s3 [%s4] Description
Failed to create the communication socket.
Parameters
%s1: Error number%s2: Error details content%s3: Host name%s4: Web server name
System processing
Web server program execution processing is canceled.
- 87 -
Cause
Failed to create the communication socket.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00016: (%s1)%s2: make_sock: for address %s3, apr_socket_opt_set: (%s4) [%s5] Description
Failed to set socket option %s4.
Parameters
%s1: Error number%s2: Error details content%s3: IP address:port number%s4: Socket option%s5: Web server name
System processing
Web server start processing is canceled.
Cause
Failed to set socket option %s4.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: WARNING: ihs00017: (%s1)%s2: make_sock: failed to set %s3 for address %s4, using default [%s5] Description
Failed to set socket option %s4.
Parameters
%s1: Error number%s2: Error details content%s3: IP address: port number%s4: Socket option%s5: Web server name
System processing
Web server start processing is continued.
Cause
Failed to set socket option %s4.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00018: (%s1)%s2: make_sock: could not bind to address %s3 [%s4] Description
Failed to allocate the address to the socket.
- 88 -
Parameters
%s1: Error number%s2: Error details content%s3: IP address: port number%s4: Web server name
System processing
Web server start processing is canceled.
Cause
Failed to allocate the address to the socket.This error may have the following causes:
[Windows]
- If this message was output and %s1 was "OS 10049", a null address has been specified.
- If this message was output when the Web server was started up and %s1 was "OS 10013" or "OS 10048", possible causes are asfollows:
- IP address and port number %s3 that were set in Web server %s4 have been used in another service.
- Port number %s3 that was set in Web server %s4 has been used in another service.
- In the environment definition file (httpd.conf), the Listen directive has been set more than once in an identical IP address andport number combination.
[Linux]
- If this message was output and %s1 was "99", possible causes are as follows:
- A nuIl address has been specified.
- The network interface assigned with IP address %s3 might not be valid.
- If this message was output and %s1 was "22", a null address has been specified.
- If this message was output when the Web server was started up and %s1 was "98", possible causes are as follows:
- IP address and port number %s3 that were set in Web server %s4 have been used in another service.
- Port number %s3 that was set in Web server %s4 has been used in another service.
- In the environment definition file (httpd.conf), the Listen directive has been set more than once in an identical IP address andport number combination.
Action method
Use the communications infrastructure environment setup command to change the port number.
SHS: ERROR: ihs00019: (%s1)%s2: make_sock: unable to listen for connections on address %s3 [%s4] Description
Transition to the socket listener status failed.
Parameters
%s1: Error number%s2: Error details content%s3: IP address: port number%s4: Web server name
System processing
Web server start processing is canceled.
- 89 -
Cause
Transition to the socket listener status failed.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00020: no listening sockets available, shutting down [%s1] Description
An internal error occurred.
Parameters
%s1: Web server name
System processing
Web server program execution processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00021: (%s1)%s2: Couldn't start ErrorLog process [%s3] Description
An internal error occurred.
Parameters
%s1: Error number%s2: Error details content%s3: Web server name
System processing
Web server program execution processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00022: (%s1)%s2: %s3: Invalid error log path %s4. [%s5] Description
An internal error occurred.
Parameters
%s1: Error number%s2: Error details content%s3: Web server program name
- 90 -
%s4: Error log file name%s5: Web server name
System processing
Web server program execution processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00023: (%s1)%s2: %s3: could not open error log file %s4. [%s5] Description
An internal error occurred.
Parameters
%s1: Error number%s2: Error details content%s3: Web server program name%s4: Error log file name%s5: Web server name
System processing
Web server program execution processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00024: piped_log_spawn: unable to setup child process '%s1': %s2 [%s3] Description
Log output program %s1 initialization processing failed.
Parameters
%s1: Log output program name%s2: Error details content%s3: Web server name
System processing
Web server program execution processing is canceled.
Cause
Log output program %s1 initialization processing failed.
Action method
Refer to %s2, and eliminate the cause of the failure.
- 91 -
SHS: ERROR: ihs00025: unable to start piped log program '%s1': %s2 [%s3] Description
Failed to start log output program %s1.
Parameters
%s1: Log output program name%s2: Error details content%s3: Web server name
System processing
Web server program execution processing is canceled.
Cause
Failed to start log output program %s1.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00026: (%s1)%s2: Invalid PID file path %s3, ignoring. [%s4] Description
Failed to obtain the process management file %s3 full path.
Parameters
%s1: Error number%s2: Error details content%s3: process management file name%s4: Web server name
System processing
Web server start processing is continued.
Cause
Failed to obtain the process management file %s3 full path.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00028: (%s1)%s2: %s3: could not log pid to file %s4 [%s5] Description
Failed to open process management file %s4.
Parameters
%s1: Error number%s2: Error details content%s3: Web server program name%s4: process management file name%s5: Web server name
System processing
Web server start processing is continued.
- 92 -
Cause
Failed to open process management file %s4.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00029: [%s1] file %s2, line %s3, assertion "%s4" failed [%s5] Description
An internal error occurred.
Parameters
%s1: Date and time of occurrence%s2: Source file name%s3: Source file line number%s4: Detailed information%s5: Web server name
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00030: (%s1)%s2: Fatal error: unable to create global pool for use with by thescoreboard [%s3] Description
Failed to create the memory management area used in scoreboard management.
Parameters
%s1: Error number%s2: Error details content%s3: Web server name
System processing
Web server start processing is canceled.
Cause
Failed to create the memory management area used in scoreboard management.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00031: (%s1)%s2: Fatal error: Invalid Scoreboard path %s3 [%s4] Description
Failed to obtain the scoreboard file %s3 full path.
Parameters
%s1: Error number%s2: Error details content
- 93 -
%s3: Scoreboard file path%s4: Web server name
System processing
Web server start processing is canceled.
Cause
Failed to obtain the scoreboard file %s3 full path.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00032: (%s1)%s2: Unable to create scoreboard (anonymous shared memory failure)[%s3] Description
Failed to get shared memory used in the scoreboard.
Parameters
%s1: Error number%s2: Error details content%s3: Web server name
System processing
Web server start processing is canceled.
Cause
Failed to get shared memory used in the scoreboard.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00033: (%s1)%s2: cannot allocate scoreboard [%s3] Description
Failed to get dynamic memory used in the scoreboard.
Parameters
%s1: Error number%s2: Error details content%s3: Web server name
System processing
Web server start processing is canceled.
Cause
Failed to get dynamic memory used in the scoreboard.
Action method
Refer to %s2, and eliminate the cause of the failure.
- 94 -
SHS: ERROR: ihs00034: (%s1)%s2: unable to create scoreboard "%s3" (name-based shared memoryfailure) [%s4] Description
Failed to get shared memory used in scoreboard %s3.
Parameters
%s1: Error number%s2: Error details content%s3: Scoreboard name%s4: Web server name
System processing
Web server start processing is canceled.
Cause
Failed to get shared memory used in scoreboard %s3.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00035: (%s1)%s2: invalid transfer log path %s3. [%s4] Description
An internal error occurred.
Parameters
%s1: Error number%s2: Error details content%s3: Access log file name%s4: Web server name
System processing
Web server program execution processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00036: (%s1)%s2: could not open transfer log file %s3. [%s4] Description
An internal error occurred.
Parameters
%s1: Error number%s2: Error details content%s3: Access log file name%s4: Web server name
System processing
Web server program execution processing is canceled.
- 95 -
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00037: (%s1)%s2: Invalid mime types config path %s3 [%s4] Description
An internal error occurred.
Parameters
%s1: Error number%s2: Error details content%s3: MIME type config file name%s4: Web server name
System processing
Web server start processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00038: (%s1)%s2: could not open mime types config file %s3. [%s4] Description
An internal error occurred.
Parameters
%s1: Error number%s2: Error details content%s3: MIME type config file name%s4: Web server name
System processing
Web server start processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00039: (%s1)%s2: mod_rewrite: could not create rewrite_log_lock [%s3] Description
Failed to create the lock resources for the rewrite log.
- 96 -
Parameters
%s1: Error number%s2: Error details content%s3: Web server name
System processing
Web server start processing is canceled.
Cause
Failed to create the lock resources for the rewrite log.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00040: (%s1)%s2: mod_rewrite: Parent could not create RewriteLock file %s3 [%s4] Description
Failed to create the lock file %s3 for the rewrite function.
Parameters
%s1: Error number%s2: Error details content%s3: Name of the lock file for the rewrite function%s4: Web server name
System processing
Web server start processing is canceled.
Cause
Failed to create the lock file %s3 for the rewrite function.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00041: (%s1)%s2: mod_unique_id: unable to find hostname of the server [%s3] Description
Failed to obtain the host name.
Parameters
%s1: Error number%s2: Error details content%s3: Web server name
System processing
Web server start processing is canceled.
Cause
Failed to obtain the host name.
Action method
Refer to %s2, and eliminate the cause of the failure.
- 97 -
SHS: ERROR: ihs00042: (%s1)%s2: mod_unique_id: unable to find IPv4 address of "%s3" [%s4] Description
Failed to obtain the socket information.
Parameters
%s1: Error number%s2: Error details content%s3: Host name%s4: Web server name
System processing
Web server start processing is canceled.
Cause
Failed to obtain the socket information.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: WARNING: ihs00043: Require %s1 > 0, setting to 1 [%s2] Description
An internal error occurred.
Parameters
%s1: Directive name%s2: Web server name
System processing
Web server processing is continued.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00100: (%s1)%s2: Failed to get the full path of %s3 Description
Failed to obtain the Web server program %s3 full path.
Parameters
%s1: Error number%s2: Error details content%s3: Web server program name
System processing
Web server program execution processing is canceled.
- 98 -
Cause
Failed to obtain the Web server program %s3 full path.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00101: %s1: Service is already installed. Description
Web server service %s1 has already been registered.
Parameters
%s1: Service name
System processing
Web server service registration processing is canceled.
Cause
Web server service %s1 has already been registered.
Action method
Check the registration status of service %s1 in the Services window (Control Panel >> Administrative Tools >> Services).
SHS: ERROR: ihs00102: (%s1)%s2: No installed service named "%s3". Description
An internal error occurred.
Parameters
%s1: Detail error number
%s2: Detail error
%s3: Service name
System processing
Web server program execution processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00103: (%s1)%s2: %s3: Unable to start the service manager. [%s4] Description
Failed to start the service control manager.
Parameters
%s1: Error number%s2: Error details content
- 99 -
%s3: Service name%s4: Web server name
System processing
Web server start processing is canceled.
Cause
Failed to start the service control manager.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00104: (%s1)%s2: Parent: Cannot create shutdown event %s3 [%s4] Description
Failed to create the event object %s3 for shutdown.
Parameters
%s1: Error number%s2: Error details content%s3: Event object name%s4: Web server name
System processing
Web server start processing is canceled.
Cause
Failed to create the event object %s3 for shutdown.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00105: (%s1)%s2: Parent: Cannot create restart event %s3 [%s4] Description
Failed to create the event object %s3 for restart.
Parameters
%s1: Error number%s2: Error details content%s3: Event object name%s4: Web server name
System processing
Web server start processing is canceled.
Cause
Failed to create the event object %s3 for restart.
Action method
Refer to %s2, and eliminate the cause of the failure.
- 100 -
SHS: ERROR: ihs00106: (%s1)%s2: %s3: Unable to create the start_mutex. [%s4] Description
Failed to create the exclusive resources for the daemon process.
Parameters
%s1: Error number%s2: Error details content%s3: Service name%s4: Web server name
System processing
Web server start processing is canceled.
Cause
Failed to create the exclusive resources for the daemon process.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00107: (%s1)%s2: master_main: create child process failed. Exiting. [%s3] Description
An error has occurred with daemon process generation processing.
Parameters
%s1: Error number (*1)%s2: Error details content (*1)%s3: Web server name*1: %s1 and %s2 might not always be output.
System processing
Web server start processing is canceled.
Cause
An error has occurred with daemon process generation processing.
Action method
Refer to the message that was output at the same time, and eliminate the cause of the error.
SHS: ERROR: ihs00108: (%s1)%s2: master_main: WaitForMultipeObjects WAIT_FAILED -- doing servershutdown [%s3] Description
An error has occurred with daemon process status monitoring.
Parameters
%s1: Error number%s2: Error details content%s3: Web server name
System processing
The Web server is shut down.
- 101 -
Cause
An error has occurred with daemon process status monitoring.
Action method
Refer to %s2, and eliminate the cause of the error.
SHS: ERROR: ihs00109: (%s1)%s2: master_main: WaitForMultipeObjects with INFINITE wait exited withWAIT_TIMEOUT [%s3] Description
A timeout has occurred with daemon process status monitoring.
Parameters
%s1: Error number%s2: Error details content%s3: Web server name
System processing
The Web server is shut down.
Cause
A timeout has occurred with daemon process status monitoring.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: INFO: ihs00110: Parent: Received restart signal -- Restarting the server. [%s1] Description
Web server %s1 restart processing is starting.
Parameters
%s1: Web server name
SHS: ERROR: ihs00111: Parent: child process exited with status %s1 -- Aborting. [%s2] Description
An error has occurred with the daemon process.
Parameters
%s1: Daemon process exit code%s2: Web server name
System processing
The daemon process is restarted.
Cause
An error has occurred with the daemon process.
Action method
Refer to the message that was output at the same time, and eliminate the cause of the error.
- 102 -
SHS: ERROR: ihs00112: (%s1)%s2: GetModuleFileName failed [%s3] Description
Failed to obtain the Web server program full path.
Parameters
%s1: Error number%s2: Error details content%s3: Web server name
System processing
Web server service registration processing is canceled.
Cause
Failed to obtain the Web server program full path.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00113: (%s1)%s2: Failed to open the WinNT service manager [%s3] Description
Failed to establish the connection with the service control manager.
Parameters
%s1: Error number%s2: Error details content%s3: Web server name
System processing
Web server program execution processing is canceled.
Cause
Failed to establish the connection with the service control manager.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00114: (%s1)%s2: OpenService failed [%s3] Description
Failed to open the Web server %s3 service.
Parameters
%s1: Error number%s2: Error details content%s3: Web server name
System processing
Web server program execution processing is canceled.
Cause
Failed to open the Web server %s3 service.
- 103 -
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00115: (%s1)%s2: ChangeServiceConfig failed [%s3] Description
Failed to change the Web server service configuration parameter.
Parameters
%s1: Error number%s2: Error details content%s3: Web server name
System processing
Web server program execution processing is canceled.
Cause
Failed to change the Web server service configuration parameter.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00116: (%s1)%s2: Failed to create WinNT Service Profile [%s3] Description
Failed to register the Web server %s3 service.
Parameters
%s1: Error number%s2: Error details content%s3: Web server name
System processing
Web server %s3 service registration processing is canceled.
Cause
Failed to register the Web server %s3 service.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00117: (%s1)%s2: %s3: Failed to store the ConfigArgs in the registry. [%s4] Description
Failed to register an option used when service %s3 of Web server %s4 was started up in the registry.
Parameters
%s1: Error number%s2: Error details content%s3: Service name%s4: Web server name
- 104 -
System processing
Web server %s4 service registration processing is canceled.
Cause
Failed to register an option used when service %s3 of Web server %s4 was started up in the registry.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00118: (%s1)%s2: %s3: Failed to delete the service. [%s4] Description
Failed to delete service %s3 of Web server %s4.
Parameters
%s1: Error number%s2: Error details content%s3: Service name%s4: Web server name
System processing
Web server %s4 service deletion processing is canceled.
Cause
Failed to delete service %s3 of Web server %s4.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00119: (%s1)%s2: Query of Service %s3 failed [%s4] Description
Failed to obtain the status of service %s3 of Web server %s4.
Parameters
%s1: Error number%s2: Error details content%s3: Service name%s4: Web server name
System processing
Web server %s4 shutdown processing is canceled.
Cause
Failed to obtain the status of service %s3 of Web server %s4.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00120: (%s1)%s2: ISAPI: could not create the isapi cache pool [%s3]
- 105 -
Description
Failed to create the memory management area used for the mod_isap module.
Parameters
%s1: Error number%s2: Error details content%s3: Web server name
System processing
Web server program execution processing is canceled.
Cause
Failed to create the memory management area used for the mod_isap module.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: WARNING: ihs00121: ThreadsPerChild of %s1 exceeds ThreadLimit value of %s2 threads, loweringThreadsPerChild to %s2. To increase, please see the ThreadLimit directive. [%s3] Description
An internal error occurred.
Parameters
%s1: Value set for the ThreadsPerChild directive%s2: Upper limit for the ThreadsPerChild directive%s3: Web server name
System processing
Web server processing is continued.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: WARNING: ihs00122: ThreadLimit of %s1 exceeds compile time limit of %s2 threads, loweringThreadLimit to %s2. [%s3] Description
An internal error occurred.
Parameters
%s1: Value set for the ThreadLimit directive%s2: Upper limit for the ThreadLimit directive%s3: Web server name
System processing
Web server processing is continued.
Cause
A system error might have occurred.
- 106 -
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00123: (%s1)%s2: Parent: Failed to get full path of %s3 [%s4] Description
Failed to obtain the Web server program %s3 full path.
Parameters
%s1: Error number%s2: Error details content%s3: Web server program name%s4: Web server name
System processing
Web server start processing is canceled.
Cause
Failed to obtain the Web server program %s3 full path.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00124: (%s1)%s2: Parent: Unable to %s3 [%s4] Description
Processing %s3 failed.
Parameters
%s1: Error number%s2: Error details content%s3: Content of the processing in which the error occurred%s4: Web server name
System processing
Web server %s4 start processing is canceled.
Cause
Processing %s3 failed.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00125: (%s1)%s2: Parent: Could not create %s3 event for child process [%s4] Description
Failed to create the event object.
Parameters
%s1: Error number%s2: Error details content
- 107 -
%s3: Event type%s4: Web server name
System processing
Web server %s4 start processing is canceled.
Cause
Failed to create the event object.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00126: (%s1)%s2: Parent: Failed to create the child process. [%s3] Description
Failed to generate the daemon process.
Parameters
%s1: Error number%s2: Error details content%s3: Web server name
System processing
Web server %s3 start processing is canceled.
Cause
Failed to generate the daemon process.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00127: (%s1)%s2: Parent: WSADuplicateSocket failed for socket %s3. Check the FAQ.[%s4] Description
Failed to duplicate the socket.
Parameters
%s1: Error number%s2: Error details content%s3: Socket descriptor%s4: Web server name
System processing
Web server %s4 start processing is canceled.
Cause
Failed to duplicate the socket.
Action method
Refer to %s2, and eliminate the cause of the failure.
- 108 -
SHS: ERROR: ihs00128: %s1: Failed to start the service process. [%s2] Description
An error has occurred with the starting of service %s1 on Web server %s2.
Parameters
%s1: Service name%s2: Web server name
System processing
Web server %s2 start processing is canceled.
Cause
An error has occurred with the starting of service %s1 on Web server %s2.
Action method
Refer to the message that was output at the same time, and eliminate the cause of the error.
SHS: ERROR: ihs00129: (%s1)%s2: Child %s3: _beginthreadex failed. Unable to create all worker threads.Created %s4 of the %s5 threads requested with the ThreadsPerChild configuration directive. [%s6] Description
Failed to generate the communication thread.
Parameters
%s1: Error number%s2: Error details content%s3: Process ID for the daemon process%s4: Number of generated communication threads%s5: Value set for the ThreadsPerChild directive%s6: Web server name
System processing
Web server %s6 is shut down.
Cause
Failed to generate the communication thread.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: INFO: ihs00130: Parent: child process exited with status %s1 -- Restarting. [%s2] Description
The daemon process is finished.
Parameters
%s1: Daemon process exit code%s2: Web server name
System processing
The daemon process is restarted.
- 109 -
SHS: ERROR: ihs00200: (%s1)%s2: Error retrieving pid file %s3 [%s4] Description
Failed to read process management file %s3.
Parameters
%s1: Error number%s2: Error details content%s3: Process management file%s4: Web server name
System processing
Web server program execution processing is canceled.
Cause
Failed to read process management file %s3.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: WARNING: ihs00201: httpd (pid %s1) already running [%s2] Description
Web server %s2 has already been started.
Parameters
%s1: Process ID%s2: Web server name
System processing
Web server %s2 start processing is canceled.
Cause
Web server %s2 has already been started.
Action method
No action required.
SHS: WARNING: ihs00202: httpd (no pid file) not running [%s1] Description
Web server %s1 has not been started.
Parameters
%s1: Web server name
System processing
Web server %s1 shutdown processing is canceled.
Cause
Web server %s1 has not been started.
- 110 -
Action method
No action required.
SHS: WARNING: ihs00203: httpd (pid %s1?) not running [%s2] Description
Process %s1 of Web server %s2 does not exist.
Parameters
%s1: Process ID%s2: Web server name
System processing
Web server %s2 shutdown processing is canceled.
Cause
Process %s1 of Web server %s2 does not exist.
Action method
No action required.
SHS: WARNING: ihs00204: httpd not running, trying to start [%s1] Description
Web server %s1 has not been started.
Parameters
%s1: Web server name
System processing
Web server %s1 start processing is starting.
Cause
Web server %s1 has not been started.
Action method
No action required.
SHS: ERROR: ihs00205: (%s1)%s2: sending signal to server [%s3] Description
Failed to send the signal to the daemon process.
Parameters
%s1: Error number%s2: Error details content%s3: Web server name
System processing
Web server program execution processing is canceled.
- 111 -
Cause
Failed to send the signal to the daemon process.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00206: Child %s1 returned a Fatal error... Apache is exiting! [%s2] Description
An error has occurred with communication process %s1.
Parameters
%s1: Process ID of the communication process%s2: Web server name
System processing
Web server %s2 is shut down.
Cause
An error has occurred with communication process %s1.
Action method
Refer to the message that was output at the same time, and eliminate the cause of the error.
SHS: ERROR: ihs00207: (%s1)%s2: apr_proc_detach failed [%s3] Description
Failed to generate the daemon process.
Parameters
%s1: Error number%s2: Error details content%s3: Web server name
System processing
Web server %s3 start processing is canceled.
Cause
Failed to generate the daemon process.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00208: (%s1)%s2: Could not open pipe-of-death. [%s3] Description
Failed to create the pipe.
Parameters
%s1: Error number%s2: Error details content%s3: Web server name
- 112 -
System processing
Web server %s3 start processing is canceled.
Cause
Failed to create the pipe.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00209: (%s1)%s2: Couldn't create accept lock [%s3] Description
Failed to create the exclusive resources for the connection.
Parameters
%s1: Error number%s2: Error details content%s3: Web server name
System processing
Web server %s3 start processing is canceled.
Cause
Failed to create the exclusive resources for the connection.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00210: (%s1)%s2: Couldn't set permissions on cross-process lock; check User andGroup directives [%s3] Description
Failed to set the exclusive resources permissions for the connection.
Parameters
%s1: Error number%s2: Error details content%s3: Web server name
System processing
Web server %s3 start processing is canceled.
Cause
Failed to set the exclusive resources permissions for the connection.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: INFO: ihs00211: Graceful restart requested, doing restart [%s1] Description
Web server %s1 restart processing is starting.
- 113 -
Parameters
%s1: Web server name
SHS: INFO: ihs00212: SIGHUP received. Attempting to restart [%s1] Description
Web server %s1 restart processing is starting.
Parameters
%s1: Web server name
SHS: ERROR: ihs00213: (%s1)%s2: Couldn't initialize cross-process lock in child [%s3] Description
Failed to initialize the exclusive resources for the connection.
Parameters
%s1: Error number%s2: Error details content%s3: Web server name
System processing
Web server %s3 is shut down.
Cause
Failed to initialize the exclusive resources for the connection.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00214: (%s1)%s2: setuid: unable to change to uid: %s3 [%s4] Description
An internal error occurred.
Parameters
%s1: Error number%s2: Error details content%s3: User ID%s4: Web server name
System processing
Web server %s4 is shut down.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
- 114 -
SHS: ERROR: ihs00215: (%s1)%s2: getpwuid: couldn't determine user name from uid %s3, you probablyneed to modify the User directive [%s4] Description
An internal error occurred.
Parameters
%s1: Error number (*1)%s2: Error details content (*1)%s3: User ID%s4: Web server name*1: %s1 and %s2 might not always be output.
System processing
Web server %s4 is shut down.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00216: (%s1)%s2: setgid: unable to set group id to Group %s3 [%s4] Description
An internal error occurred.
Parameters
%s1: Error number%s2: Error details content%s3: Group ID%s4: Web server name
System processing
Web server %s4 is shut down.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00217: (%s1)%s2: initgroups: unable to set groups for User %s3 and Group %s4 [%s5] Description
Failed to initialize the groups access list.
Parameters
%s1: Error number%s2: Error details content%s3: User ID%s4: Group ID%s5: Web server name
- 115 -
System processing
Web server %s5 is shut down.
Cause
Failed to initialize the groups access list.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00218: (%s1)%s2: mod_rewrite: Could not set permissions on rewrite_log_lock; checkUser and Group directives [%s3] Description
Failed to set the permissions for the lock resources for the rewrite log.
Parameters
%s1: Error number%s2: Error details content%s3: Web server name
System processing
Web server %s3 start processing is canceled.
Cause
Failed to set the permissions for the lock resources for the rewrite log.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00219: (%s1)%s2: mod_rewrite: Parent could not set permissions on RewriteLock;check User and Group directives [%s3] Description
Failed to set the permissions for the lock file for the rewrite function.
Parameters
%s1: Error number%s2: Error details content%s3: Web server name
System processing
Web server %s3 start processing is canceled.
Cause
Failed to set the permissions for the lock file for the rewrite function.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: WARNING: ihs00220: detected MinSpareServers set to non-positive. Resetting to 1 to avoid almostcertain Apache failure. Please read the documentation. [%s1]
- 116 -
Description
An internal error occurred.
Parameters
%s1: Web server name
System processing
Web server %s1 processing is continued.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: WARNING: ihs00221: MaxClients of %s1 exceeds ServerLimit value of %s2 servers, loweringMaxClients to %s2. To increase, please see the ServerLimit directive. [%s3] Description
An internal error occurred.
Parameters
%s1: Value set for the MaxClients directive%s2: Upper limit for the MaxClients directive%s3: Web server name
System processing
Web server %s3 processing is continued.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: WARNING: ihs00222: ServerLimit of %s1 exceeds compile time limit of %s2 servers, loweringServerLimit to %s2. [%s3] Description
An internal error occurred.
Parameters
%s1: Value set for the ServerLimit directive%s2: Upper limit for the ServerLimit directive%s3: Web server name
System processing
Web server %s3 processing is continued.
Cause
A system error might have occurred.
- 117 -
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00223: %s1: bad user name %s2 [%s3] Description
An internal error occurred.
Parameters
%s1: Web server program name%s2: User name that was specified in the User directive%s3: Web server name
System processing
Web server program execution processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00224: %s1: bad group name %s2 [%s3] Description
An internal error occurred.
Parameters
%s1: Web server program name%s2: Group name that was specified in the Group directive%s3: Web server name
System processing
Web server program %s1 execution processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00225: (%s1)%s2: couldn't grab the accept mutex [%s3] Description
Failed to get the exclusive resources for listening for connections from the client.
Parameters
%s1: Error number%s2: Error details content%s3: Web server name
- 118 -
System processing
Web server %s3 is shut down.
Cause
Failed to get the exclusive resources for listening for connections from the client.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00226: (%s1)%s2: couldn't release the accept mutex [%s3] Description
Failed to release the exclusive resources for listening for connections from the client.
Parameters
%s1: Error number%s2: Error details content%s3: Web server name
System processing
Web server %s3 is shut down.
Cause
Failed to release the exclusive resources for listening for connections from the client.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00227: (%s1)%s2: ap_listen_open: unable to make socket non-blocking [%s3] Description
Failed to unblock the socket.
Parameters
%s1: Error number%s2: Error details content%s3: Web server name
System processing
Web server %s3 start processing is canceled.
Cause
Failed to unblock the socket.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: ERROR: ihs00300: Internal error. Detail=(%s1) [%s2] Description
An internal error occurred.
- 119 -
Parameters
%s1: Error details content%s2: Web server name
System processing
Processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00301: The path to an environment definition file is invalid. Detail=%s1(%s2) [%s3] Description
An internal error occurred.
Parameters
%s1: Environment definition file name%s2: Error number%s3: Web server name
System processing
Processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00302: File copy failed. Detail=%s1->%s2(%s3) [%s4] Description
Failed to copy from file %1 to file %2.
Parameters
%s1: Copy source file name%s2: Copy destination file name%s3: Error number%s4: Web server name
System processing
Processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
- 120 -
SHS: ERROR: ihs00303: File open failed. Detail=%s1(%s2) [%s3] Description
Failed to open file %s1.
Parameters
%s1: File name%s2: Error number%s3: Web server name
System processing
Processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00304: File lock failed. Detail=%s1(%s2) [%s3] Description
Failed to lock file %s1.
Parameters
%s1: File name%s2: Error number%s3: Web server name
System processing
Processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00400: %s1: An error occurred during the Web server program execution processing.[%s2] Description
Could not execute program %s1 of Web server %s2.
Parameters
%s1: Web server program name%s2: Web server name (*1)*1: Web server %s2 might not always be output, depending on the execution method for Web server program %s1.
System processing
Web server program execution processing is canceled.
- 121 -
Cause
The Apache or httpd command was executed to operate the Web server.
Action method
The Apache and httpd commands cannot be used. Use the communications infrastructure control command to start/stop the Web server.
SHS: ERROR: ihs00401: (%s1)%s2: Couldn't start TraceLog process. [%s3] Description
An internal error occurred.
Parameters
%s1: Detail error code
%s2: Detail error
%s3: eb server name
In additional, %s1: Detail error code and %s2: detail error may not be output.
System processing
Web server program execution processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00402: (%s1)%s2: Invalid TraceLog file path %s3. [%s4] Description
An internal error occurred.
Parameters
%s1: Error number%s2: Error details content%s3: Name of the log file for trace output%s4: Web server name
System processing
Web server program execution processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00403: (%s1)%s2: Could not open TraceLog file %s3. [%s4] Description
An internal error occurred.
- 122 -
Parameters
%s1: Error number%s2: Error details content%s3: Name of the log file for trace output%s4: Web server name
System processing
Web server program execution processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00404: Failed to set the environment variable.(%s1,%s2,%s3,%s4) [%s5] Description
Failed to set the environment variable.
Parameters
%s1: Error occurrence source function name%s2: Error number 1%s3: Error number 2%s4: Error number 3%s5: Web server name
System processing
Web server program execution processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00500: SSL: Library initialization failed.(%s1,%s2) [%s3] Description
Failed to initialize the library.
Parameters
%s1: Error details content 1%s2: Error details content 2%s3: Web server name
System processing
Web server %s3 start processing is canceled.
Cause
A system error might have occurred.
- 123 -
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00501: SSL: Insufficient memory.(%s1,%s2,%s3,%s4) [%s5] Description
There was insufficient memory in the SSL library.
Parameters
%s1: Error occurrence source function name%s2: Error number 1%s3: Error number 2%s4: Site certificate nickname (*1)%s5: Web server name*1: Site certificate nickname %s4 might not always be output.
System processing
Web server %s5 start processing is canceled.
Cause
There was insufficient memory in the SSL library.
Action method
Secure the memory capacity that is required for running the Web server, for example by closing unnecessary programs.
SHS: ERROR: ihs00502: SSL: Slot information directory error.(%s1,%s2,%s3) [%s4] Description
There is an error with the slot information directory.
Parameters
%s1: Error occurrence source function name%s2: Error number 1%s3: Error number 2%s4: Web server name
System processing
Web server %s4 start processing is canceled.
Cause
There is an error with the slot information directory.
Action method
Check whether the private key management environment has been set correctly.
Check whether the slot information directory has been set correctly with the certificate management information setting command.
SHS: ERROR: ihs00503: SSL: Invalid Token label.(%s1,%s2,%s3) [%s4] Description
There is an error with the token label.
- 124 -
Parameters
%s1: Error occurrence source function name%s2: Error number 1%s3: Error number 2%s4: Web server name
System processing
Web server %s4 start processing is canceled.
Cause
There is an error with the token label.
Action method
Check whether the token label has been set correctly with the certificate management information setting command.
SHS: ERROR: ihs00504: SSL: The site certificate has expired.(%s1,%s2,%s3,%s4) [%s5] Description
The site certificate has expired.
Parameters
%s1: Error occurrence source function name%s2: Error number 1%s3: Error number 2%s4: Site certificate nickname (*1)%s5: Web server name*1: Site certificate nickname %s4 might not always be output.
System processing
Web server %s5 start processing or communication processing is canceled.
Cause
The site certificate has expired.
Action method
Submit a site certificate request to the CA (Certificate Authority), and then delete and re-register the site certificate that is currentlyregistered. The site certificate expiration date can be checked using the cmdspcert command.
SHS: ERROR: ihs00505: SSL: The CA certificate has expired.(%s1,%s2,%s3,%s4) [%s5] Description
The CA certificate has expired.
Parameters
%s1: Error occurrence source function name%s2: Error number 1%s3: Error number 2%s4: Site certificate nickname (*1)%s5: Web server name*1: Site certificate nickname %s4 might not always be output.
System processing
Web server %s5 start processing is canceled.
- 125 -
Cause
The CA certificate has expired.
Action method
Obtain the CA certificate from the CA (Certificate Authority), and then delete and re-register the CA certificate that is currentlyregistered. The site certificate expiration date can be checked using the cmdspcert command.
SHS: ERROR: ihs00506: SSL: Couldn't verify the site certificate.(%s1,%s2,%s3,%s4) [%s5] Description
Failed to verify the CA certificate and site certificate.
Parameters
%s1: Error occurrence source function name%s2: Error number 1%s3: Error number 2%s4: Site certificate nickname (*1)%s5: Web server name*1: Site certificate nickname %s4 might not always be output.
System processing
Web server %s5 start processing is canceled.
Cause
Failed to verify the CA certificate and site certificate.
Action method
Check whether there is an error with the CA (Certificate Authority) certificate and site certificate relationship.
SHS: ERROR: ihs00507: SSL: Couldn't verify the CA certificate.(%s1,%s2,%s3,%s4) [%s5] Description
Failed to verify the CA certificate.
Parameters
%s1: Error occurrence source function name%s2: Error number 1%s3: Error number 2%s4: Site certificate nickname (*1)%s5: Web server name*1: Site certificate nickname %s4 might not always be output.
System processing
Web server %s5 start processing is canceled.
Cause
Failed to verify the CA certificate.
Action method
Check whether there is an error with the CA (Certificate Authority) certificate and site certificate relationship.
SHS: ERROR: ihs00508: SSL: Couldn't analyze the site certificate.(%s1,%s2,%s3,%s4) [%s5]
- 126 -
Description
Failed to analyze the site certificate.
Parameters
%s1: Error occurrence source function name%s2: Error number 1%s3: Error number 2%s4: Site certificate nickname (*1)%s5: Web server name*1: Site certificate nickname %s4 might not always be output.
System processing
Web server %s5 start processing is canceled.
Cause
Failed to analyze the site certificate.
Action method
Submit a site certificate request to the CA (Certificate Authority), and then delete and re-register the site certificate that is currentlyregistered.
SHS: ERROR: ihs00509: SSL: Couldn't analyze the CA certificate.(%s1,%s2,%s3,%s4) [%s5] Description
Failed to analyze the CA certificate.
Parameters
%s1: Error occurrence source function name%s2: Error number 1%s3: Error number 2%s4: Site certificate nickname (*1)%s5: Web server name*1: Site certificate nickname %s4 might not always be output.
System processing
Web server %s5 start processing is canceled.
Cause
Failed to analyze the CA certificate.
Action method
Obtain the CA certificate from the CA (Certificate Authority), and then delete and re-register the CA certificate that is currentlyregistered.
SHS: ERROR: ihs00510: SSL: The site certificate has been revoked.(%s1,%s2,%s3,%s4) [%s5] Description
The site certificate has been revoked.
Parameters
%s1: Error occurrence source function name%s2: Error number 1%s3: Error number 2
- 127 -
%s4: Site certificate nickname (*1)%s5: Web server name*1: Site certificate nickname %s4 might not always be output.
System processing
Web server %s5 start processing is canceled.
Cause
The site certificate has been revoked.
Action method
Submit a site certificate request to the CA (Certificate Authority), and then delete and re-register the site certificate that is currentlyregistered.
SHS: ERROR: ihs00511: SSL: The CA certificate has been revoked.(%s1,%s2,%s3,%s4) [%s5] Description
The CA certificate has been revoked.
Parameters
%s1: Error occurrence source function name%s2: Error number 1%s3: Error number 2%s4: Site certificate nickname (*1)%s5: Web server name*1: Site certificate nickname %s4 might not always be output.
System processing
Web server %s5 start processing is canceled.
Cause
The CA certificate has been revoked.
Action method
Obtain the CA certificate from the CA (Certificate Authority), and then delete and re-register the CA certificate that is currentlyregistered.
SHS: ERROR: ihs00512: SSL: Invalid Site certificate nickname.(%s1,%s2,%s3,%s4) [%s5] Description
There is an error with the site certificate nickname.
Parameters
%s1: Error occurrence source function name%s2: Error number 1%s3: Error number 2%s4: Site certificate nickname (*1)%s5: Web server name*1: Site certificate nickname %s4 might not always be output.
System processing
Web server %s5 start processing is canceled.
- 128 -
Cause
There is an error with the site certificate nickname.
Action method
Check whether there is an error with the site certificate nickname that was set using the certificate management information settingcommand.
SHS: ERROR: ihs00513: SSL: Invalid Client CA certificate nickname.(%s1,%s2,%s3,%s4) [%s5] Description
An internal error occurred.
Parameters
%s1: Error occurrence source function name%s2: Error number 1%s3: Error number 2%s4: Site certificate nickname (*1)%s5: Web server name*1: Site certificate nickname %s4 might not always be output.
System processing
Web server %s5 start processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00514: SSL: The site certificate has no path list.(%s1,%s2,%s3,%s4) [%s5] Description
The site certificate has no path list.
Parameters
%s1: Error occurrence source function name%s2: Error number 1%s3: Error number 2%s4: Site certificate nickname (*1)%s5: Web server name*1: Site certificate nickname %s4 might not always be output.
System processing
Web server %s5 start processing is canceled.
Cause
The site certificate has no path list.
Action method
Register the digital certificate of the CA (Certificate Authority) that issued the certificate for the site, using the certificate/keymanagement environment in an appropriate order, starting with the root CA.
- 129 -
SHS: ERROR: ihs00515: SSL: The CA certificate has no path list.(%s1,%s2,%s3,%s4) [%s5] Description
The CA certificate has no path list.
Parameters
%s1: Error occurrence source function name%s2: Error number 1%s3: Error number 2%s4: Site certificate nickname (*1)%s5: Web server name*1: Site certificate nickname %s4 might not always be output.
System processing
Web server %s5 start processing is canceled.
Cause
The CA certificate has no path list.
Action method
Register the CA(Certificate Authority) certificates in the certificate/key management environment in the correct order, starting fromthe root CA.
SHS: ERROR: ihs00516: SSL: The site certificate path is invalid.(%s1,%s2,%s3,%s4) [%s5] Description
The site certificate path is incomplete.
Parameters
%s1: Error occurrence source function name%s2: Error number 1%s3: Error number 2%s4: Site certificate nickname (*1)%s5: Web server name*1: Site certificate nickname %s4 might not always be output.
System processing
Web server %s5 start processing is canceled.
Cause
The site certificate path is incomplete.
Action method
Register the digital certificate of the CA (Certificate Authority) that issued the certificate for the site, using the certificate/keymanagement environment in an appropriate order, starting with the root CA.
SHS: ERROR: ihs00517: SSL: The CA certificate path is invalid.(%s1,%s2,%s3,%s4) [%s5] Description
The CA certificate path is incomplete.
Parameters
%s1: Error occurrence source function name%s2: Error number 1
- 130 -
%s3: Error number 2%s4: Site certificate nickname (*1)%s5: Web server name*1: Site certificate nickname %s4 might not always be output.
System processing
Web server %s5 start processing is canceled.
Cause
The CA certificate path is incomplete.
Action method
Register the CA certificates in the certificate/key management environment in the correct order, starting from the root CA.
SHS: ERROR: ihs00518: SSL: Private key does not exist.(%s1,%s2,%s3,%s4) [%s5] Description
The private key does not exist.
Parameters
%s1: Error occurrence source function name%s2: Error number 1%s3: Error number 2%s4: Site certificate nickname (*1)%s5: Web server name*1: Site certificate nickname %s4 might not always be output.
System processing
Web server %s5 start processing is canceled.
Cause
This error may have one of the following causes:
- The site private key has not been registered in the private key management environment.
- A certificate issued by a CA that is not supported has been used.
Action method
Take one of the following actions:
- Check whether the site certificate used was created with the cmmakecsr command on the machine using the certificate and issuedby CSR.
- If a certificate issued by a CA that is not supported has been used, then create the application form for obtaining the certificateagain, and then submit the certificate request to the following CA:
- VeriSign, Inc.
Secure Server ID and Secure Server ID EV (EV SSL certificates) are supported.
- Cybertrust, Inc.
SureServer for SSL certificates are supported.
SHS: ERROR: ihs00519: SSL: Invalid User pin.(%s1,%s2,%s3,%s4) [%s5] Description
There is an error with the user PIN.
- 131 -
Parameters
%s1: Error occurrence source function name%s2: Error number 1%s3: Error number 2%s4: Site certificate nickname (*1)%s5: Web server name*1: Site certificate nickname %s4 might not always be output.
System processing
Web server %s5 start processing is canceled.
Cause
There is an error with the user PIN.
Action method
Re-register the user PIN.
SHS: ERROR: ihs00520: SSL: Certificate environment directory error.(%s1,%s2,%s3,%s4) [%s5] Description
There is an error with the operation management directory.
Parameters
%s1: Error occurrence source function name%s2: Error number 1%s3: Error number 2%s4: Site certificate nickname (*1)%s5: Web server name*1: Site certificate nickname %s4 might not always be output.
System processing
Web server %s5 start processing is canceled.
Cause
There is an error with the operation management directory.
Action method
Check whether the certificate/key management environment has been set correctly. Also, check whether there is an error with theoperation management directory that was set using the certificate management information setting command.
SHS: ERROR: ihs00521: SSL: Invalid cipher suite.(%s1,%s2,%s3,%s4) [%s5] Description
An internal error occurred.
Parameters
%s1: Error occurrence source function name%s2: Error number 1%s3: Error number 2%s4: Site certificate nickname (*1)%s5: Web server name*1: Site certificate nickname %s4 might not always be output.
- 132 -
System processing
Web server %s5 start processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00522: SSL: SSL definition name specification is invalid.(%s1) [%s2] Description
SSL definition %s1 does not exist.
Parameters
%s1: SSL definition name%s2: Web server name
System processing
Web server %s2 start processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00523: SSL: SSL definition acquisition failed.(%s1,%s2,%s3) [%s4] Description
Failed to obtain the SSL definition %s1 certificate information.
Parameters
%s1: SSL definition name%s2: Function name%s3: Error details content%s4: Web server name
System processing
Web server %s4 start processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00524: SSL: SSLSlotDir is not defined. [%s1] Description
An internal error occurred.
- 133 -
Parameters
%s1: Web server name
System processing
Web server %s1 start processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00525: SSL: SSLTokenLabel is not defined. [%s1] Description
An internal error occurred.
Parameters
%s1: Web server name
System processing
Web server %s1 start processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00526: SSL: SSLUserPINFile is not defined. [%s1] Description
An internal error occurred.
Parameters
%s1: Web server name
System processing
Web server %s1 start processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00527: SSL: SSLVerifyClient is not defined. [%s1] Description
An internal error occurred.
- 134 -
Parameters
%s1: Web server name
System processing
Web server %s1 start processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00528: SSL: SSLEnvDir is not defined. [%s1] Description
An internal error occurred.
Parameters
%s1: Web server name
System processing
Web server %s1 start processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00529: SSL: SSLCertName is not defined. [%s1] Description
An internal error occurred.
Parameters
%s1: Web server name
System processing
Web server %s1 start processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00530: SSL: User PIN decryption failed.(%s1,%s2) [%s3] Description
User PIN decryption failed.
- 135 -
Parameters
%s1: Error details content 1%s2: Error details content 2%s3: Web server name
System processing
Web server %s3 start processing is canceled.
Cause
User PIN decryption failed.
Action method
Re-create the user PIN file using the ihsregistupin command.
If the error still occurs, collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs00531: SSL: Couldn't open user pin file.(%s1) [%s2] Description
Failed to open user PIN file %s1.
Parameters
%s1: User PIN file name%s2: Web server name
System processing
Web server %s2 start processing is canceled.
Cause
Failed to open user PIN file %s1.
Action method
Check whether user PIN file %s1 exists.
SHS: ERROR: ihs00532: SSL: Couldn't read user pin file.(%s1) [%s2] Description
Failed to read user PIN file %s1.
Parameters
%s1: User PIN file name%s2: Web server name
System processing
Web server %s2 start processing is canceled.
Cause
Failed to read user PIN file %s1.
Action method
Check the user PIN file %s1 permissions. If the permissions have been set correctly, user PIN file %s1 might have been corrupted.Re-create the user PIN file using the ihsregistupin command.
If the error still occurs, collect the maintenance data and contact Fujitsu technical support.
- 136 -
SHS: ERROR: ihs00599: SSL: Unexcepted error.(%s1,%s2,%s3,%s4) [%s5] Description
An unexpected error was detected in the SSL function.
Parameters
%s1: Error occurrence source function name%s2: Error number 1%s3: Error number 2%s4: Site certificate nickname (*1)%s5: Web server name*1: Site certificate nickname %s4 might not always be output.
System processing
Web server %s5 start processing is canceled.
Cause
An unexpected error was detected in the SSL function.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs69000: There is no permission to execute ihsregistupin. Description
There are no ihsregistupin command access permissions.
System processing
Processing is canceled.
Cause
There are no ihsregistupin command access permissions.
Action method
The ihsregistupin command must be executed with administrative privileges.
SHS: ERROR: ihs69001: The path name of the user PIN control file is too long. Description
The path name of the user PIN control file has exceeded the maximum length.
System processing
Processing is canceled.
Cause
The path name of the user PIN control file has exceeded the maximum length.
Action method
Change the file name of the user PIN control file.
SHS: ERROR: ihs69002: The path name of the slot information directory is too long.
- 137 -
Description
The path name of the slot information directory has exceeded the maximum length.
System processing
Processing is canceled.
Cause
The path name of the slot information directory has exceeded the maximum length.
Action method
Change the name of the slot information directory.
SHS: ERROR: ihs69003: The slot information directory (%s1) does not exist. Description
Slot information directory %s1 does not exist.
Parameters
%s1: Directory name
System processing
Processing is canceled.
Cause
Slot information directory %1 does not exist.
Action method
Check whether slot information directory %1 exists.
SHS: ERROR: ihs69004: Unable to check user PIN. Description
The user PIN (UserPIN: xxx) and the user PIN that was entered for confirmation (Re-type UserPIN: xxx) do not match.
System processing
Processing is canceled.
Cause
There is an error with the input.
Action method
Enter the same character string.
SHS: ERROR: ihs69005: The user PIN control file (%s1) cannot be opened. Description
There are no user PIN control file %s1 access permissions.
Parameters
%s1: File name
- 138 -
System processing
Processing is canceled.
Cause
There are no user PIN control file %s1 access permissions.
Action method
Check the user PIN control file %s1 access permissions.
SHS: ERROR: ihs69006: Registration of user PIN (%s1) failed. Description
Failed to write user PIN control file %s1.
Parameters
%s1: File name
System processing
Processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs69007: Unable to close the user PIN control file (%s1). Description
Cannot close user PIN control file %s1.
Parameters
%s1: File name
System processing
Processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs69008: Unable to change the permission for the user PIN control file (%s1). Description
There are no user PIN control file %s1 access permissions.
Parameters
%s1: File name
- 139 -
System processing
Processing is canceled.
Cause
There are no user PIN control file %s1 access permissions.
Action method
Check the user PIN control file %s1 access permissions.
SHS: ERROR: ihs69009: Memory is insufficient. Description
There is insufficient memory.
System processing
Processing is canceled.
Cause
There is insufficient memory.
Action method
Close unnecessary programs.
SHS: ERROR: ihs69010: The disk capacity is insufficient. Description
There is insufficient disk capacity, therefore write cannot be performed in this state.
System processing
Processing is canceled.
Cause
There is insufficient disk capacity, therefore write cannot be performed in this state.
Action method
Delete unnecessary files. Alternatively, secure disk capacity.
SHS: ERROR: ihs69011: There is an error in the user PIN. Description
There is an error with the characters that were specified in the user PIN.
System processing
Processing is canceled.
Cause
There is an error with the characters that were specified in the user PIN.
Action method
Enter an alphanumeric character string (maximum: 128 bytes) in the user PIN.
- 140 -
SHS: ERROR: ihs69013: Encryption of user PIN failed.(%s1:%s2) Description
An error has occurred in function %s1 of the encryption.
Parameters
%s1: Function name%s2: Error code
System processing
Processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs69014: No slot exists. Description
A slot has not been generated.
System processing
Processing is canceled.
Cause
A slot has not been generated.
Action method
Generate the slot using the private key management environment creation/setting command, and then re-execute.
SHS: ERROR: ihs69015: No token exists. Description
A token has not been generated.
System processing
Processing is canceled.
Cause
A token has not been generated.
Action method
Generate the token using the private key management environment creation/setting command, and then re-execute.
SHS: ERROR: ihs69016: Failed to load at SCTL-Library. Description
An error has occurred with load processing of the library for operating SSL.
- 141 -
System processing
Processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs69017: Failed to symget at SCTL-Library. Description
An error has occurred with symbol extraction processing of the library for operating SSL.
System processing
Processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs69018: Failed to load at SCL-Library. Description
An error has occurred with load processing of the library for operating SSL.
System processing
Processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs69019: Failed to symget at SCL-Library. Description
An error has occurred with symbol extraction processing of the library for operating SSL.
System processing
Processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
- 142 -
SHS: ERROR: ihs70004: (%s1)%s2:Cannot get enough memory Description
Failed to get task memory.
Parameters
%s1: Error number%s2: Error details content
Cause
Failed to get task memory.
Action method
Close unnecessary programs.
SHS: ERROR: ihs70005: (%s1)%s2:Error writing to log file. %s3 messages lost. Description
Failed to write to the log file.
Parameters
%s1: Error number%s2: Error details content%s3: Log file message management number (internal code)
Cause
Failed to write to the log file.
Action method
Refer to %s2, and eliminate the cause of the failure.
SHS: INFO: ihs70007: Log can now be output to the log file(%s1). (%s2) Description
A log can now be output to log file %s1.
Parameters
%s1: File name%s2: Number of messages that could not be output
SHS: INFO: ihs70008: The file was rotated because the file size of the log file(%s1) reached the upperlimit of the system. Description
The file was rotated because the file size of log file %s1 reached the upper limit of the system.
Parameters
%s1: File name
SHS: ERROR: ihs70009: The log could not be output because the file size of the log file reached the upperlimit of the system.
- 143 -
Description
The log cannot be output because the file size of the log file reached the upper limit of the system.
System processing
Processing is canceled.
Cause
The log cannot be output because the file size of the log file reached the upper limit of the system.
Action method
Take action according to the following procedure:
1. Stop the communications infrastructure.
2. Back up the log file that has reached the file size upper limit of the system.
3. Start the communications infrastructure.
SHS: ERROR: ihs81501: There is already a path with the same name as the named pipe. path=%s1 [%s2] Description
There is already a path %s1 with the same name as the named pipe.
Parameters
%s1: Path name%s2: Web server name
System processing
Web server %s2 start processing is canceled.
Cause
There is already a path %s1 with the same name as the named pipe.
Action method
Either change the name of, or delete, the path %s1 file or directory, and then restart the communications infrastructure.
SHS: ERROR: ihs81502: (%s1)%s2: Failed to create the named pipe. pipe=%s3 [%s4] Description
Failed to create the named pipe %s3.
Parameters
%s1: Error number%s2: Error details content%s3: Named pipe name%s4: Web server name
System processing
[Windows]
The status display daemon is finished. Web server %s4 operations are continued.
[Linux]
Web server %s4 start processing is canceled.
- 144 -
Cause
Failed to create the named pipe %s3.
Action method
Refer to %s2, eliminate the cause of the failure, and then restart the communications infrastructure.
SHS: ERROR: ihs81503: (%s1)%s2: Failed to create the status display daemon. func=%s3 [%s4] Description
Failed to generate the status display daemon.
Parameters
%s1: Error number%s2: Error details content%s3: Function name%s4: Web server name
System processing
Web server %s4 start processing is canceled.
Cause
Failed to generate the status display daemon.
Action method
Refer to %s2, eliminate the cause of the failure, and then restart the communications infrastructure.
SHS: ERROR: ihs81504: (%s1)%s2: Failed to open the named pipe. pipe=%s3 [%s4] Description
Failed to open the named pipe %s3.
Parameters
%s1: Error number%s2: Error details content%s3: Named pipe name%s4: Web server name
System processing
The status display daemon is finished. Web server %s4 operations are continued.
Cause
Failed to open the named pipe %s3.
Action method
Refer to %s2, eliminate the cause of the failure, and then restart the communications infrastructure.
SHS: ERROR: ihs81505: An error occurred in status display processing. detail=%s1 [%s2] Description
An error has occurred with status display processing.
- 145 -
Parameters
%s1: Detailed information%s2: Web server name
System processing
Status display processing is canceled. Web server %s2 operations are continued.
Cause
An error has occurred with status display processing.
Action method
Re-execute the operation status display command (ihsdisp).
SHS: ERROR: ihs81506: An internal error occurred during status display daemon initializationprocessing. detail=%s1 Description
An internal error has occurred with status display daemon initialization processing.
Parameters
%s1: Detailed information
System processing
Web server start processing is canceled.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs81511: The user that executed the command does not have the authority to execute it. Description
The user that executed the command does not have permission to execute it.
System processing
The command terminates abnormally.
Cause
The user that executed the command does not have permission to execute it.
Action method
Re-execute the command with administrative privileges.
SHS: ERROR: ihs81512: The Web Server was not installed normally. Description
The Web server was not installed normally.
System processing
The command terminates abnormally.
- 146 -
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs81513: The "ihsdisp" command option was specified incorrectly.Usage: ihsdisp [-n WebServerName[,...]] [-a] Description
There is an error with the method used to specify the ihsdisp command option.
System processing
The command terminates abnormally.
Cause
There is an error with the method used to specify the ihsdisp command option.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs81514: (%s1)%s2: Failed to open the lock file. file=%s3 Description
Failed to open lock file %s3.
Parameters
%s1: Error number%s2: Error details content%s3: File name
System processing
The command terminates abnormally.
Cause
Failed to open lock file %s3.
Action method
Refer to %s2, eliminate the cause of the failure, and then re-execute the command.
SHS: ERROR: ihs81515: The "ihsdisp" command cannot be processed now because it is being processedfor something else. Description
The ihsdisp command is under execution in other processing, therefore processing cannot be performed.
System processing
The command terminates abnormally.
Cause
The ihsdisp command is under execution in other processing, therefore processing cannot be performed.
- 147 -
Action method
After the processing of the ihsdisp command that is under execution in the other processing has finished, re-execute the command.
SHS: ERROR: ihs81516: There is already a file or directory with the same name as the named pipe. path=%s1 Description
There is already a file or directory %s1 with the same name as the named pipe.
Parameters
%s1: Path name
System processing
The command terminates abnormally.
Cause
There is already a file or directory %s1 with the same name as the named pipe.
Action method
Either change the name of, or delete, the path %s1 file or directory, start the communications infrastructure, and then re-execute thecommand.
SHS: ERROR: ihs81517: The Web Server did not start. [%s1] Description
Web server %s1 has not been started.
Parameters
%s1: Web server name
System processing
The command terminates abnormally.
Cause
Web server %s1 has not been started.
Action method
Start Web server %s1, and then re-execute the command.
SHS: ERROR: ihs81518: (%s1)%s2: An error occurred in the named pipe operation. func=%s3, pipe=%s4 Description
An error has occurred with the named pipe %s4 operation.
Parameters
%s1: Error number (*1)%s2: Error details content (*1)%s3: Function name%s4: Named pipe name*1: %s1 and %s2 might not always be output.
- 148 -
System processing
The command terminates abnormally.
Cause
An error has occurred with the named pipe %s4 operation.
Action method
Take the following action:
- If an error message between ihs81500 and ihs81599 has been output to the event log (Windows(R)) or system log (Linux), takeaction according to the message and then re-execute the command.
- If %s1 and %s2 have not been output, re-execute the command.
If the above do not apply, refer to %s2, eliminate the cause of the failure, and then re-execute the command.
SHS: ERROR: ihs81519: Failed to get memory. Description
Failed to get memory.
System processing
The command terminates abnormally.
Cause
Failed to get memory.
Action method
Close unnecessary programs, and then re-execute the command.
SHS: ERROR: ihs81520: The Web server operating environment has not been created. Description
The Web server operating environment has not been created.
System processing
The command terminates abnormally.
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs81521: The specified Web server does not exist. [%s1] Description
The specified Web server %s1 does not exist.
Parameters
%s1: Web server name
System processing
The command terminates abnormally.
- 149 -
Cause
A system error might have occurred.
Action method
Collect the maintenance data and contact Fujitsu technical support.
SHS: ERROR: ihs81522: Internal error. detail=%s1 Description
An internal error occurred.
Parameters
%s1: Detailed information
System processing
The command terminates abnormally.
Cause
A system error might have occurred.
Action method
Re-execute the command. If this message is still output, collect the maintenance data and contact Fujitsu technical support.
SHS: WARNING: ihs90000: This product is a time limited version. Description
The trial period still applies to this product.
SHS: ERROR: ihs90001: This product had expired. Description
The trial period has expired.
Cause
The trial period has expired.
Action method
Purchase a product version.
SHS: ERROR: ihs90002: This product was not installed correctly. Description
The installation was not performed correctly.
Cause
The installation was not performed correctly.
Action method
Re-install the product.
- 150 -
2.7 Messages Starting with MpJobschFor the messages starting with MpJobsch, refer to the Systemwalker Operation Manager manuals which stored as below.
- DVD-ROM media name
Systemwalker Runbook Automation V15.0.0
- Stored directory
\manual\OMGR
In additional, if you read above manuals, replace the following word.
Systemwalker Operation Manager Systemwalker Runbook Automation
Calendar Holiday Calendar
Start day format Schedule Pattern
Job scheduler Scheduler
Job net Schedule definitionSchedule Definition name
Project Process Group name
Jobschcod swrba_change_systime
Jobschprint swrba_holexport/swrba_patternexpoprt
Jobschsetcal swrba_patternimport
Jobschsethol swrba_holimport
- 151 -
Chapter 3 Messages without Labels
3.1 Messages Relating to Installation and Uninstallation Error: %1 has already been installed. Description
Either Systemwalker Runbook Automation or a conflicting product has already been installed.
Parameters
%1: Product name
Action method
Uninstall Systemwalker Runbook Automation or the conflicting product, and then try the installation again.
Failed to copy %1 to %2. Description
Failed to copy file/directory.
Parameters
%1: Source file/directory
%2: Target file/directory
Action method
Take the following actions:
- Ensure that the user has write permission for the target file/directory and its parent.
- Ensure that the user has read permission for the source file/directory and its parent.
- Ensure that the target directory has sufficient disk space.
- Ensure that a file/directory with the same name as the target file/directory does not already exist.
Error: %1 does not exist. Description
The file/directory does not exist.
Parameters
%1: File/directory name
Action method
The file/directory might have been deleted while processing. If it exists in the /tmp directory, run the command again. Otherwise,restore the deleted file/directory or create a new one, and then run the command again.
Error: The user that is currently logged in does not have the privileges required to execute %1. Description
The user does not have enough privileges to execute the file.
- 152 -
Parameters
%1: File name
Action method
Login with administrator privileges and run the command again.
Error: The installation script for %1 has terminated abnormally. Description
The product installation script used in Systemwalker Runbook Automation has terminated abnormally.
Parameters
%1: Product name
Action method
Contact Fujitsu technical support.
Error: Failed to read %1. Description
Failed to load the file.
Parameters
%1: File name
Action method
Take the following actions:
- Ensure that the file exists.
- Ensure that the user has read permission for the file and its directory.
Error: Failed to write %1. Description
Failed to write the file.
Parameters
%1: File name
Action method
Take the following actions:
- Ensure that the user has write permission for the file and its directory.
- Ensure that target directory has sufficient disk space
- Ensure that a directory with the same name as the file does not exist.
Error: Failed to uninstall %1. Description
Failed to uninstall Systemwalker Runbook Automation or a product used in it.
- 153 -
Parameters
%1: Product or component name
Action method
Refer to the message displayed before this one and take the appropriate action.
Error: Failed to install %1. Description
Failed to install Systemwalker Runbook Automation or a product used in it.
Parameters
%1: Product or component name
Action method
Refer to the message displayed before this one and take the appropriate action.
Error: The root directory ("/") cannot be specified. Description
The root directory ("/") cannot be specified as the installation directory.
Action method
Change the installation directory.
Error: Specify a value between 1 and 65535. Description
An invalid value was specified.
Action method
Specify a value between 1 and 65535.
Error: Unable to install Systemwalker Network Communication Framework. Description
Failed to install Systemwalker Network Communication Framework.
Action method
Refer to the message displayed before this one and take the appropriate action.
Error: Unable to install Systemwalker Network Communication. Description
Failed to install Systemwalker Network Communication.
Action method
Refer to the message displayed before this one and take the appropriate action.
- 154 -
Error: Setup cancellation has not been executed. Description
Failed to uninstall because setup cancellation has not been executed.
Action method
Run setup cancellation.
Error: Not enough space for the installation. (%1) Description
There is not sufficient disk space for installation.
Parameters
%1: Mount point with insufficient disk space.
Action method
Specify a directory with enough disk space as the installation directory.
Error: This product cannot be installed on this operating system. Description
This product cannot be installed on this operating system.
Action method
Confirm the operating system which is compatible with the product, and install the product on one of the operating systems.
Error: Failed to register group '%1'. Description
Failed to register the group to the operating system has failed. Either the user does not have enough privileges to register the group orthe system is unstable.
Parameters
%1: Group name
Action method
Login with administrator privileges and run the command again. If the working directories (/var, /tmp) do not have sufficient diskspace, then extend it. If the system is unstable, then restart it.
Error: An unsupported character encoding was specified. (%1) Description
An unsupported character encoding was specified for the current system locale.
Parameters
%1: Encoding
Action method
Specify a supported character encoding. For details, refer to the Systemwalker Runbook Automation Installation Guide.
- 155 -
Error: User does not have system administrator (superuser) privileges. Description
The user does not have system administrator (superuser) privileges.
Action method
Login with administrator privileges and run the command again.
Error: Failed to create directory %1. Description
Failed to create the directory.
Parameters
%1: Directory name
Action method
Take the following actions:
- Ensure that the user has write permission for the directory and its parent.
- Ensure that the target directory has sufficient disk space.
- Ensure that a file with the same name as the target directory does not already exist.
- Ensure that the user has write permission for the directory, if the target directory already exist.
Error: The specified directory is already being used. Description
Separate directories must be specified for each installation destination.
Action method
Change the installation destination so that each installation directory is not duplicated.
Error: Specify the full path to the directory. Description
The full path of the installation directory was not specified.
Action method
Change the installation directory.
Error: The entered port number is already being used in other input field. Description
The port number is already being used.
Action method
Specify a port number not being used.
Error: An invalid character has been specified.
- 156 -
Description
An invalid character has been used in the input item.
Action method
Confirm the valid character range and update the input.
Specify a directory that already exists. Description
The installation directory must already exist.
Action method
Change the installation directory.
Error: The string is too long. (%1) Description
The text specified as the input item exceeds the size limit.
Parameters
%1: Size limit
Action method
Change the input value so that the value does not exceed the size limit.
Error: The user %1 is already registered. Description
User is already registered in the operating system.
Parameters
%1: User name
Action method
Delete the user from the operating system, because it is required for internal use by Systemwalker Runbook Automation.
This product cannot coexist with %1. Description
Unable to continue installation because the product is already installed on the server.
Parameters
%1: Product name
Action method
Uninstall the product.
Cannot be installed in this OS. Description
This product cannot be installed on this operating system.
- 157 -
Action method
Ensure that this OS is supported. For details, refer to the Systemwalker Runbook Automation Technical Guide.
Cannot uninstall because the service has not stopped. Description
The uninstallation cannot start because Systemwalker Runbook Automation service is running.
Action method
Run setup cancellation and all required procedures. For details, refer to the Systemwalker Runbook Automation Installation Guide.
Systemwalker Runbook Automation has been set up, it cannot be uninstalled. Description
Because Systemwalker Runbook Automation has been set up, it cannot be uninstalled.
Action method
See Systemwalker Runbook Automation Installation Guide, unsetup Systemwalker Runbook Automation environment, perform tasksbefore uninstallation and uninstall Systemwalker Runbook Automation.
The agent is running, it cannot be uninstalled. Description
Because the agent is running, Systemwalker Runbook Automation cannot be uninstalled.
Action method See Systemwalker Runbook Automation Installation Guide, perform tasks before uninstallation and uninstallSystemwalker Runbook Automation.
Interstage is running, it cannot be uninstalled. Description
Because Interstage is running, Systemwalker Runbook Automation cannot be uninstalled.
Action method
See Systemwalker Runbook Automation Installation Guide, perform tasks before uninstallation and uninstall Systemwalker RunbookAutomation.
Specify a maximum of 250 alphanumeric characters for password.(double quotation, blank space andthe horizontal tab may not be used. Password should start with an alphabet or a digit.) Description
Specify a maximum of 250 alphanumeric characters for password. (double quotation, \\, space and the horizontal tab may not be used.Password should start with an alphabet or a digit.)
Action method
See Systemwalker Runbook Automation Installation Guide and specify valid characters for a password.
An unsupported character encoding was specified. Description
An unsupported character encoding was specified.
- 158 -
Action method
Specify a supported character encoding. For details, refer to the Systemwalker Runbook Automation Installation Guide.
%1 has already been installed. Description
The product %1 is already installed.
Parameters
%1: Product name
Action method
No action is required.
The specified port number is already being used on operating systems. Description
The port number is already being used.
Action method
Specify another port number, because the system already uses the specified one.
An invalid port number format was specified. Description
An invalid port number format was specified.
Action method
Specify a value between 1 and 65535.
An invalid host name format was specified. Description
An invalid host name format was specified.
Action method
Change the host name.
An invalid host name or IP address format was specified. Description
An invalid host name format or IP address format was specified.
Action method
Change the host name or IP address.
Cannot install because there is not sufficient disk space. Description
Unable to install because there is not sufficient disk space.
- 159 -
Action method
Ensure that there is sufficient disk space. For details, refer to the Systemwalker Runbook Automation User Guide.
The folder is not on the local disk. Description
The specified installation directory is not on the local disk - it cannot be on a network drive or CD-ROM.
Action method
Specify a directory located on the local disk.
The folder is not a valid installation directory. Description
The installation directory must be empty.
Action method
Specify an empty folder.
Failed to register the user. Description
Failed to register the user swrbadbuser and swrbajobuser in the operating system - an invalid password might have been specified.
Action method
Take the appropriate action and start installation again.
The user is already registered.(%1) Description
User is already registered in the operating system.
Parameters
%1: User name
Action method
Delete the user from the operating system, because it is required for internal use by Systemwalker Runbook Automation, then startinstallation again.
An invalid password was specified. Description
A weak password was specified.
Action method
Specify a password that meets the security policy requirement provided by the operating system. For example, a password that is thesame as the user ID is prohibited on Windows Server 2008.
Error: Failed to initialize Interstage. Detail=%1
- 160 -
Description
Failed to initialize Interstage.
Parameters
%1: Detailed information
Action method
Take the following actions, run uninstallation, and then run the installation again.
- Ensure that the system parameters are specified correctly.
- Ensure that you can obtain IP address using the host name presented by hostname command.
It is required to register host name in hosts file or DNS server.
- Ensure that there is enough memory available.
- Refer to syslog (event log for Windows) and take the appropriate action if there is an error.
It has already been running in another process. Description
An attempt was made to start Uninstall (middleware) more than once. Alternatively, an attempt was made to start Uninstall (middleware)while the installer was starting.
Action method
End any Uninstall (middleware) that have already started. Alternatively, start Uninstall (middleware) after the installer has ended.
Specified option is invalid. Description
An invalid option was specified.
Action method
Specify valid options and run the command again.
Please enter a valid option. Description
An invalid character was entered. Valid characters are y, n, or item numbers.
Action method
Enter a valid character.
Failed to uninstall the following software packages: Description
Failed to uninstall the software listed in this message.
Action method
Confirm the information shown after this message and take the appropriate action.
Unable to uninstall the software as it is referred from more than one software.
- 161 -
Description
Failed to uninstall the software because it is used by other software.
Action method
No specific action is required.
Unable to uninstall the software as the software is mandatory. Description
Failed to uninstall the software because it is required by another program.
Action method
No specific action is required.
Internal data is broken. Description
Internal data used by this product is corrupt.
Action method
Collect the files stored in the following directories and contact Fujitsu technical support:
Linux/Solaris:
/var/opt/FJSVCIR/cir/
/etc/opt/FJSVCIR/cir/CIR.properties
Windows:
%SystemDrive%\FujitsuF4CR\cir\
%ProgramData%\Fujitsu\FujitsuF4CR\cir\ (other than Windows XP and Windows 2003)
%ALLUSERSPROFILE%\Application Data\Fujitsu\FujitsuF4CR\cir\ (Windows XP/Windows 2003)
Unable to uninstall the software you were about to uninstall as the existence of the software is aprecondition for the operation of another software. Description
Failed to uninstall the software because it is required by another program.
Action method
No specific action is required.
The program terminated abnormally. Description
The program has terminated abnormally
Action method
Collect the files stored in the following directories and contact Fujitsu technical support:
Linux/Solaris:
/var/opt/FJSVCIR/cir/
- 162 -
/etc/opt/FJSVCIR/cir/CIR.properties
Windows:
%ProgramData%\Fujitsu\FujitsuF4CR\cir\
An unexpected error has occurred during uninstall. Description
An error occurred during uninstall.
Action method
Collect the files stored in the following directories and contact Fujitsu technical support:
Linux/Solaris:
/var/opt/FJSVCIR/cir/
/etc/opt/FJSVCIR/cir/CIR.properties
Windows:
%ProgramData%\Fujitsu\FujitsuF4CR\cir\
Enter a subsystem number between 1 and 9. Description
An invalid subsystem number has been specified.
Action method
Enter a subsystem number between 1 and 9.
The host name of the machine on which you are attempting to install is incorrect. Description
The host name of the machine you are attempting to install is incorrect.
Action method
Specify a correct host name for the machine you are attempting to install.
The Scheduling must be set up. The default value for the subsystem number is already being used. Description
The subsystem number default value is already being used, therefore Scheduling must be configured.
Action method
In the Advanced Setup for Scheduling window, specify a subsystem number that is not being used.
The Scheduling must be set up. Some of the default values for the port numbers are already being used. Description
The default port is already being used in the system, therefore Scheduling must be configured.
Action method
In the Advanced Setup for Scheduling window, specify a port that is not being used in the system.
- 163 -
The Scheduling must be set up. Some of the default values for the port numbers are duplicated. Description
The default values for the port numbers are duplicated, therefore Scheduling must be configured.
Action method
In the Advanced Setup for Scheduling window, specify a port that is not being used in other input item
The specified subsystem number is already being used. Description
The subsystem creation failed because the specified subsystem number is already being used.
Action method
Specify a subsystem number that is not being used.
The Business Server function has already been installed on the Management Server, so it does not haveto be installed. Description
The Business Server function is already installed on the Management Server and so does not need to be installed.
Action method
No specific action is required.
The localhost setting of the machine on which you are attempting to install is incorrect. Description
The localhost setting of the machine on which you are attempting to install is incorrect.
Action method
- Check the /etc/hosts settings to confirm whether "localhost" has been set in IPv4 format (127.0.0.1). If it has been set in IPv6format, change the setting to IPv4 format (127.0.0.1).
- Please confirm /etc/hosts and make sure "127.0.0.1" is not set to localhostname.
Error: The specified FQDN is invalid. Description
The specified FQDN is invalid.
Action method
Specify the SSO repository FQDN which is built in the current environment and used by Interstage Single Sign-on. Refer to "UpgradingSystemwalker Runbook Automation" in the Systemwalker Runbook Automation Installation Guide for information on how to checkthe SSO repository FQDN.
Error: Failed to update the installed Management Server. Detail=%1
- 164 -
Description
Failed to update the installed Management Server because of the error shown in %1.
Parameters
%1: Error information
Action method
Take the following actions, then re-execute the command.
- Check the system log (in Windows, this is the event log), and ensure that no errors have occurred.
- Ensure that there is sufficient free memory.
If the problem persists, collect the following investigation data and contact Fujitsu technical support.
- Working area information
- Data collected using the swrba_collectinfo command (for details, refer to the Systemwalker Runbook Automation ReferenceGuide).
Error: The target product for installation does not exist. Description
Systemwalker Runbook Automation, which is the target of the installation preparation command, does not exist.
Action method
The version of Systemwalker Runbook Automation is not correct as the installation target, or this version has not been installed.
Check whether the target product for installation is installed in this environment.
Error: Systemwalker Runbook Automation has not stopped. Description
Systemwalker Runbook Automation has not stopped, therefore processing cannot continue.
Action method
Refer to the following before stopping Systemwalker Runbook Automation:
- When performing an upgrade from the previous version/level
Refer to "Upgrading from a Previous Version/Level" in the Systemwalker Runbook Automation Installation Guide, then stopSystemwalker Runbook Automation.
- When installing ServerView Resource Orchestrator Cloud Edition
Refer to "Installing ServerView Resource Orchestrator Cloud Edition" in the Systemwalker Runbook Automation InstallationGuide, then stop ServerView Resource Orchestrator.
Error: The specified working area is invalid. Detail=%1 Description
The specified working area is invalid.
Parameters
%1: Detailed error information
Action method
Possible causes are as follows. Using the detailed error information shown in %1, eliminate the cause of the error then re-execute thecommand.
- 165 -
- The directory that was specified in the working area does not exist. Create the directory beforehand, then specify it in the workingarea.
- There are already files and directories in the working area. Specify an empty, write-enabled directory.
- The path specified in the working area is not a directory path. Specify an empty, write-enabled directory.
Error: There is insufficient working area capacity. Capacity=%1 Required=%2 Description
The disk space shown in %2 is required for the working area, however only %1 is available.
Parameters
%1: Available working area disk space
%2: Required working area disk space
Action method
Secure the available disk space shown in %2, then re-execute the command.
Error: There is insufficient capacity in the installation destination. Capacity=%1 Required=%2 Description
In the installation destination, the disk space shown in %2 is required for the working area, however only %1 is available.
Parameters
%1: Available disk space in the installation destination
%2: Required disk space in the installation destination
Action method
Secure the available disk space shown in %2, then re-execute the command.
Error: Failed to back up Systemwalker Runbook Automation. Description
Failed to back up Systemwalker Runbook Automation.
Action method
Take action according to the error message that was output immediately before.
The message may be listed in 3.1 Messages Relating to Installation and Uninstallation.
Eliminate the cause of the error, specify the same working area used previously, then re-execute the command.
Error: Failed to cancel the Systemwalker Runbook Automation setup. Description
Failed to cancel the Systemwalker Runbook Automation setup.
Action method
Take action according to the error message that was output immediately before.
The message may be listed in 3.1 Messages Relating to Installation and Uninstallation.
Eliminate the cause of the error, specify the same working area used previously, then re-execute the command.
Error: Failed to update Systemwalker Runbook Automation. Description
The failure occurred while Systemwalker Runbook Automation was being uninstalled or installed.
- 166 -
Action method
Take action according to the error message that was output immediately before.
The message may be listed in 3.1 Messages Relating to Installation and Uninstallation.
Eliminate the cause of the error, specify the same working area used previously, then re-execute the command.
Error: Failed to update the Systemwalker Runbook Automation installation information. Description
Failed to update the Systemwalker Runbook Automation installation information.
Action method
Check that the installation/uninstallation of the other product has finished, then re-execute the command.
Error: Failed to set up Systemwalker Runbook Automation. Description
Failed to set up Systemwalker Runbook Automation.
Action method
Take action according to the error message that was output immediately before.
The message may be listed in 3.1 Messages Relating to Installation and Uninstallation.
Eliminate the cause of the error, specify the same working area used previously, then re-execute the command.
Error: Failed to restore Systemwalker Runbook Automation. Description
Failed to restore Systemwalker Runbook Automation.
Action method
Take action according to the error message that was output immediately before.
The message may be listed in 3.1 Messages Relating to Installation and Uninstallation.
Eliminate the cause of the error, specify the same working area used previously, then re-execute the command.
Error: Failed to stop the Interstage Application Server. Detail=%1 Description
Failed to stop the Interstage Application Server.
Parameters
%1: Error information
Action method
Using the content displayed in the error information as a reference, eliminate the cause of the error.
Once eliminated, specify the same working area used previously, then re-execute the command.
Error: Failed to back up the Interstage Application Server. Description
Failed to back up the Interstage Application Server.
Action method
If this message is output, use the error message that was output immediately before to eliminate the cause of the error. Once eliminated,specify the same working area used previously, then re-execute the command.
- 167 -
Error: Failed to restore the Interstage Application Server. Description
Failed to restore the Interstage Application Server.
Action method
If this message is output, use the error message that was output immediately before to eliminate the cause of the error. Once eliminated,specify the same working area used previously, then re-execute the command.
Error: Failed to uninstall the Interstage Application Server. Description
Failed to uninstall the Interstage Application Server.
Action method
- If the following software have been installed, stop them.
- ServerView Resource Orchestrator Cloud Edition
- Systemwalker Service Quality Coordinator
- If the windows programs such as Event Viewer, Internet Explorer and Note Pad have been started, stop them.
- Use the error message that was output immediately before to eliminate the cause of the error.
Once eliminated, specify the same working area used previously, then re-execute the command.
Error:The network environment is invalid.Target=%1 Description
The content that was set for the item shown in %1 is invalid.
Parameters
%1: Invalid item
Action method
If localhost is displayed in %1, check the following for the /etc/hosts setting.
- Check that "localhost" has been set in the IPv4 format (127.0.0.1). If it has been set in IPv6 format, change the setting to IPv4format (127.0.0.1).
- Check that a local host name has not been set for "127.0.0.1".
Error: Failed to authenticate with the LDAP server. HOST='%1' PORT='%2' USER='%3' Description
LDAP server authentication failed for the specified host, port and user.
Parameters
%1: LDAP server host name
%2: LDAP server port number
%3: Authenticated user
Action method
Take the following actions, then re-execute the command:
- Ensure that the LDAP server is running, based on the information shown in %1 and %2.
- 168 -
- Ensure that the user is registered in the LDAP server, and that the password has not been changed.
- If it is displayed on Interstage Single Sign-On setting window, repository name of SSO repository may be incorrect. Ensure thatrepository name of SSO repository which used in Single Sign-On is correct.
If the problem persists, collect investigation data using the swrba_collectinfo command (for details, refer to the Systemwalker RunbookAutomation Reference Guide) and contact Fujitsu technical support.
Error: Failed to authenticate with the LDAP server. There is an error with either the user for startingschedules or the information on the LDAP server. Description
Failed to check the user for starting schedules. The specified user for starting schedules or the LDAP server information is invalid.
Action method
Take the following actions:
- Ensure that the user name and password are correct.
- If there is an error in LDAP server information, then specify valid values for LDAP server host name, port number, directory name,organizational unit, account storage unit, administrator DN and password.
- Ensure that LDAP server is running.
Error: A function required to update the installed Management Server is not running. Function name=%1 Description
The function shown in %1 is not running.
Parameters
%1: Function that is not running
Action method
- If "Interstage" is displayed in %1, Interstage may have stopped. Execute the isstat command to check whether it is running. If itis not, start it by executing the isstart command. Refer to the Interstage Application Server manuals for information on the isstatand isstart commands.
- If "Interstage Java EE DAS" is displayed in %1, the Interstage Java EE DAS service may have stopped. Execute the ijdasstatcommand to check whether it is running. If it is not, start it by executing the ijdasstart command. Refer to the Interstage ApplicationServer manuals for information on the ijdasstat and ijdasstart commands.
- If "Interstage Java EE Node Agent" is displayed in %1, the Interstage Java EE Node Agent service may have stopped. Executethe ijnastat command to check whether it is running. If it is not, start it by executing the ijnastart command. Refer to the InterstageApplication Server manuals for information on the ijnastat and ijnastart commands.
- Check whether the Systemwalker Runbook Automation installation destination directory has sufficient disk space.
- Ensure that the system parameters are set correctly.
- Check the system log (in Windows, this is the event log), and ensure that no errors have occurred.
Error: Processing failed due to an environment problem. Detail=%1 Description
Processing failed due to an environment problem.
Parameters
%1: Error information
Action method
- Ensure that the system parameters are set correctly.
- 169 -
- Check whether the cancel setup command is running.
- Ensure that there is sufficient disk space in the installation directory.
- Ensure that there is sufficient memory.
3.2 Messages Relating to Setup and Setup Cancellation Error:An invalid command option was specified. Description
An invalid command option was specified.
Action method
Specify valid options and run the command again.
Error:User does not have enough privileges to execute the command. Description
The user does not have enough privileges to execute the command.
Action method
Login with administrator privileges and run the command again.
In Windows Server 2008 or subsequent versions, login as administrator and run the command again.
Error:Process cannot be performed because another command is running. Description
The process could not be performed because another command is running.
Action method
Wait for the command to finish and run the process again.
Error:Failed to obtain operation build setting. Description
Failed to obtain the operation build setting, which is required for setup and setup cancellation.
Action method
Take the following actions:
- Ensure that the system parameters are specified correctly.
- Ensure that there is enough memory available.
- Check whether Systemwalker Runbook Automation installation environment is corrupt. If so, uninstall Systemwalker RunbookAutomation and install it again.
Error:The specified "Process Management Database Directory" does not exist. Description
The specified directory does not exist.
- 170 -
Action method
Specify an existing directory.
Error:File with the same name as "Process Management Database Directory" already exists. Description
A file with the same name as the specified directory already exists.
Action method
Specify a different directory.
Error:An invalid value was specified in "Process Management Database Directory". Description
An invalid value was specified.
Action method
Specify a valid directory name. For details, refer to the Systemwalker Runbook Automation Installation Guide.
Error:"Process Management Database Directory" does not exist or is not empty. Description
The specified directory does not exist or is not empty.
Action method
Specify an empty existing directory. Alternatively, if the specified directory is not necessary, delete it and run the command again.
Error:An error occurred while checking the value of "Process Management Database Directory". Description
An error occurred while checking the value.
Action method
- Ensure that the value does not end with '/' or '\'.
- If there is not enough disk space or an I/O error has occurred in the directory, then either eliminate the cause of failure or specifyanother directory.
Error:"Process Management Database Communication Port" is already being used. Description
The port number, specified in "Process Management Database Communication Port", is already used by another program.
Action method
Specify another port number.
Error:An invalid value was specified in "Process Management Database Communication Port". Description
An invalid value was specified.
- 171 -
Action method
Specify a value between 1 and 65535.
Error:Password does not match "Process Management Database access account password". Description
The password does not match "Process Management Database access account password".
Action method
Specify the correct password.
Error:An invalid value was specified in "Process Management Database access account password". Description
A value with invalid characters was specified.
Action method
Specify a valid value.
Error:An invalid value was specified in "Port Number". Description
An invalid value was specified.
Action method
Specify a value between 1 and 65535.
Error:An invalid value was specified in "Host Name or IP Address". Description
An invalid value was specified.
Action method
Specify a valid value.
Error:An invalid value was specified in "Host Name". Description
An invalid value was specified.
Action method
Specify a valid value.
Error:The wrong value was specified in "Enter Administrator DN". Description
The wrong value was specified.
Action method
Specify the correct value.
- 172 -
Error:The wrong value was specified in "Enter Administrator DN". Description
The wrong value was specified.
Action method
Specify the correct value.
Error:Interstage Business Process Manager Server is not installed. Description
Interstage Business Process Manager Server is not installed - Systemwalker Runbook Automation installation might have failed, orits required program was uninstalled
Action method
Uninstall Systemwalker Runbook Automation, and then install it again.
Error:Failed to check LDAP server authentication. Description
Failed to check LDAP server authentication.
Action method
Take the following actions:
- If there is an error in LDAP server information, then specify valid values for LDAP server host name, port number, directory name,organizational unit, account storage unit, administrator DN and password.
- Ensure that LDAP server is running.
Error:Failed to authenticate a user. The user or the LDAP server information is incorrect. Description
User authentication has failed. The user or the LDAP server information is incorrect.
Action method
Take the following actions:
- Ensure that the user name and password are correct.
- If there is an error in LDAP server information, then specify valid values for LDAP server host name, port number, directory name,organizational unit, account storage unit, administrator DN and password.
- Ensure that LDAP server is running.
Error:Systemwalker Runbook Automation is not installed. Description
Systemwalker Runbook Automation is not installed - installation might have failed or its required program was uninstalled.
Action method
Install Systemwalker Runbook Automation.
- 173 -
Error:Systemwalker Runbook Automation is not setup. Description
Systemwalker Runbook Automation is not setup.
Action method
Setup Systemwalker Runbook Automation.
Error:An error occurred while setting up Systemwalker Runbook Automation. Detail=%1 Description
An error occurred while setting up Systemwalker Runbook Automation.
Parameters
%1: Error cause
Action method
Refer to the error cause and eliminate the cause of the failure.
Error:An environment for Systemwalker Runbook Automation has already been created. Description
An environment for Systemwalker Runbook Automation has already been created.
Action method
If setup needs to be performed again, then run setup cancellation for Systemwalker Runbook Automation.
Error:An environment for Systemwalker Runbook Automation has not been created. Description
An environment for Systemwalker Runbook Automation has not been created or setup was cancelled.
Action method
No specific action is required.
Error:Failed to obtain the state of Systemwalker Runbook Automation. Description
Failed to obtain the state of Systemwalker Runbook Automation.
Action method
Take the following actions:
- The Interstage Java EE DAS service might be stopped. Execute the ijdasstat command to check if the Interstage Java EE DASservice has been started. If it is stopped, execute the ijdasstart command to start it. Refer to the Interstage Application Servermanuals for information on the ijdasstat and ijdasstart commands.
- The Interstage Java EE Node Agent service might be stopped. Execute the ijnastat command to check if the Interstage Java EENode Agent service has been started. If it is stopped, execute the ijnastart command to start it. Refer to the Interstage ApplicationServer manuals for information on the ijnastat and ijnastart commands.
- The message broker might be stopped.[Windows]Select Control Panel - Administrative Tools - Services, and check if the Interstage Message Queue Broker service has been
- 174 -
started. If it is stopped, start the Interstage Message Queue Broker service from Control Panel - Administrative Tools - Services.[Linux]Execute the following command to check if the message broker has been started:/etc/init.d/ijmq01 statusIf it is stopped, execute the following command to start the message broker:/etc/init.d/ijmq01 startRefer to the Interstage Application Server manuals for information on the message broker.
- Ensure that the system parameters are specified correctly.
- Ensure that Interstage Application Server is running by issuing the isstat command - if it is not, then start it by issuing the isstartcommand.
- Ensure that LDAP server is running and network connection is available.
- Ensure that the password or group information of the user stored in LDAP and used to control process has not been changed - ifit has, then restore the values.
- Ensure that there is sufficient memory available.
- Ensure that there is sufficient disk space at Systemwalker Runbook Automation installation directory.
- Ensure that the Systemwalker Runbook Automation installation environment is not corrupt - if it is, then uninstall SystemwalkerRunbook Automation and install it again.
Error:Failed to confirm the port number. Description
Failed to confirm the port number.
Action method
Take the following actions:
- Ensure that an available port number is specified.
- Ensure that the system parameters are specified correctly.
- Ensure that there is sufficient memory available.
Error:An incorrect password was specified. Description
An invalid password was specified.
Action method
Specify the correct password.
Error:Failed to obtain LDAP settings. Description
Failed to obtain LDAP settings.
Action method
Take the following actions:
- Ensure that the system parameters are specified correctly.
- 175 -
- Ensure that there is sufficient memory available.
Error:Failed to obtain exclusive key - another command is being executed. Description
Failed to obtain exclusive key because setup or setup cancellation is running.
Action method
Wait for the setup or setup cancellation to finish, and retry.
Failed to build the Interstage Business Process Manager environment. Description
Failed to build the Interstage Business Process Manager environment.
Action method
- Ensure that there is sufficient disk space for the Process Management Database Directory and install directory.
- The Interstage Java EE DAS service might be stopped. Execute the ijdasstat command to check if the Interstage Java EE DASservice has been started. If it is stopped, execute the ijdasstart command to start it. Refer to the Interstage Application Servermanuals for information on the ijdasstat and ijdasstart commands.
- The Interstage Java EE Node Agent service might be stopped. Execute the ijnastat command to check if the Interstage Java EENode Agent service has been started. If it is stopped, execute the ijnastart command to start it. Refer to the Interstage ApplicationServer manuals for information on the ijnastat and ijnastart commands.
- Ensure that the system parameters are specified correctly.
- Ensure that LDAP server is running.
- Ensure that the user for process control and group required for running Systemwalker Runbook Automation are registered onLDAP. For details, refer to the Systemwalker Runbook Automation Installation Guide.
- Refer to syslog (event log for Windows) and take the appropriate action if there is an error.
Failed to setup Interstage Business Process Manager environment. Description
Failed to set up Interstage Business Process Manager environment.
Action method
- The hosts file settings might be incorrect. Refer to "Checking the Settings in the hosts File" in the Systemwalker RunbookAutomation Installation Guide and check that the local host name is correct.
- Ensure that there is sufficient disk space for the Process Management Database Directory and install directory.
- Ensure that the system parameters are specified correctly.
- Ensure that LDAP server is running or network with LDAP
- Ensure the user for process control and group required for running Systemwalker Runbook Automation are registered on LDAP.For details, refer to the Systemwalker Runbook Automation Installation Guide.
- Refer to syslog (event log for Windows) and take the appropriate action if there is an error.
Failed to create the Process Management Database.
- 176 -
Description
Failed to create the Process Management Database
Action method
- Ensure that the system parameters are specified correctly.
- Ensure that there is sufficient disk space for the Process Management Database Directory
- Ensure that the operating system user swrbadbuser has permission to access the Process Management Database Directory.
- Check if the operation was executed by a local computer user who has administrator privileges.
- Ensure that I/O errors do not occur on the Process Management Database Directory.
Failed to set up the CMDB environment. Description
Failed to set up the CMDB environment.
Action method
Do the following action
- Confirm that system parameter has been set correctly.
- Confirm that Interstage HTTP Server has been started. You can confirm it by ihsdisp command. If it has not been started, start itby ihsstart command or start it from Interstage Management console. For the detail of ihsdisp command and ihsstart command,refer to the Interstage Application Server manuals.
- Confirm that the space of CMDB stored directory has not sufficient.
- Confirm that I/O error has not been occurred in CMDB stored directory.
- Confirm that free memory is enough.
- Confirm that Interstage HTTP Server has been started.
- Refer to the error messages which output by command or output in systemlog (for windows, event log), obey the action to itsmessage.
Failed to obtain LDAP authentication information. Description
Obtaining LDAP authentication information has failed.
Action method
- Ensure that the system parameters are specified correctly.
- Ensure that LDAP server is running.
- Ensure the user for process control, user for schedule startup and group required for running Systemwalker Runbook Automationare registered on LDAP. For details, refer to the Systemwalker Runbook Automation Installation Guide.
Failed to delete operation component environment. Description
Failed to delete the operation component environment during setup cancellation, due to an I/O error of file lock.
- 177 -
Action method
Files could not be deleted during uninstallation because there was an I/O error or files were locked. If the following directories or filesremain after uninstallation, delete them.
[Windows]:
%SWRBA_SHARE_HOME%\rbaope
%SWRBA_HOME%\rbaope\opeparts
%SWRBA_HOME%\rbaope\work\temp\connection_method.csv
[Linux]:
/etc/opt/FJSVswrbam/share/rbaope
/var/opt/FJSVswrbam/rbaope/opeparts
/var/opt/FJSVswrbam/rbaope/work/temp/connection_method.csv
Failed to start Systemwalker Runbook Automation. Description
Failed to start Systemwalker Runbook Automation.
Action method
Take the following actions:
- Ensure that Interstage is running by issuing the isstat command.
- Ensure that the event service is running by issuing the esstart command - if it is not, then start it by issuing the esstat command.For details on the commands, refer to the Interstage Application Server manuals.
- Ensure that the system parameters are specified correctly.
- Ensure that LDAP server is running.
- Ensure the user for process control and group required for running Systemwalker Runbook Automation are registered on LDAP.For details, refer to the Systemwalker Runbook Automation Installation Guide.
- Ensure that there is sufficient memory available.
- Refer to the error message output by the command and in the syslog (event log for Windows) and take the appropriate action.
Failed to stop Systemwalker Runbook Automation. Description
Failed to stop Systemwalker Runbook Automation.
Action method
Take the following actions:
- Ensure that Interstage is running by issuing the isstat command.
- Ensure that there is sufficient memory available.
- Refer to the error message output by the command and in the syslog (event log for Windows) and take the appropriate action.
I/O error occurred. Description
An I/O error occurred while handling a file on the Systemwalker Runbook Automation installation directory.
- 178 -
Action method
Take the following actions, run setup cancellation and then setup again.
- Ensure that there is sufficient disk space.
- Ensure that sufficient memory can be allocated.
- Ensure that the user has access permission to the installation directory.
- Ensure that the disk is not damaged.
Error:Interstage is not running. Description
Interstage is not running.
Action method
Take the following actions:
- Interstage automatically starts during operating system startup. If the message appears soon after starting up the system, Interstagemay be waiting for the operating system to start. Wait until the operating system is up and running, and run the command. Useisstat command to confirm the Interstage status.
- If the message appears when the operating system is not starting up, then check whether Interstage is running by issuing the isstatcommand - if it is not, then start it by issuing the isstart command.
Error:User does not have access permission for "Process Management Directory". Description
User swrbadbuser does not have access permission for the specified directory.
Action method
Specify a directory that grants access permission to the user swrbadbuser. Note that access permission for all directories, starting fromthe root, must be granted for the user.
Error:Management server environment not configured in "Inherit File Storage Directory" Description
Management server environment is not configured in "Inherit File Storage Directory"
Action method
Take the following actions:
- If the setup for the primary node has not been done or has not finished, then run the setup.
- Ensure that the shared disk is online and that environment created on the primary node can be accessed.
Failed to obtain preliminary setup information. Description
Failed to obtain the preliminary setup information.
Action method
Take the following actions:
- 179 -
- If the information built on the primary node could not be accessed, then ensure that the Inherit File Storage Directory created onthe primary node has been specified correctly.
- Ensure that LDAP server is running and network connection is available.
- The LDAP administrator password, user password for process control/group information stored in LDAP, or password of the userfor schedule startup/group information stored in LDAP may have been changed - if they have, then restore the values.
Error:Process failed due to an environment issue. Description
Process failed due to an environment issue.
Action method
- Ensure that the system parameters are specified correctly.
- Ensure that setup cancellation command is not running.
- Ensure that there is sufficient disk space for the installation directory.
- Ensure that sufficient memory can be allocated.
Failed to create an environment for the Scheduling. Description
Failed to build the Scheduling environment.
Action method
- Ensure that there is sufficient space for the process management database storage directory, installation directory, and storagedirectory for inherited files.
- Ensure that there is sufficient memory.
- Ensure that the system parameters are set correctly.
- Check the system log (in Windows, this is the event log), and ensure that no errors have occurred.
Failed to delete an environment for the Scheduling. Description
Failed to delete the Scheduling environment.
Action method
Take the following actions:
- Ensure that there is sufficient space for the process management database storage directory, installation directory, and storagedirectory for inherited files.
- Ensure that there is sufficient memory.
- Ensure that the system parameters are set correctly.
- Check the system log (in Windows, this is the event log), and ensure that no errors have occurred.
Warning:The host name of the primary node or the secondary node has been changed. Description
The primary node or secondary node host name is different from the value specified during setup of the primary node.
- 180 -
Action method
Edit the [Systemwalker Operation Manager dir]\MPWALKER.JM\mpjmcal\etc\calcphost.def file on the primary node so that itmatches the primary node host name and secondary node host name specified on the secondary node.
Error:Failed to stop the following service. Service name=%1 Description
Failed to stop service %1.
Parameters
%1: Service name
Action method
Take the following actions:
- If Systemwalker Centric Manager is running on the machine, services shared with it must be stopped first - stop SystemwalkerOperation Manager (in Windows, poperationmgr /a, in Linux, poperationmgr -a), stop the Systemwalker Centric Manager servicethen re-execute the command.
- Ensure that there is sufficient memory.
- Ensure that there is sufficient disk space in the installation directory.
- Ensure that the system parameters are set correctly.
- Check the syslog (in Windows, the event log), and ensure that no errors have occurred.
Error:Failed to stop the following daemon. Daemon Name=%s Description
Failed to stop daemon specified in %1
Parameters
%1: Daemon name failed to stop.
Action method
Do the following action
- If operate Systemwalker Centric Manager in the same system, it is necessary to stop common daemon with Systemwalker CentricManager. Execute the following command, stop the daemon of Systemwalker Centric Manager, and execute command again.
poperationmgr -a
- Refer to system log, and confirm that error has not been occurred.
- Confirm that the capacity shortage in install directory has not been occurred.
- Confirm that system parameter has been set correctly.
- Confirm that memory shortage has not been occurred.
Error:An invalid value has been specified in Primary Node Host Name. Description
The value specified in Primary Node Host Name is invalid.
Action method
Refer to the Systemwalker Runbook Automation Installation Guide, and enter a valid host name in Primary Node Host Name.
Error:An invalid value has been specified in Secondary Node Host Name.
- 181 -
Description
The value specified in Secondary Node Host Name is invalid or the host name for the node currently set up is not included in PrimaryNode Host Name or Secondary Node Host Name.
Action method
Refer to the Systemwalker Runbook Automation Installation Guide, and enter a valid host name in Secondary Node Host Name.Additionally, ensure that the host name for the node currently set up is included in Primary Node Host Name or Secondary NodeHost Name.
Error:The same value has been specified for Primary Node Host Name and Secondary Node Host Name. Description
The same value was entered in Primary Node Host Name and Secondary Node Host Name.
Action method
Enter different values in Primary Node Host Name and Secondary Node Host Name.
Error:Failed to authenticate with the LDAP server. There is an error with either the user for startingschedules or the information on the LDAP server. Description
Failed to check the user for schedule startup because the specified user for schedule startup or LDAP server information is invalid.
Action method
Take the following actions:
- Ensure that the user name and password are correct.
- Specify the correct LDAP server host name, port number, public directory name, organizational unit, account storage unit,administrator DN and password.
- Ensure that the LDAP server is running - if it is not, then start it.
Error:The user name specified in Schedule Startup User is invalid. Description
The value specified in User for Schedule Startup is invalid.
Action method
Refer to the Systemwalker Runbook Automation Installation Guide, and enter a valid user name in [User for Schedule Startup].
Error:The password specified in Schedule Startup User Password is invalid. Description
The value specified in Password of User for Schedule Startup is invalid.
Action method
Specify the correct password.
Error:The user name specified in Process Control User or Schedule Startup User is invalid. Description
The same value was specified in User for Process Control and User for Schedule Startup.
Action method
Specify different users in User for Process Control and User for Schedule Startup.
- 182 -
Error:An invalid value was specified in User Name for the SMTP Server. Description
The value entered in SMTP server user name is invalid.
Action method
Specify the correct SMTP server user name.
Error:An invalid value was specified in User Password for the SMTP Server. Description
The value entered in SMTP server user password is invalid.
Action method
Specify the correct password.
Error:An invalid value was specified in Mail Sender. Description
The value entered in Mail sender is invalid.
Action method
Specify the correct email address.
Error:An invalid value was specified in Host Name for the Web Console URL. Description
The value entered in Web console URL host name is invalid.
Action method
Specify the correct host name.
Error:The port number specified for %1 is already being used by another system. Description
The input item port number that was specified in %1 is already being used by something else.
Parameters
%1: Name of input item
Action method
Specify a different port number.
Error:Invalid value in %1. Description
The value entered in %1 is invalid.
Parameters
%1: Name of input item
Action method
Specify the correct port number.
- 183 -
Error:The same value has been specified for %1 and %2. Description
The same value was entered in %1 and %2.
Parameters
%1: Name of input item
%2: Name of input item
Action method
The values that are entered in %1 and %2 must be different.
Error:A function required to set up Systemwalker Runbook Automation is not running. Function name=%1 Description
The function shown in %1 has not been started.
Parameters
%1: Function that has not been started
Action method
- If Interstage Java EE DAS is displayed in %1, the Interstage Java EE DAS service might be stopped. Execute the ijdasstat commandto check if the Interstage Java EE DAS service has been started. If it is stopped, execute the ijdasstart command to start it. Referto the Interstage Application Server manuals for information on the ijdasstat and ijdasstart commands.
- If Interstage Java EE Node Agent is displayed in %1, the Interstage Java EE Node Agent service might be stopped. Execute theijnastat command to check if the Interstage Java EE Node Agent service has been started. If it is stopped, execute the ijnastartcommand to start it. Refer to the Interstage Application Server manuals for information on the ijnastat and ijnastart commands.
- There might not be enough space in the Systemwalker Runbook Automation install destination directory. Check if there is sufficientspace.
- Check if the system parameters are set correctly.
- Refer to the system log (if Windows, the event log) to check if errors have occurred.
Failed to build an environment for the message broker. Description
The message broker environment build failed.
Action method
- There might not be enough space in the install destination directory. Check if there is sufficient space.
- Check if the system parameters are set correctly.
- Refer to the system log (if Windows, the event log) to check if errors have occurred.
Failed to delete the environment for the message broker. Description
Message broker environment deletion failed.
- 184 -
Action method
- There might not be enough space in the install destination directory. Check if there is sufficient space.
- Check if the system parameters are set correctly.
- Refer to the system log (if Windows, the event log) to check if errors have occurred.
Failed to build an environment for the server function. Description
The server function environment build failed.
Action method
- The Interstage Java EE DAS service might not be operating normally. Execute the ijdasstat command to check if the InterstageJava EE DAS service has started normally. Refer to the Interstage Application Server manuals for information on the ijdasstatcommand.
- The Interstage Java EE Node Agent service might not be operating normally. Execute the ijnastat command to check if the InterstageJava EE Node Agent service has been started. Refer to the Interstage Application Server manuals for information on the ijnastatcommand.
- There might not be enough space in the install destination directory. Check if there is sufficient space.
- Check if the system parameters are set correctly.
- Refer to the system log (if Windows, the event log) to check if errors have occurred.
Failed to delete the environment for the server function. Description
Server function environment deletion failed.
Action method
- The Interstage Java EE DAS service might not be operating normally. Execute the ijdasstat command to check if the InterstageJava EE DAS service has started normally. Refer to the Interstage Application Server manuals for information on the ijdasstatcommand.
- The Interstage Java EE Node Agent service might not be operating normally. Execute the ijnastat command to check if the InterstageJava EE Node Agent service has been started. Refer to the Interstage Application Server manuals for information on the ijnastatcommand.
- There might not be enough space in the install destination directory. Check if there is sufficient space.
- Check if the system parameters are set correctly.
- Refer to the system log (if Windows, the event log) to check if errors have occurred.
Failed to create the table in the Process Management Database. Description
An attempt to create a table for the Process Management Database failed.
Action method
- There is not enough space in the storage destination directory of the Process Management Database.
- Check whether an input-output error has occurred in the storage destination directory of the Process Management Database.
- Check if the system parameters are set correctly.
- 185 -
Failed to delete the table from the Process Management Database. Description
An attempt to delete a table from the Process Management Database failed.
Action method
- Check whether an input-output error has occurred in the storage destination directory of the Process Management Database.
- There is not enough space in the storage destination directory of the Process Management Database.
- Check if the system parameters are set correctly.
Error: Unable to cancel the setup, because it is referred by other software. Description
Unable to cancel the setup, because it is referred by other software.
Action method
No need to action.
3.3 Messages Relating to Starting and Stopping No get environment variable (%1) Description
Failed to obtain the environment variable.
Parameters
%1: Environment variable
Action method
Ensure that the environment variable is defined on the console where swrba_start or swrba_stop command has been used. If it is notdefined, then restart the system (because it might not have been restarted after product installation).
Error:Process failed due to an environment issue. Description
Process failed due to an environment issue.
Action method
- Ensure that the system parameters are specified correctly.
- Ensure that setup cancellation is not running.
- Ensure that there is sufficient disk space for the installation directory.
- Ensure that sufficient memory can be allocated.
Failed to confirm the startup account. Description
Failed to confirm the startup account.
- 186 -
Action method
Take the following actions:
- Ensure that the system parameters are specified correctly.
- Ensure that there is sufficient memory available.
If the problem persists, collect information by information gathering command, and contact Fujitsu technical support.
User does not have administrator privileges. Description
User does not have administrator privileges.
Action method
Login with administrator privileges and run the command again.
In Windows Server 2008 or subsequent versions, login as administrator and run the command again.
An invalid command argument was specified. Description
An invalid command argument was specified.
Action method
Specify a valid argument. For details, refer to the Systemwalker Runbook Automation Reference Guide.
Failed to confirm exclusive control status. Description
Failed to check the exclusive control status.
Action method
Take the following actions:
- Ensure that the system parameters are specified correctly.
- Ensure that there is sufficient memory available.
- Ensure that no other Systemwalker Runbook Automation command is running.
If the problem persists, collect information by information gathering command, and contact Fujitsu technical support.
Failed to obtain exclusive key - another command is being executed. Description
Failed to obtain exclusive key because another command is running.
Action method
Wait for the command to finish, and retry.
Failed to obtain the installation directory. Description
Failed to obtain the installation directory.
- 187 -
Action method
Take the following actions:
- If the operating system has not restarted after product installation, then restart it.
- Ensure that the system parameters are specified correctly.
- Ensure that there is sufficient memory available.
- Ensure that the product installation directory is not corrupt - if it is, then install the product again.
Systemwalker Runbook Automation is not setup. Description
Systemwalker Runbook Automation is not setup.
Action method
Setup Systemwalker Runbook Automation.
Systemwalker Runbook Automation startup has completed successfully. Description
Systemwalker Runbook Automation startup has completed successfully.
Action method
This message informs the progress. No action is required.
Error: Failed to authenticate with the LDAP server. HOST='%1' PORT='%2' ID='%3' Description
LDAP server authentication failed for the specified host, port and user.
Parameters
%1: LDAP server host name
%2: LDAP server port number
%3: Authenticated user
Action method
Take the following actions, then re-execute the command:
- Ensure that the LDAP server is running, based on the information shown in %1 and %2.
- Ensure that the user is registered in the LDAP server, and that the password has not been changed.
If the problem persists, collect investigation data using the swrba_collectinfo command(for details, refer to the Systemwalker RunbookAutomation Reference Guide) and contact Fujitsu technical support.
Systemwalker Runbook Automation startup has failed. Description
Systemwalker Runbook Automation startup has failed.
Action method
Take the following actions:
- 188 -
- Ensure that the system parameters are specified correctly.
- Ensure that LDAP server is running.
- Ensure that the user for process control and user group required for running Systemwalker Runbook Automation are registered onLDAP.
- Ensure that there is sufficient memory available.
- Refer to the error message output by the command and in the syslog (event log for Windows), and take the appropriate action.
Systemwalker Runbook Automation is starting up. Description
Systemwalker Runbook Automation is starting up.
Action method
This message informs the progress. No action is required.
Systemwalker Runbook Automation stop has completed successfully. Description
Systemwalker Runbook Automation stop has completed successfully.
Action method
This message informs the progress. No action is required.
Systemwalker Runbook Automation stop has failed. Description
Systemwalker Runbook Automation stop has failed.
Action method
Take the following actions:
- Ensure that there is sufficient memory available.
- Refer to the error message output by the command and in the syslog (event log for Windows), and take the appropriate action.
Systemwalker Runbook Automation is stopping. Description
Systemwalker Runbook Automation is stopping.
Action method
This message informs the progress. No action is required.
Systemwalker Runbook Automation has not been started. Description
Systemwalker Runbook Automation is not running.
Action method
Systemwalker Runbook Automation has already stopped. No action is required.
- 189 -
Systemwalker Runbook Automation has already started. Description
Systemwalker Runbook Automation has already started.
Action method
Systemwalker Runbook Automation has already started. No action is required.
The console function has started. Description
The console function has started.
Action method
This message informs the progress. No action is required.
The console function has stopped. Description
The console function has stopped.
Action method
This message informs the progress. No action is required.
Failed to check the console function start status. Description
Failed to confirm the console function status.
Action method
Take the following actions:
- The Interstage Java EE DAS service might not be operating normally. Execute the ijdasstat command to check if the InterstageJava EE DAS service has started normally. Refer to the Interstage Application Server manuals for information on the ijdasstatcommand.
- The Interstage Java EE Node Agent service might not be operating normally. Execute the ijnastat command to check if the InterstageJava EE Node Agent service has been started. Refer to the Interstage Application Server manuals for information on the ijnastatcommand.
- Ensure that the system parameters are specified correctly.
- Ensure that there is sufficient memory available.
- Refer to the error message output by the command and in the syslog (event log for Windows), and take the appropriate action.
Failed to start the console function. Description
Failed to start the console function.
Action method
Take the following actions:
- 190 -
- The Interstage Java EE DAS service might not be operating normally. Execute the ijdasstat command to check if the InterstageJava EE DAS service has started normally. Refer to the Interstage Application Server manuals for information on the ijdasstatcommand.
- The Interstage Java EE Node Agent service might not be operating normally. Execute the ijnastat command to check if the InterstageJava EE Node Agent service has been started. Refer to the Interstage Application Server manuals for information on the ijnastatcommand.
- Ensure that the system parameters are specified correctly.
- Ensure that there is sufficient memory available.
- Refer to the error message output by the command and in the syslog (event log for Windows), and take the appropriate action.
Failed to stop the console function. Description
Failed to stop the console function.
Action method
Take the following actions:
- The Interstage Java EE DAS service might not be operating normally. Execute the ijdasstat command to check if the InterstageJava EE DAS service has started normally. Refer to the Interstage Application Server manuals for information on the ijdasstatcommand.
- The Interstage Java EE Node Agent service might not be operating normally. Execute the ijnastat command to check if the InterstageJava EE Node Agent service has been started. Refer to the Interstage Application Server manuals for information on the ijnastatcommand.
- Ensure that there is sufficient memory available.
- Refer to the error message output by the command and in the syslog (event log for Windows), and take the appropriate action.
The console function has not been started. Description
Console function is not running.
Action method
Console function has already stopped. No action is required.
The console function has already started. Description
The console function has already started.
Action method
Console function has already started. No action is required.
The server function has started. Description
The server function has started.
Action method
No action is required.
- 191 -
The server function has stopped. Description
The server function has stopped.
Action method
No action is required.
Failed to check the start status of server function %1 Description
Failed to check the start status of server function %1.
Parameters
%1: Service name
Action method
Take the following actions for the service:
- The Interstage Java EE DAS service might not be operating normally. Execute the ijdasstat command to check if the InterstageJava EE DAS service has started normally. Refer to the Interstage Application Server manuals for information on the ijdasstatcommand.
- The Interstage Java EE Node Agent service might not be operating normally. Execute the ijnastat command to check if the InterstageJava EE Node Agent service has been started. Refer to the Interstage Application Server manuals for information on the ijnastatcommand.
- Ensure that the system parameters are specified correctly.
- Ensure that there is sufficient memory available.
- Ensure that LDAP server is running.
- Ensure that the user for process control and group required for running Systemwalker Runbook Automation are registered onLDAP.
- Refer to the error message output by the command and in the syslog (event log for Windows), and take the appropriate action.
After that, run swrba_stop command and then run swrba_start command to restart Systemwalker Runbook Automation.
Failed to start the server function %1 Description
Failed to start server function %1.
Parameters
%1: Service name
Action method
Take the following actions:
- The Interstage Java EE DAS service might not be operating normally. Execute the ijdasstat command to check if the InterstageJava EE DAS service has started normally. Refer to the Interstage Application Server manuals for information on the ijdasstatcommand.
- The Interstage Java EE Node Agent service might not be operating normally. Execute the ijnastat command to check if the InterstageJava EE Node Agent service has been started. Refer to the Interstage Application Server manuals for information on the ijnastatcommand.
- Ensure that the system parameters are specified correctly.
- 192 -
- Ensure that there is sufficient memory available.
- Ensure that LDAP server is running.
- Ensure that the user for process control and group required for running Systemwalker Runbook Automation are registered onLDAP.
- Refer to the error message output by the command and in the syslog (event log for Windows), and take the appropriate action.
After that, run swrba_stop command and then run swrba_start command to restart Systemwalker Runbook Automation.
If the problem persists, collect information by information gathering command, and contact Fujitsu technical support.
Failed to stop the server function. Detail=%1 Description
Failed to stop server function %1.
Parameters
%1: Service name
Action method
Take the following actions for the service:
- The Interstage Java EE DAS service might not be operating normally. Execute the ijdasstat command to check if the InterstageJava EE DAS service has started normally. Refer to the Interstage Application Server manuals for information on the ijdasstatcommand.
- The Interstage Java EE Node Agent service might not be operating normally. Execute the ijnastat command to check if the InterstageJava EE Node Agent service has been started. Refer to the Interstage Application Server manuals for information on the ijnastatcommand.
- Refer to the error message output by the command and in the syslog (event log for Windows), and take the appropriate action.
- Ensure that there is sufficient memory available.
The server function has not been started. Description
The server function has not been started.
Action method
The server function has already stopped. No action is required.
The server function has already started. Description
The server function has already started.
Action method
The server function has already started. No action is required.
Job Execution Control has started. Description
Job Execution Control has started.
- 193 -
Action method
This message informs the progress. No action is required.
Job Execution Control has stopped. Description
Job Execution Control has stopped.
Action method
This message informs the progress. No action is required.
Failed to start Job Execution Control. Description
Failed to start Job Execution Control.
Action method
Take the following actions:
- Ensure that the system parameters are specified correctly.
- Ensure that there is sufficient memory available.
- Refer to the error message output by the command and in the syslog (event log for Windows), and take the appropriate action.
Failed to check the startup status of Job Execution Control. Description
Failed to check the startup status of Job Execution Control.
Action method
Take the following actions:
- Ensure that the system parameters are specified correctly.
- Ensure that there is sufficient memory available.
- Refer to the error message output by the command and in the syslog (event log for Windows), and take the appropriate action.
Failed to stop Job Execution Control. Description
Failed to stop Job Execution Control.
Action method
Take the following actions:
- Ensure that no process is running.
- Refer to the error message output by the command and in the syslog (event log for Windows), and take the appropriate action.
- Ensure that there is sufficient memory available.
Job Execution Control has not been started.
- 194 -
Description
Job Execution Control has not been started.
Action method
Job Execution Control has already stopped. No action is required.
Job Execution Control has been started. Description
Job Execution Control has been started.
Action method
Job Execution Control has already started. No action is required.
The Scheduling has started. Description
Scheduling has started.
Action method
This is a progress message. No action is required.
The Scheduling has stopped. Description
Scheduling has stopped.
Action method
This is a progress message. No action is required.
Failed to check the startup status of the Scheduling.%1 Description
Failed to check the start status of Scheduling service %1.
Parameters
%1: Service name
Action method
Take the following actions for the service:
- Refer to the error message output by the command and in the syslog (event log for Windows) and take the appropriate action.
- Ensure that the system parameters are set correctly.
- Ensure that there is sufficient memory available.
Failed to start the Scheduling. Details=%1 Description
Failed to start Scheduling service %1.
- 195 -
Parameters
%1: Service name
Action method
Take the following actions for the service:
- Refer to the error message output by the command and in the syslog (event log for Windows) and take the appropriate action.
- Ensure that the system parameters are set correctly.
- Ensure that there is sufficient memory available.
Failed to stop the Scheduling. Details=%1 Description
Failed to stop Scheduling service %1.
Parameters
%1: Service name
Action method
Take the following actions for the service:
- Refer to the error message output by the command and in the syslog (event log for Windows) and take the appropriate action.
- Ensure that there is sufficient memory available.
The Scheduling is not running. Description
Scheduling has not been started.
Action method
Scheduling has already stopped. No action is required.
The Scheduling is already running. Description
Scheduling has already started.
Action method
Scheduling has already started. No action is required.
Failed to obtain the subsystem number. Details=%1 Description
Failed to get the subsystem number for the displayed reason.
Parameters
%1: Detailed information
- 196 -
Action method
Take the following actions:
- Ensure that there is sufficient memory available.
- Ensure that the product has been installed correctly and that the installation directory is not corrupt - if necessary, re-install theproduct.
If the problem persists, collect investigation data using the swrba_collectinfo command (for details, refer to the Systemwalker RunbookAutomation Reference Guide), and contact Fujitsu technical support.
The Process Management Database has started. Description
The Process Management Database has started.
Action method
This message informs the progress. No action is required.
The Process Management Database has stopped. Description
The Process Management Database has stopped.
Action method
This message informs the progress. No action is required.
Failed to check the Process Management Database start status. Description
Failed to check the Process Management Database start status.
Action method
Take the following actions:
- Ensure that the system parameters are specified correctly.
- Ensure that there is sufficient memory available.
- Refer to the error message output by the command and in the syslog (event log for Windows), and take the appropriate action.
- If the user swrbadbuser is not registered in the operating system or its password has been changed, then install the product again.
Failed to start the Process Management Database. Description
Failed to start the Process Management Database.
Action method
Take the following actions:
- Ensure that the system parameters are specified correctly.
- Ensure that there is sufficient memory available.
- Refer to the error message output by the command and in the syslog (event log for Windows), and take the appropriate action.
- If the user swrbadbuser is not registered in the operating system or its password has been changed, then install the product again.
- 197 -
If the problem persists, collect information by information gathering command, and contact Fujitsu technical support.
Failed to stop the Process Management Database. Description
Failed to stop the Process Management Database.
Action method
Take the following actions:
- Ensure that no process is running.
- Refer to the error message output by the command and in the syslog (event log for Windows), and take the appropriate action.
- Ensure that there is sufficient memory available.
The Process Management Database has already started. Description
The Process Management Database has already started.
Action method
Process Management Database has already started. No action is required.
The Process Management Database has not started. Description
The Process Management Database has not started.
Action method
Process Management Database has already stopped. No action is required.
CMDB Manager has started. Description
CMDB Manager has started.
Action method
This message informs the progress. No action is required.
CMDB Manager has stopped. Description
CMDB Manager has stopped.
Action method
This message informs the progress. No action is required.
Failed to check the CMDB Manager start status. Description
Failed to check the CMDB Manager start status.
- 198 -
Action method
Take the following actions:
- Ensure that the system parameters are specified correctly.
- Ensure that there is sufficient memory available.
- Refer to the error message output by the command and in the syslog (event log for Windows), and take the appropriate action.
Failed to start CMDB Manager. Description
Failed to start CMDB Manager.
Action method
Take the following actions:
- Ensure that the system parameters are specified correctly.
- Ensure that there is sufficient memory available.
- Ensure that CMDB Manager database directory does not cause I/O error.
- Refer to the error message output by the command and in the syslog (event log for Windows), and take the appropriate action.
Failed to stop CMDB Manager. Description
Failed to stop CMDB Manager.
Action method
Take the following actions:
- Ensure that all users have logged out of Systemwalker Runbook Automation.
- Ensure that no CMDB commands are running.
- Ensure that there is sufficient memory available.
CMDB Manager has already started. Description
CMDB Manager has already started.
Action method
CMDB Manager has already started. No action is required.
CMDB Manager has not started. Description
CMDB Manager has not started.
Action method
CMDB Manager has not started. No action is required.
Interstage is not running.
- 199 -
Description
Interstage is not running.
Action method
Start Interstage using isstart command.
Failed to check Interstage start status. Description
Failed to check Interstage start status.
Action method
Take the following actions:
- Ensure that the system parameters are specified correctly.
- Ensure that there is sufficient memory available.
- Refer to the error message output by the command and in the syslog (event log for Windows), and take the appropriate action.
Failed to update start information file. Description
Failed to update start information file.
Action method
Take the following actions:
- Ensure that the system parameters are specified correctly.
- Ensure that there is sufficient memory available.
- Ensure that I/O error does not occur on the Systemwalker Runbook Automation installation directory.
If the problem persists, collect information by information gathering command, and contact Fujitsu technical support.
Failed to delete start information file. Description
Failed to delete start information file.
Action method
Take the following actions:
- Ensure that the system parameters are specified correctly.
- Ensure that there is sufficient memory available.
- Ensure that I/O error did not occur on the Systemwalker Runbook Automation installation directory.
If the problem persists, collect information by information gathering command, and contact Fujitsu technical support.
Error: Process failed due to an environment issue. Description
Process has failed due to an environment issue.
- 200 -
Action method
- Ensure that the system parameters are specified correctly.
- Ensure that setup cancellation is not running.
- Ensure that there is sufficient disk space for the installation directory.
- Ensure that sufficient memory can be allocated.
Error: A function required to operate Systemwalker Runbook Automation is not running. Function name=%1 Description
The function shown in %1 has not been started.
Parameters
%1: Function that has not been started
Action method
- If Interstage Java EE DAS is displayed in %1, the Interstage Java EE DAS service might be stopped. Execute the ijdasstat commandto check if the Interstage Java EE DAS service has been started. If it is stopped, execute the ijdasstart command to start it. Referto the Interstage Application Server manuals for information on the ijdasstat and ijdasstart commands.
- If Interstage Java EE Node Agent is displayed in %1, the Interstage Java EE Node Agent service might be stopped. Execute theijnastat command to check if the Interstage Java EE Node Agent service has been started. If it is stopped, execute the ijnastartcommand to start it. Refer to the Interstage Application Server manuals for information on the ijnastat and ijnastart commands.
- If Message Broker is displayed in %1, the message broker might be stopped.[Windows]Select Control Panel >> Administrative Tools >> Services, and check if the Interstage Message Queue Broker service has beenstarted. If it is stopped, start the Interstage Message Queue Broker service from Control Panel >> Administrative Tools >>Services.[Linux]Execute the following command to check if the message broker has been started:/etc/init.d/ijmq01 statusIf it is stopped, execute the following command to start the message broker:/etc/init.d/ijmq01 startRefer to the Interstage Application Server manuals for information on the message broker.
- There might not be enough space in the Systemwalker Runbook Automation install destination directory. Check if there is sufficientspace.
- Check if the system parameters are set correctly.
- Refer to the system log (if Windows, the event log) to check if errors have occurred.
3.4 Messages Relating to Execution Status Confirmation No get environment variable (%1) Description
Failed to obtain the environment variable.
Parameters
%1: Environment variable
Action method
Ensure that the environment variable is defined on the console where swrba_status command has been used. If it is not defined, thenrestart the system (because it might not have been restarted after product installation).
- 201 -
An invalid command argument was specified. Description
An invalid command argument was specified.
Action method
Specify a valid argument. For details, refer to the Systemwalker Runbook Automation Reference Guide.
Error: Failed to authenticate with the LDAP server. HOST='%1' PORT='%2' ID='%3' Description
LDAP server authentication failed for the specified host, port and user.
Parameters
%1: LDAP server host name
%2: LDAP server port number
%3: Authenticated user
Action method
Take the following actions, then re-execute the command:
- Ensure that the LDAP server is running, based on the information shown in %1 and %2.
- Ensure that the user is registered in the LDAP server, and that the password has not been changed.
If the problem persists, collect investigation data using the swrba_collectinfo command (for details, refer to the Systemwalker RunbookAutomation Reference Guide), and contact Fujitsu technical support.
Startup status check command caused an error. Description
An error has occurred while running the startup status check command.
Action method
Take the following actions:
- The Interstage Java EE DAS service might be stopped. Execute the ijdasstat command to check if the Interstage Java EE DASservice has been started. If it is stopped, execute the ijdasstart command to start it. Refer to the Interstage Application Servermanuals for information on the ijdasstat and ijdasstart commands.
- The Interstage Java EE Node Agent service might be stopped. Execute the ijnastat command to check if the Interstage Java EENode Agent service has been started. If it is stopped, execute the ijnastart command to start it. Refer to the Interstage ApplicationServer manuals for information on the ijnastat and ijnastart commands.
- The message broker might be stopped.[Windows]Select Control Panel >> Administrative Tools >> Services, and check if the Interstage Message Queue Broker service has beenstarted. If it is stopped, start the Interstage Message Queue Broker service from Control Panel >> Administrative Tools >>Services.[Linux]Execute the following command to check if the message broker has been started:/etc/init.d/ijmq01 statusIf it is stopped, execute the following command to start the message broker:/etc/init.d/ijmq01 startRefer to the Interstage Application Server manuals for information on the message broker.
- 202 -
- Ensure that Interstage is running.
- Ensure that the system parameters are specified correctly.
- Ensure that there is sufficient memory available.
- Ensure that LDAP server is running.
- Ensure that the user for process control and group required for running Systemwalker Runbook Automation are registered onLDAP.
- Refer to the error message output by the command and in the syslog (event log for Windows), and take the appropriate action.
- Ensure that the product installation directory is not corrupt - if it is, then install the product again.
User does not have enough privileges to run the startup status check command. Description
User does not have enough privileges to run the startup status check command.
Action method
Login with administrator privileges and run the command again.
In Windows Server 2008 or subsequent versions, login as administrator and run the command again.
Systemwalker Runbook Automation is working normally. Description
Systemwalker Runbook Automation is working normally.
Action method
This message informs the current status of Systemwalker Runbook Automation. No action is required.
Systemwalker Runbook Automation is not running. Description
Systemwalker Runbook Automation is not running.
Action method
This message informs the current status of Systemwalker Runbook Automation. No action is required.
Systemwalker Runbook Automation has not been set up. Description
An environment for Systemwalker Runbook Automation has not been created.
Action method
Run setup for Systemwalker Runbook Automation.
Processes required for Systemwalker Runbook Automation are not running. Description
The followings are the possible causes:
- Systemwalker Runbook Automation is starting or closing.
- 203 -
- One or more services have terminated abnormally.
Action method
If Systemwalker Runbook Automation is starting or closing, then wait until if finishes. Otherwise, refer to syslog (event log forWindows) and confirm error has not occurred.
Error:Process failed due to an environment issue. Description
Process failed due to an environment issue.
Action method
- Ensure that the system parameters are specified correctly.
- Ensure that setup cancellation command is not running.
- Ensure that there is sufficient disk space for the installation directory.
- Ensure that sufficient memory can be allocated.
3.5 Messages Relating to Backup and Restore Systemwalker Runbook Automation backup has started. Description
The backup process has started.
Action method
This message informs the progress. No specific action is required.
Systemwalker Runbook Automation backup has completed successfully. Description
The backup process has completed successfully.
Action method
This message informs the progress. No specific action is required.
Systemwalker Runbook Automation restore has started. Description
The restore process for has started.
Action method
This message informs the progress. No specific action is required.
Systemwalker Runbook Automation restore has completed successfully. Description
The restore process has completed successfully.
- 204 -
Action method
This message informs the progress. No specific action is required.
Database backup has started. Description
The backup process has started.
Action method
This message informs the progress. No specific action is required.
Database backup has completed successfully. Description
The backup process has completed successfully.
Action method
This message informs the progress. No specific action is required.
Database restore has started. Description
The restore process has started.
Action method
This message informs the progress. No specific action is required.
Database restore has completed successfully. Description
The restore process has completed successfully.
Action method
This message informs the progress. No specific action is required.
File backup has started. Description
The backup process has started.
Action method
This message informs the progress. No specific action is required.
File backup has completed successfully. Description
The backup process has completed successfully.
Action method
This message informs the progress. No specific action is required.
- 205 -
File restore has started. Description
The restore process has started.
Action method
This message informs the progress. No specific action is required.
File restore has completed successfully. Description
The restore process has completed successfully.
Action method
This message informs the progress. No specific action is required.
Initialization of the restoration destination directory will start. Description
Deletion of unnecessary directories and files in the restoration target directory will start.
Action method
This is a progress message. No action is required.
Initialization of the restoration destination directory has finished. Description
Deletion of unnecessary directories and files in the restoration target directory has finished.
Action method
This is a progress message. No action is required.
The Systemwalker Runbook Automation environment build to the restoration destination managementserver will start. Description
The Systemwalker Runbook Automation environment on the restoration target Management Server has not been built, therefore it willstart.
Action method
This is a progress message. No action is required.
The Systemwalker Runbook Automation environment build to the restoration destination managementserver has finished. Description
The Systemwalker Runbook Automation environment build on the restoration target Management Server has finished.
Action method
This is a progress message. No action is required.
- 206 -
Deletion of the Systemwalker Runbook Automation environment from the restoration destinationmanagement server will start. Description
The previous Systemwalker Runbook Automation setup ended abnormally, therefore deletion of the Systemwalker RunbookAutomation environment from the restoration target Management Server will start.
Action method
This is a progress message. No action is required.
Deletion of the Systemwalker Runbook Automation environment from the restoration destinationmanagement server has finished. Description
The previous Systemwalker Runbook Automation setup ended abnormally, therefore the Systemwalker Runbook Automationenvironment was deleted from the restoration target Management Server.
Action method
This is a progress message. No action is required.
Backup of Scheduling has started. Description
Backup of Scheduling has started.
Action method
This is a progress message .No action is required.
Backup of Scheduling has finished. Description
Backup of Scheduling has finished.
Action method
This is a progress message. No action is required.
Restoration of Scheduling has started. Description
Restoration of Scheduling has started.
Action method
This is a progress message. No action is required.
Restoration of Scheduling has finished. Description
Restoration of Scheduling has finished.
- 207 -
Action method
This is a progress message. No action is required.
Starting to restore the Interstage Business Process Manager. Description
Restoring Interstage Business Process Manager starts.
Action method
This is a progression message. No action required.
Finished restoring the Interstage Business Process Manager. Description
Restoring Interstage Business Process Manager has normally completed.
Action method
This is a progression message. No action required.
Error:An invalid command option was specified.Usage: %1 Description
An invalid command option was specified.
Parameters
%1: Command usage
Action method
Specify valid options and run the command again.
Error:User does not have enough privileges to execute the command. Description
The user does not have enough privileges to execute the command.
Action method
Login with administrator privileges and run the command again.
In Windows Server 2008 or subsequent versions, login as administrator and run the command again.
Error:Cannot restore - backup locale is different from system locale. Description
Cannot restore because the backup locale is different from system locale.
Action method
Restore the backup on an environment that uses the same locale as the backup.
Error:Failed to backup the file.
- 208 -
Description
File backup has failed.
Action method
Take the following actions, then re-execute the command:
- Ensure that there is sufficient disk space for the destination directory for backup.
- Ensure that the user has access permission for the backup target directory.
Error:Failed to restore the file. Description
File restore has failed.
Action method
Ensure that there is sufficient disk space for the directories below and that user has access permission to them:
- Systemwalker Runbook Automation installation directory.
- Process Management Database Directory.
Error:Failed to create restore target directory.[%1] Description
Target directory creation has failed.
Parameters
%1: Directory name
Action method
Take the following actions, then re-execute the command:
- Ensure that a file does not exist with the same name as the directory - if there is, then delete the file.
- Ensure that sufficient disk space can be allocated.
Error:Failed to backup registry information. Description
Registry information backup has failed.
Action method
Collect information using information gathering command, and contact Fujitsu technical support.
Error:The specified backup target directory does not exist. Description
The specified backup target directory does not exist.
Action method
Specify an existing directory and run the command again.
- 209 -
Error:There is an error in the specified backup target path. Description
There is an error in the specified backup target path.
Action method
Specify a correct path and run the command again.
Error:Process cannot be executed - another command is running. Description
The process cannot not be executed because another command is running.
Action method
Wait for the command to finish.
Error:Backup target directory is not writable. Description
The backup target directory is not writable.
Action method
Specify a writable directory and run the command again.
Error:Backup target directory is not empty. Description
The backup target directory is not empty.
Action method
Specify an empty directory and run the command again.
Error:The backup data is incomplete Description
Restore was attempted with incomplete backup.
Action method
Take the following actions:
- There is no access permission to read from backup target directory. Ensure that the backup target directory has access permission.
- It is not backup target directory where the backup has completed or backup target directory is destroyed. Specify a backup targetdirectory where the backup has completed and run the command again. The backup data is corrupt.
Error:Systemwalker Runbook Automation has not stopped. Description
Backup and restore commands cannot be used because Systemwalker Runbook Automation has not stopped.
- 210 -
Action method
Stop Systemwalker Runbook Automation and run the backup or restore command again.
Error:An environment for Systemwalker Runbook Automation has not been created. Description
An environment for Systemwalker Runbook Automation has not been created.
Action method
Run setup and run the command again.
Error:Failed to obtain the state of Systemwalker Runbook Automation. Description
Failed to obtain the state of Systemwalker Runbook Automation.
Action method
Take the following actions:
- The Interstage Java EE DAS service might be stopped. Execute the ijdasstat command to check if the Interstage Java EE DASservice has been started. If it is stopped, execute the ijdasstart command to start it. Refer to the Interstage Application Servermanuals for information on the ijdasstat and ijdasstart commands.
- The Interstage Java EE Node Agent service might be stopped. Execute the ijnastat command to check if the Interstage Java EENode Agent service has been started. If it is stopped, execute the ijnastart command to start it. Refer to the Interstage ApplicationServer manuals for information on the ijnastat and ijnastart commands.
- The message broker might be stopped.[Windows]Select Control Panel >> Administrative Tools >> Services, and check if the Interstage Message Queue Broker service has beenstarted. If it is stopped, start the Interstage Message Queue Broker service from Control Panel >> Administrative Tools >>Services.[Linux]Execute the following command to check if the message broker has been started:/etc/init.d/ijmq01 statusIf it is stopped, execute the following command to start the message broker:/etc/init.d/ijmq01 startRefer to the Interstage Application Server manuals for information on the message broker.
- Ensure that Interstage Application Server is running by issuing the isstat command - if it is not, then start it by issuing the isstartcommand.
- Ensure that LDAP server is running and network connection is available.
- Ensure that the password or group information of the user stored in LDAP and used to control process has not been changed - ifit has, then restore the values.
- Ensure that there is sufficient disk space at Systemwalker Runbook Automation installation directory.
Error:Cannot restore - backup encoding is different from OS encoding. Description
Cannot restore because the backup encoding is different from OS encoding.
Action method
Restore the backup on an environment that uses the same encoding as the backup.
- 211 -
Error:Failed to obtain Process Management Database information. Description
Failed to obtain Process Management Database information.
Action method
- Ensure that there is sufficient disk space for the backup target directory.
- Ensure that the user has access permission for the backup target directory.
Error:The information for Process Management Database does not match in the backup environment andrestore environment. Description
Cannot restore because the information for Process Management Database does not match in the backup environment and restoreenvironment.
Action method
Specify the correct directory.
Error:Process failed due to an environment issue. Description
Process has failed due to an environment issue.
Action method
- Ensure that the system parameters are specified correctly.
- Ensure that setup cancellation command is not running.
- Ensure that there is sufficient disk space for the database stored directory for process management, installation directory, transitionfile stored directory..
- Ensure that sufficient memory can be allocated.
- Refer to the system log ( when Windows, event log), ensure that error is not been occurred.
Error:Failed to restore Interstage Business Process Manager. Description
Restoring Interstage Business Process Manager has failed.
Action method
- Check if there is enough disk space in the installation directory.
- Check if there is enough disk space in the process management database storage directory.
- Check there is an error message in the system log(in the event log for Windows).If there is an error message, follow the actionmethod of this message.
Error:Server type differs between backup environment and restore environment. Description
Server type differs between backup environment and restore environment.
- 212 -
Action method
- Perform setup with specifying server type of previous backup. Next perform restore processing.
Error:Authentication server differs between backup environment and restore environment. Description
Authentication server type differs between backup environment and restore environment.
Action method
- Perform setup with specifying the authentication server type of previous backup(Interstage single sign-on authentication server,or LDAP authentication server). Next perform restore processing.
Error:LDAP type differs between backup environment and restore environment Description
LDAP type differs between backup environment and restore environment.
Action method
- Perform setup with specifying the LDAP type of previous backup (Interstage directory service, Active Directory, or OpenLDAP).Next perform restore processing.
Error:Failure in the acquisition of the server type. Description
Obtaining the server type failed.
Action method
- An I/O error has occurred on the installation directory or the installation directory is broken. Re-install Systemwalker RunbookAutomation.
- Backup data is broken. Check the backup data.
Error:Falure in the acquisition of the authentication server type. Description
Obtaining the authentication server type failed.
Action method
- An I/O error has occurred on the installation directory or the installation directory is broken. Re-install Systemwalker RunbookAutomation.
- Backup data is broken. Check the backup data.
Error:Failure in the acquisition of the LDAP type. Description
Obtaining the LDAP type failed.
- 213 -
Action method
- An I/O error has occurred on the installation directory or the installation directory is broken. Re-install Systemwalker RunbookAutomation.
- Backup data is broken. Check the backup data.
Error:Initialization of the restoration destination directory has failed. Description
Failed to delete unnecessary directories and files in the restoration target directory.
Action method
Take action according to the error message output immediately before this one.
Error:Initialization of the restoration destination directory has failed PATH='%1' DETAIL='%2' Description
Failed to delete the restoration target directory or file - take action based on the information provided.
Parameters
%1: Directory or file
%2: Detailed information
Action method
Take the following actions, then re-execute the command:
- Ensure that the directory and file are not being used.
- Ensure that the user has enough privileges to run the command (for details, refer to the Systemwalker Runbook AutomationReference Guide).
- Ensure that there is sufficient memory available.
If the problem persists, collect investigation data using the swrba_collectinfo command (for details, refer to the Systemwalker RunbookAutomation Reference Guide), and contact Fujitsu technical support.
Error:The Systemwalker Runbook Automation environment build to the restoration destinationmanagement server has failed. Description
The Systemwalker Runbook Automation environment build to the restoration target Management Server has failed.
Action method
Take action according to the error message output immediately before this one (check if the message is mentioned in "3.2 MessagesRelating to Setup and Setup Cancellation").
If the problem persists, collect investigation data using the swrba_collectinfo command (for details, refer to the Systemwalker RunbookAutomation Reference Guide), and contact Fujitsu technical support.
Error:Deletion of the Systemwalker Runbook Automation environment from the restoration destinationmanagement server has failed. Description
Deletion of the Systemwalker Runbook Automation environment from the restoration target Management Server has failed.
- 214 -
Action method
Take action according to the error message output immediately before this one (check if the message is mentioned in "3.2 MessagesRelating to Setup and Setup Cancellation").
If the problem persists, collect investigation data using the swrba_collectinfo command (for details, refer to the Systemwalker RunbookAutomation Reference Guide), and contact Fujitsu technical support.
Error:An I/O error has occurred. PATH='%1' DETAIL='%2' Description
An I/O problem has occurred - take action based on the information provided.
Parameters
%1: Directory
%2: Detailed information
Action method
Take action based on the error message, then re-execute the command.
If the problem persists, collect investigation data using the swrba_collectinfo command (for details, refer to the Systemwalker RunbookAutomation Reference Guide), and contact Fujitsu technical support.
Error:Failed to restore a file or directory. PATH='%1' DETAIL='%2' Description
Failed to restore the file or directory - take action based on the information provided.
Parameters
%1: File or directory
%2: Detailed information
Action method
Take the following actions, then re-execute the command:
- Ensure that there is sufficient disk space for the file or directory.
- Ensure that the user has access permission for the file or directory.
- Ensure that there is sufficient memory.
If the problem persists, collect investigation data using the swrba_collectinfo command (for details, refer to the Systemwalker RunbookAutomation Reference Guide), and contact Fujitsu technical support.
Error:Failed to back up a file or directory. PATH='%1' DETAIL='%2' Description
Failed to back up the file or directory - take action based on the information provided.
Parameters
%1: File or directory
%2: Detailed information
Action method
Take the following actions, then re-execute the command:
- 215 -
- Ensure that there is sufficient disk space for the file or directory.
- Ensure that the user has access permission for the file or directory.
If the problem persists, collect investigation data using the swrba_collectinfo command (for details, refer to the Systemwalker RunbookAutomation Reference Guide), and contact Fujitsu technical support.
Error:Failed to authenticate with the LDAP server. HOST='%1' PORT='%2' USER='%3' Description
LDAP server authentication failed for the specified host, port and user.
Parameters
%1: LDAP server host name
%2: LDAP server port number
%3: User
Action method
Take the following actions, then re-execute the command:
- Ensure that the LDAP server is running, based on the information shown in %1 and %2.
- Ensure that the user is registered in the LDAP server, and that the password has not been changed.
If the problem persists, collect investigation data using the swrba_collectinfo command (for details, refer to the Systemwalker RunbookAutomation Reference Guide), and contact Fujitsu technical support.
Error:Failed to obtain information about the restoration destination environment. Description
Failed to get restoration target environment information.
Action method
Take the following actions, then re-execute the command:
- Ensure that the system parameters are set correctly.
- Ensure that there is sufficient memory available.
- Ensure that there is sufficient disk space in the Systemwalker Runbook Automation installation directory.
If the problem persists, collect investigation data using the swrba_collectinfo command (for details, refer to the Systemwalker RunbookAutomation Reference Guide), and contact Fujitsu technical support.
The stop processing for Systemwalker Runbook Automation has failed. Description
Failed to stop Systemwalker Runbook Automation.
Action method
Take the following actions:
- Ensure that Interstage is running by issuing the isstat command.
- Ensure that there is sufficient memory available.
- Refer to the error message output by the command and in the syslog (event log for Windows) and take the appropriate action.
- 216 -
If the problem persists, collect investigation data using the swrba_collectinfo command (for details, refer to the Systemwalker RunbookAutomation Reference Guide), and contact Fujitsu technical support.
Error:The specified backup cannot be used in this version. Description
The specified backup cannot be used in this version of the product.
Action method
Re-execute the command using a backup created in this version of the product.
Error:Failed to stop the following service. Service name=%1 Description
Failed to stop service %1.
Parameters
%1: Service name
Action method
Take the following actions:
- If Systemwalker Centric Manager is running on the machine, services shared with it must be stopped first - stop SystemwalkerOperation Manager (in Windows, poperationmgr /a, in Linux, poperationmgr -a), stop the Systemwalker Centric Manager servicethen re-execute the command.
- Ensure that there is sufficient memory.
- Ensure that there is sufficient disk space in the installation directory.
- Ensure that the system parameters are set correctly.
- Check the syslog (in Windows, the event log), and ensure that no errors have occurred.
Error:Failed to stop the following daemon. Daemon Name=%s Description
Failed to stop daemon specified in %1
Parameters
%1: Daemon name failed to stop.
Action method
Do the following action
- If operate Systemwalker Centric Manager in the same system, it is necessary to stop common daemon with Systemwalker CentricManager. Execute the following command, stop the daemon of Systemwalker Centric Manager, and execute command again.
poperationmgr -a
- Refer to system log, and confirm that error has not been occurred.
- Confirm that the capacity shortage in install directory has not been occurred.
- Confirm that system parameter has been set correctly.
- Confirm that memory shortage has not been occurred.
- 217 -
Error:Failed to back up Scheduling Detail=%1 Description
Failed to back up Scheduling.
Parameters
%1: Detailed information
Action method
Take the following actions, then re-execute the command:
- Ensure that there is sufficient disk space in the backup directory.
- Ensure that there are access permissions for the backup directory.
- Ensure that there is sufficient memory.
Error:Failed to restore Scheduling. Detail=%1 Description
Failed to restore Scheduling.
Parameters
%1: Detailed information
Action method
Take the following actions, then re-execute the command:
- Ensure that there is sufficient disk space in the Systemwalker Runbook Automation installation directory and in the SystemwalkerOperation Manager installation directory.
- Ensure that the user has access permissions for the Systemwalker Runbook Automation installation directory and in theSystemwalker Operation Manager installation directory.
- Ensure that there is sufficient memory.
Error:Sub system number of Scheduling differs between backup environment and restore environment. Description
Because sub system number of Scheduling differs between backup environment and restore environment, not to restore.
Action method
Confirm the sub system number of Scheduling is same in backup environment and restore environment.
Error: The port number in the backup environment and the restore environment is different. Detail=%1 Description
The port number used in %1 is different for the backup environment and the restore environment, therefore the resources cannot berestored.
Parameters
%1: Name of the item that uses the port number
- 218 -
Action method
- If "Message Broker" is displayed in %1, check whether the message broker port number is the same for the backup environmentand the restore environment.
- If "Server Function" is displayed in %1, check whether the port number used for the server function is the same for the backupenvironment and the restore environment.
- If "Web Server" is displayed in %1, check whether the Web server (Interstage HTTP Server) port number is the same for thebackup environment and the restore environment.
Error: Failed to initialize Message Broker Description
The message broker failed to initialize.
Parameters
Possible causes are as shown below. Eliminate the cause of the error, then re-execute the command.
- Check that there is sufficient free memory.
- The message broker may not be running.
[Windows]
Click Control Panel >> Administrative Tools >> Services, and check whether the Interstage Message Queue Broker service isrunning. If it is not running, click Control Panel >> Administrative Tools >> Services and start the Interstage Message QueueBroker service.
[Linux]
Execute the following command to confirm that the message broker is running:
/etc/init.d/ijmq01 status
If the message broker is not running, execute the following command to start it:
/etc/init.d/ijmq01 start
Refer to the Interstage Application Server manuals for information on the message broker.
3.6 Messages Relating to Changes in the Host Name/IP Address ERROR:An invalid command option was specified.USAGE : %1 Description
An invalid command option was specified.
Parameters
%1: Command format
Action method
Following the displayed format, specify a valid option then re-execute the command.
Error:The specified host name or IP address is invalid. Description
The specified host name or IP address is invalid.
Action method
Take the following actions:
- 219 -
- Check whether the host name or IP address format is valid.
- Check whether the host name or IP address is correct for the server that is used to run the Management Server.
Error: The specified working area is invalid. Detail=%1 Description
The specified working area is invalid.
Parameters
%1: Detailed error information
Action method
Possible causes are as follows. Using the detailed error information shown in %1, eliminate the cause of the error then re-execute thecommand.
- The directory that was specified in the working area does not exist. Create the directory beforehand, then specify it in the workingarea.
- There are already files and directories in the working area. Specify an empty, write-enabled directory.
- The path specified in the working area is not a directory path. Specify an empty, write-enabled directory.
Error: There is insufficient working area capacity. Capacity=%1 Required=%2 Description
The disk space shown in %2 is required for the working area, however only %1 is available.
Parameters
%1: Available working area disk space
%2: Required working area disk space
Action method
Secure the available disk space shown in %2, then re-execute the command.
Error:The user who is currently logged in does not have the required privileges for executing thecommand. Description
The user that executed the command does not have the required privileges for executing it.
Action method
Re-execute the command as a user with Administrator privileges.
If the operating system used is Windows Server 2008 or a subsequent version, execute the command as an Administrator.
Error:Systemwalker Runbook Automation has not stopped. Description
Systemwalker Runbook Automation has not stopped, therefore processing cannot continue.
Action method
Stop Systemwalker Runbook Automation by executing the stop command.
Error:Processing cannot be executed because another command is running. Description
Processing cannot be executed because another command is running.
- 220 -
Action method
Wait until the other command ends, then re-execute the attempted command.
Host name/IP address preprocess command completed normally. After updating the host name/IPaddress and restarting the OS, execute the host name/IP address postprocess command. Description
The host name/IP address preprocess command completed normally.
Action method
This is a progress message. No action is required.
Host name/IP address postprocess command completed normally. Description
The host name/IP address postprocess command completed normally.
Action method
This is a progress message. No action is required.
Error:Failed to execute the host name/IP address preprocess command. Description
Failed to execute the host name/IP address preprocess command.
Action method
Take the following actions, then re-execute the command:
- Check the system log (in Windows, this is the event log), and ensure that no errors have occurred.
- Ensure that there is sufficient free memory.
If the problem persists, collect the following investigation data and contact Fujitsu technical support.
- Working area information
- Data collected using the swrba_collectinfo command (for details, refer to the Systemwalker Runbook Automation ReferenceGuide).
Refer to the Systemwalker Runbook Automation Reference Guide for information on the swrba_collectinfo command.
Error:Failed to execute the host name/IP address postprocess command. Description
Failed to execute the host name/IP address postprocess command.
Action method
Take the following actions then re-execute the command:
- Check the system log (in Windows, this is the event log), and ensure that no errors have occurred.
- Ensure that there is sufficient free memory.
If the problem persists, collect the following investigation data and contact Fujitsu technical support.
- Working area information
- Data collected using the swrba_collectinfo command (for details, refer to the Systemwalker Runbook Automation ReferenceGuide).
Error:Host name/IP address preprocess command is already completed.
- 221 -
Description
The host name/IP address preprocess command is already completed.
Action method
Restart the system, then re-execute the host name/IP address postprocess command.
Error:Host name/IP address preprocess command is not completed. Description
The host name/IP address preprocess command has either not been executed, or stopped before it reached completion.
Action method
Re-execute the host name/IP address preprocess command.
Error:Not restarted after host name/IP address preprocess command. Description
Execute the host name/IP address preprocess command, then restart the system.
Action method
Restart the system.
Error:Systemwalker Runbook Automation has not been set up. Description
Systemwalker Runbook Automation has not been set up.
Action method
Wait until the Systemwalker Runbook Automation setup has finished, then re-execute the command.
Error:Failed to stop the following service. Service name=%1 Description
Failed to stop the service shown in %1.
Parameters
%1: Service name that failed to stop
Action method
Take the following actions:
- If Systemwalker Centric Manager is running on the same machine, services shared with it must be stopped first. Execute thefollowing command, stop the Systemwalker Centric Manager services then re-execute the attempted command.
poperationmgr -a
- If Interstage Single Sign-On authentication infrastructure is in use, Interstage Single Sign-On must be stopped first. Execute thefollowing command, stop Interstage Single Sign-On then re-execute the attempted command.
<Systemwalker Runbook Automation Management Server installation directory>\sso\bin\ssoclservicectl stop
- Refer to the event log and check whether an error has occurred.
- Ensure that there is sufficient disk space in the installation directory.
- Ensure that the system parameters are set correctly.
- Ensure that there is sufficient memory.
- 222 -
Error:Failed to stop the following daemon. Daemon name=%1 Description
Failed to stop the daemon shown in %1.
Parameters
%1: Daemon name that failed to stop
Action method
Take the following actions:
- If Systemwalker Centric Manager is running on the same machine, daemons shared with it must be stopped first. Execute thefollowing command, stop the Systemwalker Centric Manager daemon then re-execute the attempted command.
poperationmgr -a
- If Interstage Single Sign-On authentication infrastructure is in use, Interstage Single Sign-On must be stopped first. Execute thefollowing command, stop Interstage Single Sign-On then re-execute the attempted command.
/opt/FJSVswrbam/sso/bin/ssoclservicectl stop
- Refer to the system log and check whether an error has occurred.
- Ensure that there is sufficient disk space in the installation directory.
- Ensure that the system parameters are set correctly.
- Ensure that there is sufficient memory.
Error:Failed to start the following service. Service name=%1 Description
Failed to start the service shown in %1.
Parameters
%1: Service name that failed to start
Action method
Take the following actions:
- Refer to the event log and check whether an error has occurred.
- Ensure that there is sufficient disk space in the installation directory.
- Ensure that the system parameters are set correctly.
- Ensure that there is sufficient memory.
Error:Failed to start the following daemon. Daemon name=%1 Description
Failed to start the daemon shown in %1.
Parameters
%1: Daemon name that failed to start
Action method
Take the following actions:
- Refer to the system log and check whether an error has occurred.
- 223 -
- Ensure that there is sufficient disk space in the installation directory.
- Ensure that the system parameters are set correctly.
- Ensure that there is sufficient memory.
Error:The specified host name is different from the one previously specified. Host name=%1 Description
The specified host name is different from the one previously specified as shown in %1.
Parameters
%1: Previously specified host name
Action method
Specify the host name previously as shown in %1, then re-execute the command.
Error:The specified IP address is different from the one previously specified. IP address=%1 Description
The specified IP address is different from the one previously specified in %1.
Parameters
%1: Previously specified IP address
Action method
Specify the IP address previously as shown in %1, then re-execute the command.
Error:An I/O error has occurred. PATH='%1' DETAIL='%2' Description
The I/O problem shown in the path in %1 occurred. Take action using the detail shown in %2 as a reference.
Parameters
%1: Path of the I/O problem which occurred
%2: Detail error message
Action method
Check the content of the detail error message, eliminate the cause of the error, then re-execute the command.
If the problem persists, collect investigation data using the swrba_collectinfo command (for details, refer to the Systemwalker RunbookAutomation Reference Guide), and contact Fujitsu technical support.
Error:Processing failed because of an environment problem. Description
Processing failed because of an environment problem.
Action method
- Ensure that the system parameters are set correctly.
- Check whether the cancel setup command is running.
- Ensure that there is sufficient memory.
- Check the system log (in Windows, this is the event log), and ensure that no errors have occurred.
- 224 -
3.7 Messages Relating to the Server Account ManagementFunction
Processing is complete. Description
Processing is complete.
User was successfully registered. LogicalServer=%1 User=%2 Description
User was successfully registered in the LogicalServer.
Parameters
%1: LogicalServer
%2: User name
Error: Failed to register the user. Detail=%1 Description
Failed to register the user.
Parameters
%1: Error detail
Action method
- Ensure that there are no errors in the CSV file.
- Ensure that the specified LogicalServer exists.
- Ensure that Systemwalker Runbook Automation is running - if it is not, then start it by issuing the swrba_start command.
- Ensure that CMDB data is valid.
If the error cause cannot be identified, collect the following data and contact Fujitsu technical support:
- Messages output by the command.
- Data collected using the iscollectinfo command.
Error: Failed to output the user account information. Detail=%1 Description
Failed to output the user account information.
Parameters
%1: Error detail
Action method
- Ensure that Systemwalker Runbook Automation is running - if it is not, then start it by issuing the swrba_start command.
- Ensure that CMDB data is valid.
If the error cause cannot be identified, collect the following data and contact Fujitsu technical support:
- Messages output by the command.
- 225 -
- Data collected using the iscollectinfo command.
Failed to execute all or part of the processing. Description
Failed to execute all or part of the processing.
Action method
Refer to the error message and take the appropriate action.
Error: The user that is currently logged in does not have system administrator (superuser) privileges. Description
User cannot run the command because the user does not have administrator privileges.
Action method
If necessary, ask the system administrator to run the process.
Error: The command cannot be executed. Description
The command cannot be executed because a process that has an exclusive relation with it is running.
Action method
Wait for the process to finish and run the command again.
Error: An invalid command option was specified. Description
An invalid option was specified.
Action method
Specify a valid option and run the command again.
Error: The specified file cannot be found. File=%1 Description
The specified file cannot be found.
Parameters
%1: File name
Action method
Specify an existing file name and run the command again.
Error: Failed to set the character encoding. Detail=%1 Description
Failed to set the character encoding.
- 226 -
Parameters
%1: Error detail
Action method
Take the appropriate action and run the command again.
Error: An I/O error occurred in the file. File=%1 Detail=%2 Description
An I/O error occurred in the file.
Parameters
%1: File name
%2: Error detail
Action method
Take the appropriate action and run the command again.
Error: The file already exists. File=%1 Description
The file already exists.
Parameters
%1: File name
Action method
Specify a file that does not already exist and run the command again.
Error: An error occurred accessing CMDB. Detail=%1 Description
An error occurred accessing CMDB.
Parameters
%1: Error detail
Action method
Take the following actions, then re-execute the command:
- Ensure that Systemwalker Runbook Automation is setup.
If the error cause cannot be identified, mop up the error cause with according to error message in Detail,and then re-execute thecommand.
Error: An internal error occurred. Detail=%1 Description
An internal error occurred.
Parameters
%1: Error detail
- 227 -
Action method
Collect investigation data using the iscollectinfo command and contact Fujitsu technical support.
3.8 Messages Relating to the IPMI Information AccountManagement Function
Processing is complete. Description
Processing is complete.
IPMI information was successfully registered. LogicalServer=%1 IPAddress=%2 User=%3 Description
IPMI information was successfully registered in the LogicalServer for the IP address and the user.
Parameters
%1: LogicalServer
%2: IP address
%3: User name
ERROR: Failed to register the IPMI information. Detail=%1 Description
Failed to register the IPMI information.
Parameters
%1: Detailed information
Action method
Take the following actions:
- Ensure that the CSV file definition is valid.
- Ensure that the LogicalServer that registers the IPMI information exists.
- Ensure that Systemwalker Runbook Automation is running - if it is not, then start it by issuing the swrba_start command.
- Ensure that CMDB data is valid.
If the error cause cannot be identified, collect the following data and contact Fujitsu technical support:
- Messages output by the command.
- Data collected using the iscollectinfo command.
ERROR: Failed to output the IPMI information. Detail=%1 Description
Failed to output the IPMI information.
Parameters
%1: Detailed information
- 228 -
Action method
Take the following actions:
- Ensure that Systemwalker Runbook Automation is running - if it is not, then start it by issuing the swrba_start command.
- Ensure that CMDB data is valid.
If the error cause cannot be identified, collect the following data and contact Fujitsu technical support:
- Messages output by the command.
- Data collected using the iscollectinfo command.
Failed to execute all or part of the processing. Description
Failed to execute all or some processes.
Action method
Refer to the error message and take action.
ERROR: The user currently logged in does not have system administrator privileges. Description
User cannot run the command because the user does not have administrator privileges.
Action method
If necessary, ask the system administrator to run the process.
ERROR: The command cannot be executed. Description
The command cannot be executed because a process that has an exclusive relation with it is running.
Action method
Wait for the process to finish and run the command again.
ERROR: An invalid command option was specified. Description
An invalid option was specified.
Action method
Specify a valid option and run the command again.
ERROR: The specified file cannot be found. File=%1 Description
The specified file cannot be found.
Parameters
%1: File name
- 229 -
Action method
Specify an existing file name and run the command again.
ERROR: Failed to set the character code. Detail=%1 Description
Failed to set the character encoding.
Parameters
%1: Detailed information
Action method
Take the appropriate action and run the command again.
ERROR: An error occurred in the file I/O. File=%1 Detail=%2 Description
An I/O error occurred in the file.
Parameters
%1: File name
%2: Detailed information
Action method
Take the appropriate action and run the command again.
ERROR: The file already exists. File=%1 Description
The file already exists.
Parameters
%1: File name
Action method
Specify a file that does not already exist and run the command again.
ERROR: An internal error occurred. Detail=%1 Description
An internal error occurred.
Parameters
%1: Detailed information
Action method
Collect investigation data using the iscollectinfo command and contact Fujitsu technical support.
3.9 Messages Relating to Data Collection
- 230 -
No get environment variable (%1) Description
Failed to obtain the environment variable.
Parameters
%1: Environment variable
Action method
Ensure that the system has been restarted after Systemwalker Runbook Automation installation.
Ensure that this was not caused by value change - if it was, then restore the value.
Please Specify the material collection directory. Description
The material collection directory name was not specified.
Action method
Specify the material collection directory and run the command again.
The account check is abnormal. Description
An error occurred while checking the account.
Action method
- Ensure that the system parameters are specified correctly.
- Ensure that there is sufficient memory available .
User does not have enough privileges to execute the information gathering command. Description
User does not have enough privileges to execute the information gathering command.
Action method
Login with administrator privileges and run the command again.
In Windows Server 2008 or subsequent versions, login as administrator and run the command again.
Information was collected in %1. Description
Data has been collected and stored in the specified directory.
Parameters
%1: Directory name
Action method
This message informs the progress. No action is required.
- 231 -
Bad input parameter. Description
An invalid parameter was specified.
Action method
Specify a valid parameter and run the command again.
It failed in the information gathering. Material collection directory(%1) Description
Failed to gather information.
Parameters
%1: Directory name
Action method
The followings are the possible causes. Remove the cause of the error, and run the command again.
- Ensure that the directory exists.
- Ensure that an error has not occurred while accessing directory.
- Ensure that a file with the same name as the directory does not already exists.
- Ensure that the directory is empty.
It failed in making the collection directory. Description
Failed to create the information gathering directory because it is write-protected.
Action method
Ensure that the directory is not write-protected.
3.10 Messages Relating to Registering/Changing Password Error: User does not have enough privileges to execute the command. Description
The user does not have enough privileges to execute the command.
Action method
Login with administrator privileges and run the command again.
Error: Process cannot be executed - another command is running. Description
Failed to obtain an exclusive lock on a key has because another command is running.
Action method
Wait for the command to finish and execute the process again.
- 232 -
Error: Systemwalker Runbook Automation is not setup. Description
Systemwalker Runbook Automation is not setup.
Action method
Setup Systemwalker Runbook Automation and run the command again.
Error: Systemwalker Runbook Automation has not stopped. Description
Systemwalker Runbook automation has not stopped.
Action method
Stop Systemwalker Runbook Automation and run the backup or restore command again.
Error: The specified string cannot be used as the password. Description
The specified string cannot be used as a password because it contains invalid characters.
Action method
Specify a valid value. For details, refer to Systemwalker Runbook Automation Reference Guide.
Error: LDAP authentication failed. Description
LDAP authentication failed.
Action method
- Ensure that LDAP server is running.
- Ensure that the correct password was specified.
Error: Failed to start the Process Management DATABASE. Description
Failed to start Process Management Database.
Action method
- Ensure that the system parameters are specified correctly.
- Ensure that I/O error did not occur on the Process Management Database Directory.
- Ensure that the operating system user swrbadbuser has access permission to the Process Management Database Directory.
Error: Failed to connect to the Process Management Database. Description
Failed to connect to the Process Management Database.
- 233 -
Action method
- Ensure that the correct password was specified.
- Ensure that I/O error did not occur on the Process Management Database Directory.
- Ensure that the operating system user swrbadbuser has access permission to the Process Management Database Directory.
Error: Specified string does not match the new password. Description
The specified string does not match the new password.
Action method
Enter the new password again.
Error: Failed to obtain the state of Systemwalker Runbook Automation. Description
Failed to obtain the state of Systemwalker Runbook Automation.
Action method
- The Interstage Java EE DAS service might be stopped. Execute the ijdasstat command to check if the Interstage Java EE DASservice has been started. If it is stopped, execute the ijdasstart command to start it. Refer to the Interstage Application Servermanuals for information on the ijdasstat and ijdasstart commands.
- The Interstage Java EE Node Agent service might be stopped. Execute the ijnastat command to check if the Interstage Java EENode Agent service has been started. If it is stopped, execute the ijnastart command to start it. Refer to the Interstage ApplicationServer manuals for information on the ijnastat and ijnastart commands.
- The message broker might be stopped.[Windows]Select Control Panel - Administrative Tools - Services, and check if the Interstage Message Queue Broker service has beenstarted. If it is stopped, start the Interstage Message Queue Broker service from Control Panel - Administrative Tools - Services.[Linux]Execute the following command to check if the message broker has been started:/etc/init.d/ijmq01 statusIf it is stopped, execute the following command to start the message broker:/etc/init.d/ijmq01 startRefer to the Interstage Application Server manuals for information on the message broker.
- Ensure that Interstage Application Server is running by issuing the isstat command - if it is not, then start it by issuing the isstartcommand.
- Ensure that LDAP server is running and network connection is available.
- Ensure that the password or group information of the user stored in LDAP and used to control process has not been changed - ifit has, then restore the values.
- Ensure that there is sufficient disk space at Systemwalker Runbook Automation installation directory.
- Ensure that the Systemwalker Runbook Automation installation environment is not corrupt - if it is, then uninstall SystemwalkerRunbook Automation and install it again.
Error: Failed to register the password. Description
Failed to register the password.
- 234 -
Action method
Refer to Message Guide based on the error messages displayed before this one and take the appropriate action.
Error: Failed to change the password. Description
Failed to change the password.
Action method
Refer to Message Guide based on the error messages displayed before this one and take the appropriate action.
Error: Process failed due to an environment issue. Description
Process failed due to an environment issue.
Action method
- Ensure that the system parameters are specified correctly.
- Ensure that setup cancellation command is not running.
- Make sure that there is sufficient disk space for the installation directory.
- Ensure that sufficient memory can be allocated.
The password was successfully changed. Description
The password was successfully changed.
Action method
This message informs the progress. No action is required.
The password was successfully registered. Description
The password was successfully registered.
Action method
This message informs the progress. No action is required.
3.11 Messages Relating to Communications InfrastructureCommands
%1 : SUCCESS Description
The command process is complete.
- 235 -
Parameters
%1: Command name
System processing
The command process is complete.
%1 : FAILURE [%2] Description
An internal error occurred while running the command.
Parameters
%1: Command name
%2: Return code
System processing
The command process has aborted.
Cause
The system may be malfunctioning.
Action method
Confirm that no system malfunction (such as insufficient memory or disk fault) has not occurred.
If no system malfunction is found, contact Fujitsu technical support.
%1 : FAILURE [0x82] : You do not have execution permissions. Check the execution permissions. Description
A user without execution privileges has executed the command.
Parameters
%1: Command name
System processing
The command process has aborted.
Cause
A user without execution privileges has executed the command.
Action method
Check the privileges, and then execute the command as a user with execution privileges.
%1 : FAILURE [0x83] : Systemwalker is running. Stop Systemwalker, and then execute again. Description
The Systemwalker product is running.
Parameters
%1: Command name
- 236 -
System processing
The command process has aborted.
Cause
The Systemwalker product is running.
Action method
Stop the Systemwalker product and communications infrastructure, and then run the command again.
%1 : FAILURE [%2] : The specified file/directory is invalid. Check the specified file/directory. Description
There might be a file copy error, or an error with the directory that was specified.
Parameters
%1: Command name
%2: Return code
System processing
The command process has aborted.
Cause
There might be a file copy error, or an error with the directory that was specified.
Action method
Check whether the directory exists and has sufficient disk space, and run the process again.
3.12 Messages Relating to start history of Schedule DefinitionThis section explains the messages output by start history of Schedule Definition.
INFO: Process instance has been started. Process definition name=%1 Version=%2 Process instance ID=%3 Description
Process instance has been started according to Schedule Definition.
Parameters
%1: Process definition name
%2: Process definition version
%3: Process instance ID
ERROR:Failed to start process instance. Process definition name=%1 Version=%2 Detail = %3 Description
Process instance has been started according to Schedule Definition, but it was failed.
Parameters
%1: Process definition name to failed starting
%2: Process definition version to failed starting(if the version is not identified , '-' will be output)
%3: Detailed messages
- 237 -
System processing
Abort to start Process instance
Cause
Failed to start process instance because of the cause displayed in detailed messages.
Action method
Do action by referring detailed message
Detailed message Action method
Automated operation process group is not online. Automated operation process group is not online. Set it online status
The published process definition does not exist. Confirm that process definition has been published by referring displayedprocess definition name. If it is not be published, to do so.
Process definition has not been registered. Process definition has not been registered. Register it.
The owner of Schedule Definition does not have theprivileges for starting process.
Add privileges of process start owner to the owner of ScheduleDefinition.
User definition attribute of process definition hasbeen changed.
Update the value of user definition attribute of process definition set inSchedule Definition.
There is a possibility that Systemwalker RunbookAutomation has stopped.
Confirm that Systemwalker Runbook Automation has been started at thetime of start time of automated operation process, with referring systemlog (In Windows, event log)
And if the error has been displayed in system log (In Windows, Eventlog), do action to obey the error messages.
other than those above messages From detailed messages, identify cause and do action.
If you can not identify cause, contact Fujitsu technical support.
3.13 Messages Relating to the Interstage Single Sign-On
3.13.1 ssoclsetup Command MessagesThis section explains the messages output by the ssoclsetup command.
[Linux][0001]Parameter error : <option>[Windows][0001]Parameter error : <option> Description
The parameter in the specified command contains an error.
Action method
Check <option> in the parameter, and re-execute the command.Refer to the Systemwalker Runbook Automation Reference Guide for the parameters that can be specified.
[Linux][0002]Internal error[Windows][0002]Internal error Description
An internal error occurred while processing the command.
- 238 -
Action method
Re-execute the command. If the same message is output after re-executing the command, collect error information using theiscollectinfo command, and contact Fujitsu technical support. Also notify Fujitsu technical support of the message details.Refer to the Interstage Application Server Reference Manual (Command Edition) for information on the iscollectinfo command.
[Linux][0004]Invalid file path : <file path>[Windows][0004]Invalid file path : <file path> Description
Because an internal error occurred in the command, the attempt to obtain the path failed. The resources installed may have beendamaged.
Action method
Re-execute the command. If the same message is output after re-executing the command, install Systemwalker Runbook Automationagain, and re-execute the command.
[Linux][0005]Allocation of a memory failed[Windows][0005]Allocation of a memory failed Description
Memory allocation failed.
Action method
Close unnecessary programs, and re-execute the command.
[Linux][0006]No space in disk[Windows][0006]No space in disk Description
The disk space required to set up Interstage Single Sign-on is insufficient.
Action method
Delete unnecessary files, and re-execute the command.
[Linux][0012]File access denied : <file path>[Windows][0012]File access denied : <file path> Description
Accessing a file required to set up Interstage Single Sign-on failed. The resources installed may have been damaged.
Action method
Re-execute the command. If the same message is output after re-executing the command, install Systemwalker Runbook Automationagain, and re-execute the command.
[Linux][0017]File not found : <file path>[Windows][0017]File not found. : <file path> Description
A file required to set up Interstage Single Sign-on does not exist. The resources installed may have been damaged.
Action method
Re-execute the command. If the same message is output after re-executing the command, install Systemwalker Runbook Automationagain, and re-execute the command.
[Linux][0032]Execution is not permitted[Windows][0032]Execution is not permitted
- 239 -
Description
The command cannot be executed because the user does not have administrator privileges.
Action method
The user with the following privileges must re-execute the command:
[Windows]
The user with administrator privileges. If the operating system used is Windows Server 2008 or a subsequent version, execute thecommand as an administrator.
[Linux]
System Administrator(Superuser)
[Linux][0051]Interstage Single Sign-on package is not installed[Windows][0051]Interstage Single Sign-on package is not installed Description
The Interstage Single Sign-on package is not installed. Alternatively, the resources installed for Interstage Single Sign-on may havebeen damaged.
Action method
Install Systemwalker Runbook Automation again, and re-execute the command.
[Linux][0052]Web Server (Interstage HTTP Server) package is not installed[Windows][0052]Web server (Interstage HTTP Server) package is not installed Description
The Web server (Interstage HTTP Server) package is not installed.
Action method
Install Systemwalker Runbook Automation again, and re-execute the command.
[Linux][0053]Secure Communication Service package is not installed[Windows][0053]Secure Communication Service package is not installed Description
The Secure Communication Service package is not installed.
Action method
Install Systemwalker Runbook Automation again, and re-execute the command.
[Linux][0060]Single Sign-on server already exists[Windows][0060]Single Sign-on server already exists Description
Either the Interstage Single Sign-on repository server, authentication server, or business server has already been built on the machinewhere the command is executed.
Action method
If the pre-existing Interstage Single Sign-on server is to be used, no action is required.
To set up a new Interstage Single Sign-on, delete the pre-existing Interstage Single Sign-on server, and re-execute the command.
For information on deletion of the Interstage Single Sign-on server, refer to one of the following items depending on how the serverwas built:
- 240 -
- Built using the Interstage Management Console
Refer to "Deleting Single Sign-on" of "Operation and Maintenance" in the Interstage Application Server Single Sign-on Operator'sGuide.
- Built using this command
Set up Interstage Single Sign-on using the ssoclunsetup command.
[Linux][0069]Abnormality occurred by Web Server (Interstage HTTP Server)[Windows][0069]Abnormality occurred by Web Server (Interstage HTTP Server) Description
Interstage Single Sign-on was set up but the Interstage Single Sign-on server failed to start.
Action method
Rectify the problem by referring to the error message with a message number starting with ihs output during the execution of thiscommand. If the action method in the error message with a message number starting with ihs directs the user to refer to the systemlog, refer to an error message with a message number starting with ihs or sso, and rectify the problem.Refer to the Interstage Application Server Messages for information on error messages.
After the problem is rectified, start the Interstage Single Sign-on server which failed to start earlier. The Interstage Single Sign-onserver which failed to start earlier can be identified from the Web server name shown in the error message with a message numberstarting with ihs as follows:
- SSOauth:Repository server (update type), authentication server
- FJapache:Business server
Refer to "Starting Single Sign-on" of "Operation and Maintenance" in the Interstage Application Server Single Sign-on Operator'sGuide for information on starting the Interstage Single Sign-on server.
About messages starting with "his" or "sso", refer to the Interstage Application Server Messages.
[Linux][0072]Interstage Directory Service package is not installed[Windows][0072]Interstage Directory Service package is not installed Description
The Interstage Directory Service is not installed.
Action method
Install Systemwalker Systemwalker Runbook Automation again, and re-execute the command.
[Linux][0088]The specified SSL configuration does not exist : <SSLconf>[Windows][0088]The specified SSL configuration does not exist : <SSLconf> Description
The specified SSL definition name does not exist.
Action method
Specify the SSL definition name that exists, and re-execute the command.Check the SSL definition name using the Interstage Management Console on the System >> Security >> SSL >> View SSLConfigurations tab.
[Linux][0091]An error occurred using the system function : <detail>[Windows][0091]An error occurred using the system function : <detail> Description
An error occurred in the system function while processing the command.
- 241 -
Action method
Re-execute the command. If the same message is output after re-executing the command, collect error information using theiscollectinfo command, and contact Fujitsu technical support. Also notify Fujitsu technical support of the message details.Refer to the Interstage Application Server Reference Manual (Command Edition) for information on the iscollectinfo command.
[Linux][0092]Internal error : <detail>[Windows][0092]Internal error : <detail> Description
An internal error occurred while processing the command.
Action method
Collect error information using the iscollectinfo command, and contact Fujitsu technical support. Also notify Fujitsu technical supportof the message details.Refer to the Interstage Application Server Reference Manual (Command Edition) for information on the iscollectinfo command.
[Linux][0095]The environment variable (IS_HOME) is not set[Windows][0095]The environment variable (IS_HOME) is not set Description
The environmental variable (IS_HOME) is not set.
Action method
Install Systemwalker Runbook Automation again, and re-execute the command.
[Linux][0102]Failed to load the config file : <filename>[Windows][0102]Failed to load the config file : <filename> Description
Loading of the definition file required to set up Interstage Single Sign-on failed. The resources installed may have been damaged.
Action method
Re-execute the command. If the same message is output after re-executing the command, install Systemwalker Runbook Automationagain, and re-execute the command.
[Linux][0103]Invalid config file[Windows][0103]Invalid config file Description
Settings of the definition file required to set up Interstage Single Sign-on contain an error. The resources installed may have beendamaged.
Action method
Re-execute the command. If the same message is output after re-executing the command, install Systemwalker Runbook Automationagain, and re-execute the command.
[Linux][0114]Repository server (update system) for session management was not created[Windows][0114]Repository server (update system) for session management was not created Meaning
Settings of the repository server definition file required to set up Interstage Single Sign-on contain an error. The resources installedmay have been damaged.
Action method
Re-execute the command. If the same message is output after re-executing the command, install Systemwalker Runbook Automationagain, and re-execute the command.
- 242 -
[Linux][0135]Interstage Single Sign-on package is not installed : <server name>[Windows][0135]Interstage Single Sign-on package is not installed : <server name> Description
The Interstage Single Sign-on package is not installed. Alternatively, the resources installed for Interstage Single Sign-on may havebeen damaged.
Action method
Install Systemwalker Runbook Automation again, and re-execute the command.
[Linux][0151]Web Server (Interstage HTTP Server) already exists : <web server name>[Windows][0151]Web server (Interstage HTTP Server) already exists : <web server name> Description
The Web server (Interstage HTTP Server) <web server name> already exists.
Action method
After deleting the Web server (Interstage HTTP Server) <web server name>, re-execute the command.For details on deletion of the Web server, refer to the following items depending on how the server was built
- Built using this command or an unknown method of building
Delete the Web server using the ihsdelete command. Specify -c option in the ihsdelete command when executing it.
Refer to the Interstage Application Server Reference Manual (Command Edition) for information on the ihsdelete command.
[Linux][0152]Web Server (Interstage HTTP Server) does not exist : <web server name>[Windows][0152]Web server (Interstage HTTP Server) does not exist : <web server name> Description
The Web server (Interstage HTTP Server) <web server name> does not exist. Alternatively, the port number used by the Web serveris not 80.
Action method
Check if the Web server (Interstage HTTP Server) <web server name> has been built. Take the following action according to thebuilding status of the Web server.
- Web server has been built
Change the port number used by the Web server to 80, and re-execute the command.To change the port number, select System >> Services >> Web Server >> <web server name> >> Environment settings tab onthe Interstage Management Console, and set Port number on General settings.
- Web server has not been built
Build the Web server, and re-execute the command.
[Linux][0153]SSO Repository already exists : <repository name>[Windows][0153]SSO Repository already exists : <repository name> Description
The SSO repository <repository name> already exists.
Action method
Take the following action.
- 243 -
- Delete the SSO repository <repository name>, and re-execute the command. For details on deletion of the SSO repository, referto one of the following items depending on how the server was built:
- Built using the Interstage Management Console
Refer to "Deleting the Repository" in " Operating and Maintaining Repositories" in the Interstage Application Server DirectoryService Operator's Guide.
- Built using this command or an unknown method of building
Using ssoclunsetup command, delete SSO repository
Note
After you do action method and execute this command, but same messages been displayed again,
delete SSO repository using the Interstage Management Console.
For deleting SSO repository, refer to "Deleting the Repository" in " Operating and Maintaining Repositories" in the InterstageApplication Server Directory Service Operator's Guide.
[Linux][0154]The setup of Interstage Single Sign-on failed[Windows][0154]The setup of Interstage Single Sign-on failed Description
An attempt to set up Interstage Single Sign-on failed because an error occurred while setting up Interstage Single Sign-on.
Action method
Refer to the error message output while executing this command, and rectify the problem. After the problem is rectified, re-executethe command.The following SSO repository and Web server (Interstage HTTP Server) are used to set up Interstage Single Sign-on.
[SSO repository]
Repository name Create new Port number to be used
rep001 *1 Create new 389 *2 *3
[Web server]
Web server name Create new Port number to be used
SSOauth Create new 10443
FJapache Do not create new
(Use the existing Web server)
80
*1: The repository name when the -rn option is omitted. When the -rn option is specified, the specified repository name will be used.
*2: The port number when the -lp option is omitted. When the -lp option is specified, the specified port number will be used.
*3: When Interstage Single Sign-on setup failed due to the port number to be used by the SSO repository, the problem can be rectifiedby specifying a different port number in the -lp option.
[Linux][0155]An error occurred in the system command : <command name>[Windows][0155]An error occurred in the system command : <command name> Description
An error occurred in the system command. The cause of the error may be one of the following.
- Memory is insufficient.
- Disk space required to set up Interstage Single Sign-on is insufficient.
- 244 -
- Resources installed may have been damaged.
Action method
After taking one of the following actions, re-execute the command:
- Close unnecessary programs.
- Delete unnecessary files.
If the same message is output after taking the above actions, install Systemwalker Runbook Automation again, and re-execute thecommand.
[Linux][0156]Failed in the start of the service : <windows service name>[Windows][0156]Failed in the start of the service : <windows service name> Description
An attempt to start the service <windows service name> failed.
Action method
Refer to the error message with a message number starting with ihs, irep or sso output in the system log, and rectify the problem. Afterrectifying the problem, re-execute the command.
Refer to the Interstage Application Server Messages for information on error messages.
The following SSO repository and Web server (Interstage HTTP Server) are used to set up Interstage Single Sign-on.
[SSO repository]
Repository name Create new Port number to be used
rep001 *1 Create new 389 *2, *3
[Web server]
Web server name Create new Port number to be used
SSOauth Create new 10443
FJapache Do not create new
(Use the existing Web server)
80
*1: The repository name when the -rn option is omitted. When the -rn option is specified, the specified repository name will be used.
*2: The port number when the -lp option is omitted. When the -lp option is specified, the specified port number will be used.
*3: When Interstage Single Sign-on setup failed due to the port number to be used by the SSO repository, the problem can be rectifiedby specifying a different port number in the -lp option.
3.13.2 ssoclunsetup Command MessagesThis section explains the messages output by the ssoclunsetup command.
[Linux][0005]Allocation of a memory failed[Windows][0005]Allocation of a memory failed Description
Memory allocation failed.
Action method
Close unnecessary programs, and re-execute the command.
- 245 -
[Linux][0032]Execution is not permitted[Windows][0032]Execution is not permitted Description
The command cannot be executed because the user does not have administrator privileges.
Action method
The user with the following privileges must re-execute the command:
[Windows]
The user with administrator privileges. When you use on Windows Server 2008 or a subsequent version, execute as an administrator.
[Linux]
System Administrator (Superuser)
[Linux][0051]Interstage Single Sign-on package is not installed[Windows][0051]Interstage Single Sign-on package is not installed Description
The Interstage Single Sign-on package is not installed.
Action method
Interstage Single Sign-on cannot be removed using this command. Take one of the following actions:
- To set up Interstage Single Sign-on again
Install Systemwalker Runbook Automation again.
- Not to operate Interstage Single Sign-on
Uninstall Systemwalker Runbook Automation.
[Linux][0052]Web Server (Interstage HTTP Server) package is not installed[Windows][0052]Web server (Interstage HTTP Server) package is not installed Description
The Web server (Interstage HTTP Server) package is not installed.
Action method
Interstage Single Sign-on cannot be removed using this command. Take one of the following actions:
- To set up Interstage Single Sign-on again
Install Systemwalker Runbook Automation again.
- Not to operate Interstage Single Sign-on
Uninstall Systemwalker Runbook Automation.
[Linux][0072]Interstage Directory Service package is not installed[Windows][0072]Interstage Directory Service package is not installed Description
The Interstage Directory Service is not installed.
Action method
Interstage Single Sign-on cannot be removed using this command. Take one of the following actions:
- 246 -
- To set up Interstage Single Sign-on again
Install Systemwalker Runbook Automation again.
- Not to operate Interstage Single Sign-on
Uninstall Systemwalker. Runbook Automation
[Linux][0091]An error occurred using the system function : <detail>[Windows][0091]An error occurred using system function : <detail> Description
An error occurred in the system function while processing the command.
Action method
Re-execute the command. If the same message is output after re-executing the command, collect error information using theiscollectinfo command, and contact Fujitsu technical support. Also notify Fujitsu technical support of the message details.
Refer to the Interstage Application Server Reference Manual (Command Edition) for information on the iscollectinfo command.
[Linux][0095]The environment variable (IS_HOME) is not set[Windows][0095]The environment variable (IS_HOME) is not set Description
The environment variable (IS_HOME) is not set.
Action method
Interstage Single Sign-on cannot be removed using this command. Take one of the following actions:
- To set up Interstage Single Sign-on again
Install Systemwalker Runbook Automation again.
- Not to operate Interstage Single Sign-on
Uninstall Systemwalker Runbook Automation.
[Linux][0157]The unsetup of Interstage Single Sign-on failed[Windows][0157]The unsetup of Interstage Single Sign-on failed Description
An attempt to remove Interstage Single Sign-on failed because an error occurred while performing removal of Interstage Single Sign-on.
Action method
After taking one of the following actions, re-execute the command:
- When an error message with a message number starting with ihs or irep is output, refer to the error message and rectify the problem.If the action method in the error message directs the user to refer to the system log, refer to the error message with a messagenumber starting with ihs or irep output to the system log, and rectify the problem.
Refer to the Interstage Application Server Messages for information on error messages.
- Refer to an error message with a message number starting with ihs or irep output to the system log, and rectify the problem.
- If an error message output indicates that file access had failed, check if the file is not used by another application etc. If used, stopthat application.
- Close unnecessary programs.
- 247 -
- Delete unnecessary files.
If the same message is output after taking the above action, take one of the following actions:
- To set up Interstage Single Sign-on again
Install Systemwalker Runbook Automation again.
- Not to operate Interstage Single Sign-on
Uninstall Systemwalker Runbook Automation.
3.13.3 ssoclservicectl Command MessagesIt explains the message that the ssoclservicectl command outputs.
[Linux][0001]Parameter error : <option>[Windows][0001]Parameter error : <option> Description
The specified parameter is incorrect.
Action method
Check the <option> parameter, then re-execute the command.
Refer to the Systemwalker Runbook Automation Reference Guide for parameters that can be specified.
[Linux][0005]Allocation of a memory failed[Windows][0005]Allocation of a memory failed Description
Memory could not be allocated.
Action method
Close all programs no longer needed, then re-execute the command.
[Linux][0032]Execution is not permitted[Windows][0032]Execution is not permitted Description
You cannot execute the command because you do not have administrator permission.
Action method
Re-execute the command as a user with the following permission.
[Windows]
User who has administrator authority. If the operating system used is Windows Server 2008 or a subsequent version, execute thecommand as an administrator.
[Linux]
Super user
[Linux][0051]Interstage Single Sign-on package is not installed[Windows][0051]Interstage Single Sign-on package is not installed Description
The Interstage Single Sign-on package is not installed or the Interstage Single Sign-on package resource is corrupt.
- 248 -
Action method
It is not possible to start or stop services concerning Interstage Single Sign-on by this command. Reinstall Systemwalker RunbookAutomation, and execute it again.
[Linux][0052]Web Server (Interstage HTTP Server) package is not installed[Windows][0052]Web Server (Interstage HTTP Server) package is not installed Description
The Web Server (Interstage HTTP Server) package is not installed.
Action method
It is not possible to start or stop services concerning Interstage Single Sign-on by this command. Reinstall Systemwalker RunbookAutomation and execute it again.
[Linux][0054]Authentication server is not created[Windows][0054]Authentication server is not created Description
The authentication server of the Interstage Single Sign-on has not been set up.
Action method
Re-execute the command again on the machine where the environmental construction command (ssoclsetup) of the Interstage SingleSign-on system was executed. Refer to the Systemwalker Runbook Automation Reference Guide for ssoclsetup command.
[Linux][0057]Business server is not created[Windows][0057]Business server is not created Description
The business server of the Interstage Single Sign-on has not been set up.
Action method
Re-execute the command again on the machine where the environmental construction command (ssoclsetup) of the Interstage SingleSign-on system was executed. Refer to the Systemwalker Runbook Automation Reference Guide for ssoclsetup command.
[Linux][0072]Interstage Directory Service package is not installed[Windows][0072]Interstage Directory Service package is not installed Description
Interstage Directory Service package is not installed.
Action method
It is not possible to start or stop services concerning Interstage Single Sign-on by this command. Reinstall Systemwalker RunbookAutomation, and execute it again.
[Linux][0091]An error occurred using the system function : <detail>[Windows][0091]An error occurred using the system function : <detail> Description
An error occurred in the system function during processing.
Action method
Re-execute. If the message is still output, use iscollectinfo command to collect diagnostic information, then contact your serviceengineer. Also inform the notified message to the service engineer.Refer to the Interstage Application Server Reference Manual (Command Edition) for the iscollectinfo command.
- 249 -
[Linux][0095]The environment variable (IS_HOME) is not set[Windows][0095]The environment variable (IS_HOME) is not set Description
The environment variable (IS_HOME) is not set.
Action method
It is not possible to start or stop services concerning Interstage Single Sign-on by this command. Reinstall Systemwalker RunbookAutomation and execute it again.
[Linux][0113]Repository server was not created[Windows][0113]Repository server was not created Description
The repository server of the Interstage Single Sign-on has not been set up.
Action method
Re-execute the command again on the machine where the environmental construction command (ssoclsetup) of the single Interstagesign-on system was executed. Refer to the Systemwalker Runbook Automation Reference Guide for ssoclsetup command.
[Linux][0128]A necessary configuration item does not exit[Windows][0128]A necessary configuration item does not exit Description
A configuration item required for starting and stopping services concerning operation of Interstage Single Sign-on does not exist.
Action method
Use iscollectinfo command to collect diagnostic information, then contact your service engineer. Also inform the notified message tothe service engineer.
Refer to the "Interstage Application Server Reference Manual (Command Edition)" for the iscollectinfo command.
[Linux][0167]Interstage Operation Tool package is not installed[Windows][0167]Interstage Operation Tool package is not installed Description
Interstage Operation Tool package is not installed.
Action method
It is not possible to start or stop services concerning Interstage Single Sign-on by this command. Reinstall Systemwalker RunbookAutomation , and execute it again.
3.13.4 ssoclbackup Command MessagesIt explains the message that the ssoclbackup command outputs.
[Linux][0002]Internal error[Windows][0002]Internal error Description
An internal error occurred during processing the command.
Action method
Re-execute. If the message is still output, use the iscollectinfo command to collect diagnostic information, then contact your serviceengineer. Also inform the notified message to the service engineer.
Refer to the "Interstage Application Server Reference Manual (Command Edition)" for the iscollectinfo command.
- 250 -
[Linux][0003]System function detect error[Windows][0003]System function detect error Description
An error occurred in the system function during processing.
[Windows]
A file name or directory name consisting of 260 bytes or more exists or a path exceeding 520 bytes exists.
Action method
[Windows]
Check if an incorrect path (such as a file name or directory name of 260 bytes or more or a path exceeding 520 bytes) exists in thefollowing directories:
- <Interstage Application Server install folder>\F3FMsso\ssoatzag\conf
- <Interstage Application Server install folder>\F3FMsso\ssoatzag\pub\template
- <Interstage Application Server install folder>\F3FMsso\ssoatcag\conf
- <Interstage Application Server install folder>\F3FMsso\ssoatcag\pub\template
- <Interstage Application Server install folder >\F3FMsso\ssoatcag\webapps\winauth\custom\page
- <Interstage Application Server install folder >\F3FMsso\ssoatcag\webapps\winauth\WEB-INF
- <Interstage Application Server install folder >\F3FMsso\ssofsv\conf
- <Interstage Application Server install folder >\F3FMsso\ssofsv\webapps\ssofsv\custom
- <Interstage Application Server install folder >\F3FMsso\ssoatcsv\conf
If there is not an incorrect path, re-execute. If the message is still output, use the iscollectinfo command to collect investigationinformation, then contact your service engineer. Also inform the notified message to the service engineer.Refer to the Interstage Application Server Reference Manual (Command Edition) for the iscollectinfo command.
[Linux]
Re-execute. If the message is still output, use the iscollectinfo command to collect investigation information, then contact your serviceengineer. Also inform the notified message to the service engineer. Refer to the Interstage Application Server Reference Manual(Command Edition) for the iscollectinfo command.
[Linux][0004]Invalid file path : <file path>[Windows][0004]Invalid file path : <file path> Description
The backup directory < file path > is invalid.
Action method
Check the parameter (backup directory) and execute it again.
Refer to the Systemwalker Runbook Automation Reference Guide for the parameter(backup directory).
[Linux][0005]Allocation of a memory failed[Windows][0005]Allocation of a memory failed Description
Memory could not be allocated.
Action method
Close all programs no longer needed, then re-execute the command.
- 251 -
[Linux][0006]No space in disk[Windows][0006]No space in disk Description
There is not enough disk space for backing up the Interstage Single Sign-on.
Action method
Delete unnecessary files and then re-execute.
[Linux][0012]File access denied : <file path>[Windows][0012]File access denied : <file path> Description
Possible causes of the error are as follows:
- There is no access authority for file < file path >.
[Windows]
- A DOS device name may have been used for the backup directory.
Action method
Take the following action, and then re-execute.
- Check whether the file < file path > is being used by another application.
[Windows]
- If a DOS device name was used for the backup directory, specify a different path with the DOS device name.
[Linux][0032]Execution is not permitted[Windows][0032]Execution is not permitted Description
You cannot execute the command because you do not have administrator permission.
Action method
Re-execute the command as a user with the following permission.
[Windows]
User who has administrator authority
If your operating system is Windows Server 2008 or a subsequent version, execute as an administrator.
[Linux]
Super user
[Linux][0051]Interstage Single Sign-on package is not installed[Windows][0051]Interstage Single Sign-on package is not installed Description
The Interstage Single Sign-on package is not installed or the Interstage Single Sign-on package resource is corrupt.
Action method
Reinstall Systemwalker Runbook Automation, and execute it again.
[Linux][0052]Web Server (Interstage HTTP Server) package is not installed[Windows][0052]Web Server (Interstage HTTP Server) package is not installed
- 252 -
Description
Web Server (Interstage HTTP Server) package is not installed
Action method
Reinstall Systemwalker Runbook Automation, and execute it again.
[Linux][0053]Secure Communication Service package is not installed[Windows][0053]Secure Communication Service package is not installed Description
Secure Communication Service package is not installed.
Action method
Reinstall Systemwalker Runbook Automation . and execute it again.
[Linux][0054]Authentication server is not created[Windows][0054]Authentication server is not created Description
The authentication server of the Interstage Single Sign-on has not been set up on the machine used to perform backup.
Action method
Re-execute the command again on the machine where the environmental construction command (ssoclsetup) of the Interstage SingleSign-on system was executed. Refer to the Systemwalker Runbook Automation Reference Guide for ssoclsetup command.
[Linux][0057]Business server is not created[Windows][0057]Business server is not created Description
The business server of the Interstage Single Sign-on has not been set up.
Action method
Re-execute the command again on the machine where the environmental construction command (ssoclsetup) of the Interstage SingleSign-on system was executed. Refer to the Systemwalker Runbook Automation Reference Guide for ssoclsetup command.
[Linux][0072]Interstage Directory Service package is not installed[Windows][0072]Interstage Directory Service package is not installed Description
Interstage Directory Service package is not installed.
Action method
Reinstall Systemwalker Runbook Automation, and execute it again.
[Linux][0091]An error occurred using the system function : <detail>[Windows][0091]An error occurred using the system function : <detail> Description
An error occurred in the system function during processing the command.
Action method
Re-execute. If the message is still output, use iscollectinfo command to collect diagnostic information, then contact your serviceengineer. Also inform the notified message to the service engineer.
Refer to the Interstage Application Server Reference Manual (Command Edition) for the iscollectinfo command.
- 253 -
[Linux][0095]The environment variable (IS_HOME) is not set[Windows][0095]The environment variable (IS_HOME) is not set Description
The environment variable (IS_HOME) is not set.
Action method
Reinstall Systemwalker Runbook Automation, and execute it again.
[Linux][0113]Repository server is not created[Windows][0113]Repository server is not created Description
The repository server of the Interstage Single Sign-on has not been set up.
Action method
Re-execute the command again on the machine where the environmental construction command (ssoclsetup) of the Interstage SingleSign-on system was executed. Refer to the Systemwalker Runbook Automation Reference Guide for ssoclsetup command.
[Linux][0128]A necessary configuration item does not exit[Windows][0128]A necessary configuration item does not exit Description
A configuration item required for starting and stopping services concerning operation of Interstage Single Sign-on does not exit.
Action method
Use iscollectinfo command to collect diagnostic information, then contact your service engineer. Also inform the notified message tothe service engineer.
Refer to the Interstage Application Server Reference Manual (Command Edition) for the iscollectinfo command.
[Linux][0135]Interstage Single Sign-on package is not installed : <server name>[Windows][0135]Interstage Single Sign-on package is not installed : <server name> Description
The Interstage Single Sign-on package is not installed or the Interstage Single Sign-on package resource is corrupt.
Action method
Reinstall Systemwalker Runbook Automation, and execute it again.
[Linux][0155]An error occurred in the system command : <command name>[Windows][0155]An error occurred in the system command : <command name> Description
An error occurred in the system command. Possible causes of the error are as follows:
- There is not enough memory.
- There is not enough disk space for setting up the Interstage Single Sign-on.
- Installed resource is corrupt.
Action method
Take the following action, then re-execute the command:
- Close all programs no longer needed.
- Delete unnecessary files.
- 254 -
- Check if the file is being used by another application when the error message of the content that the access to the file has failed isoutput. Terminate the pertinent application when it is used.
When same error occurred after taking the above action, reinstall Systemwalker Runbook Automation, and execute it again.
[Linux][0158]Interstage Operation Tool is running[Windows][0158]Interstage Operation Tool is running Description
The Interstage Single Sign-on cannot be backed up if Interstage Operation Tool is running.
Action method
Stop the service by using the ssoclservicectl command. Refer to the Systemwalker Runbook Automation Reference Guide for thessoclservicectl command.
[Linux][0159]SSO Repository is running : <repository-name>[Windows][0159]SSO Repository is running : <repository-name> Description
The Interstage Single Sign-on cannot be backed up if SSO Repository <repository-name> is running.
Action method
Stop the service by using the ssoclservicectl command. Refer to the Systemwalker Runbook Automation Reference Guide for thessoclservicectl command.
[Linux][0160]Web Server (Interstage HTTP Server) is running[Windows][0160]Web Server (Interstage HTTP Server) is running Description
The Interstage Single Sign-on cannot be backed up of Web Server (Interstage HTTP Server) is running.
Action method
Stop the service by using the ssoclservicectl command. Refer to the Systemwalker Runbook Automation Reference Guide for thessoclservicectl command.
[Linux] [0161]Interstage Certificate Environment is not created[Windows] [0161]Interstage Certificate Environment is not created Description
The Interstage Single Sign-on cannot be backed up if Interstage Certificate Environment is not created.
Action method
Re-execute the command again on the machine where the environmental construction command (ssoclsetup) of the Interstage SingleSign-on system was executed. Refer to the Systemwalker Runbook Automation Reference Guide for ssoclsetup command.
[Linux] [0162]SSO Repository is not created[Windows] [0162]SSO Repository is not created Description
The SSO Repository is not created on the machine for backup.
Action method
Re-execute the command again on the machine where the environmental construction command (ssoclsetup) of the Interstage Singlesign-on system was executed. Refer to the Systemwalker Runbook Automation Reference Guide for ssoclsetup command.
[Linux] [0163]Web Server (Interstage HTTP Server) is not created[Windows] [0163]Web Server (Interstage HTTP Server) is not created
- 255 -
Description
Possible causes of the error are as follows:
- Web Server (Interstage HTTP Server) is not created on the machine for backup.
- In the environment constructed by using environmental construction command (ssoclsetup) of the Interstage Single Sign-on system,there is a possibility that Web server (Interstage HTTP Server) is deleted.
Action method
Take the following action.
- When Web server (Interstage HTTP Server) is not created, re-execute on the machine where environmental construction command(ssoclsetup) of the Interstage Single Sign-on system was executed. Refer to the Systemwalker Runbook Automation ReferenceGuide for the ssoclsetup command.
- When Web server (Interstage HTTP Server) has been deleted, the Interstage Single Sign-on system cannot be backed up by thiscommand. Restore the Single Sign-on system from the resources backed up before by the following actions.
1. Execute the ssoclunsetup command, and delete the environment of the Interstage Single Sign-on system. Refer to theSystemwalker Runbook Automation Reference Guide for ssoclunsetup command.
2. Execute the ssoclrestore command to restore the resource of the Interstage Single Sign-on system from the resources backedup before. Refer to the Systemwalker Runbook Automation Reference Guide for the ssoclrestore command.
[Linux] [0164]The backup resource already exists in the specified directory : <directory path>[Windows] [0164]The backup resource already exists in the specified directory : <directory path> Description
The backup resource already exists in the specified directory <directory path>.
Action method
Take the following action, then re-execute the command:
- Change the backup directory.
- Delete the "ssoroot" directory under the backup directory.
[Linux] [0165]The backup of Interstage Single Sign-on failed[Windows] [0165]The backup of Interstage Single Sign-on failed Description
The backup of the Interstage Single Sign-on fails because the error had occurred during backing up the Interstage Single Sign-on.
Action method
Execute the actions for the error message output in this command execution. Execute it again after the actions.
3.13.5 ssoclrestore Command MessagesIt explains the message that the ssoclrestore command outputs.
[Linux][0002]Internal error[Windows][0002]Internal error Description
An internal error occurred during processing the command.
Action method
Re-execute. If the message is still output, use the iscollectinfo command to collect diagnostic information, then contact your serviceengineer. And inform the notified message to the service engineer.
Refer to the Interstage Application Server Reference Manual (Command Edition) for the iscollectinfo command.
- 256 -
[Linux][0003]System function detect error[Windows][0003]System function detect error Description
An error occurred in the system function during processing.
[Windows]
There is a possibility to specify the DOS device name for the resource storage file of Interstage Single Sign-on.
Action method
Re-execute. If the message is still output, use the iscollectinfo command to collect diagnostic information, then contact your serviceengineer. And inform the notified message to the service engineer.
[Windows]
If a DOS device name was used for the specified Interstage Single Sign-on resource storage file, specify a different file name in re-executing the command.
[Linux][0004]Invalid file path : <file path>[Windows][0004]Invalid file path : <file path> Description
Possible causes of the error are as follows:
- The backup directory<file path> is invalid.
- The backup directory<file path> does not exist.
- It is not the directory where the backup resource was stored by the ssoclbackup command.
- The backup resource that was stored by the ssoclbackup command is corrupt.
Action method
Check the parameter (backup directory) and execute it again.
Refer to the Systemwalker Runbook Automation Reference Guide for the ssoclbackup command.
[Linux][0005]Allocation of a memory failed[Windows][0005]Allocation of a memory failed Description
Memory could not be allocated.
Action method
Close all programs no longer needed, then re-execute the command.
[Linux][0006]No space in disk[Windows][0006]No space in disk Description
There is not enough disk space for restoring the Interstage Single Sign-on.
Action method
Delete unnecessary files and then re-execute.
[Linux][0011]Failed to write to the file : <directory path>[Windows][0011]Failed to write to the file : <directory path> Description
A directory with the same name as the directory for restore <directory path> already exists.
- 257 -
Action method
Delete the directory <directory path> and then re-execute.
[Linux][0012]File access denied : <file path>[Windows][0012]File access denied : <file path> Description
Possible causes of this error are as follows:
- There is no access authority for file < file path >.
[Windows]
- A DOS device name may have been used for the specified backup directory.
Action method
Take the following action, then re-execute the command:
- Check whether the file < file path > is being used by another application.
[Windows]
- If DOS device name was used for the specified backup Directory, specify a different file path.
[Linux][0017]File not found : <file path>[Windows][0017]File not found : <file path> Description
The specified resource file of the Interstage Single Sign-on does not exist.
Action method
Check whether the specified resource file of the Interstage Single Sign-on exists, and then re-execute.
[Linux][0032]Execution is not permitted[Windows][0032]Execution is not permitted Description
You cannot execute the command because you do not have administrator permission.
Action method
Re-execute the command as a user with the following permission.
[Windows]
User who has administrator authority
If your operating system is Windows Server 2008 or a subsequent version, execute as an administrator
[Linux]
System Administrator (Super user)
[Linux][0051]Interstage Single Sign-on package is not installed[Windows][0051]Interstage Single Sign-on package is not installed Description
The Interstage Single Sign-on package is not installed or Interstage Single Sign-on package resource is corrupt.
Action method
Reinstall Systemwalker Runbook Automation, and execute it again.
- 258 -
[Linux][0052]Web Server (Interstage HTTP Server) package is not installed[Windows][0052]Web Server (Interstage HTTP Server) package is not installed Description
Web Server (Interstage HTTP Server) package is not installed.
Action method
Reinstall Systemwalker Runbook Automation, and execute it again.
[Linux][0053]Secure Communication Service package is not installed[Windows][0053]Secure Communication Service package is not installed Description
Secure Communication Service package is not installed.
Action method
Reinstall Systemwalker Runbook Automation, and execute it again.
[Linux][0072]Interstage Directory Service package is not installed[Windows][0072]Interstage Directory Service package is not installed Description
Interstage Directory Service package is not installed.
Action method
Reinstall Systemwalker Runbook Automation, and execute it again.
[Linux][0091]An error occurred using the system function : <detail>[Windows][0091]An error occurred using the system function : <detail> Description
An error occurred using the system function during processing the command.
Action method
Re-execute. If the message is still output, use iscollectinfo command to collect diagnostic information, then contact your serviceengineer. Also inform the notified message to the service engineer.
Refer to the Interstage Application Server Reference Manual (Command Edition) for the iscollectinfo command.
[Linux][0095]The environment variable (IS_HOME) is not set[Windows][0095]The environment variable (IS_HOME) is not set Description
The environment variable (IS_HOME) is not set.
Action method
Reinstall Systemwalker Service Catalog Manager, and execute it again.
[Linux][0132]Invalid file format[Windows][0132] Invalid file format Description
Possible causes of the error are as follows:
- The file that was specified was not an Interstage Single Sign-on resource storage file.
- The Interstage Single Sign-on resource storage file is corrupt.
- The specified Interstage Single Sign-on resource storage file was created on a different platform.
- 259 -
[Windows]
- A DOS device name may have been used for the specified Interstage Single Sign-on resource storage file.
[Linux]
- The Interstage Single Sign-on resource storage file which was created on the environment that the variable (LANG) is differentwas specified.
Action method
Take the following action, then re-execute the command:
- Specify the Interstage Single Sign-on resource storage file correctly.
- Check the backup/export procedure, and create the Interstage Single Sign-on resource storage file on the machine used to performbackup/export again.
- Specify an Interstage Single Sign-on resource storage file that was created on the same platform.
[Windows]
- If a DOS device name was used for the specified Interstage Single Sign-on resource storage file, specify a different file name.
[Linux]
- Specify the resource storage file of the Interstage Single Sign-on which was created on the environment that the variable (LANG)is same.
Or restore and import it by the following procedures.
1. Stop all services and the server applications.
2. Set the environment variable (LANG) temporarily to the value of the environment variable (LANG) of the machine which youperformed the backup and the export.
3. Execute this command.
4. Set the environment variable (LANG) to previous value before clause 2 is executed.
5. Change the character-code of the environmental definition file of each server that is restored and imported if necessary.
For changing character valuable, Refer to the "Note: Interstage Application Server of "Note"-"Notes for changing system locale
6. Start the stopped service and server application.
[Linux][0133]The file already exists : <file path>[Windows][0133]The file already exists : <file path> Description
A file with the same name as the directory for restore <file path> already exists.
Action method
Delete the file <file path> and re-execute.
[Linux][0134]The installation directory is different to the environment that was backed up : <install path>[Windows][0134]The installation directory is different to the environment that was backed up: <install path> Description
The Interstage Application Server installation directory is different to the installation directory < install path > that was used to performbackup.
Action method
Make the Interstage Application Server installation directory the same as the installation directory < install path > that was used toperform backup and re-execute.
- 260 -
[Linux][0135]Interstage Single Sign-on package is not installed : <server name>[Windows][0135]Interstage Single Sign-on package is not installed : <server name> Description
The Interstage Single Sign-on package is not installed or Interstage Single Sign-on package resource is corrupt.
Action method
Reinstall Systemwalker Runbook Automation, and execute it again.
[Linux][0155]An error occurred in the system command : <command name>[Windows][0155]An error occurred in the system command : <command name> Description
An error occurred in the system command. Possible causes of the error are as follows:
- There is not enough memory.
- There is not enough disk space for setting up the Interstage Single Sign-on.
- Installed resource is corrupt.
Action method
Take the following action, then re-execute the command:
- Close all programs no longer needed.
- Delete unnecessary files.
- Check if the file is being used by another application when the error message of the content that the access to the file has failed isoutput. Terminate the pertinent application when it is used.
When same error occurred after taking the above action, reinstall Systemwalker Runbook Automation, and execute it again.
[Linux][0158]Interstage Operation Tool is running[Windows][0158]Interstage Operation Tool is running Description
The Interstage Single Sign-on cannot be restored because Interstage Operation Tool is running.
Action method
Stop the service by using the ssoclservicectl command. Refer to the Systemwalker Runbook Automation Reference Guide for thessoclservicectl command.
[Linux][0159]SSO Repository is running : <repository-name>[Windows][0159]SSO Repository is running : <repository-name> Description
The Interstage Single Sign-on cannot be restored because SSO Repository <repository-name> is running.
Action method
Stop the service by using the ssoclservicectl command. Refer to the Systemwalker Runbook Automation Reference Guide for thessoclservicectl command.
[Linux][0160]Web Server (Interstage HTTP Server) is running[Windows][0160]Web Server (Interstage HTTP Server) is running Description
The Interstage Single Sign-on cannot be restored because Web Server (Interstage HTTP Server) is running.
- 261 -
Action method
Stop the service by using the ssoclservicectl command. Refer to the Systemwalker Runbook Automation Reference Guide for thessoclservicectl command.
[Linux][0166]The restore of Interstage Single Sign-on failed[Windows][0166]The restore of Interstage Single Sign-on failed Description
The restore of the Interstage Single Sign-on fails because the error had occurred during restoring the Interstage Single Sign-on.
Action method
Execute it again after executing either of the following actions.
- Execute the actions for the error message output in this command execution.
- When the error message is not output in this command execution, execute the actions for the error message output to the log ofthe system.
3.14 Messages Relating to Systemwalker Runbook AutomationStudio Maintenance Commands
3.14.1 swrbaexport Settings Export Command FAILURE [2]: Failed to export the settings information. (%1) Description
Failed to export the settings information.
Parameters
%1: Detailed information
Cause
The possible causes are listed below:
- User does not have access permission for the directory.
- Insufficient disk space.
- An invalid path was specified..
Action method
- Ensure that the user has access permission to the directory.
- Ensure that there is sufficient disk space.
- Ensure that a valid path was specified.
FAILURE [255]: An internal error occurred. (%1) Description
An internal error occurred while running the command.
Parameters
%1: Detailed information
- 262 -
Cause
A system error (such as insufficient memory) might occurred.
Action method
If no system error occurred, contact Fujitsu technical support.
3.14.2 swrbaimport Settings Import Command FAILURE [2]: Failed to import the settings information. (%1) Description
Failed to export the settings information.
Parameters
%1: Detailed information
Cause
The possible causes are listed below:
- User does not have access permission for the file.
- Insufficient disk space.
- User does not have access permission to the target directory.
Action method
Confirm the followings and run the command again.
- Ensure that the file exists.
- Ensure that there is sufficient disk space.
- Ensure that the user has access permission to the directory.
FAILURE [255]: An internal error occurred. (%1) Description
An internal error occurred while running the command.
Parameters
%1: Detailed information
Cause
A system error (such as insufficient memory) occurred.
Action method
If no system error occurred, contact Fujitsu technical support.
3.14.3 swrbacolinf Collecting Maintenance Information Command FAILURE [2]: Failed to collect the maintenance information. (%1)
- 263 -
Description
Failed to collect the maintenance information.
Parameters
%1: Detailed information
Cause
The possible causes are listed below:
- User does not have access permission for the directory.
- Insufficient disk space
- An invalid path was specified.
Action method
- Ensure that the user has access permission to the directory.
- Ensure that there is sufficient disk space.
- Ensure that a file can be created on the specified path.
FAILURE [255]: An internal error occurred. (%1) Description
An internal error occurred while running the command.
Parameters
%1: Detailed information
Cause
A system error (such as insufficient memory) occurred.
Action method
If no system error occurred, contact Fujitsu technical support.
3.15 Messages Relating to QuickForm UI Components RCF11000: Duplicate component id. id=%1 Description
More than one UI component has the same ID.
Parameters
%1: ID
Action method
Ensure that all component IDs are unique.
RCF11001: Invalid attribute value. name=rcf:%1, value=%2 Description
A value of the wrong data type is defined in the property.
- 264 -
Parameters
%1: Property name
%2: Value
Action method
Specify a value of the correct data type in the property.
RCF12604: Specified index of "%1" property(%2) is out of range. Description
The selectedIndex or the selectedIndexes property in the Select component contains a value out of range.
The valid values are:
- selectedIndex:
from -1 to (array length of the 'options' property) -1
- selectedIndexes:
from 0 to (array length of the 'options' property) -1
Parameters
%1: Property name
%2: Index value
Action method
Specify a valid value.
RCF12605: Specified value of "%1" property(%2) is not found in values of "options" property. Description
The value specified for selectedValue or selectedValues property in the Select component does not match any of the values specifiedfor options property.
Parameters
%1: Property name
%2: Value
Action method
Specify a value that matched one of the values in options property.
RCF13302: Specified index of "%1" property(%2) is out of range. Description
The selectedIndex or the selectedIndexes property in the SelectList component contains a value out of range.
The valid values are:
- selectedIndex:
from -1 to (array length of the 'options' property) -1
- selectedIndexes:
from 0 to (array length of the 'options' property) -1
- 265 -
Parameters
%1: Property name
%2: Index value
Action method
Specify a valid value.
RCF13402: Specified index of "%1" property(%2) is out of range. Description
The selectedIndex or the selectedIndexes property in the CheckList component contains a value out of range.
The valid value are:
- selectedIndex:
from -1 to (array length of the 'options' property) -1
- selectedIndexes:
from 0 to (array length of the 'options' property) -1
Parameters
%1: Property name
%2: Index value
Action method
Specify a valid value.
3.16 Messages Relating to the REST Interface
3.16.1 Response messages Authorization failed. Description
Authentication processing failed.
System processing
Processing is aborted.
Cause
The specified authentication information is invalid.
Action method
Ensure that the method use to specify the authentication information is valid.
The specified user ID or password is incorrect. User:%1 Description
The specified user ID or password is incorrect.
Parameters
%1: User ID
- 266 -
System processing
Processing is aborted.
Cause
The user ID or password specified in the HTTP request header is invalid.
Action method
Ensure that the specified user ID or password is correct, then re-execute.
Authorization Required. Code=%1 Description
The authentication information has not been set.
Parameters
%1: Error code
System processing
Processing is aborted.
Cause
There is no Authorization header in the HTTP header, or the specified content is invalid.
Action method
Take the appropriate action according to the error code, then re-execute the command.
Error code Meaning Action method
0001 There is no Authorization header for the HTTPheader.
Add the Authorization header.
0002 The Basic authentication information has not beenset in the Authorization header of the HTTP header.
Add the Basic authentication information to theAuthorization header.
0003 The Basic authentication information has not beenset.
Set the Basic authentication information.
0004 The user name and password have not beenconcatenated using a colon (:).
Specify the user name and password concatenated bya colon (:), and using Base64 encoded strings.
0005 The method used to specify the user name andpassword is invalid.
Specify the user name and password using the correctmethod.
The parameter is invalid. param:%1=%2 Description
The request parameter settings are invalid.
Parameters
%1: Parameter
%2: Value
System processing
Processing is aborted.
Cause
The value that was specified for the parameter name specified for the request parameter is invalid.
- 267 -
Action method
Check the content that was specified for the request parameter, then re-execute.
An required parameter is not set. %1 Description
A required parameter has not been specified or an empty value was specified for it.
Parameters
%1: Parameter
System processing
Processing is aborted.
Cause
A required parameter has not been specified or an empty value was specified for it.
Action method
Refer to the API Reference and specify an appropriate value.
An unnecessary parameter is set. %1 Description
An invalid parameter has been specified or the same parameter has been specified more than once.
Parameters
%1: Parameter
System processing
Processing is aborted.
Cause
An invalid parameter has been specified or the same parameter has been specified more than once.
Action method
Refer to the API Reference and specify an appropriate value.
I/O error occurred. Description
An I/O error occurred.
System processing
Processing is aborted.
Cause
An error occurred in the file operation.
Action method
Take the following actions, then re-execute the command:
- Ensure that there is sufficient disk space.
- Ensure that the operating system administrator has read and write permissions to the disk.
- Ensure that an abnormality has not occurred on the disk.
- 268 -
The specified automated operation process group does not exist. Automated operation process groupID:%1 Description
The specified Automated Operation Process Group does not exist.
Parameters
%1: Automated Operation Process Group ID
System processing
Processing is aborted.
Cause
The Automated Operation Process Group specified in the request parameter does not exist.
Action method
Specify an existing Automated Operation Process Group.
The status of specified automated operation process group is DELETED or OFFLINE. Automatedoperation process group ID:%1 Description
The status of the specified Automated Operation Process Group is not existed or is OFFLINE.
Parameters
%1: Automated Operation Process Group ID
System processing
Processing is aborted.
Cause
The status of the Automated Operation Process Group specified in the request parameter is not exist or is OFFLINE.
Action method
Specify an Automated Operation Process Group that has ONLINE status.
The UDA specified in request body does not exist in the process definition. Description
The UDA specified in the request body does not exist in the process definition.
System processing
Processing is aborted.
Cause
The UDA specified in the request body does not exist in the process definition.
Action method
Check the request body, then specify a UDA that exists in the process definition.
The parameter data syntax is invalid. Description
The file syntax of the parameter information specified in the request body is invalid.
- 269 -
There is no '=' between the UDA key and the value specified in the request body.
System processing
Processing is aborted.
Cause
There is no '=' between the parameter information UDA key and the value specified in the request body.
Action method
Set the parameter information using the correct syntax.
The specified process definition UDA type is not STRING. Process definition name:%1 Description
The specified process definition UDA type is not STRING.
Parameters
%1: Process definition name
System processing
Processing is aborted.
Cause
The specified process definition UDA type is not STRING.
Action method
Specify a STRING type process definition UDA.
An internal error occurred. Code=%1 Description
An internal error occurred.
Parameters
%1: Internal code
System processing
Processing is aborted.
Cause
An internal error occurred.
Action method
Refer to the event log or system log, and check whether an error has occurred.
If you do not find any problems after performing the above check, contact Fujitsu technical support.
Processing was completed. Description
Processing was successful.
System processing
Processing was completed.
- 270 -
Failed to connect to Workflow Server. Description
Failed to connect to Workflow Server.
System processing
Processing is aborted.
Cause
Failed to connect to Workflow Server.
Action method
Ensure that Systemwalker Runbook Automation is running.
If you do not find any problems after performing the above check, contact Fujitsu technical support.
The specified process definition does not exist. Process definition name:%1 Description
Specified process definition does not exist.
Parameters
%1: process definition name
System processing
Processing is aborted
Cause
Specified process definition does not exist.
Action method
Specify the exist process definition.
User %1 is not an owner of process definition, so user %1 has not be able to start process instance byprocess definition. Process definition name: %2 Description
Failed to start process
Parameters
%1:User name
%2: process definition name
System processing
Processing is aborted
Cause
Specified user is not an owner of process definition.
Action method
Specify the owner of process definition
- 271 -
User %1 is not an owner of process definition, so user %1 has not be able to start process instance byprocess definition (Name=%2, Version=%3, Owner=%4). Description
Failed to start process
Parameters
%1:User name
%2:process definition name
%3:version
%4:owner of process definition
System processing
Processing is aborted
Cause
Specified user is not an owner of process definition.
Action method
Specify the owner of process definition
User %1 has not be able to start process instance by process definition (Name=%2, Version=%3). Processinstance is able to start by only published or draft status of process definition. Description
Failed to start from specified process definition
Parameters
%1:user name
%2:process definition name
%3:version
System processing
Processing is aborted
Cause
Specified process definition status is not published or draft.
Action method
Specify process definition which status is published or draft.
The published or draft status of process definition does not exist. Process definition name:%1 Description
Process definition which published or draft status does not exist.
Parameters
%1: process definition name
System processing
Processing is aborted
- 272 -
Cause
Process definition which published or draft status does not exist.
Action method
Specify process definition which status is published or draft.
The specified version process definition does not exist. Process definition name:%1 Version:%2 Description
Process definition which specified version does not exist.
Parameters
%1: process definition name
%2: version
System processing
Processing is aborted
Cause
Process definition which specified version does not exist. Or no authority to start process definition which specified.
Action method
Specify process definition which it has been published status.
If it is draft status, only the owner of process definition you can start it.
A system error occurred. Description
A system error occurred.
System processing
Processing is aborted
Cause
A system error occurred.
Action method
Confirm that shortage of disk resource or memory has been occurred.
If you do not find any problems after performing the above check, contact Fujitsu technical support.
3.17 Messages Displayed in the Custom Messages Dialog BoxThe messages displayed in the Custom Messages dialog box are displayed in the custom messages in the operation component executionstatus and result confirmation windows. Users can refer to these messages to check how far operation component execution has progressed.Refer to Operation Component Execution Status/Execution Results Confirmation Windows in the Systemwalker Runbook AutomationOperation Guide for information on the operation component execution status and result confirmation windows.
A list of the operation component progress notification messages is given below.
- 273 -
Variable items
- <PROCESSID>=%1 <ACTIVITYID>=%2 <NAME>=%3
%1: Displays the process ID of the executed operation process
%2: Displays the activity ID of the executed operation component
%3: Displays the node name of the executed operation component
- <Option name>=%1
%1: Displays the character string specified in the option
- <Operation target name>=%1 <Completed>=%2 <In progress>=%3 <Total number>=%4
%1: Displays information on the operation target
%2: Of the multiple operations specified in the option, displays the number of completed operations
%3: Of the multiple operations specified in the option, displays the number of operations still in progress
%4: Displays the total number of the multiple operations specified in the option
Messages
Category name Operation component name Progress notification message
Common Common - Execution of the operation component is about to start. PROCESSID=%1ACTIVITYID=%2 NAME=%3
- Execution of the operation component has finished. PROCESSID=%1ACTIVITYID=%2 NAME=%3
Note
The above two progress notification messages are the first and last messagesdisplayed for an executed operation component. Each of the other operationcomponent progress notification messages are displayed between the above twoprogress notification messages.
- An error occurred while executing the operation component.
Note
The progress notification messages shown above are displayed if the erroroccurs while each operation component is running.
CommandExecution
Execute arbitrary command - Executes the specified command. hostname=%1
- The specified command was executed.
Execute WMI query - Executes the WMI query.hostname=%1
- The WMI query was executed.
Execute multiple commands <For Telnet communication>
- telnet communication will start. hostname=%1
- The specified command was executed. commandline=%1
- telnet communication is complete.
<For SSH communication>
- SSH communication will start.hostname=%1
- The specified command was executed. commandline=%1
- SSH communication is complete.
Execute multi-operationprocesses
- Executes the specified operation process.
- 274 -
- The specified operation process was executed. processId=%1 Executed=%2Running=%3 Total number of items=%4
- The specified operation process was executed.
Email Operations Send emails - The mail will be sent.
- The mail has been sent.
File Operations Transfer files - File acceptance will start.sourcehostname=%1 -> hostname=localhost
- File acceptance is complete.
- File sending will start.sourcehostname=localhost -> hostname=%1
- File sending is complete.
Change file access permissions - File access permissions will change.hostname=%1
- File access permissions have been changed.
Check that the file exists - The check to determine whether the file exists will start.hostname=%1
- The check to determine whether the file exists is complete.
Check that file/directory exists - The check to determine whether the file/directory exists will start. hostname=%1
- The check to determine whether the file/directory exists is complete.
Create files - The file will be created.hostname=%1
- The file has been created.
Delete files - The file will be deleted. hostname=%1
- The file has been deleted.
Copy files/directories - Copying of the file/directory will start.hostname=%1
- Copying of the file/directory is complete.
Move files/directories - Moving of the file/directory will start. hostname=%1
- Moving of the file/directory is complete.
Get list of files/directories - The list of files/directories will be obtained.hostname=%1
- The list of files/directories has been obtained.
Get file/directory size - The file/directory size will be obtained.hostname=%1
- The file/directory size has been obtained.
Check file/directory accesspermissions
- Confirmation of the file/directory access permissions will start. hostname=%1
- Confirmation of the file/directory access permissions is complete.
Get file/directory update dateand time
- The file/directory last modified date and time will be obtained.hostname=%1
- The file/directory last modified date and time has been obtained.
Create directory - The directory will be created. hostname=%1
- The directory has been created.
Delete directory - The directory will be deleted. hostname=%1
- The directory has been deleted.
Change directory accesspermissions
- The directory access permissions will be changed. hostname=%1
- The directory access permissions have been changed.
Compress files - File compression will start.hostname=%1
- File compression is complete.
- 275 -
Compress directory - Directory compression will start.hostname=%1
- Directory compression is complete.
Decompress files - Extraction of the compressed files will start.hostname=%1
- Extraction of the compressed files is complete.
Load file - File loading will start.hostname=%1
- File loading is complete.
Print file - File printing will start. hostname=%1
- File printing is complete.
Search string in file - The string search in the file will start.hostname=%1
- The string search in the file is complete.
Add string to file - The string will be added to the file. hostname=%1
- The string has been added to the file.
Replace string in file - The string replacement in the file will start.hostname=%1
- The string replacement in the file is complete.
Convert file character encoding - File character code conversion will start.
- File character code conversion is complete.
Collect fingerprint - Fingerprint will be collected. filename=%1
- Fingerprint has been collected.
ConfigurationItem Operations
Obtain configuration item - The configuration item will be obtained.hostname=%1
- The configuration item has been obtained.
Update configuration item - The configuration item will be updated.hostname=%1
- The configuration item has been updated.
Delete configuration item - The configuration item will be deleted. hostname=%1
- The configuration item has been deleted.
Register logical node - Registration of the logical node will start.
- Registration of the logical node is complete.
CommunicationOperations
Perform REST-basedcommunications
- REST communication will start. hostname=%1
- REST communication is complete.
Get value using SNMP - The SNMP value will be obtained.hostname=%1
- The SNMP value has been obtained.
Set value using SNMP - The SNMP value will be set. hostname=%1
- The SNMP value has been set.
Send SNMP trap - The SNMP trap will be sent.hostname=%1
- The SNMP trap has been sent.
Execute Web service - Execution of the Web service will start. wsdlpath=%1
- Execution of the Web service is complete.
Service/ProcessOperations
Check that service/process hasstarted
- The check to determine whether the service/process has started willbegin.hostname=%1
- The check to determine whether the service/process has started is complete.
- 276 -
Check that service/process hasstopped
- The check to determine whether the service/process has stopped will start.hostname=%1
- The check to determine whether the service/process has stopped is complete.
Check that service has started - The check to determine whether the service has started will begin.hostname=%1
- The check to determine whether the service has started has ended. service=%1 Checked=%2 Checking=%3 Total number of items=%4
- The check to determine whether the service has started is complete.
Check that service has stopped - The check to determine whether the service has stopped will start.hostname=%1
- The check to determine whether the service has stopped is complete.
Check that process has started - The check to determine whether the process has started will begin.hostname=%1
- The check to determine whether the process has started is complete.
Check that process has stopped - The check to determine whether the process has stopped will start.hostname=%1
- The check to determine whether the process has stopped is complete.
Start service - The service startup will start.hostname=%1
- The service startup is complete.
Stop service - The service will be stopped. hostname=%1
- The service has been stopped.
Pause service - The service will be paused. hostname=%1
- The service has been paused.
Change service account - The service execution account will be changed.hostname=%1
- The service execution account has been changed.
Change service startup type - The service startup type will be changed. hostname=%1
- The service startup type has been changed.
Get service status - The service status will be obtained.hostname=%1
- The service status has been obtained.
End process - The process will end.hostname=%1
- The process has ended.
Load balancingand clusteroperations
Remove as load balancing target - Removal as a load balancing target will start. hostname=%1
- Removal as a load balancing target is complete.
Include as load balancing target - Inclusion as a load balancing target will start.hostname=%1
- Inclusion as a load balancing target is complete.
Get cluster resource status - The cluster system resource status will be obtained.hostname=%1
- The cluster system resource status has been obtained.
Switch cluster resource - The cluster system resource will be switched. hostname=%1
- The cluster system resource has been switched.
Server operations Start the server - The server startup request will start.
- The server startup request has ended. hostname=%1 Startup requested=%2Requesting startup=%3 Total number of items=%4
- 277 -
- The server startup request is complete.
Stop the server - The server stop request will start.
- The server stop request has ended. hostname=%1 Stop requested=%2Requesting stop=%3 Total number of items=%4
- The server stop request is complete.
Stop OS - The operating system stop request will start.
- The operating system stop request has ended. hostname=%1 Stop requested=%2 Requesting stop=%3 Total number of items=%4
- The operating system stop request is complete.
Restart OS - The operating system restart request will start.
- The operating system restart request has ended. hostname=%1 Restartrequested=%2 Requesting restart=%3 Total number of items=%4
- The operating system restart request is complete.
Start WorkUnit - The WorkUnit startup will start. hostname=%1
- The WorkUnit startup is complete.
Stop WorkUnit - The WorkUnit will stop.hostname=%1
- The WorkUnit has stopped.
Restart WorkUnit - The WorkUnit will restart. hostname=%1
- The WorkUnit has restarted.
Start virtual server - The virtual server startup will start.
- The virtual server startup has ended. servername=%1 Started=%2 Running=%3 Total number of items=%4
- The virtual server startup is complete.
Stop virtual server - The virtual server will stop.
- The virtual server has stopped. servername=%1 Stopped=%2 Not running=%3 Total number of items=%4
- The stopping of the virtual server is complete.
Restart virtual server - The virtual server will restart.
- The restart of the virtual server has ended. servername=%1 Restarted=%2Restarting=%3 Total number of items=%4
- The restart of the virtual server is complete.
Build virtual server - The virtual server build will start.servername=%1
- The virtual server build is complete.
Delete virtual server - The virtual server will be deleted.servername=%1
- The virtual server has been deleted.
Change virtual server system - The virtual server system will be changed.servername=%1
- The virtual server system has been changed.
Get virtual server list - The list of virtual servers will be obtained.
- The list of virtual servers has been obtained.
Get detailed virtual serverinformation
- The virtual server advanced information will be obtained. servername=%1
- The virtual server advanced information has been obtained
Create virtual server snapshot - The virtual server snapshot will be created. servername=%1
- 278 -
- The virtual server snapshot has been created.
Restore virtual server snapshot - The virtual server snapshot will be restored.servername=%1
- The virtual server snapshot has been restored.
Change host name - The host name will be changed. hostname=%1
- The host name has been changed.
- The configuration item will be updated.hostname=localhost
- The configuration item has been updated.
Stop virtual server on the VMhost
- Stopping the VM host virtual servers will start.
- Stopping the VM host virtual servers has ended. vmhost=%1 Launched=%2Stopping=%3 Total number of items=%4
- Stopping the VM host virtual servers is complete.
Set the maintenance mode of theVM host
- The VM host maintenance mode will be set.
- The setting of the VM host maintenance mode has ended. vmhost=%1Launched=%2 Setting=%3 Total number of items=%4
- The setting of the VM host maintenance mode is complete.
Stop VM host forcibly - Forcibly stopping the VM host will start.
- Forcibly stopping the VM host has ended. vmhost=%1 Launched=%2Stopping=%3 Total number of items=%4
- Forcibly stopping the VM host is complete.
Monitoringoperations
Check for hardware errors - The check to determine whether there are any hardware errors willstart.ipmiipaddress=%1
- The check to determine whether there are any hardware errors is complete.
Get server power status - The server's power status will be obtained. hostname=%1
- The server's power status has been obtained.
Check server running normally - The check to determine whether the server is running normally will start.hostname=%1
- The check to determine whether the server is running normally has ended.service=%1
Checked=%2 Checking=%3 Total number of items=%4
- The check to determine whether the server is running normally has ended.port=%1
Checked=%2 Checking=%3 Total number of items=%4
- The check to determine whether the server is running normally is complete.
Notify event to monitoredproduct
- Notice of events in the monitored product will start.hostname=%1
- Notice of events in the monitored product is complete.
Check whether an event hasoccurred in the monitoredproduct
- The check to determine whether a monitored product event has occurred willstart.hostname=%1
- The check to determine whether a monitored product event has occurred iscomplete.
Change monitored productevent status
- The monitored product event's status will be changed. hostname=%1
- The monitored product event's status has been changed.
Get monitored product event - The monitored product event for the specified time will be obtained.hostname=%1
- 279 -
- The monitored product event for the specified time has been obtained.
Disable server monitoring - Server monitoring in the monitored product will be disabled.hostname=%1
- Server monitoring in the monitored product has been disabled.
Enable server monitoring - Server monitoring in the monitored product will be enabled. hostname=%1
- Server monitoring in the monitored product has been enabled.
Get event log - The event log will be obtained.hostname=%1
- The event log has been obtained.
Create event log - The event log will be created. hostname=%1
- The event log has been created.
Get performance counter - The performance counter value will be obtained. hostname=%1
- The performance counter value has been obtained.
Job operations Obtain job net status - The job net status will be obtained.hostname=%1
- The job net status has been obtained.
Start job net - The job net startup will start.hostname=%1
- The job net startup is complete.
Networkoperations
Check operational status ofnode
- The check to determine whether the node is running will start.
- The check to determine whether the node is running has ended. hostname=%1 Checked=%2
Checking=%3 Total number of items=%4
- The check to determine whether the node is running is complete.
Check port connection - The check to determine the port connection will start. hostname=%1
- The check to determine the port connection has ended. port=%1 Checked=%2 Checking=%3 Total number of items=%4
- The check to determine the port connection is complete.
System operations Obtain current date - The current date and time will be obtained.
- The current date and time has been obtained.
Compare date and time - Date and time comparison will start.
- Date and time comparison is complete.
Set OS network - The domain will be set. hostname=%1
- The domain has been set.
- The workgroup will be set. hostname=%1
- The workgroup has been set.
- The DNS server address will be set. hostname=%1
- The DNS server address has been set.
- The WINS address will be set. hostname=%1
- The WINS address has been set.
- The configuration item will be updated. hostname=localhost
- The configuration item has been updated.
Install software - Forwarding of the software will start. sourcehostname=%1 -> hostname=%2
- Forwarding of the software is complete.
- Installation of the software will start. hostname=%1
- 280 -
- Installation of the software is complete.
Install OS update - Forwarding of the operating system update will start. sourcehostname=%1 -> hostname=%2
- Forwarding of the operating system update is complete.
- Installation of the operating system update will start. hostname=%1Update=%2 Executed=%3 Total number of items=%4I
- Installation of the operating system update is complete.
Operation processcontrol
Check that the specified timehas elapsed
<First time>
- Processing will start.
- Processing is complete.
<Second and subsequent times>
- Processing will start.
- Waits for the specified time to elapse. iteration_sleep_time=%1
- Processing is complete.
Sort strings - The string sorting will start.
- The string sorting is complete.
Store data as execution results <No notification messages>
Register Schedule Definitions - The Schedule Definition will be registered. schedule_definition_name=%1
- The Schedule Definition has been registered.
Delete Schedule Definitions - The Schedule Definition will be deleted. schedule_definition_id=%1
- The Schedule Definition has been deleted.
- 281 -