uCosminexus Service Platform, Messages
A command issued to Cosminexus Reliable Messaging failed. (system name = aa....aa, command = bb....bb, name = cc....cc, error code = dd....dd, error message = ee....ee)
| Error code | Cause | Action |
|---|---|---|
| HRM-00822 | An internal error occurred. | Check the messages issued before and after this error, and eliminate the cause of the error. If the error cannot be corrected, collect the log and trace of Reliable Messaging, and then contact the maintenance personnel. |
| HRM-01201 | The value of a method argument was null. | Collect the log and trace information, and then contact the maintenance personnel. |
| HRM-01202 | The value of a method argument was invalid. | Collect the log and trace information, and then contact the maintenance personnel. |
| HRM-01203 | An unsupported command was executed. | Collect the log and trace information, and then contact the maintenance personnel. |
| HRM-01204 | A method execution failed because CommandAdapter was in the close status. | Check the messages issued before and after this error, and eliminate the cause of the error. If the error cannot be corrected, collect the log and trace of Reliable Messaging, and then contact the maintenance personnel. |
| HRM-20010 | The value specified in a command option was invalid. | Check the messages issued before and after this error, and eliminate the cause of the error. If the error cannot be corrected, collect the log and trace of Reliable Messaging, and then contact the maintenance personnel. |
| HRM-20011 | The command format is invalid. | Collect the log and trace information, and then contact the maintenance personnel. |
| HRM-20012 | The command failed. | Check the message log file, identify the message indicating the cause of the error, and then take appropriate action according to that message. After eliminating the cause of the error, re-execute the command. |
| Error code | Cause | Action |
|---|---|---|
| HRM-20000 | The specified queue name exceeds 20 characters, which is the maximum. | Collect the log and trace information, and then contact the maintenance personnel. |
| HRM-20001 | The specified queue name contains an invalid character. | Collect the log and trace information, and then contact the maintenance personnel. |
| HRM-20002 | The specified queue name already exists. | Check to see if a queue having any of the following queue name used by HCSC already exists:
|
| HRM-20006 | The system status is invalid. | Check whether the system status allows execution of the command issued by the Reliable Messaging system. If necessary, change the status of the Reliable Messaging system, and then re-execute the command. |
| HRM-20036 | A destination with the specified name does not exist. | Collect the log and trace information, and then contact the maintenance personnel. |
| HRM-20037 | The queue-to-queue transfer function cannot be used because the function is now disabled. | Specify true in Reliable Messaging's configuration property RMTRConnectFlag, restart Reliable Messaging, and then re-execute the command. |
| HRM-20060 | Queue creation failed because the same queue name as RMDeadMessageQueueName was specified in the system status other than MANAGED_STATE. | Make sure that RMDeadMessageQueueName of Reliable Messaging does not match the following queue names used by HCSC:
|
| HRM-20061 | Queue creation failed because an attempt was made to use the same name as a deleted queue with a different type. | First, restart Reliable Messaging, and then re-execute the command. |
| HRM-20062 | Queue creation failed because an attempt was made to use the same name as a deleted queue with a different queue mode. | First, restart Reliable Messaging, and then re-execute the command. |
| HRM-20063 | Creation of a shared receive queue failed because an attempt was made to use the same name as a deleted queue with a different maximum message length. | First, restart Reliable Messaging, and then re-execute the command. |
| HRM-20064 | Queue creation failed because the version is not supported by the shared receive queue. | Collect the log and trace information, and then contact the maintenance personnel. |
| HRM-20065 | Creation of a shared queue failed due to a database access error. | Either the database has been stopped or the corresponding share receive queue has been deleted. After eliminating the cause of the error, re-execute the command. |
| HRM-20100 | The specified display name already exists. | Check and if necessary, revise the value of the display name of the specified queue, and then re-execute the command. |
| Error code | Cause | Action |
|---|---|---|
| HRM-20000 | The specified queue name exceeds 20 characters, which is the maximum. | Collect the log and trace information, and then contact the maintenance personnel. |
| HRM-20001 | The specified queue name contains an invalid character. | Collect the log and trace information, and then contact the maintenance personnel. |
| HRM-20003 | A queue having the specified queue name does not exist. | This error code is output when deleting once again, and therefore, you are not required to take any action. |
| HRM-20006 | The system status is invalid. | Check whether the system status allows execution of the command issued by the Reliable Messaging system. If necessary, change the status of the Reliable Messaging system, and then re-execute the command. |
| HRM-20009 | The specified queue cannot be deleted or its attributes cannot be changed because messages have been registered in that queue. | Wait until the messages have been sent and then delete the adapter, or forcibly delete the adapter. |
| HRM-20035 | The current status does not allow changing of the queue configuration. | Collect the log and trace information, and then contact the maintenance personnel. |
| HRM-20037 | The queue-to-queue transfer function cannot be used because the function is now disabled. | Specify true in Reliable Messaging's configuration property RMTRConnectFlag, restart Reliable Messaging, and then re-execute the command. |
| HRM-20059 | Queue deletion processing failed because the queue was monitored by a Message-driven Bean. | Collect the log and trace information, and then contact the maintenance personnel. |
| HRM-20066 | Queue deletion processing failed because the queue was not suppressed or in shutdown status. | Collect the log and trace information, and then contact the maintenance personnel. |
| HRM-20067 | Queue deletion processing failed because a transaction on that queue was under execution. | Re-execute the command after the transaction for the queue is committed. |
| HRM-20068 | Queue deletion processing failed because the same queue name as RMDeadMessageQueueName was specified at a system status other than MANAGED_STATE immediately after the start of Reliable Messaging. | Collect the log and trace information, and then contact the maintenance personnel. |
| HRM-20072 | Queue deletion failed due to shutdown status with an unknown queue type. | Collect the log and trace information, and then contact the maintenance personnel. |
| Error code | Cause | Action |
|---|---|---|
| HRM-20006 | The system status is invalid. | Check whether the system status allows execution of the command issued by the Reliable Messaging system. If necessary, change the status of the Reliable Messaging system, and then re-execute the command. |
| HRM-20037 | The queue-to-queue transfer function cannot be used because the function is now disabled. | Specify true in Reliable Messaging's configuration property RMTRConnectFlag, restart Reliable Messaging, and then re-execute the command. |
| HRM-20038 | The specified destination name already exists. | Check whether the destination name shown as name already exists. Make sure that the destination name created by the user does not match the following destination name used by HCSC:
|
| Error code | Cause | Action |
|---|---|---|
| HRM-20006 | The system status is invalid. | Check whether the system status allows execution of the command issued by the Reliable Messaging system. If necessary, change the status of the Reliable Messaging system, and then re-execute the command. |
| HRM-20036 | A destination with the specified name does not exist. | This error code is output when deleting once again, and therefore, you are not required to take any action. |
| HRM-20037 | The queue-to-queue transfer function cannot be used because the function is now disabled. | Specify true in Reliable Messaging's configuration property RMTRConnectFlag, restart Reliable Messaging, and then re-execute the command. |
| HRM-20039 | The specified destination cannot be deleted because it is referenced by a queue. | Re-execute the command. If re-execution of the command does not recover the error, collect the log and trace, and then contact the maintenance personnel. |
| Error code | Cause | Action |
|---|---|---|
| HRM-20000 | The specified queue name exceeds 20 characters, which is the maximum. | Collect the log and trace information, and then contact the maintenance personnel. |
| HRM-20001 | The specified queue name contains an invalid character. | Collect the log and trace information, and then contact the maintenance personnel. |
| HRM-20003 | A queue having the specified queue name does not exist. | Collect the log and trace information, and then contact the maintenance personnel. |
| HRM-20006 | The system status is invalid. | Check whether the system status allows execution of the command issued by the Reliable Messaging system. If necessary, change the status of the Reliable Messaging system, and then re-execute the command. |
| HRM-20007 | The command cannot be executed because the specified queue is in shutdown status. | Collect the log and trace information, and then contact the maintenance personnel. |
| HRM-20037 | The queue-to-queue transfer function cannot be used because the function is now disabled. | Specify true in Reliable Messaging's configuration property RMTRConnectFlag, restart Reliable Messaging, and then re-execute the command. |
| Error code | Cause | Action |
|---|---|---|
| HRM-20000 | The specified queue name exceeds 20 characters, which is the maximum. | Collect the log and trace information, and then contact the maintenance personnel. |
| HRM-20001 | The specified queue name contains an invalid character. | Collect the log and trace information, and then contact the maintenance personnel. |
| HRM-20003 | A queue having the specified queue name does not exist. | There is no problem if this message was displayed during adapter deletion or cancellation of HCSC server setup. For any other case, collect the log and trace information, and then contact the maintenance personnel. |
| HRM-20006 | The system status is invalid. | Check whether the system status allows execution of the command issued by the Reliable Messaging system. If necessary, change the status of the Reliable Messaging system, and then re-execute the command. |
| HRM-20007 | The command cannot be executed because the specified queue is in shutdown status. | Collect the log and trace information, and then contact the maintenance personnel. |
| HRM-20037 | The queue-to-queue transfer function cannot be used because the function is now disabled. | Specify true in Reliable Messaging's configuration property RMTRConnectFlag, restart Reliable Messaging, and then re-execute the command. |
| HRM-20041 | The specified queue type is invalid. | Collect the log and trace information, and then contact the maintenance personnel. |
All Rights Reserved. Copyright (C) 2015, Hitachi, Ltd.