This pop-up message usually indicates one of three common issues:
Check the status of each license. If a license is present but its status is , you have identified the culprit. Proceed to the advanced recovery steps.
Siemens treats advanced data features as modular add-ons. If your WinCC project contains even a single historical data log or long-term alarm log, the system actively scans for a specific supplemental license at startup. If that license is missing, unfragmented, or corrupted, the runtime triggers the "License key not available" error. The Missing License: WinCC Logging for Runtime Advanced
If you had the license installed but the error appeared after a power failure, the license might be marked as "defective". Open . This pop-up message usually indicates one of three
It sounds like you are encountering the error for WinCC Logging when trying to use the Runtime Advanced link in Siemens TIA Portal.
The license key was never transferred to this PC. Proceed to Step 3.
You activated the WinCC Audit option for GMP or FDA regulated tracking. Step-by-Step Resolution Framework Siemens treats advanced data features as modular add-ons
Siemens structures its TIA Portal and WinCC ecosystems using modular licenses. While a standard license allows you to run the Human-Machine Interface (HMI) on a PC, it does not cover historical data storage. The Missing License Component
: Launch the Automation License Manager on the target machine.
from your project configuration to stop the runtime from requesting the license. Siemens SiePortal Common Triggers for This Error Simulation vs. Hardware WinCC Runtime Advanced Simulation The Missing License: WinCC Logging for Runtime Advanced
Identifying the underlying cause is essential for applying the correct fix. The error can stem from a simple missing license to more complex licensing conflicts or configuration issues.
Ensure the license status icon turns completely green, indicating an active, valid license key. Step 5: Restart the WinCC Runtime Service
Siemens licenses are generally backwards compatible but not always forwards compatible. A WinCC Logging v17 license will work for a v15 Runtime, but a v15 Logging license will trigger an error on a v18 Runtime. Ensure your logging license version matches or exceeds your Runtime project version. 2. Defective Log File Paths