Resolving WinCC Runtime Advanced Power Tag Limit Errors

1. Problem Overview

Siemens WinCC Runtime Advanced (the HMI runtime that ships with TIA Portal) raises a modal dialog at startup with the message:

"Too many tags (power tags) have been configured. WinCC Runtime Advanced 128 power tags."

The error appears even when the engineer has only configured 60–70 tags, which is what makes the message confusing. The dialog halts the runtime before the project screen can be displayed, blocks the simulation environment, and prevents any HMI panel from coming online. The error fires identically in:

• The PC-based WinCC Runtime Advanced loader
• The integrated simulator (Start > Simulation > Start with simulator)
• Comfort Panel and WinCC RT Advanced on a Unified Comfort Panel (where applicable)

2. What Is a Power Tag?

WinCC distinguishes two categories of tags:

A configured power tag is any tag created in the HMI tag table that has a valid connection assigned in its properties (PLC name, address, and acquisition cycle). A tag created but left without a connection is an internal tag and is not counted.

Each of the following also counts as one power tag per occurrence:

• HMI tags bound to a PLC via an S7 / PROFINET / PROFIBUS connection
• Tags used as the trigger of a scheduler
• Tags referenced by an area pointer (coordination, job mailbox, date/time, etc.)
• Tags used in the Tag simulation table
• Tags driven by the Logging subsystem for active logging tags

3. Root Cause Analysis

The "too many power tags" error is fundamentally a license capacity issue, not a configuration defect. The runtime is enforcing the upper bound of the active license at startup before opening any project screen.

Three underlying conditions can trigger the dialog:

1. No Automation License Manager (ALM) license installed. WinCC Runtime Advanced runs in a 30-day trial mode by default. If no license was activated (or the trial expired), the runtime is treated as if it had a 0-power-tag license. The error dialog then displays the size of the trial allocation the user is attempting to exceed.
2. License tier undersized for the project. A 128-power-tag license cannot serve a 200-tag project. TIA Portal does not block you from authoring more tags than the license supports; the runtime enforces the cap at load time.
3. Stale license key / license moved to a different PC. If a license was installed on the engineering station, moved, or the hard disk was re-imaged, the runtime can fall back to a missing-license state even though TIA Portal still appears to have an entitlement.

4. WinCC Runtime Advanced License Tiers

The WinCC Runtime Advanced power tag entitlements (TIA Portal V15 / V15.1 / V16 / V17) are sold in fixed tiers. Each tier adds archive tags, scripts, and user administration scope, but the power tag count is the binding limit on what the runtime will load.

Counts are cumulative: a 2 048-power-tag license accepts any project up to 2 048 power tags. A 128-power-tag license is the minimum commercial entitlement; smaller projects must still purchase the 128-tier or higher.

5. Diagnostic Procedure

Run the following checks in order before reinstalling anything.

5.1 Verify the project tag count

1. Open the TIA Portal project.
2. Select the HMI device in the project tree.
3. Open Device view > Information (or Properties > General > Tag list).
4. Note the Power tags used count. Cross-check it against the configured HMI tag table (right-click > Used filter).

5.2 Verify the installed license

1. Close TIA Portal.
2. Start Automation License Manager (Start > Siemens Automation > Automation License Manager).
3. Confirm the target PC is selected in the left pane.
4. Look for the WinCC Runtime Advanced entry. Verify:

• The status field shows the correct power-tag count.
• The "Valid until" date is in the future.
• The license is not marked as Missing, Defective, or Not licensed.

5.3 Verify the ALM service is running

1. Open services.msc (Win + R > services.msc).
2. Locate ALM (or Automation License Manager Service). Confirm Startup Type is Automatic and Status is Running.
3. If the service has stopped, right-click > Start and re-test.

5.4 Distinguish a license fault from a tag-count fault

To isolate the two cases, create a minimal test project with five power tags and the same HMI device type. If the same dialog appears, the issue is purely licensing. If the dialog disappears, the production project has crossed the license tier threshold and the resolution path is "upgrade license" rather than "reinstall license".

6. Resolution Steps

6.1 Reinstall or repair the license

1. Insert the license USB stick from Siemens (or download the license file from the Software Delivery Portal).
2. Open Automation License Manager.
3. Select the target PC in the left pane.
4. Drag the WinCC Runtime Advanced license from the right pane onto the target PC, or use Edit > Install License.
5. Wait for the transfer to complete; the ALM will show a green check beside the license.

6.2 Activate a trial license

1. In Automation License Manager, click Edit > Activate Trial License.
2. Select WinCC Runtime Advanced.
3. Confirm. A 30-day trial license will be written to the ALM repository.

6.3 Upgrade the license tier

If the tag count has genuinely grown above 128:

1. Order a higher-tier license (512, 2 048, 4 096, or 8 192 power tags) from your Siemens representative.
2. Transfer the new license key through ALM. The upgrade replaces the 128-tier entry; the runtime reads the higher value on next start.
3. Reboot the HMI runtime PC. License changes are only read at process launch.

6.4 Reduce the project's power-tag footprint

When budget constraints prevent an upgrade, restructure the project to use fewer power tags:

• Convert raw bit tags to word-level tags and read individual bits via tag multiplexing in scripts.
• Use arrays of tags (e.g. one array of 50 words equals 50 power tags instead of 800 bit tags).
• Move rarely-used faceplate references to internal tags if the value is computed locally.
• Delete unused tags from the HMI tag table; the runtime counts every configured tag, even if no screen references it.

6.5 Reset the trial clock (engineering station only)

7. Verification

After applying any fix, verify the runtime launches cleanly:

1. Restart the WinCC Runtime Advanced loader (or the TIA Portal simulator).
2. Confirm the error dialog does not appear.
3. Confirm the start screen of the HMI project is rendered within 5–10 s.
4. From the HMI project, open the online diagnostics: System > Diagnostics > License Information. Confirm the displayed power-tag tier matches the entitlement.
5. In the project, perform an end-to-end tag check: trigger one input from the PLC side and confirm the HMI value updates within one acquisition cycle.

Expected runtime log line

When the runtime starts successfully, the Windows Event Log (Application channel) shows an entry from CCAgent or HMIRuntime indicating the active license tier, e.g.:

8. Common Pitfalls

9. Edge Cases and Field Notes

9.1 Power tags vs. archive tags

Archive tags are counted separately from power tags, but a tag that is both an HMI tag and an archive entry still counts as one power tag. The 128/512/etc. limits apply to power tags; the archive tag ceiling is governed by the same license but reported independently in Runtime > Reports > Licensing.

9.2 Indirect tag creation

Tags are created silently by some wizards:

• Recipe views add power tags for each recipe element.
• User administration enables power tags for user IDs, passwords, and group memberships.
• Alarm logging adds system tags for acknowledged state, lock state, and time stamps.

A project with no "user-authored" HMI tags can still report 30–60 power tags once alarms and user administration are enabled. Always audit the project tree, not just the HMI tag table.

9.3 Mixed Comfort Panel / RT Advanced environments

If a Unified Comfort Panel (UCP) is used in parallel with a separate PC-based WinCC Runtime Advanced instance, each device needs its own license. The "128 power tags" in the dialog refers only to the device that raised it.

9.4 TIA Portal V15 vs V16 vs V17 license compatibility

Licenses issued for V15 are forward-compatible with V16 and V17. A V17 license is also downward-compatible to V16 and V15. The runtime checks the entitlement text in the license key, not the TIA Portal version that issued it. However, license files generated under a newer ALM may not transfer cleanly to an older ALM on legacy panels; keep the ALM version in step with the runtime version.

9.5 Virtualization

WinCC Runtime Advanced licenses are bound to the host hardware. In virtual machines, the license binds to the VM's virtual hardware ID. Cloning a VM after licensing invalidates the bound license. Use the Siemens SUS (Software Update Service) portal to reissue, or transfer the license to a fresh VM after each clone.

10. Preventive Measures

• Document license tier in the project header (e.g. HMI splash screen info text) so future engineers know the limit.
• Track tag count in version control: add a pre-build step that reads the TIA Portal project XML and asserts the configured power tag count is below 80% of the active tier.
• Keep the ALM service automatic in Group Policy to prevent Windows updates from disabling it.
• Order the next tier up front during commissioning; a license upgrade in a live production environment is more disruptive than during build-up.
• Avoid bit-bomb tag patterns: a 16-bit boolean status is one word, not 16 booleans.

11. Related Errors You May Also See