B.3 Error Codes for Repository Access

The error codes relating to repository access problems are described below.

Table B.3 Error Codes for Repository Access
Error Code	Explanation	Action Plan
101	A memory shortage occurred.	Investigate the memory usage state and if a memory shortage has occurred, expand the memory.
102 103 104	Communication with the communication daemon/service of the Management Server has failed.	Use the following method that corresponds to the operating system type of the Management Server to check whether the communication daemon or service of the Management Server is active. For Windows: For clustered systems: Check whether the "AdvancedCopy Manager COM Service for logicalNodeName" service is active. (1) For non-clustered systems: Check whether the "AdvancedCopy Manager COM Service" service is active. For Solaris or Linux: For clustered systems: Check whether there is an active process in the "ps -ef \| grep stgxfws \| grep logicalNodeName" execution result. (1) For non-clustered systems: Check whether there is an active process in the "ps -ef \| grep stgxfws" execution result. If the name is inactive, refer to the following manuals and start the communication daemon/service: For Windows: "Starting and Stopping a Service" in the ETERNUS SF AdvancedCopy Manager Operation Guide For Solaris or Linux: "Starting and Stopping Daemons" in the ETERNUS SF AdvancedCopy Manager Operation Guide
105	A registry access error occurred.	If the command is executed in cluster operation, check whether environment variable SWSTGNODE is set, and re-execute the command. If you still have a problem, check whether swnode.ini file and swstg.ini file exist in the following directories: For Windows: For clustered systems: sharedDrive:\etc\opt\swstorage\etc For non-clustered systems: envDir\etc For UNIX systems: For clustered systems: /etc/opt/swstorage/logicalNodeName (1) For non-clustered systems: /etc/opt/swstorage If environment variable setting is not the cause, collect the information required for troubleshooting and contact Fujitsu Technical Support. (2)
302	Connection to the repository database failed.	Refer to the following manuals that correspond to the operating system type of the Management Server, and take the corrective action. "Troubleshooting for a failure in access to a repository database" in the ETERNUS SF AdvancedCopy Manager Operation Guide
303	The maximum number of connections to the repository database is exceeded.	Wait a while and re-execute the processing. If you still have a problem, refer to the following manual that corresponds to the operating system type of the Management Server, and take the corrective action. "Troubleshooting for a failure in access to a repository database" in the ETERNUS SF AdvancedCopy Manager Operation Guide
304 305 306 307 308	Access to the repository database failed.	Refer to the following manual that corresponds to the operating system type of the Management Server, and take the corrective action. "Troubleshooting for a failure in access to a repository database" in the ETERNUS SF AdvancedCopy Manager Operation Guide
Except the above	An error has occurred that is not described above.	Collect the information required for troubleshooting and contact Fujitsu Technical Support. (*2)

*1: The logicalNodeName is the value specified during cluster setup.

*2: Refer to "Collecting maintenance information" in the ETERNUS SF AdvancedCopy Manager Operation Guide for information on how to collect the information required for troubleshooting. Collect the information on the server where the error occurred and on the Management Server.