Resolving WinCC Flexible Runtime License Version Mismatch

Problem Description

A common field failure on SIMATIC Panel PC installations (for example, an OP12 panel with a PCU50 industrial PC) is the inability to authorize a WinCC flexible Runtime after the engineering station used a newer configuration software than the available license. The panel either refuses to start, logs a license error, or runs in trial/demo mode and stops after the timeout elapses.

Typical symptoms reported by maintenance engineers:

• Error message: "No valid WinCC flexible Runtime license was found" when the PC RT service starts.
• Error message: "The Runtime version does not match the license" after retransfer of a project.
• Successful compilation and download in WinCC flexible 2008 ES, but authorization fails because the installed Automation License Manager holds a 2007 Runtime license key.
• Message "No matching upgrade license keys were found" when running the upgrade wizard with the wrong source/target license pair.

This article documents the version compatibility matrix, the underlying legal and technical restrictions, and the four supported recovery paths.

Root Cause: Configuration Software and Runtime Coupling

WinCC flexible ties the Configuration Software (CS) version used to compile the project, the Runtime (RT) version installed on the target, and the license key version checked by the Automation License Manager. The three values must agree within tightly constrained rules.

Siemens differentiates between major versions (2005, 2007, 2008, 2008 SP2) and Hotfix levels (HF1, HF2, HF3, HF4, etc.) within a major version. The hotfix level only loosely affects licensing:

Versioning Model and Hotfix Behavior

From WinCC flexible 2007 Hotfix 3 onward, Siemens introduced a narrow compatibility window: a 2007 HF3+ Runtime can boot and execute a project compiled by an earlier 2007 hotfix level (HF1 or HF2) and even run with a 2005 Runtime license. This is documented in the German release note:

"Ab dem Hotfix 3 ist eine 'WinCC flexible 2007 Runtime' auch mit einem Lizenz Key der 'WinCC flexible 2005 Runtime' ablauffähig. Hierfür muss das Hotfix 3 oder höher auf dem Runtimesystem installiert sein. Die Nutzung des Lizenz Keys aus der Vorgängerversion ist ausschließlich für Test- bzw. Inbetriebnahmezwecke gedacht."

Translation: From Hotfix 3 onward, a WinCC flexible 2007 Runtime will execute with a 2005 Runtime license key, provided Hotfix 3 or higher is installed on the Runtime system. Use of the prior-version license key is permitted exclusively for test and commissioning purposes.

The same hotfix leniency does not extend across major versions. A 2008 project will not run on a 2007 Runtime, and a 2007 RT license cannot authorize a 2008 RT installation.

Impact on OP12 with PCU50

The SIMATIC PCU50 (PC Unit 50) is the backplane-mounted industrial PC supplied with early SIMATIC Panel PCs and is typically loaded with Windows XP Embedded or Windows Embedded Standard 2009. The OP12 is the 12-inch operator panel connected to the PCU50. The WinCC flexible PC Runtime is installed on the PCU50's operating system, while the project is compiled in the engineering station and transferred to the PCU50 over Ethernet or PROFIBUS.

Failure mode in this topology:

1. Engineer builds the project in WinCC flexible 2008 ES on the development PC.
2. Project compiles successfully and transfers to the PCU50 without error.
3. On startup, the PC Runtime cannot find a valid license because the only available license key was purchased for WinCC flexible 2007 Runtime (often an older delivery or a reused license from a 2007 fleet).
4. Runtime enters countdown mode or refuses to launch.

The license is independent of the panel hardware - the OP12 has no role in license validation. The PCU50 is the host that runs the RT and stores the license key, typically under C:\Program Files\Siemens\Automation\WinCC flexible\WinCC flexible 2008\RT\License\ or the equivalent 2007 path.

Solution Path 1: Exchange the Runtime Package with Siemens

If the unopened Runtime media or backup is still available and within the Siemens exchange policy window, it can be returned and replaced with the correct major version.

1. Locate the original WinCC flexible Runtime DVD or downloaded installer that was never opened (license card must be intact).
2. Contact your Siemens regional sales or the Siemens Industry Online Support hotline for an RMA/return.
3. Provide the original license number and proof of purchase; Siemens will issue a 2008 Runtime for a service fee.
4. Install the new Runtime on the PCU50, transfer the original 2008 license key to the Automation License Manager, and start the project.

Solution Path 2: Purchase a 2007 to 2008 Upgrade Package

The standard OEM-supported recovery is to purchase a version upgrade license. The Automation License Manager supports an in-place upgrade of an existing key when a matching upgrade key is present.

Step-by-Step Upgrade Procedure

1. Install the new WinCC flexible 2008 Runtime on the PCU50 (do not uninstall 2007 first - the Automation License Manager can hold both keys simultaneously during transition).
2. Insert the upgrade license USB dongle (or run the license transfer) on the target PC so the new upgrade key is written to the local hard drive. The default location is C:\Program Files\Siemens\Automation\Automation License Manager\Bin\almsrvx.exe managed store, or the dedicated C:\Siemens\License\ folder if configured.
3. Open Automation License Manager from Start → Siemens Automation → Automation License Manager.
4. Confirm that both the original 2007 license and the upgrade license are visible in the list. If only the upgrade license is listed, transfer the 2007 license to the local drive first using License → Transfer with the original USB stick.
5. Select the original 2007 Runtime license in the license list. Do not select the upgrade key.
6. From the menu, select License → Upgrade License.
7. Choose the matching upgrade license from the drop-down list. Tag count, type (PC Runtime vs. Panel Runtime), and major version must match exactly.
8. Click Upgrade. The original 2007 key is replaced in the local license store with an upgraded 2008 key that retains the original CoL lineage.
9. Remove the upgrade USB dongle; the upgraded license remains on the hard drive.
10. Restart the WinCC flexible Runtime service and verify the project starts.

Solution Path 3: Downrev the Project to 2007

If a 2008 upgrade license is not procurable, the project itself can be rolled back to a 2007-compatible source tree. This path requires the engineer to have both CS 2008 and CS 2007 installed (or virtualized).

1. Open the project in WinCC flexible 2008.
2. Use Project → Save As Version and select WinCC flexible 2007 as the target. The Save As process strips features introduced after 2007 and renames internal references.
3. Open WinCC flexible 2007 on the same machine (or a VMware image).
4. Open the just-saved 2007 project file. The project will be upgraded internally by the 2007 CS to its native format.
5. Recompile the project in 2007 CS. The resulting Runtime file matches the 2007 license family.
6. Transfer the recompiled project to the PCU50. The 2007 license authorizes the Runtime.

Solution Path 4: Multi-Version Engineering Workstation via VMware

Many OEMs support long-life PC Runtime installations across multiple WinCC flexible versions. The practical approach is to run each major CS version in an isolated Windows XP or Windows 7 virtual machine:

1. Create one VMware Workstation or VMware Player VM per CS version (2005 SP1, 2007, 2008 SP2).
2. Disable license borrowing or transfer the license between host and VM using Automation License Manager remote view.
3. Compile the project inside the matching VM to guarantee the binary Runtime file is signed against the correct CS version.
4. Transfer the compiled RT file to the physical PCU50 or any other Runtime target.

This eliminates the Save As round-trip and gives the engineer a clean CS for each major revision when supporting legacy equipment.

Hotfix Compatibility Decision Matrix

Verification Procedure

After applying any of the four solution paths, run the following verification sequence on the PCU50:

1. Open Automation License Manager on the PCU50 and confirm the correct major version Runtime license is listed as valid (green check) in the local store.
2. Verify the installed Runtime version: navigate to Start → Programs → Siemens Automation → WinCC flexible → About on the PCU50. Confirm the major version matches the project.
3. Start the Runtime from the start menu or the auto-start service. Observe the splash screen - it should not show a license countdown.
4. Log in as the operator and exercise at least one screen change, one alarm, and one tag write to confirm full functionality.
5. Reboot the PCU50 cold (power cycle) and confirm the Runtime starts in authorized state without manual intervention.
6. Check the WinCCflexibleRT.log in the Runtime install directory for any E00xx license error codes. A clean log is the strongest verification.

Common License Error Codes and Fixes

Preventive Recommendations for OEMs

• Tag the license asset. Record the CoL number, major version, and tag count in the project documentation. Storing the CoL in the HMI project header avoids field surprises.
• Bundle CS and RT versions per machine. Deliver the engineering PC with the exact CS version that matches the RT license installed on the target fleet.
• Maintain a VMware library. Keep at least CS 2005, 2007, 2008 SP2, and TIA Portal WinCC images to recompile any legacy project that comes back for service.
• Procure upgrade keys during PC RT rollout, not after. Lead time for upgrade packages is several weeks; plan for it during the initial bill of materials.
• Avoid relying on the HF3 downrev license workaround in production. Treat it as a commissioning emergency stop-gap only.

FAQ