Error Code

| Print out this category

Error Code
The error code list is shown below. Remedy are error codes of "-", and for all the error codes out of the list, contact Field Suppot Group in the sales company.

Error Code (hex number) | Description | Remedy | Cause of error
The first digit Error field | The second digit Operator | The 3rd - 4th digits Method category | The 5th digit Category code | The 6 - 8th digits Description code | CDS delivery server | UP DATER | CDS file server | Network
8 | Error
| 0 | Not defined.
| 1 | CDS server
|  | x | x | Relating method code
|  |  |  | 0 | Not categorized
|  |  |  |  | 0 | 0 | 1 | No value is set in a mandatory data entry item | - | - |  | - | -
|  |  |  |  | 0 | 0 | 2 | In a string type of a data entry item, digit number and/or character type is/are set against the regulations | - | - |  | - | -
|  |  |  |  | 0 | 0 | 3 | In an data entry item, the value is set against the regulations (E.g. the set value is other than "Operator: 4. Service person, 5. User") | - | - |  | - | -
|  |  |  |  | 0 | 0 | 4 | No applicable delivery information exists | - |  | - | - | -
|  |  |  | 1 | Operation
|  |  |  |  | 0 | 0 | 1 | Inconsistency between the current firmware component in the data entry item and delivery information (E.g. the conditions for automatic update are not met. The settings of a mandatory additional set are invalid) | - |  |  | - | -
|  |  |  |  | 0 | 0 | 2 | In a notice of delivery-allowed information, an install-set was release to the market, but the market release was stopped during the delivery | - |  | - | - | -
|  |  |  |  | 0 | 0 | 3 | No mail template file exists | - |  | - | - | -
|  |  |  |  | 0 | 0 | 4 | The device serial number in the data entry item differs from that in delivery information | - |  | - | - | -
|  |  |  |  | 0 | 0 | 5 | User is selected as Operator in the data entry items and the retrieval type is other than the latest | - |  | - | - | -
|  |  |  |  | 0 | 0 | 6 | The retrieval type in the data entry item is special and registration ID and individual Password are not set (* Operator did not enter registration ID and individual Password) | - |  | - | - | -
|  |  |  |  | 0 | 0 | 7 | The retrieval type in the data entry item is special and Operator is not Service person | - |  | - | - | -
|  |  |  |  | 0 | 0 | 8 | As to the device serial number in the data entry items, there is no applicable device code product | - |  | - | - | -
|  |  |  |  | 0 | 0 | 9 | The retrieval type in the data entry items is special and there are no basic-set applicable to the registration ID and Password (* When wrong registration ID or Password was entered by an operator) | - |  | - | - | -
|  |  |  |  | 0 | 0 | A | The delivery status is Applying | - |  | - | - | -
|  |  |  |  | 0 | 0 | B | No approval information exists about EULA or the export criteria when the delivery is determined | - |  | - | - | -
|  |  |  |  | 0 | 0 | C | The delivery status is Distributing/Distributed/Applying/Finished/Failed | - |  | - | - | -
|  |  |  |  | 0 | 0 | D | The delivery status is Distributing/Distributed/Applying/Finished/Failed | - |  | - | - | -
|  |  |  |  | 0 | 0 | E | The delivery status is New/Waiting to Distribute/Distributed/Applying/Finished/Failed | - |  | - | - | -
|  |  |  |  | 0 | 0 | F | The delivery code is other than Distributing. (Firmware delivery) | - |  | - | - | -
|  |  |  |  | 0 | 0 | 0 | The delivery status is New/Waiting to Distribute/Distributing/Applying/Finished/Failed | - |  | - | - | -
|  |  |  |  | 0 | 0 | 1 | The delivery status is Distributing/Distributed/Applying/Finished/Failed | - |  | - | - | -
|  |  |  |  | 0 | 0 | 2 | Device is "Not applicable to CDS" (Firmware delivery) | - |  | - | - | -
|  |  |  | 2 | I/O
|  |  |  |  | 0 | 0 | 1 | The specified license access number does not exist in LMS | - |  | - | - | -
|  |  |  |  | 0 | 0 | 2 | The specified license access number has been deauthorized | - |  | - | - | -
|  |  |  |  | 0 | 0 | 3 | The package product of the entered license access number doesn't include MEAP application/System Option | - |  | - | - | -
|  |  |  |  | 0 | 0 | 4 | The sales company for the MEAP application isn't identical with the sale company for the package product | - |  | - | - | -
|  |  |  |  | 0 | 0 | 5 | The number of licenses to be issued will exceed the limit number allowed to register | - |  | - | - | -
|  |  |  |  | 0 | 0 | 6 | As for System Option for the same function, the license keys were issued more than the defined number of times for the same device serial number | - |  | - | - | -
|  |  |  |  | 0 | 0 | 7 | No device product exists applicable to the optional product | - |  | - | - | -
|  |  |  |  | 0 | 0 | 8 | No product exists applicable to the device serial number | - |  | - | - | -
|  |  |  |  | 0 | 0 | 9 | The product of the entered license access number cannot be used with this device because the settings of the sales company are incorrect | - |  | - | - | -
|  |  |  |  | 0 | 0 | A | No product linked to the license access number is registered in CDS for delivery | - |  | - | - | -
|  |  |  |  | 0 | 0 | B | Although the product linked to the license access number is registered in CDS for delivery, the delivery is stopped now | - |  | - | - | -
|  |  |  |  | 0 | 0 | C | No existence of optional product applicable to the device serial number. | - |  | - | - | -
|  |  |  |  | 0 | 0 | D | The license access number has been registered for another device | - |  | - | - | -
|  |  |  |  | 0 | 0 | E | For the device product applicable to the device serial number, no available software (MEAP application, System Option) exists | - |  | - | - | -
|  |  |  |  | 0 | 1 | 0 | LMS system error | - |  | - | - | -
| 2~5
|  | x | x | Relating method code
|  |  |  | 0 | Not cartelized
|  |  |  |  | 0 | 0 | 0 | Not defined | Normally not indicated
|  |  |  |  | 1 | 0 | 0 | Unknown error | Normally not indicated
|  |  |  | 1 | Operation
|  |  |  |  | 0 | 0 | 1 | Processing exclusively | Start the operation again after terminating other Updater operations being executed simultaneously | - |  | - | -
|  |  |  |  | 1 | 0 | 1 | Failed to process preparation for use | - | - |  | - | -
|  |  |  |  | 1 | 0 | 2 | Failed to process use end | - | - |  | - | -
|  |  |  |  | 1 | 0 | 3 | Time out during restart of readiness preparation | - | - |  | - | -
|  |  |  |  | 1 | 0 | 4 | Session time-out excluding after application inquiry (after issuing delivery ID) | Start the operation again from the beginning |  |  | - | -
|  |  |  |  | 1 | 0 | 5 | CDS URL is not set | Set CDS URL | - |  | - | -
|  |  |  |  | 1 | 0 | 6 | There is another job | Start the operation again after terminating the job of the device | - |  | - | -
|  |  |  | 2 | I/O
|  |  |  |  | 1 | x | x | An internal error about file operation | - | - |  | - | -
|  |  |  |  | 2 | x | x | An internal error about xML file operation | - | - |  | - | -
|  |  |  |  | 3 | 0 | 1 | Failed to output the license file | - | - |  | - | -
|  |  |  | 3 | Device
|  |  |  |  | 1 | x | x | An internal error in CPCA | - | - |  | - | -
|  |  |  |  | 2 | x | x | An internal error in IMI | - | - |  | - | -
|  |  |  |  | 3 | x | x | An internal error in SMS | - | - |  | - | -
|  |  |  |  | 4 | x | x | An internal error in NLM | - | - |  | - | -
|  |  |  | 4 | SOAP communication
|  |  |  |  | 1 | 0 | 1 | The processing thread stopped | - | - |  | - | -
|  |  |  |  | 1 | 0 | 2 | Processing SOAP communication now | - | - |  | - | -
|  |  |  |  | 1 | 0 | 3 | The function type is not matched | - | - |  | - | -
|  |  |  |  | 1 | 0 | 4 | An invalid SOAP response error | - |  | - | - | -
|  |  |  |  | 2 | 0 | 1 | An internal error about application information | - | - |  | - | -
|  |  |  |  | 2 | 0 | 2 | config.xml is NOT FOUND | - | - |  | - | -
|  |  |  |  | 2 | 0 | 3 | type.xml is NOT FOUND | - | - |  | - | -
|  |  |  |  | 2 | 0 | 4 | An error in binding type.xml | - | - |  | - | -
|  |  |  |  | 2 | 0 | 5 | An error in creating a service tab | - | - |  | - | -
|  |  |  |  | 2 | 0 | 6 | A runtime error in performing the web method | - | - |  | - |
|  |  |  |  | 2 | 0 | 7 | An unknown host error in performing the web method | Check the network environment of the device and start the operation again Check if the URL settings of the CDS server are correct, and start the operation again after resetting |  |  | - |
|  |  |  |  | 3 | 0 | 1 | The delivery server is stopped | - |  | - | - | -
|  |  |  |  | 3 | 0 | 2 | An error occurrence in the delivery server | - |  |  | - | -
|  |  |  | 5 | HTTP communication
|  |  |  |  | 1 | 0 | 1 | Specified Hash Algorithm is unknown | - | - |  | - | -
|  |  |  |  | 2 | 0 | 1 | Invalid HTTP request | - | - |  |  |
|  |  |  |  | 2 | 0 | 2 | Failed to connect to the server | Check the network environment of the device and start the operation again | - |  |  |
|  |  |  |  | 2 | 0 | 3 | Failed to find the server | Check the network environment of the device and start the operation again | - |  |  |
|  |  |  |  | 2 | 0 | 4 | An input/output error occurred during the connecting process to the server | - | - |  |  |
|  |  |  |  | 2 | 0 | 5 | Failed to read a HTTP response | - | - |  |  |
|  |  |  |  | 2 | 0 | 6 | Error in a HTTP response | - | - |  |  |
|  |  |  |  | 3 | 0 | 1 | Failed to retrieve the data stream | - | - |  | - |
|  |  |  |  | 3 | 0 | 2 | Failed to create the file object for receipt | - | - |  | - |
|  |  |  |  | 3 | 0 | 3 | Failed to create the data stream of the file for receipt | - | - |  | - |
|  |  |  |  | 3 | 0 | 4 | Failed to receive the data | Check the network environment of the device and start the operation again | - |  |  |
|  |  |  |  | 3 | 0 | 5 | An error about reserving the file data for receipt | - | - |  | - | -
|  |  |  |  | 3 | 0 | 6 | Failed to close the data stream | - | - |  | - | -
|  |  |  |  | 3 | 0 | 7 | Failed to close the file data for receipt | - | - |  | - | -
|  |  |  |  | 3 | 0 | 8 | Invalid hash code of the download file | Check the network environment of the device and start the operation again |  |  |  |
|  |  |  |  | 3 | 0 | 9 | The prosy authorization method is not applicable | Check the proxy authentication method used, and start the operation again after changing the settings to use the corresponding proxy anthentication | - |  | - |
|  |  |  | 6 | Socket communication
|  |  |  |  | 1 | 0 | 1 | Failed to connect the eRDS | - | - |  | - |
|  |  |  |  | 1 | 0 | 2 | No response from eRDS | - | - |  | - |
|  |  |  |  | 1 | 0 | 3 | No notice of start from the eRDS | - | - |  | - |
|  |  |  |  | 1 | 0 | 4 | Error of socket reading | - | - |  | - |
|  |  |  |  | 1 | 0 | 5 | Socket communication time-out | - | - |  | - |
|  |  |  | 7 | Other internal codes
|  |  |  |  | 0 | 0 | 2 | One of installation, start or authorization failed (When installation or authorization failed, it is regarded as an error) * | - | - |  | - | -
|  |  |  |  | 0 | 3 | x | An internal error in processing the installation | - | - |  | - | -
|  |  |  |  | 1 | x | x | An error by using invalid API | - | - |  | - | -
|  |  |  |  | 2 | x | x | An internal error in SMS | - | - |  | - | -
|  |  |  |  | 3 | 0 | 1 | No existence of delivery ID | - | - |  | - | -
|  |  |  |  | 3 | 0 | 2 | Invalid delivery ID | - | - |  | - | -
|  |  |  |  | 3 | 0 | 3 | The updated firmware information is not identical with the firmware information after activation of the Updater | - | - |  | - | -
|  |  |  |  | 3 | 0 | 4 | The process of firmware download is incomplete | - | - |  | - | -
|  |  |  |  | 3 | 0 | 5 | The update process is incomplete | - | - |  | - | -
|  |  |  |  | 3 | 0 | 6 | The installment process is incomplete | - | - |  | - | -
|  |  |  |  | 4 | 0 | 1 | Failed to retrieve delivery information | - | - |  | - | -
|  |  |  |  | 5 | 0 | 1 | Failed to execute the delivery process | - | - |  | - | -
|  |  |  |  | 5 | 0 | 2 | The scheduled delivery was not executed within the defined period of time | Scheduled deliveries not executed within the defined period of time are abandoned, so register a scheduled delivery again. When setting the date and time of the scheduled delivery, be sure to designate a time when the device is ON | - |  | - | -

* Not displayed on a device UI