ODIS software error codes — what they mean and how to fix them
Complete list of ODIS Service error codes including ODS1003E, ODS1007E, ODS2007E, ODS9212E and others with causes and step-by-step fixes.
Getting an error code when using ODIS (Offboard Diagnostic Information System) software for Volkswagen or Audi diagnostics? This article explains what each ODIS error code means and how to resolve it. In many cases, these issues can be self-resolved without contacting Diagnostic Software Support (DSS).
ODS1003E — Security certificate not imported
Cause: The security certificate was not imported to the application before the PostSetup installation steps.
Fix: Refer to erWin > Vehicle Diagnostics > Step 4 > ODIS Software Installation & Configuration Instructions, Section 3.0 – Import Security Certificate to Application.
ODS1003E — Certificate revoked or wrong certificate imported
Cause: The certificate was revoked, or the wrong certificate (one meant for another device) was imported.
Fix: Verify you are using the correct certificate for your specific device. Contact DSS for resolution assistance if needed.
ODS1003E — Network blocking MirrorServer URL
Cause: The dealership network is blocking the MirrorServer URL.
Fix: Contact your local network administrator. Ask them to verify that access to https://mirrorserver2.vwhub.com/dav/ is allowed.
ODS1003E — Internet connection interrupted during update
Cause: The internet connection was interrupted during the update download.
Fix: Hardwire the diagnostic device to the network with an ethernet cable and retry the download.
ODS1007E — Incorrect login credentials
Cause: You are entering an incorrect ID or password.
Fix: Refer to the email you received from VWGoA Dealer Fax which contains your ID and password format. Passwords are case sensitive.
ODS2007E — Missing flat rate subscription
Cause: You do not have a flat rate. A flat rate is obtained when you purchase your ODIS subscription in erWin > Vehicle Diagnostics > Step 5.
Fix: Purchase the flat rate in erWin. If you feel your flat rate is still valid or if you just purchased one and it's still not working, email techinfo@vw.com or techinfo@audi.com for resolution. The DSS team cannot assist with this issue.
ODS2508F / ODS2519F — Corrupt installation
Cause: Corrupt ODIS installation.
Fix: Uninstall and reinstall ODIS Service. Refer to erWin > Vehicle Diagnostics > Step 4 for ODIS Uninstallation and Reinstallation Instructions.
ODS300XE (X = 1-9) — File permission error
Cause: File permission error on the diagnostic device, often caused by a full hard drive.
Fix: Make sure the hard drive is not out of space. Delete all content from
C:\windows\logs
C:\windows\temp
Reboot the diagnostic device and try the update again. If it fails again, contact DSS.
ODS4001E — License renewal prompt error
Cause: User selected Yes from the license renewal prompt in ODIS Service.
Fix: The license renewal process integrated with ODIS Service is not valid for the US/CDN market. Refer to erWin > Vehicle Diagnostics > Step 3 and follow the ODIS License Renewal Instructions posted at the top of the page.
ODS4009E — GFF logs stuck or corrupt installation
Cause: Old GFF log files are stuck in the queue folder, or the installation is corrupt.
Fix: Delete all files in C:\Program Files (x86)\Offboard_Diagnostic_Information_System_Service\queue\core.
If there are no files in that folder, the installation is corrupt and must be reinstalled. Refer to erWin > Vehicle Diagnostics > Step 4 for reinstallation instructions.
ODS4010E — Corrupt installation
Cause: Corrupt ODIS installation.
Fix: Uninstall and reinstall ODIS Service. Refer to erWin > Vehicle Diagnostics > Step 4 for reinstallation instructions.
ODS5003E — Missing or corrupt test plan
Cause: Missing or corrupt test plan file.
Fix: Attempt the same procedure on a different diagnostic device. If the result is the same, send feedback using the ODIS Service Support Button.
ODS6501E — Corrupt file
Cause: A file in the ODIS installation is corrupt.
Fix: Contact DSS for file resolution assistance.
ODS7004E — Corrupt installation
Cause: Corrupt ODIS installation.
Fix: Contact DSS for resolution assistance.
ODS8003E / ODS8031E — Corrupt installation
Cause: Corrupt ODIS installation.
Fix: Uninstall and reinstall ODIS Service. Refer to erWin > Vehicle Diagnostics > Step 4 for reinstallation instructions.
ODS9004E — Certificate not installed or revoked
Cause: The ODIS certificate is not installed or was revoked.
Fix: Contact DSS for resolution assistance.
ODS9006E — ODIS not running as administrator
Cause: ODIS Service must be started as an administrator even if full admin rights are granted on the device.
Fix: From the Windows desktop, right-click the ODIS Service icon and select Properties. Select the Compatibility tab. Check "Run this program as an administrator" and click Apply then OK.
ODS9018E — Non-current ODIS version installed
Cause: An outdated version of ODIS Service was installed.
Fix: Uninstall and reinstall ODIS Service with the current version. Refer to erWin > Vehicle Diagnostics > Step 4 for reinstallation instructions.
ODS9019E — PostSetup save data error
Cause: Missing "s" in the MirrorServer address during PostSetup.
Fix: Make sure you have the "s" in the address: https://mirrorserver2.vwhub.com/dav/
ODS9212E — Connection type set to CPN
Cause: The connection type is set to CPN instead of Internet.
Fix: Go to Admin > Connections > Brand Settings. Change the connection type to Internet and then restart ODIS Service.
ODS9212E — Certificate not installed, revoked, or expired
Cause: The ODIS certificate is not installed, has been revoked, or has expired.
Fix: Check the certificate expiration date under Admin > Certificate > Available Certificate. Contact DSS for further assistance if the certificate needs to be renewed or replaced.
ODS9212E — No internet connection
Cause: The diagnostic device has no internet connection and cannot reach the VW/Audi server.
Fix: Try reaching other websites using your browser to confirm whether the internet is working. If it is not, ask your local network administrator for assistance. Make sure no firewall or VPN is blocking the connection.
ODS9215E — GFF logs saved with wrong connection type
Cause: GFF logs were saved with the connection type set to CPN. This error occurs when performing any GeKo function since ODIS will attempt to send stored logs.
Fix: Delete all files from C:\Program Files (x86)\Offboard_Diagnostic_Information_System_Service\queue\core and
C:\Program Files (x86)\Offboard_Diagnostic_Information_System_Service\DiagnosticProtocols\autosave.
Start ODIS Service and confirm the connection type is set to Internet under Admin > Connections.
ODS9219E — Two certificates installed
Cause: Two ODIS certificates are installed on the same device.
Fix: Go to Admin > Certificates. Under "Available Certificates," remove the extra certificate so only one remains.
Still need help with an ODIS error
If your error code is not listed here or the steps above did not resolve your issue, contact AETools at https://aetools.us or call us directly for assistance.