The following is a list of the seeded error messages that may be included in a notification to the Trading Partner or System Administrator. The same error message may also appear in the process log file depending on the trace level activated. Along with each error message is an explanation of possible causes and recommended corrective actions.
The list is organized by functional area and error type for easy reference. The list contains the following columns:
Error Type
Error Code
Message Code
Message
Corrective Action
The Error Type identifies the target recipient of a notification. The target recipient is predetermined and is based on which party is most able to resolve the error. In a few instances, a notification is sent to both the Trading Partner and System Administrator so that the two parties may collaborate to resolve the error. The valid Error Types are listed in the following table:
| Error Type | Description |
|---|---|
| 10 | No notification |
| 20 | Notification sent to Trading Partner |
| 25 | Notification sent to both Trading Partner and System Administrator |
| 30 | Notification sent to System Administrator |
The Error Code identifies the status of the process. The valid Error Codes are shown in the following table:
| Error Code | Description |
|---|---|
| 10 | In Process |
| 0 | Success |
| 1 | Warning |
| 2 | Error |
Because the focus of this section is on troubleshooting, Error Type 10 (No Notification) and Error Code 0 (Success) are excluded from the list. Error Code 10 (In Process) is included to support troubleshooting, although this group does not represent an error. The engine will abort and roll back any process that does not have a status of "Success."
The Message Code is a code related to the message text string. This is used for quick identification of an error.
There are several error messages that can originate from multiple sources. The Message Code and Message string may be the same, but the Error Type and Error Code will be different. Ensure not to regard these as duplicates.
There are several categories of corrective action identified in the troubleshooting guide. The following table summarizes the categories and lists the corresponding reference section in this book:
| Corrective Action Category | Reference Section |
|---|---|
| Verify lookup data | XML Gateway Setup chapter: Define Lookup Values |
| Verify development setup data | XML Gateway Setup chapter: Define XML Standards Define Transactions |
| Verify implementation setup data | XML Gateway Setup chapter: Define System Profile Options Define Trading Partner Define Code Conversion |
| Verify queues and agent listeners are enabled | Integrating XML Gateway with Workflow Business Event System chapter: Manage Workflow Processes Monitor Workflow Processes |
| Enable trace or configure event subscriptions | Integrating XML Gateway with Workflow Business Event System chapter: Manage Workflow Processes Monitor Workflow Processes |
| Modify a message map: Action Definition | Message Designer chapter (see note following table): Reference the specific action under Transaction Map - Actions |
| Modify a message map: Root Element | Message Designer chapter (see note following table): File > Properties menu option |
| Load/Delete a map or DTD | Message Designer chapter (see note following table): How to Load/Delete Message Maps and DTDs |
| Verify Confirmation Message setup | Execution Engine chapter: How to Implement a Confirmation Message |
| Enter a bug | Work with Oracle World Wide Support to enter a bug. Include log file, message map, (.xgm file), and the associated DTD in the bug report. |
| Enter an enhancement request | Work with Oracle World Wide Support to enter an enhancement request. Include business justification and your specific scenario. Be as specific as possible. |
Note: Updated maps must be loaded into the XML Gateway repository.
Changes in the relationship between a map (.xgm) and the corresponding DTD may require the map, the DTD, or both to be loaded into the XML Gateway repository.
| Error Type | Error Code | Message Code | Message | Corrective Action |
|---|---|---|---|---|
| 30 | 1 | ECX_UTL_INVALID_OPERATION | UTL FILE Error: The file could not be opened or operated on as requested. | Verify that the file is read and write enabled. Use commands appropriate for your operating system to change protections if necessary. |
| 30 | 1 | ECX_UTL_INVALID_PATH | UTL FILE Error: File location or file name was invalid. | Verify that the directory identified by the profile option exists. Verify that the file name exists. Change the directory or file name if necessary. |
| 30 | 1 | ECX_UTL_WRITE_ERROR | UTL FILE Error: An operating system error occurred during the write operation. | Verify the setting for the directory identified by the profile option. Change UTL_FILE_DIR setting in INIT.ORA if necessary and bounce the database. Verify that the directory and file exist and are write-enabled. Use commands appropriate for your operating system to change protections if necessary. Change the directory or file name if necessary. |
| Error Type | Error Code | Error Message Code | Message | Corrective Action |
|---|---|---|---|---|
| 25 | 1 | ECX_NO_UNIQUE_TP_SETUP | Could not resolve a Unique/Destination Configuration for this Partner. | The inbound message envelope contained a Trading Partner ID that was not uniquely defined in XML Gateway. This occurs when the wrong ID was sent or the Trading Partner has not been defined in XML Gateway. Use the window to view/add the Trading Partner profile. |
| 30 | 1 | ECX_ADDR_DERIVATION_ERR | Unable to derive internal address ID for address type: &p_address_type and location code: &p_location_code. | Cannot successfully execute Derive Address ID from Location Code action. This occurs when the address type or the location code is invalid. Check the section of the Message Designer chapter for a list of supported address types. Verify that the location code is valid. |
| 30 | 1 | ECX_DELIVERY_TP_NOT_SETUP | Unable to determine the trading partner setup for Transaction type: &p_transaction_type, Transaction subtype: &p_transaction_subtype, Party site id: &p_party_site_id, Party id: &p_party_id, and Party type: &p_party_type. | Cannot determine Trading Partner with token values for Party Type, Party ID, Party Site ID, Transaction Type, and Transaction Subtype. Use the window/API to view/update the Trading Partner setup data. |
| 30 | 1 | ECX_DESTINATION_ADDR_NULL | Protocol Address missing for party id: &p_party_site_id and location code: &p_source_code. | The Protocol Address is null for the given Trading Partner (Party Site ID) and Source Location Code. Use the window to view/update the Trading Partner's protocol address. |
| 30 | 1 | ECX_DYN_ROUTING_NOT_ENABLED | &p_ext_type and &p_ext_subtype Not enabled for &p_party_ext_code in Oracle XML Gateway Server for Dynamic Routing. | The inbound transaction associated with the given external transaction type, transaction subtype, and source location code is not enabled for dynamic routing. Ensure that the "attribute3" variable in the message envelope contains a valid value. Use the window to view/update the Trading Partner Routing information representing the route to the Trading Partner. |
| 30 | 1 | ECX_INVALID_PARTY_TYPE | Party Type: &p_party_type is invalid. | Review seeded Party Type lookup and use a valid party type code. Enter an Enhancement Request for new Party Type if required. |
| 30 | 1 | ECX_INVALID_TP_HDR_ID | Tp_header_id: &p_tp_header_id is invalid. | Invalid Trading Partner ID. Use the retrieve/update APIs in ECXTPXFB to query/update a Trading Partner profile. |
| 30 | 1 | ECX_INVALID_TXN_PARAMS | Party Site ID or Transaction Type or Transaction Subtype cannot be NULL. | Use the window to view/update the Trading Partner profile and ensure that the Trading Partner Site, Transaction Type, and Transaction Subtype are valid. |
| 30 | 1 | ECX_NO_EMAIL_ADDR | Unable to determine TP email address for party_type: &p_party_type, transaction_type: &p_transaction_type, transaction_subtype: &p_transaction_subtype, and party_site_id: &p_party_site_id. | Cannot determine Trading Partner e-mail address with given token values to send notification. Use the window to review/update the e-mail address in the Trading Partner setup. |
| 30 | 1 | ECX_NO_ENVELOPE | Unable to determine envelope information for internal control number: &p_icn. | Envelope information for the given internal control number was not found. The internal control number is a system-generated number that uniquely identifies the XML message being processed. Verify that the internal control number is valid. |
| 30 | 1 | ECX_NO_UNIQUE_TP_SETUP | Could not resolve a Unique/Destination Configuration for this Partner. | Cannot determine unique Trading Partner detail for outbound transaction with the information identified. Check parameters for Party Type, Party ID, Party Site ID, Transaction Type, and Transaction Subtype. |
| 30 | 1 | ECX_PARTY_ID_NOT_NULL | Party ID is a required parameter. | Pass valid Party ID, Party ID cannot be null. |
| 30 | 1 | ECX_PARTY_SITE_ID_NOT_NULL | Party Site ID is a required parameter. | Pass valid Party Site ID, Party Site ID cannot be null. |
| 30 | 1 | ECX_PARTY_TYPE_NOT_NULL | Party Type is a required parameter. | Review seeded Party Type lookup and pass valid Party Type. Party Type cannot be NULL. |
| 30 | 1 | ECX_PARTY_TYPE_NOT_SET | Please provide party_type for the trading partner. | Party Type not available for XML Gateway to uniquely determine Trading Partner. Provide valid Party Type from seeded Party Type lookup. |
| 30 | 2 | ECX_PARTY_TYPE_NOT_SET | Please provide party_type for the trading partner. | Party type not available for XML Gateway to uniquely determine Trading Partner. Provide valid Party Type from seeded Party Type lookup. |
| 30 | 1 | ECX_RCVR_NOT_SETUP | Receiver TP setup not found for tp header id: &p_tp_header_id. | The Receiving Trading Partner was not found. Use the window to verify that the Trading Partner is defined. |
| 30 | 2 | ECX_RULE_INVALID_TP_SETUP | The Standard: &p_standard_code, Transaction Type: &p_transaction_type, Transaction Subtype: &p_transaction_subtype, and Location Code: &p_party_site_id is not enabled in the XML Gateway Server. Please check your Setup. | Either invalid transaction, standard code, or Trading Partner encountered. Use the Define Transactions window to view/update the transaction setup. Use the window/API to view/update the Trading Partner setup and the transactions enabled for the the Trading Partner. |
| 30 | 1 | ECX_SNDR_NOT_SETUP | Sender TP setup not found for tp_header_id: &p_tp_header_id. | The Sending Trading Partner was not found. Use the window to verify that the Trading Partner is defined. |
| 30 | 1 | ECX_STATIC_ROUTING_NOT_ENABLED | &p_ext_type and &p_ext_subtype Not enabled for &p_party_ext_code in Oracle XML Gateway Server for Static Routing. | Could not determine routing information for given Trading Partner and transaction. Use the window to view/update the Trading Partner details for the Routing ID. |
| 30 | 1 | ECX_TRANSACTION_NOT_ENABLED | &p_ext_type and &p_ext_subtype Not enabled for &p_party_ext_code in Oracle XML Gateway Server. | Inbound transaction not enabled in XML Gateway. Check envelope parameter values for Message Standard, Transaction Type, Transaction Subtype, and Source Trading Partner Location. Either the envelope information contains an error or the Trading Partner has not been defined. Use the window to define the Trading Partner to process this inbound transaction. |
| 30 | 1 | ECX_TRANSACTION_NOT_FOUND | No Transaction defined for Transaction Type: &p_transaction_type, Transaction Subtype: &p_transaction_subtype, and Party Type: &p_party_type. | Given Party Type, Transaction Type, and Transaction Subtype not found. Check parameter values being passed. |
| 30 | 2 | ECX_USER_TP_VALID | The Standard: &p_standard_code, Transaction Type: &p_transaction_type, Transaction SubType: &p_transaction_subtype, Location Code: &p_party_site_id and User Name:&p_user_name is not enabled in the XML Gateway Server. Please check your Setup. | Either invalid standard code, transaction, user name, or Trading Partner encountered. Use the Trading Partner User Setup form to associate a user with a specific Trading Partner. Use the Trading Partner Setup form to view or update the Trading Partner setup. |
| 30 | 2 | ECX_TP_USER_ASSIGNED | The user &user_name is already assigned to another Trading Partner. | Assign different users to the Trading Partner in the Trading Partner User Setup form. |
| 30 | 2 | ECX_TP_INSUFFICIENT_VAL | Please save the header record before selecting User Setup. | In the Trading Partner Setup form, save the Trading Partner header record including Trading Partner Type, Trading Partner Name, Trading Partner Site, and Company Admin Email first before clicking the User Setup button to have access to the Trading Partner User Setup form. |
Note: Party Side ID would be used almost everywhere in Oracle XML Gateway. If you get an error like "Party Site ID not authorized", then make sure that Party Site ID is passed in the Message Envelope for Inbound transactions. Also, Party Site ID should be passed in ATRRIBUTE3 of Message envelope. Otherwise transactions will not work properly.
| Error Type | Error Code | Error Message Code | Message | Corrective Action |
|---|---|---|---|---|
| 25 | 1 | ECX_DELIVERY_HUB_NOT_SETUP | Unable to resolve the hub destination parameters for this trading partner hub. | Cannot determine the hub attributes (for inbound transaction) for this Trading Partner. Use the Define Hubs and windows to view/update hub attributes. Hub attributes are used if Trading Partner "Connection/Hub" attribute is set to "Hub." |
| 30 | 1 | ECX_DELIVERY_HUB_NOT_SETUP | Unable to resolve the hub destination parameters for this trading partner hub. | Cannot determine the hub attributes (for outbound transaction) for this Trading Partner. Use the Define Hubs and windows to view/update hub attributes. Hub attributes are used if Trading Partner "Connection/Hub" attribute is set to "Hub." |
| Error Type | Error Code | Error Message Code | Message | Corrective Action |
|---|---|---|---|---|
| 30 | 1 | ECX_CODE_CONVERSION_DISABLED | Standard Code: &MESSAGE_STANDARD not Found. Code Conversion is disabled. | The execution engine is using an XML standard not defined in ECX_STANDARDS, so the code conversion cannot be performed. Use the Define XML Standards window to review the seeded XML standards. Enter an enhancement request for required XML standard and identify the transactions that require this new standard. |
| 30 | 1 | ECX_TP_NOT_FOUND | Trading Partner not Found. Code Conversion is disabled. | A warning indicating that the Trading Partner was not found, so Trading Partner code conversion cannot be performed. Use the window to view/update the Trading Partner setup. |
| Error Type | Error Code | Error Message Code | Message | Corrective Action |
|---|---|---|---|---|
| 10 | 10 | ECX_DEQUEUED_LOGGED | Message dequeued and logged | Message dequeued and logged. |
| 30 | 2 | ECX_MANY_PROCESSING_QUEUES | More than one row resulted while querying the queue name. | Unable to determine unique queue for inbound transaction. Use the Define Transactions window to view/update the queue definition for the inbound transaction being processed. |
| 30 | 1 | ECX_NO_PROCESSING_QUEUE | Unable to determine processing engine queue. | Unable to determine processing queue for inbound transaction. Use the Define Transactions window to view/update the queue definition for the inbound transaction being processed. |
| 30 | 1 | ECX_PROCESSING_ENQ_ERROR | Error enqueuing to processing engine: &p_queue_name | Unable to enqueue when processing inbound transaction. Ensure that the transaction queue and agent listener are enabled. |
| 30 | 1 | ECX_REPROCESSING_ERROR | Error enqueuing to processing engine, while REPROCESSING: &p_out_queue | Unable to enqueue when reprocessing inbound transaction. Ensure that the transaction queue and agent listener are enabled. |
Note: The enqueue_enabled and dequeue_enabled are YES for all ECX% queues in the DBA_QUEUES view. Make sure that you always get 'Y' for all the transaction queues.
| Error Type | Error Code | Error Message Code | Message | Corrective Action |
|---|---|---|---|---|
| 10 | 10 | ECX_PROCESSING_RULE | Processing rule | Processing rule |
| 30 | 2 | ECX_BUSINESS_EVT_NOT_SET | Business Event Not Set for the Transaction | Check that the message map for the inbound transaction concludes with root level, postprocess procedure call action to call the ECX_STANDARD.setEventDetails API. This API sets the business event to be raised to indicate an inbound transaction has been successfully processed. The corresponding application event subscription will consume this event. |
| 30 | 2 | ECX_IN_RULE_PROCESSING_ERROR | Error in processing inbound rule | Unexpected exception when processing inbound rule. Check the setup for event and agent listener. |
| Error Type | Error Code | Error Message Code | Message | Corrective Action |
|---|---|---|---|---|
| 30 | 2 | ECX_CONFIRM_DOC_NOT_FOUND | Unable to determine the inbound document for which this confirmation is being sent. | Verify that the Workflow for the outbound confirmation includes the internal control number corresponding to the inbound business document. Refer to the Workflow Development Guidelines on how to implement the Confirmation BoD for the details. |
| 30 | 2 | ECX_CONFIRM_GENERATE_FAILED | Cannot generate confirmation for Confirmation Inbound. Loop Detected. | Cannot use a Confirmation message to acknowledge a Confirmation message. |
| 30 | 2 | ECX_CONFIRM_STATUS_NOT_FOUND | Cannot find confirmation status for the trading partner. | Could not determine the Confirmation flag setting for the Trading Partner. Use the window to view/update the Trading Partner setup and set the Confirmation flag if necessary. |
| 30 | 2 | ECX_CONFIRM_TP_NOT_SETUP | Unable to determine trading partner setup for the Confirmation. Transaction Type: &p_transaction_type, Transaction Subtype: &p_transaction_subtype, Location Code: &p_location_code. | Cannot determine Trading Partner to send the Confirmation. Use the window to view/update the Trading Partner setup for the given Transaction Type, Transaction Subtype, and Source Trading Partner Location Code. |
| Error Type | Error Code | Error Message Code | Message | Corrective Action |
|---|---|---|---|---|
| 20 | 1 | ECX_INCOMPLETE_OAG_DATE | Incomplete OAG Date: &p_datetime. | A warning indicating the incoming OAG date was incomplete. This could cause the conversion to the Oracle date to be incomplete. |
| 20 | 1 | ECX_USER_INVOKED_EXIT | Program Exit invoked by the User. | A warning indicating a user-programmed exit was executed. |
| 30 | 1 | ECX_CANNOT_CONVERT_TO_DATE | Cannot Convert to Date. | Usage of (or other data conversion APIs) in the message map triggered an error. Use Message Designer to verify that the map action/API is defined correctly. Make the necessary changes and reload the updated map. |
| 30 | 2 | ECX_CANNOT_CONVERT_TO_NUM | Cannot convert the value &p_value to number. | Invalid number used with math function. Verify that the variable/literal value is numeric. Make the necessary changes and reload the updated map. |
| 30 | 1 | ECX_CANNOT_CONVERT_TO_NUMBER | Cannot Convert to number. | Condition evaluation error, inform the System Administrator or log a bug. |
| 30 | 1 | ECX_COND_NOT_DEFINED | Condition type: &TYPE not defined. | Review map actions using Message Designer to ensure that the condition expressions are defined correctly with two operands and a valid operator. Make the necessary changes and reload the updated map. |
| 30 | 2 | ECX_DATATYPE_CONV_FAILED | DataType conversion failed while inserting the level into the table. | Datatype mismatch between source and database datatype. Make the necessary changes and reload the updated map. |
| 30 | 1 | ECX_INVALID_ADDRESS_TYPE | Address type: &p_address_type is invalid. | Invalid address type. Check section of Message Designer chapter for list of supported address types. |
| 30 | 1 | ECX_INVALID_NUMBER | Binding value &pre_var_value for bind variable &variable_name is an invalid number. | Usage of the action in the message map contained an invalid number for the given Bind Value and Bind Variable combination. Use Message Designer to review the Source Definition of the map for all usage of the Append Where Clause, make the necessary changes, and reload the updated map. |
| 30 | 1 | ECX_MAPPINGS_NOT_FOUND | Mappings for Map ID: &MAP_ID not found. | Map details for given Map ID not found because incorrect mappings, such as level cross overs, were detected. Use Message Designer to review the message map. Make the necessary changes, and reload the updated map. |
| 30 | 1 | ECX_MATH_FUNC_NOT_NULL | Math function type cannot be null. | Usage of Math function is incomplete. Use Message Designer to review all math functions defined, make the necessary changes, and reload the updated map. |
| 30 | 1 | ECX_ROOT_ELEMENT_NOT_FOUND | Root Element information not found for Map ID: &MAP_ID. | Root element information not found for given message map. Use the Message Designer to open the map and use the option to add the root element. Reload the updated map. |
| 30 | 1 | ECX_ROOT_INFO_NOT_FOUND | Map root element or parent node ID not found. | Root element or parent node ID not found for given message map. Use Message Designer to open the map, and use the option to add the root element or parent node ID. Reload the updated map. |
| 30 | 1 | ECX_SEED_DATA_NOT_FOUND | Seed Data is missing for Map ID: &MAP_ID. | Map data missing for given Map ID. Make sure you are operating in the desired database instance. |
| 30 | 2 | ECX_STACKVAR_NOT_FOUND | Stack Variable not found. | Error in processing global variables. Inform System Administrator or log a bug. |
| 30 | 1 | ECX_UNSUPPORTED_COND_TYPE | Unsupported condition type: &TYPE. | Review map actions using Message Designer to ensure that the condition expressions are defined correctly with two operands and a valid operator. Make the necessary changes and reload the updated map. |
| 30 | 2 | ECX_UNSUPPORTED_DATATYPE | Unsupported Data Type. | The message map contained usage of unsupported data types. Use the Message Designer to review the message map to verify that only the VARCHAR2, NUMBER, DATE, CHAR, and CLOB data types are used. Make the necessary map changes and reload the updated map. |
| 30 | 1 | ECX_UNSUPPORTEDDATE_COND | Unsupported Condition for Date. | Cannot use Condition Expression to compare dates. Use database functions instead to compare dates. |
| 30 | 1 | ECX_UNSUPPORTED_MATH_FUNC | Unsupported Math function. | XML Gateway supports the four basic math functions: add, subtract, multiply, and divide. Use database functions for other math functions. |
| 30 | 1 | ECX_UNSUPPORTED_NUMBER_COND | Unsupported Condition for Number. | Unsupported condition for numbers. Verify that the condition operator is relevant for numbers. Make the necessary map changes and reload the updated map. |
| 30 | 1 | ECX_UNSUPPORTED_STRING_COND | Unsupported Condition for Strings. | Unsupported condition for strings. Verify that condition operator is relevant for strings. Make the necessary map changes and reload the updated map. |
| Error Type | Error Code | Error Message Code | Message | Corrective Action |
|---|---|---|---|---|
| 10 | 10 | ECX_REPROCESSING_MESSAGE | Reprocessing message. | Reprocessing message. |
| 25 | 1 | ECX_PROTOCOL_ADDR_NULL | Destination Address missing for party ID: &p_tp_detail_id. | Inbound message envelope did not contain a protocol address for the given Trading Partner. Use the window to view/update the Trading Partner's protocol address. |
| 30 | 2 | ECX_MSG_EXISTS_IN_LOG | Message already in the Log &p_msgid. | Inbound message already exists; duplicate not allowed. |
| 30 | 1 | ECX_MSGID_NOT_FOUND | Msg Id: &p_msgid not Found. | Inbound message for given message ID not found. Make sure the message ID is valid. |
| 30 | 1 | ECX_UNSUPPORTED_STANDARD | Not a Supported Standard in the XML Gateway Server. | Inbound message envelope indicates message is for an XML standard not supported by Oracle E-Business Suite. Use the Define XML Standards window to view the list of supported standards. Enter an enhancement request for the required XML standard and identify the transactions that require this new standard. |
| Error Type | Error Code | Error Message Code | Message | Corrective Action |
|---|---|---|---|---|
| 10 | 10 | ECX_PROCESSING_MESSAGE | Processing message. | N/A |
| 10 | 10 | ECX_TRIGGER_OUTBOUND | Triggering outbound. | N/A |
| 25 | 1 | ECX_PARSE_ERROR | Parse Error. | Parse error encountered because the generated or received XML message was poorly formed or invalid as per the DTD. The other possible reason for a parse error is that the DTD referenced in the map is not the same DTD that was passed. Make sure that the DTD referenced in the map is loaded into the XML Gateway repository. |
| 30 | 1 | ECX_DOCLOGS_NOT_EXISTS | No document log exists for message ID: &p_msgid. | ECX_DOCLOGS entry does not exist for the given message ID. Ensure that the message ID is valid. |
| 30 | 1 | ECX_DTD_NOT_FOUND | DTD not found for Map ID: &MAP_ID. | The DTD referenced in the message map was not found because the map referenced the wrong DTD or the DTD was not loaded into the XML Gateway repository. Use Message Designer to check the DTD referenced in the map, make the necessary changes, and reload the updated map. If necessary load the correct DTD into the XML Gateway repository. |
| 30 | 2 | ECX_ERROR_NOT_SET | Unable to set error information. | Inform System Administrator or log a bug. |
| 30 | 1 | ECX_MAP_NOT_FOUND | Not a Supported Map &p_map_code in the XML Gateway Server. | Given map code associated with the outbound transaction enabled for a Trading Partner is not supported. Use the window to view/update the map code associated with the enabled outbound transaction. Make sure the map has been loaded in the XML Gateway repository. |
| 30 | 2 | ECX_MAP_NOT_FOUND | Not a Supported Map &p_map_code in the XML Gateway Server. | Given map code associated with the inbound transaction enabled for a Trading Partner is not supported. Use the window to view/update the map code associated with the enabled inbound transaction. Make sure the map has been loaded in the XML Gateway repository. |
| 30 | 1 | ECX_MSGID_NOT_FOUND | Message ID cannot be NULL. | Pass valid value for Message ID parameter. |
| 30 | 1 | ECX_MSGID_NOT_NULL | Message ID cannot be NULL. | Pass valid value for Message ID parameter. |