zenon 6.51 and zenon 7 were reported to run on the same PC when paired with Microsoft SQL Server 2005 and Microsoft SQL Server 2008 R2 Express, respectively. The documented way to change between the zenon versions is the zenon startup tool; treat this as a version-specific configuration, not as proof that every SQL Server or zenon combination can share a computer.
Does this configuration match the documented coexistence case?
Check the installed zenon versions and the SQL Server editions and versions associated with them before changing anything. The coexistence case is specifically zenon 6.51 with SQL Server 2005 and zenon 7 with SQL Server 2008 R2 Express. The post describing it dates to 2012, so verify compatibility against the requirements for the exact software you are maintaining before applying it to a newer installation.
Record which zenon version opens successfully and which database installation it expects. If the installed products do not match the two-version pairing above, stop treating this configuration as a direct template and check the relevant product documentation or support channel.
Which installation reading should you take next?
Inventory the installed software and check the selected zenon environment using the startup tool. Compare those readings with the intended version-to-database pairing:
| Reading | Source | Wrong-value symptom |
|---|---|---|
| zenon version selected to start | zenon startup tool | The wrong zenon environment opens, or the project is opened in an unintended version. |
| SQL Server version and edition present | Installed software inventory or SQL Server installation details | The expected database version is absent, or the installation does not match the stated pairing. |
| Project or workspace backup available | Project files and backup inventory | There is no known recovery copy before attempting import or conversion. |
If the versions and backup align, select the required zenon version with the startup tool and test it with the intended project. If the selected version is wrong, correct the selection before opening or converting project data. If the SQL installation differs from the expected pairing, do not assume that switching zenon versions will resolve the mismatch; verify compatibility first.
How does switching versions affect project data?
The startup tool changes which zenon version is used; it does not make a project created or maintained in one version automatically safe to use in another. In the reported workflow, projects were brought into zenon 7 by importing a project backup or workspace backup. The import restored the project and automatically converted it.
That conversion is the key decision point: keep the original backup as the recovery source, and do not make the converted copy your only copy. The described workflow does not specify a rollback method, conversion details, or whether a converted project can be reopened in zenon 6.51. Plan around the possibility that the converted project is for zenon 7 unless the applicable product documentation confirms otherwise.
What should you check before changing versions?
- Record the installed zenon versions and SQL Server versions and editions.
- Identify which zenon version currently opens the required project and confirm the intended target version.
- Create or locate a project backup or workspace backup. Confirm that the backup is available before importing it.
- Use the zenon startup tool to select the version you intend to run.
- For a move to zenon 7, import the project backup or workspace backup into zenon 7 rather than assuming the existing project will be converted merely by switching versions.
Take these readings before adjusting installations or attempting a conversion. If a required backup is missing, resolve that first; if version pairing or compatibility is uncertain, pause rather than experimenting on the only project copy.
How do you verify the selected version and converted project?
After switching, confirm that the intended zenon version actually starts, then open the intended project in that environment. For a zenon 7 migration, verify that the import completes and that the restored, converted project opens as expected. Record the selected version and the backup used so the next operator can distinguish the original project from the converted one.
If the project does not open or import as expected, return to the recorded version and backup state rather than repeatedly importing or converting the same files. Recheck the selected zenon version and the SQL Server pairing, then consult product-specific documentation for the failing step.
What questions do engineers ask about zenon and SQL Server?
Can zenon 6.51 and zenon 7 run on the same PC?
They were reported to coexist on one PC when zenon 6.51 used SQL Server 2005 and zenon 7 used SQL Server 2008 R2 Express. Use the zenon startup tool to switch versions.
How do I switch between zenon 6.51 and zenon 7?
Select the required zenon version in the zenon startup tool. Confirm the associated SQL Server installation and project before opening the environment.
How do I move a project from zenon 6.51 to zenon 7?
Import a project backup or workspace backup into zenon 7; the described workflow restores and automatically converts the project. Retain the original backup as your recovery copy.
Stop before conversion if you cannot identify the target version, confirm the database pairing, or preserve a backup. Escalate unresolved compatibility or import failures to the official product support channel with the installed versions and the exact step that fails.