Use Control F to search for a specific error code.
| Code | Severity | Message | Cause | Action |
|---|---|---|---|---|
| 141000 | ERROR | Config value is invalid (key=”%s”, value=”%s”, rc=%d) | The property setting value is invalid. | Refer to the description column of the table in JP1/AJS Resource Hierarchy Properties . |
| 141001 | ERROR | Config key “%s” is invalid. | The specified property name is invalid. | Please contact support. |
| 141002 | ERROR | The value of config “%s” is empty. | The specified property’s setting value is empty. | Refer to the description column of the table in JP1/AJS Resource Hierarchy Properties . |
| 141003 | ERROR | The value of config “%s” is not numeric. | The specified property’s setting value is not a numeric value. | Refer to the description column of the table in JP1/AJS Resource Hierarchy Properties . |
| 141004 | ERROR | The value of config “%s” must be in the range from “%d” to “%d”. | The specified property’s setting value is out of range. | Refer to the description column of the table in JP1/AJS Resource Hierarchy Properties . |
| 141005 | ERROR | Failed to init the object. | The App type or Res type is invalid. | Please contact support. |
| 141006 | ERROR | The component “%s” is unknown. | The specified JP1 component is invalid. | Please verify the specified JP1 component name. For a list of available JP1 components, refer to the JP1 component field in Creating a JP1/AJS Resource Hierarchy . |
| 141007 | ERROR | The logical host is empty. | The logical host name is not specified. | Please verify the specified logical host name. For acceptable logical host names, refer to the logical host name field in Creating a JP1/AJS Resource Hierarchy . |
| 141013 | ERROR | Stop failed. | Failed to call the resource stop operation, which is executed when an error occurs during resource startup. | Please check the corresponding JP1 logs. |
| 141014 | ERROR | Cannot be stopped. | The resource stop operation, executed when an error occurs during resource startup, failed. | Please check the corresponding JP1 logs. |
| 141018 | ERROR | %s | If an error occurs while starting JP1 processes during resource startup, the details of the exception will be output. | Please check the corresponding JP1 logs. |
| 141025 | ERROR | %s | If an error occurs while stopping JP1 processes during resource termination, the details of the exception will be output. | Please check the corresponding JP1 logs. |
| 141028 | ERROR | QuickCheck failed. | An abnormality was detected during resource monitoring. | Please check the corresponding JP1 logs. |
| 141029 | ERROR | %s | If an error occurs while checking JP1 process status during resource monitoring, the details of the exception will be output. | Please check the corresponding JP1 logs. |
| 141303 | ERROR | Failed to stop “JP1_Base_%s”, rc=%d | Failed to stop the JP1/Base Windows service (“JP1_Base_logical_hostname”). | Please check the corresponding JP1 logs. |
| 141305 | ERROR | Failed to stop “JP1_Base_Event %s”, rc=%d | Failed to stop the JP1/Base Event Windows service (“JP1_Base_Event logical_hostname”). | Please check the corresponding JP1 logs. |
| 141307 | ERROR | Failed to start “JP1_Base_Event %s”, rc=%d | Failed to start the JP1/Base Event Windows service (“JP1_Base_Event logical_hostname”). | Please check the corresponding JP1 logs. |
| 141309 | ERROR | Failed to start “JP1_Base_%s”, rc=%d | Failed to start the JP1/Base Windows service (“JP1_Base_logical_hostname”). | Please check the corresponding JP1 logs. |
| 141312 | ERROR | Failed to stop “JP1_AJS2_%s”, rc=%d | Failed to stop the JP1/AJS3 Windows service (“JP1_AJS2_logical_hostname”). | Please check the corresponding JP1 logs. |
| 141314 | ERROR | Failed to start “JP1_AJS2_%s”, rc=%d | Failed to start the JP1/AJS3 Windows service (“JP1_AJS2_logical_hostname”). | Please check the corresponding JP1 logs. |
| 141401 | ERROR | Not found childTag(“%s”) | The specified child resource does not exist. | Please verify that the child resources (IP, Volume, or JP1/Base resources) specified during resource creation are correct. |
| 141402 | ERROR | Failed to execute command=[%s], rc=%d | The command to retrieve resource dependencies failed. | Please check the command line output in the log. |
| 141404 | ERROR | Failed to create dependency parentTag=[%s], childTag=[%s], rc=%d | Failed to create resource dependencies. | Please verify the existence of the parent and child resources. |
| 141406 | ERROR | Resource should be created on the local node. (local=%s, sys=%s) | The name does not match the local node. | Please contact support. |
| 141408 | ERROR | Invalid component label. (label=%s) | The JP1 component name specified during resource creation is invalid. | Please verify the specified JP1 component name. For a list of available JP1 components, refer to the JP1 component field in Creating a JP1/AJS Resource Hierarchy . |
| 141409 | ERROR | Error bringing resource “%s” in service on server “%s”’ | Failed to start the created resource. | Please check the corresponding JP1 logs. |
| 141503 | ERROR | A resource with the specified tag name “%s” already exists on the target machine “%s”. | The tag of the resource you attempted to extend already exists on the target node. | Please delete the corresponding resource hierarchy of the target node before extending a resource. |
| 141550 | ERROR | usage: %s [—server <server>] —tag <tag> <sub-command> sub-command: —set <cfg>=<value> —get <cfg> —default-get <cfg> —list-configs —show [—format <text|json>] |
The usage information was displayed because of an error in the arguments for the config.pl script, which handles property-related operations. | Check the log output and execute with the correct arguments. |
| 141552 | ERROR | resource “%s” not found on %s | The tag specified in the property configuration command does not exist. | Please specify the tag name of the existing resource. |
| 141553 | ERROR | “%s” is an unknown configuration. | The property name specified in the property configuration command is invalid. | Verify the property name using the —list-configs option, and then specify the correct property name. |
| 141554 | ERROR | The —set option must be in the format “<cfg>=<value>”. | The format of the property name and value specified in the property configuration command is invalid. | Please execute the command with the correct format. |
| 141602 | WARN | Could not resolve hostname “%s”. | Failed to resolve the logical host name. | Configure the network so that virtual IP addresses can be obtained using logical host names. |
| 141603 | WARN | Not found IP resource of “%s (%s)”. | There is no IP resource in ISP corresponding to the logical host’s IP address. | Ensure that the IP resource corresponding to the logical host’s IP address exists, and that it is in the ISP state on the server where the resource is being created. |
| 141606 | WARN | Not found FS resource (logical host: “%s”, shared file directory: “%s”). | The volume resource corresponding to the storage location for shared files used by the logical host does not exist. | Ensure that the volume resource corresponding to the storage location for the shared files used by the logical host exists, and that it is in the ISP state on the server where the resource is being created. |
| 141611 | ERROR | usage: depResources.pl <ip|ip-tag|fs|fs-tag|jp1ajsbase|jp1ajsbase-tag> <logicalHost> | The usage information was displayed because of invalid arguments for depResources.pl, a script that retrieves dependency information. | Please specify the correct arguments based on the usage information.. |
| 141650 | ERROR | usage: %s —list-event-server|—directory <event-server> | The usage information was displayed because of invalid arguments for parse-index.pl, a script that retrieves logical host information from the JP1 event server index file (*1) | Please specify the correct arguments based on the usage information. |
| 141652 | ERROR | Cannot open file “%s” | Failed to open the JP1 event server index file (*1). | Please check the status of the event server index file. |
| 141654 | ERROR | No logical host candidates were found in the index file. | No logical host candidates were found in the JP1 event server index file (*1). | Please configure the logical host for JP1. |
| 141656 | ERROR | There is no event-server “%s” entry in the index file. | No event-server entry matching the specified logical host was found in the JP1 event server index file (*1). | Check the configuration of the JP1 logical host and specify an existing logical host. |
*1 : This is the configuration file which maps logical hostnames to their respective settings and data storage paths used by the event server. For details, please refer to the JP1 documentation .
Post your comment on this topic.