Troubleshooting
Why a standalone HMI project will not open in your integrated editor
Short answer
A standalone Vijeo Designer .vdz archive usually fails in an integrated editor because the two editors sit at different version levels and accept different project operations, not because a license is missing. Open the copy through the destination editor's documented import or restore route, with the destination editor at the same version level or newer than the editor that saved the archive, then verify target and communication settings.
On this page
- Why can't I open a standalone Vijeo Designer .vdz file through Machine Expert?
- Is a missing license the reason the archive will not open?
- Which editor versions have to match before the archive loads?
- What do I record before changing anything?
- How do I move the project into the integrated editor the supported way?
- What if the versions match but the editor rejects a target or an object?
- Do other integrated HMI environments refuse a load the same way?
- When should I stop transferring and rebuild or migrate instead?
- Which fix matches each failure message?
- Questions asked
A standalone Vijeo Designer .vdz archive fails to open through Machine Expert for a diagnosable reason, and the reason is almost never the extra editor license you were quoted. The standalone and integrated editors share one product line but sit at different version levels, and each accepts project transfers at its own level and through its own entry points. This guide puts the checks in order: read the exact failure text, match editor versions, use the destination editor's documented import route, then verify the HMI target and the controller links. Work on copies throughout, change one condition at a time, and treat the separate license as the last hypothesis, not the first.
Why can't I open a standalone Vijeo Designer .vdz file through Machine Expert? #
Because creating HMI code inside the Vijeo Designer container of a Machine Expert project and loading an externally saved .vdz archive are two different operations, and an integrated editor only accepts archives saved by an editor version it can read.
A file extension names a file type, not the operation that loads it. The open command at the top of the engineering shell is a different entry point from the HMI editor's own import or restore command, so a refusal at the file-selection stage means something different from a message produced after the archive was actually read. Capture the complete message text before anything else: a version-style refusal points at editor levels, a named object or target points at content, and a message about damaged or incomplete content points at the file itself. Also prove the integrated editor runs at all by opening an existing integrated HMI application first; if that fails, the installation is the problem, not this archive.
Is a missing license the reason the archive will not open? #
Treat a license as the last hypothesis, because a licensing refusal names the entitlement it wants, and an archive that fails with a version, target or object message is telling you the project transfer path is the fault rather than the entitlement.
Buying a second editor changes nothing about the version level the first one reads: the identical archive fails identically after the purchase unless the destination version changes too, which is why the cost of a standalone package answers a question the message never asked. Act on licensing only when the message explicitly reports an activation or entitlement restriction, and then verify the installed entitlement through the vendor's documented channel. Decision: no license purchase until a message names licensing as the restriction.
Which editor versions have to match before the archive loads? #
The destination editor must sit at the same version level as the editor that saved the archive or newer at that level, because the documented "Project version Mismatch" error means the file was saved by a newer Vijeo Designer than the one now opening it.
The standalone and integrated releases are mostly identical but not completely, and the standalone line is generally a little further ahead, so standalone-saved archives are the ones that arrive ahead of the bundled editor's level. That asymmetry also sets the easy direction: an integrated editor project opened in the standalone editor is the low-risk move, while standalone into integrated is where refusals concentrate.
Worked example with illustrative version numbers: the archive was saved by editor 6.2.5 and your integrated editor reports 6.2.1. Major levels match (6.2 = 6.2) but the service level does not (5 > 1), so the destination is behind and refuses the load. Bring the destination to 6.2.5 or later and the comparison 6.2.5 ≥ 6.2.5 passes; an archive saved by 6.1.4 meeting a 6.2.1 destination also passes, because 6.2.1 > 6.1.4. Confirm the exact version strings against the manufacturer's compatibility documentation before installing anything, because a newer editor also changes the stored project format in ways an older one never reads.
If nobody can say which editor produced the archive but the panel still runs the project, the running project identifies the level that saved it; the guide on how to verify the HMI project version running on a panel gives that check.
What do I record before changing anything? #
Record four things before any install or import attempt: the saving editor's version, the destination integrated editor's version, the Machine Expert version, and the complete failure text word for word, because each of the four selects a different branch of the fix. Take them from working copies and from the editors' own version displays, never by opening the original.
- Saving editor version and build — the level that saved the archive, and the number the destination has to reach.
- Destination editor version and build — what will actually read the file, and the side you can usually change.
- Machine Expert version — the engineering shell whose documentation states which integrated editor combination is supported; check that combination before installing any editor level.
- Complete message text, including any named object or target — the detail that separates a version refusal from a feature refusal from an integrity fault.
How do I move the project into the integrated editor the supported way? #
Offer the copy to the destination HMI editor's own documented import or restore command once the version question is settled, because the top-level open dialog of the engineering shell is a different entry point and is not the documented route for a standalone archive.
- Keep the original archive untouched and make two copies: one to work on and one that is never offered to any editor.
- Back up the destination Machine Expert project so every attempt starts from the same known state.
- Open an existing integrated HMI application through the normal HMI workflow to prove the editor itself runs before blaming the archive.
- Check the documented import or restore route and the file types it accepts; if the archive type is not accepted there, stop retrying that entry point.
- Change one condition at a time — destination version first, entry point second — so each new result names the change that produced it.
- When a conversion is offered, keep the pre-conversion copy, record the destination version applied, and confirm the project tree and the configured HMI target load before saving.
When the transferred project is later downloaded to a panel operators are using, do that download with the machine in a safe state, because it replaces the screens they are looking at. The backup-first habit is the same one for any refused project load; when an HMI project fails to open: recovery and backup covers the recovery side in detail.
What if the versions match but the editor rejects a target or an object? #
Then the refusal has moved from format to content: take the named target or object out of the message, confirm that HMI target exists in the destination editor's target list, and confirm the named object is supported in the installed edition before editing the project.
Read the edition as well as the number. The manufacturer documents Vijeo Designer Basic as a simplified version of Vijeo Designer intended for specific models such as HMIGXU, so an archive saved with the full product can carry screens or objects the installed edition has no support for even at a matching version level. A missing target calls for a supported target configuration or software combination; a named object missing from the edition is either a rebuild of that screen in the destination or, only now, an entitlement conversation with a feature name attached to it.
After a load succeeds, re-check the controller association and the variable references, because an integrated project carries links to the surrounding PLC project that the imported archive alone does not recreate. The import is not finished until a live value moves between editor and controller.
Do other integrated HMI environments refuse a load the same way? #
Yes, and the mechanism is common enough to reuse: an integrated engineering shell refuses a load when project version, device support or stated load preconditions do not line up, which is the same failure you are diagnosing here in a different ecosystem.
The pattern appears elsewhere as a precondition check that blocks the transfer before any project data is read; the guide on resolving the TIA Portal loading-preconditions error documents one such case, and the ordering is the same — versions and device support first, entry point second, content last.
When should I stop transferring and rebuild or migrate instead? #
Stop transferring when no supported combination reaches the saving editor's level or when the project needs functions the integrated build does not carry, and rebuild the required screens into the editor your installed hardware supports instead of forcing the archive through.
The Vijeo Designer line now serves mainly the maintenance of existing installations, and the manufacturer's current Harmony panels are programmed with EcoStruxure Operator Terminal Expert, so weigh the panel's own lifecycle status before sinking archive work into a target with no future. If the archive cannot be opened anywhere but the panel still runs, read the project back from the terminal first; the guide on reading an old HMI program before panel replacement covers recovering it before the panel is replaced.
Which fix matches each failure message? #
Match the message to one of five outcomes and the diagnosis is finished: version wording leads to a destination-side level change, a named target or object leads to an edition or rebuild decision, and entitlement wording is the only text that starts a licensing action.
- Version mismatch reported — raise the destination editor to the saving level on a documented combination, or continue the project in the standalone editor, the easier direction.
- Target the destination lacks — install a supported target configuration or move the project to hardware the destination actually supports.
- Object or function named — rebuild that screen in the destination edition, or resolve the edition gap now that a named feature justifies the entitlement action.
- Damaged or incomplete content reported — discard the working copy and take a fresh one from the untouched source; never put a repaired original back into service.
- No supported combination exists — rebuild in the editor the installed hardware supports, with the original archive kept as read-only reference.
Questions asked
The same archive opens on a colleague's installation — what does that tell me?
It tells you the failure follows the destination editor, not the file. Their editor sits at the archive's level or newer, so the load is accepted there. Compare the version and build each installation reports about itself before changing anything, and if theirs is the matching level, produce any converted copy on that machine while your own installation stays untouched.
Can I save the project down a version so an older editor will open it?
No. The documented meaning of the Project version Mismatch message is that the file was saved by a newer editor than the one attempting the load, and deleting screens does not reverse the stored-format changes a newer editor made. The correction belongs on the destination side: match or exceed the saving level, or use the documented transfer route.
Does EcoStruxure Operator Terminal Expert open a Vijeo Designer archive directly?
Treat that conversion as unconfirmed until the manufacturer's migration documentation names your exact panel family as convertible. Plan the move as a rebuild of screens, symbols and communication variables into the new editor, with the old archive and the running panel kept as reference, rather than as a file open that preserves the whole project tree.
Will upgrading Machine Expert alone fix the refusal?
Only when the newer engineering level also hosts a newer integrated editor, which is the combination to confirm in the compatibility documentation before installing anything. Upgrading the shell without checking the editor level it bundles can leave you at the same refusal, now with a larger installation to unwind if the combination does not fit your targets.