IMDTouchKnowledge BaseShop main store

Troubleshooting

Fix a Vijeo Designer project version mismatch by updating the build

HMI and touchscreens Published 6 min read

Short answer

The project version mismatch error means the project was saved by a newer Vijeo Designer build than the 6.3.0.103 you have installed, so copying the file locally cannot fix it. Update through Schneider Electric Software Update to a later 6.3-series build such as the reported 6.3.1.32, confirm the version inside the running application, then retest.

On this page
  1. Why does Vijeo Designer report a project version mismatch?
  2. Why does the installer say 6.3.1 while Designer reports 6.3.0.103?
  3. Does copying the project to a local drive fix the mismatch?
  4. Should you suspect licensing when the project will not open?
  5. How do you update Vijeo Designer to the build the project needs?
  6. How do you verify which build is actually installed?
  7. Can you save the project back to an older Vijeo Designer version?
  8. What should you do if the mismatch survives the update?
  9. Questions asked

Vijeo Designer refuses the project because the installed build, 6.3.0.103, is older than the build that last saved the project, and moving the file cannot change that. The 6.3.1 label on the installer describes a build line the installation never reached. Fix it by updating through Schneider Electric Software Update, confirming the new build number inside the running application, and retesting a copied project. The sections below separate the version fault from the path and licensing dead ends, show the version arithmetic, and state what to record if the error survives the update.

Why does Vijeo Designer report a project version mismatch? #

The error means the project file was saved by a newer Vijeo Designer than the one installed; Schneider Electric documents this cause for the message, and your 6.3.0.103 build falls on the wrong side of it for this project.

The dialog reports the project was created in 6.0.0 and modified in 6.3.0, which makes the rejection look wrong, because 6.3.0.103 appears to outrank 6.3.0. Those dialog values are major-and-minor markers, not the full internal version stamp that the open check compares. The project file, extension VDZ, carries the stamp of the build that last saved it; when that stamp is newer than the installed build, the file is refused wherever it is stored.

Vijeo Designer binds every project to the versions allowed to edit it — the same compatibility question that decides which Vijeo Designer version edits an XBTG5230 project. The stamp inside the file decides, not the folder, the drive, or the shortcut it was opened from.

Why does the installer say 6.3.1 while Designer reports 6.3.0.103? #

Because the download label and the installed build are two different numbers, and here they disagree: the page said 6.3.1, the delivered build reports 6.3.0.103, and the application's own version display is the reading that counts.

Read the four fields left to right and let the first difference decide:

Where the number came from Field 1 Field 2 Field 3 Field 4
Installed build, application display 6 3 0 103
Installer label, download page 6 3 1 —
Reported newest 6.3-series build 6 3 1 32

Field 1 ties at 6, field 2 ties at 3, and field 3 decides it: 0 < 1, so any 6.3.1.x build is later than any 6.3.0.x build. The comparison never reaches field 4, which is why 103 versus 32 is irrelevant to the ordering. Your station sits on the 6.3.0 line; the decision for this symptom is the 6.3.1 line or later, and 6.3.1.32 is the build reported as newest when the fault was documented.

Does copying the project to a local drive fix the mismatch? #

No — the same error from the local copy is the diagnostic result: it clears the network share of suspicion for this message and leaves the installed build as the cause to fix.

A path or permission fault changes the message or blocks the copy; a version check runs after the file opens, from any location. Keep the local copy for the retest so the version test stays isolated from network access, and keep the network original untouched — the same copy discipline that applies when an HMI project fails to open. If the local copy opens later but the network copy fails, that residual failure is share access or copy integrity, not versions.

Should you suspect licensing when the project will not open? #

No — nothing in these symptoms names a license: the same version message appeared from the network drive and the local copy, so the evidence points at the build comparison rather than at entitlement.

A license fault would have to explain why the message quotes version fields from two storage locations; it cannot. Update the build and retest.

How do you update Vijeo Designer to the build the project needs? #

Run Schneider Electric Software Update on an internet-connected engineering station and apply the Vijeo Designer update it offers; offline, take the installer only from Schneider Electric's official distribution for your release.

  1. Close Vijeo Designer and every open project.
  2. On the connected station, run Schneider Electric Software Update and let it list the update for the installed release.
  3. Apply the update, accepting its prerequisites and restarts.
  4. If the station is offline, obtain the matching installer from Schneider Electric's official Vijeo Designer distribution, never a third-party mirror.
  5. Relaunch the application before touching any project.

The update target is the engineering computer, not the operator panel; a runtime mismatch reported during a download to the panel is a separate fault with its own message.

How do you verify which build is actually installed? #

Read the version from the running application's own information display, compare it field by field with the build you intended to install, and treat the installer's filename as a label, not as the confirming reading.

If the application still reports 6.3.0.103 after the update, the update did not apply — resolve that before opening anything. Once the number is right, open the local working copy first. If the build offers a conversion or upgrade of the project, apply it to a duplicate, keep the original unchanged, then close and reopen the converted copy to confirm it loads. Copy the validated project to the network location and open it there only after the local test passes; a network-only failure at that point is an access problem.

Can you save the project back to an older Vijeo Designer version? #

No — there is no documented save-as-older-version path in Vijeo Designer, so once the project is saved by the newer build, every workstation that edits it needs that build or later.

Compatibility runs one way: older projects open in newer builds, the forward move made when opening a legacy Vijeo Designer project in version 6.2, but a project saved by a 6.3.1.x build never returns to a 6.3.0.x station. Before anyone saves this project, put every workstation that will edit it on the same confirmed build: each save raises the project's stamp and narrows who can open it next.

What should you do if the mismatch survives the update? #

Stop converting and record three things — the installed build as the application reports it, the created-in and modified-in values from the mismatch dialog, and the complete error text — because those are the inputs that determine the supported compatibility path.

Repeated conversions on the sole copy of a project are how projects get damaged, so first confirm the untouched original still exists. Then capture:

  • the installed build number, exactly as displayed;
  • the created-in and modified-in values from the dialog;
  • the full error text, not a paraphrase.

State the label-versus-build discrepancy to support as well: a download labeled 6.3.1 that installed 6.3.0.103 is diagnostic on its own.

Questions asked

Is 6.3.1.32 the newest Vijeo Designer build?

It was the newest 6.3-series build reported when this failure was documented, not a permanently valid number. Schneider Electric releases builds over time, so let Schneider Electric Software Update name the current build for your release. The number that decides the fix is the one the running application reports after the update.

What is the difference between a project version mismatch and a runtime mismatch?

A project version mismatch stops the engineering tool: the installed designer build is older than the project, and the file will not open. A runtime mismatch appears later, when downloading to the panel, because the target's runtime version does not match the project. Fix the designer build first; the panel download is a separate check.

Is this ever a licensing fault?

Not from these symptoms. The identical message appeared from the network drive and the local copy, and nothing shown is a licensing message, so the evidence points at the build comparison. Update and retest; if a licensing-specific message appears afterward, treat it as its own fault with its own documentation.

What details does support need if the error stays after updating?

The installed build exactly as the running application reports it, the created-in and modified-in values from the mismatch dialog, and the complete error text. Add the installer source: the gap between the 6.3.1 label and the 6.3.0.103 build is itself diagnostic. Keep the untouched copy and stop converting while support reviews it.

Keep reading

  • How-to

    Open a legacy Vijeo Designer project in version 6.2

    Open the project in the release the error names — Vijeo Designer 4.7 in this case — compile and save it there, then climb release by release until 6.2 opens and builds it. Only then change the target to HMIGTO6310, configure Unitelway, and choose one documented transfer route.

    HMI and touchscreens

  • Troubleshooting

    Which Vijeo Designer version edits an XBTG5230 project

    Edit an XBTG5230 application with a licensed Vijeo Designer release from 4.5 through V5.0 SP2 — V5.0, all service packs included, is the last line supporting the XBTG series (Schneider Electric FAQ FA280491). Version 4.2.2 cannot load a 4.5 project and releases after V5.0 cannot select the target, so the fix is the release window, not a cable or terminal fault.

    HMI and touchscreens

  • How-to

    Activating the XBTOT Target Family in Vijeo Designer 6.2

    Enter upgrade code VJDHTGTOPV62M in the full Vijeo Designer 6.2 edition under Help > About > License > Upgrade, restart the software, and XBT OT appears in the new-project target list. Vijeo Designer Lite 1.2 or 1.3 cannot list or unlock the family.

    HMI and touchscreens