Resolving Simatic Net License Popup Errors in PCS 7 V8.2

1. Problem Overview

On PCS 7 V8.2 systems (including V8.2 SPx updates) running a single AS (Automation Station) with a single OS (Operator Station) server, the WinCC Runtime periodically displays a "Simatic Net License" dialog at OS startup or when a connection is established. The same symptom appears on OS Single Station installations that combine the engineering and runtime role on one PC. The popup blocks the OS taskbar and may force the operator to acknowledge the dialog every reboot. Two architectural patterns trigger the issue most often:

• A single OS server with one AS and one or more S7 named connections.
• An OS Single Station (ES + OS) with a single AS and standard Ethernet interface.

2. Root Cause Analysis

The dialog is generated when the S7DOS / OPC / Named Connection service on the OS station requests a license that the ALM cannot resolve. The underlying reasons observed in field installations are:

1. Wrong license type installed. The OS PC is using a Standard Ethernet interface (Intel/Broadcom/Realtek onboard NIC) but a SIMATIC NET IE HARDNET S7 or SOFTNET-S7 LEAN license is allocated. The correct license for a standard NIC is SIMATIC NET IE S7 Basic Communication Engine (BCE).
2. No SIMATIC NET license transferred at all. Only the WinCC RT license is present in ALM, while S7 communication requires an explicit SIMATIC NET license.
3. OS-RT Single Station license is not in ALM. The OS Runtime license must be transferred onto the same physical drive on which WinCC Explorer was started, otherwise the OS server cannot authenticate against the ALM during startup.
4. Connection count exceeds the bundled limit. BCE and SOFTNET-S7 LEAN carry a cap (typically 8 S7 connections); additional named connections force the S7DOS to ask for an upgraded license key.
5. License version mismatch. The license key on the ALM was generated for a different SIMATIC NET version (for example, a V13 key while the installed SIMATIC NET is V14) — the version stamp on the license does not match the runtime binary and the ALM rejects it.
6. ALM service is not started. The Windows service "ALM" or "SLM" (older naming) is disabled, or its startup account lacks the local "Siemens TIA Engineer" or "SIMATIC HMI" group rights.

3. License Types and When to Use Each

Siemens bundles three license families for S7 communication from a PC station. Selecting the wrong family is the single most common root cause for the popup.

4. Network Adapter Classification

Open SIMATIC NET Configuration Console (Start » Siemens Automation » SIMATIC » SIMATIC NET » Configuration Console). The "Network adapters" tab lists every Windows NIC as one of the following:

• General IE — refers to a standard Windows NIC. Use BCE or SOFTNET-S7 LEAN.
• IE SOFTNET — Siemens Softnet driver binding. Requires SOFTNET-S7 LEAN or higher.
• IE HARDNET — Siemens CP 16xx PCIe card with HARDNET driver. Requires HARDNET-S7.

Misreading "General IE" as a Siemens hardware interface is a frequent commissioning mistake. Verify the adapter type before ordering a license.

5. Verifying the Automation License Manager (ALM)

ALM is the single source of truth for license allocation. Inspect it on the OS server:

1. Start Automation License Manager from the desktop icon or C:\Program Files\Siemens\Automation\License Manager\alm.exe.
2. Right-click the system drive (usually C:\) and choose Connect target system » Local computer.
3. Expand the drive. Verify the following keys are present and unexpired:
   • WinCC RT (Single Station) or WinCC RT Server — depending on architecture
   • SIMATIC NET IE S7 BCE or SIMATIC NET IE SOFTNET-S7 LEAN or SIMATIC NET IE HARDNET S7
   • PCS 7 OS RT V8.2 license (matches the installed software version)
4. Check the version stamp column. The version on the license key (for example "V14.0") must match the SIMATIC NET version installed. If the installed SIMATIC NET is V14.0 SP1 but the key says V13, the ALM cannot assign the key.

6. Checking the SIMATIC NET and ALM Windows Services

Both services must be running before WinCC starts the S7 channel:

• ALM (Automation License Manager Service) — Startup type: Automatic, Status: Started
• SIMATIC NET Configuration Service — Startup type: Automatic, Status: Started
• S7DOS Help Service (S7DOS / S7-DOS) — Startup type: Automatic, Status: Started
• WinCC License Service — Startup type: Automatic, Status: Started

To restart safely from an elevated command prompt:

net stop "ALM"
net start "ALM"
net stop "SIMATIC NET Configuration Service"
net start "SIMATIC NET Configuration Service"
net stop "S7DOS"
net start "S7DOS"

7. Inspecting WinCC Named Connections

The number of S7 named connections in the WinCC project directly drives the SIMATIC NET licensing demand.

1. Open WinCC Explorer on the OS server (or via remote ES).
2. Right-click Tag Management and select the SIMATIC S7 PROTOCOL SUITE channel.
3. Expand TCP/IP » Named Connections.
4. Count the connections. If the count exceeds 8 and the installed license is BCE or SOFTNET-S7 LEAN, the S7DOS will demand an upgrade license (popup).

For a single-AS, single-OS PCS 7 V8.2 plant, one named connection is the typical minimum. Each redundant partner AS or each secondary AS adds another connection entry and consumes one connection slot from the bundle.

8. Resolving the Version Mismatch (V14 vs V13 License)

When the popup specifically requests a "v14 license" while the ALM only shows a "v13 license", the version stamp on the key is older than the installed SIMATIC NET runtime.

Resolution path:

1. Confirm installed version: Help » About in the SIMATIC NET Configuration Console, or inspect C:\Program Files\Siemens\Automation\SimaticNet\snetsns.ini for the build tag.
2. Request an upgrade license from Siemens via the License Key Generator (LKG) portal using the License Key Request form. The existing V13 key can be rehosted to the new V14 fingerprint.
3. Alternatively, install the matching SIMATIC NET version (V13 SPx) that matches the available key. This is acceptable on PCS 7 V8.2 because SIMATIC NET V13 is still compatible as a downgrade path.

9. Step-by-Step Resolution Procedure

1. Identify the OS station architecture: PC Station with BCE, PC Station with SOFTNET, or PC Station with HARDNET. Use the SIMATIC NET Configuration Console to confirm.
2. Open ALM. Confirm an unexpired SIMATIC NET IE S7 BCE (or higher) key is present and that the version stamp matches the SIMATIC NET runtime major version.
3. Confirm the OS RT (or WinCC RT Single Station) license is present and on the same drive as the WinCC installation.
4. Count named connections in WinCC Explorer. If ≤ 8 and BCE is present, the popup should clear after the next OS reboot.
5. If connections > 8, replace BCE with SOFTNET-S7 (up to 64 connections) or HARDNET-S7 (CP 16xx required).
6. Restart the ALM service, the S7DOS service, and the WinCC Runtime in that order.
7. Trigger a WinCC Runtime restart from WinCC Explorer: Computer » Properties » Start WinCC Runtime. Observe whether the popup reappears.
8. If the popup persists, re-export the license key from the ALM, re-import it on the same drive, and reboot the OS server.

10. Verification Checklist

11. Troubleshooting Matrix

12. Special Case: Redundant OS Servers (H-System)

If the plant later migrates to a redundant AS 410 H architecture, the OS server must also be configured for connection redundancy. The single OS station using BCE is no longer sufficient. Re-license as follows:

• Install a CP 1623 or CP 1628 PCIe card in each OS server (two NICs in total per server for the S7 channel).
• Bind the cards in SIMATIC NET Configuration Console as IE HARDNET.
• Allocate the SIMATIC NET IE HARDNET S7 REDCONNECT license (MLFB 6GK1 716-1EX11-0AA0 for H variant).
• Configure two named connections per AS in WinCC Explorer — one for each physical path.

The HARDNET S7 license (non-redundant) is intended for H-system topologies but with single-path configuration; the REDCONNECT variant enables WinCC to switch the connection transparently when one AS rack fails. The license model is version-specific to the CP card family and the SIMATIC NET version, so always re-verify with the Siemens Industry Online Support manual corresponding to the deployed SIMATIC NET version.

13. Notes on PCS 7 V8.2 and Cemat V8.2 Library

The Cemat V8.2 mining/cement library is a superset of PCS 7 V8.2 and inherits its licensing rules. The Cemat OS server still requires a separate WinCC RT Server license in addition to the OS RT license of PCS 7. If both OS servers (PCS 7 main + Cemat) coexist on the same machine, count both sets of named connections against the SIMATIC NET bundle limit. A Cemat OS with eight PCS 7 connections plus four Cemat-specific connections will exceed the BCE 8-connection bundle.

For multi-server Cemat installations, plan for SIMATIC NET IE SOFTNET-S7 (64 connections) or HARDNET-S7 (CP-based) to avoid the popup at first OS activation.

14. Long-Term Hardening

1. Document the license stack in the plant's System Manual and link the ALM export PDF to the document control system.
2. Add an OS server health check that verifies the ALM, S7DOS, and WinCC services are running before the OS enters production. Siemens PCS 7 Maintenance Station can monitor these services and raise a "License not available" alarm.
3. Subscribe to Siemens Industry Online Support notifications for the SIMATIC NET version in use, so version-mismatch popups are addressed before a planned OS upgrade.
4. Re-verify the connection count after every AS or OS project migration. Every added S7 connection consumes one slot in the license bundle.

15. Frequently Asked Questions