Find the cause before exporting again
Keep the original file. Read the error code, rule and XML path where available. The tables below explain what each result means and where to investigate. SignECOC checks your file; it does not generate or repair manufacturer data.
File checks before validation
| Message or field | What to check next |
|---|---|
| UTF-8 | This file could not be read as UTF-8 XML. Export the unsigned IVI XML again from your source system using UTF-8 encoding, then upload the new file. Renaming the file does not change its encoding. |
| Empty file or over 5 MB | The XML file is empty or exceeds the allowed size. Choose a valid file within the upload limit. |
| XML cannot be read | The file could not be parsed as XML. Export it again from the source system and upload the new file. If a signature is required, sign the newly exported file; do not edit an already signed file manually. |
| InitialVehicleInformation | This file is not an IVI XML document with the required InitialVehicleInformation root element. Upload the correct IVI file. |
| DTD / ENTITY / xml-stylesheet | DTD, entity declarations and XML stylesheet instructions are not allowed. Correct the source XML before uploading. If the file is already signed, generate a new signature after correcting it. |
| XMLDSig Signature | This XML already contains an XMLDSig signature. Use the signed XML submission area instead. |
Read XSD, ICM and service results
| Message or field | What to check next |
|---|---|
| XSD | If the result reports an XSD issue, inspect the named element, its position and expected value format against the schema for your destination. Correct the export in your source system; changing a filename does not change the XML structure. |
| ICM | An ICM message concerns a business-rule check. Read the rule name and affected field together, then compare the value with the vehicle and type-approval records. Do not invent a replacement value merely to clear the message. |
| XSD_ICM | This label identifies schema and business-rule checks; read the pass/fail result and messages as well. SignECOC’s unsigned-file precheck does not validate the digital signature. Passing it does not prove authority acceptance or vehicle registration. |
| Validation service unavailable | The validation service is currently unavailable. Your XML has not been confirmed valid or invalid. Try again later or contact support. |
Locate the reported vehicle field
Use the element name or XPath in the returned message to locate the field. The suggestions below explain where to verify a value; the provider’s original rule and message determine the reported issue.
| Message or field | What to check next |
|---|---|
| VehicleIdentificationNumber | Check the vehicle identification number (VIN) against the manufacturer’s vehicle record and the reported validation requirement. |
| TypeApprovalNumber | Check the type-approval number against the vehicle’s applicable approval document and the reported validation requirement. |
| Type / Variant / Version | Check the vehicle’s type, variant and version together against its applicable approval records. Confirm that the combination matches this vehicle before changing a value. |
| IviReferenceId | Check the IVI reference in the document header against the reference assigned to this document. Review the provider’s reported requirement before changing it. |
Example: the wrong root element
rootName: VehicleInformation
requiredRoot: InitialVehicleInformationThis synthetic example contains no vehicle data and is not an IVI template. The selected document has a different root name. Choose the manufacturer’s correct IVI export and run the checks again. Renaming the root alone does not supply missing vehicle data or make the document schema-valid.
If you need support, describe the step and share the error code or a non-sensitive field name. Do not paste XML, vehicle identifiers, certificate files, passwords or PINs into the contact form.
Before you continue
- Match the XML schema to the intended destination.
- Correct the source record, export again and repeat the check.
- Sign only after resolving blocking validation messages.
Does a service error mean my XML is invalid?
No. If the validation service cannot return a usable result, the file’s validity is undetermined. Retry later; if the problem persists, contact support with the error code and time.