Technical Service Bulletin
Topic

ODIS Error Message – Best Practice When Performing Baseline (BiL) Updates

Market area

Bentley: worldwide (2WBE),China 796 VW Import Comp. Ltd (Vico), Beijing (6796)

Brand

Bentley

Transaction No. 2078962/1
Level

EH

Status

Released for publishing

Release date

Aug 21, 2025

New customer code

Object of complaint

Complaint type

vehicle service -> IT systems -> SVM (Software Version
Management)

control modules, services -> error
message

Vehicle data
24-26MY Bentayga | 25-26MY Continental GT/GTC/Flying Spur
Sales types

Type MY

Brand Designation Engine code Gearbox code Final drive code

4V1* 2024 E

*

*

*

4V1* 2025 E

*

*

*

4V1* 2026 E

*

*

*

Z23* 2025 E

*

*

*

Z23* 2026 E

*

*

*

Z24* 2025 E

*

*

*

Z24* 2026 E

*

*

*

Z32* 2025 E

*

*

*

Z32* 2026 E

*

*

*

ZV1* 2024 E

*

*

*

ZV1* 2025 E

*

*

*

Documents
Document name

Position

master.xml
best_practice_guide.pdf

Technical Service Bulletin

Transaction No.: 2078962/1

ODIS Error Message – Best Practice When Performing Baseline (BiL) Updates

Release date: Aug 21, 2025

Condition
Workshop Findings:
During vehicle baseline (BiL) updates using ODIS, users may encounter various error messages. These
errors can interrupt the update process and may be caused by issues related to the vehicle’s current
configuration, communication faults, or problems with the SVM code being applied.
To support initial fault diagnosis, a best practice guide is attached to this TPI. It provides recommended
checks and troubleshooting steps to help resolve common issues encountered during BiL updates.

Technical Background
The ODIS diagnostic tool relies on accurate vehicle status and valid SVM codes to perform baseline
updates. Errors may occur if:
•

The vehicle is not in the correct state (e.g., ignition on, stable voltage).

•

There are communication faults between the vehicle and diagnostic interface.

•

The SVM code is incorrect or incompatible.

•

Backend server or network issues are present.

Understanding these factors is key to resolving issues efficiently and avoiding unnecessary delays.

Production Solution
Not applicable

Service
Please refer to the best practice guide attached to assist with initial fault diagnosis when ODIS errors occur
during BiL updates.
It includes:
•

Common error messages and likely causes.

•

Step-by-step troubleshooting actions.

For specific faults including, Error 9999, Error Flash Container Linkage & Error 8118. Refer to the
information below.

Error 9999 – Best Practice

Step

Action

Images

•

Check
that the
D3 Edge
Box is
connected

•

Perform the ‘connection
test’ within the extra
menu
‒

Navigate to ‘’
Extras’’ -> ‘’
Connection Test’’ > Select ‘’
Bentley’’ (If Multi
Brand) -> ‘’Select
ALL -> Start

‒

If the Mirror
Server does not
return a green ✓ > Check your D3
setup and IP
settings as per
the next step.

Check that the URL in
the Mirror Server 2 is
correct for the new D3
edge box.
‒

Mirror
Server
Settings

Refer to ‘’
Operating
Modes’’ -> ‘’
Admin’’ -> ‘’
Connections’’ -> ‘’
Mirror Server 2;;.

•

Ensure that the URL is
http://.. And NOT https://

•

Enter the mirror server
URL into a web
browser, and ensure
that the flash files are
visible on the server.
‒

Copy & paste the
Mirror server
address into a
web browser e.g
Microsoft edge) ->
Navigate to the
flash files
location: XXX.

XXX.X.XX/DAV
/Service42/TradeRetail/Brand-E/
•

Ensure that your
localised GRP
administrator has
assigned the correct
roles for completing
work in ODIS.

Issues
with GRP
Roles

•

N/A

Depending on the
retailer / brand /
importer structure, there
are different processes
for D3 Edge Box
Support.
‒

Additional
D3 Edge
Box
Support
‒

If the D3 Edge
Box is Bentley
Supplied –
Contact ODIS.
Support@Bentley.
co.uk

N/A

If the D3 Edge
Box is owned by
another Group
brand, contact the
relevant support
for that group
brand.

Error – Flash Container Linkage

Type of
Flash
Container

Best Fixes

•

If a flash file is being used locally, eg ED40, ED42 download from atheer – this means
that the flash container is extracted directly form the C:/temp folder on the users ODIS
tester.

•

If the flash files are downloaded incorrectly, or not extracted from the ZIP folders
correctly, this means ODIS cannot identify the correct flash file.

Example of Bad file structure / naming:

Local
Flash
Containers
(Using
files from c:
/temp)

Type of
Flash
Container

Online
Link Flash
Containers
(using an
SVM
Code)

•

Duplicated Download Suffix

•

Multiple or incorrect file extension types

Best Fixes

•

When an ECU requires a software update through SVM, ODIS will pull the file from the
mirror server/ D3 edge box.

•

If the Flash Container can not to be linked, check if the files is present on the mirror
server

•

To do this:
‒

Enter the mirror server URL into a web browser, and ensure that flash files are
visible on the server.

‒

Copy & paste the mirror server address into a web browser (eg Microsoft edge) ->
Navigate to the flash files location: XXX.XXX.X.XX/dav/Service42/Trade-Retail
/Brand-E/

•

Then press ‘ctrl’ + ‘f’ and search the Mirror Server for that flash container.

•

In this example, the FRF file is available to be flashed with ODIS:

Error 8118 – Best Practice

8118 Issues

Actions
•

Check that a suitable battery charger is
connected – Low / Insufficient battery voltage
can cause ECUs like the MIB (005F) to fall
asleep and enter energy management mode

•

Allow the vehicle to sleep, clear all DTCs and
try again.

•

The wireless mobile phone charger (00DE) is
a common offender for not reporting the
correct or any identification data. To fix this,
allow a full CAN bus sleep, clear all DTCs and
run a Read Identification data (to ensure its
communicating, then repeat the SVM code
input with a mobile phone on the charging pad
to keep the ECU awake.

•

If a specific ECU is reporting ‘’general errors’’,
check the communication with the ECU. If it is
OK try pulling the fuse to the ECU to perform a
re-set (dependant on the Role of the ECU).

Step 1

Step 2

Step 3

•

If the 8118 error persists after multiple sleep
cycles, attempt a whole vehicle terminal 30
reset by removing the 12v battery for 15-20
minutes.
Step 4

•
Step 5

‒

Ensure the battery charger is
disconnected at this point.

‒

Ensure the vehicle has reached a CAN
sleep before removing the terminal 30 to
all ECUs.

If the issue persists after the above steps,
raise a full technical DISS query to the BIL
update support team.

Additional Support
If the issue persists after following the attached guide, please raise a Full Technical DISS query for further
support from Bentley Product Support.

INTERNAL