B.2 Error Codes for Configuration Management

The error codes for configuration management function are listed below.

Table B.2 Error Codes for Configuration Management
Error Code	Explanation	Corrective action
1	An invalid parameter was specified.	Check the specified parameter. If the parameter is valid, collect the information required for troubleshooting, and then contact a Fujitsu systems engineer. (NOTE1)
2	An internal error occurred.	Collect the information required for troubleshooting, and then contact a Fujitsu systems engineer. (NOTE1)
3	A memory shortage occurred at the server that sent the request.	Check the memory operating condition. If a memory shortage has occurred, increase the size of memory.
4	An internal error occurred.	Collect the information required for troubleshooting, and then contact a Fujitsu systems engineer. (NOTE1)
5	Inconsistent repository data.
102	A registry access error occurred.	Check whether /env/swstg.ini and /etc/swnode.ini exist. [Windows version] For cluster system: "Shared devices"\etc\opt\swstorage\etc For non cluster system: "Environment set directory"\etc [Solaris, Linux, and HP-UX versions] For cluster system: /etc/opt/swstorage/"logical node name" (NOTE2) For non cluster system: /etc/opt/swstorage If they exist, collect the information required for troubleshooting, and then contact a Fujitsu systems engineer. (NOTE1)
199	An internal error occurred.	Collect the information required for troubleshooting, and then contact a Fujitsu systems engineer. (NOTE1)
201	Insufficient memory on the Storage Management Server side.	Check the memory operating condition. If a memory shortage has occurred, increase the size of memory.
202	A communication error occurred.	Make sure that the Storage Management Server and the communication service or communication daemon of the Storage Management Server are active. If the communication service or communication daemon has already been started, check if the network load is high. If the load is high, remove the cause of this and re-execute the operation.
203	A timeout occurred during communication processing.	Make sure that the Storage Management Server and the communication service or communication daemon of the Storage Management Server are active.
204	The Storage Management Server failed.
205	The IP address of the Storage Management Server could not be obtained.	If the command is executed in cluster operation, check whether the environment variable SWSTGNODE is set, and re-execute the command. If this fails to solve the problem, check whether swnode.ini exists. [Windows version] For cluster system: "Shared devices"\etc\opt\swstorage\etc For non cluster system: "Environment set directory"\etc [Solaris, Linux, and HP-UX versions] For cluster system: /etc/opt/swstorage/"logical node name" (NOTE2) For non cluster system: /etc/opt/swstorage If they exist, collect the information required for troubleshooting, and then contact a Fujitsu systems engineer. (NOTE1)
299	An internal error occurred.	Collect the information required for troubleshooting, and then contact a Fujitsu systems engineer. (NOTE1)
399 401	An internal discrepancy was detected on the Storage Management Server.
402	Repository access failed.	Check whether the repository is active. If it is active, collect the information required for troubleshooting, and then contact a Fujitsu systems engineer. (NOTE1)
403	The maximum allowable number of connections to the repository was exceeded.	The maximum allowable number of concurrent connections to the repository was exceeded. Re-execute processing later. If the same error recurs, collect the information required for troubleshooting, and then contact a Fujitsu systems engineer. (NOTE1)
404 405 406 407 408	Repository access failed.	Check whether the repository is active. If it is, collect the information required for troubleshooting, and then contact a Fujitsu systems engineer. (NOTE1)
409 499	An internal discrepancy was detected on the Storage Management Server.	Collect the information required for troubleshooting, and then contact a Fujitsu systems engineer. (NOTE1)
504	There is no server or device registered that meets the specified conditions.	Check whether the specified parameter is correct.
505	The repository cannot be accessed.	Check whether the repository is active. If it is, collect the information required for troubleshooting, and then contact a Fujitsu systems engineer. (NOTE1)
506	Insufficient memory on the Storage Management Server side.	Check the memory operating condition. If a memory shortage has occurred, increase the size of memory.
510 599	An internal discrepancy was detected on the Storage Management Server.	Collect the information required for troubleshooting, and then contact a Fujitsu systems engineer. (NOTE1)

NOTE1:: Refer to the following manual for information on how to collect the data necessary to solve the error.
"Collecting maintenance information" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide".

NOTE2:: The "logic node name" is the value specified by the cluster setup.