Resolving CEMAT License Manager Warning (No Valid Server License Found) on WinCC Faceplates in PCS 7
The popup notification 'No valid server license found' in SIMATIC PCS 7 CEMAT occurs when an operator opens a technological group faceplate and the CEMAT License Manager cannot detect a valid runtime license on the host OS Server. This error is triggered by version mismatches after upgrading CEMAT libraries (e.g. running V7.1 blocks under V7.0 licenses), omitting the CEMAT Server license from the local Automation License Manager (ALM) storage, or network communication failures between OS Clients and the license server. To eliminate the notification, install the matching CEMAT Server runtime license on each OS Server, verify license availability via ALM, synchronize CEMAT faceplate scripts by running the OS Project Editor, and re-establish client-server license routing.
Table of Contents
- Executive Summary
- CEMAT Licensing Architecture: Engineering vs Server vs Client Entitlements
- Root Cause Analysis: Why Faceplate C-Scripts Query Server Licenses
- Version Compatibility Mismatches Following CEMAT Library Upgrades
- Step-by-Step Procedure to Install and Validate CEMAT Server Licenses
- CEMAT Licensing and Diagnostic Error Matrix
- Verification
- Network License Server Configuration via Automation License Manager
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Executive Summary
In heavy industrial processing plants—such as cement plants, mining facilities, and mineral processing units—SIMATIC PCS 7 utilizes the specialized industry software package CEMAT (Cement & Minerals Automation). CEMAT provides standardized, interlocked group blocks, drive control modules, and specialized WinCC faceplates. During commissioning or following a software upgrade to CEMAT V7, plant operators frequently encounter an intrusive popup warning whenever opening a technological group faceplate:
CEMAT License Manager: No valid server license found.
While clicking 'OK' allows temporary operation, the dialog reappears on every subsequent faceplate selection, disrupting control room workflows. This technical guide explains the internal licensing mechanisms of CEMAT, analyzes version mismatch triggers, and presents the definitive remediation procedure.
CEMAT Licensing Architecture: Engineering vs Server vs Client Entitlements
CEMAT enforces a multi-tiered commercial licensing structure administered via SIMATIC Automation License Manager (ALM):
- CEMAT Engineering License: Required on the Engineering Station (ES) to compile CFC charts, configure group interlocks, and generate module drivers.
- CEMAT Server License (
CEMAT Server V7.x): Mandatory on each WinCC OS Server (and each redundant server pair). This license authorizes server-side background scripts and group status evaluation. - CEMAT Client License: Authorizes visualization and operator control on dedicated OS Client stations.
- License Enforcement Point: Unlike standard PCS 7 APL blocks that evaluate Process Objects (PO), CEMAT embeds dedicated C-script queries inside its standard faceplate templates (
@PG_C_GROUP.pdl). The script queries the server license state during faceplate instantiation.
Root Cause Analysis: Why Faceplate C-Scripts Query Server Licenses
When an operator clicks a CEMAT group icon, the faceplate execution sequence initiates:
- License Query Execution: The faceplate script invokes internal function
C_LicenseCheck(). This function communicates with the Automation License Manager service over internal port 4410. - Failure Modes: If ALM cannot find a valid license key matching the exact CEMAT major version, or if the license was installed only on the Engineering Station and never transferred to the live OS Server,
C_LicenseCheck()evaluates to FALSE. - Warning Box Presentation: The CEMAT runtime engine displays the modal error box. Because CEMAT does not immediately halt plant operations upon a license deficit, clicking OK bypasses the warning, but the query re-executes on the next click.
Version Compatibility Mismatches Following CEMAT Library Upgrades
The most common cause of the error is an uncoordinated software migration:
- An engineer copies updated technological blocks from a newer CEMAT version (e.g. V7.1) into the project's Master Data Library.
- The AS program is compiled and downloaded, updating block interfaces and faceplate templates.
- However, the physical OS Server remains equipped with older CEMAT V7.0 or V6.x license keys in ALM.
- The newer faceplate script explicitly demands a V7.1 license key. Finding an older license, it flags the server license as missing.
Step-by-Step Procedure to Install and Validate CEMAT Server Licenses
To permanently eliminate the 'No valid server license found' notification:
- Audit Active Licenses via ALM:
* On each OS Server, open Automation License Manager.
* Select local hard driveC:andD:.
* Verify whetherCEMAT Server V7.x(or matching version) is present, valid, and has remaining license counts. - Transfer Server License:
* If the license exists on the USB License Stick or Engineering Station, use ALM (License Key -> Transfer...) to move the license key directly to the target OS Server drive. - Run OS Project Editor on All Stations:
* In WinCC Explorer on each OS Server and OS Client project, open OS Project Editor.
* Click OK to regenerate system scripts and update CEMAT faceplate libraries. - Synchronize Redundant Servers:
* Ensure that both Master Server A and Standby Server B possess identical CEMAT Server licenses. - Restart WinCC Runtime: Deactivate and reactivate WinCC Runtime to initialize the fresh license state.
CEMAT Licensing and Diagnostic Error Matrix
The following table provides diagnosis and remediation for CEMAT licensing alarms:
No valid server license foundNo valid PLC license foundCEMAT Client License missingALM Service not respondingAutomation License Manager Service and open port 4410License expired (Demo Mode)Verification
To verify that CEMAT licensing is fully operational:
- ALM Status Check: In Automation License Manager on the OS Server, confirm that the
CEMAT Server V7.xlicense indicates statusOKwith zero defective clusters. - Faceplate Click Test: In WinCC Runtime, open multiple technological group and route faceplates (
C_GROUP,C_DRIVE). Confirm that the faceplates open instantly without presenting license popup warnings. - Diagnostic Script Inspection: Open
apdiag.exeand monitor the output window while clicking group faceplates. Confirm thatC_LicenseCheckreports valid license verification with zero scripting errors.
Network License Server Configuration via Automation License Manager
In multi-client installations, licensing can be centralized:
- In ALM, navigate to
File -> Settings -> Connection. - Check Allow remote connection and configure ALM as a license server.
- OS Clients can borrow or query licenses dynamically across the Terminal Bus without requiring local USB dongles.
Limitations and Operational Precautions
Never attempt to disable CEMAT license checking by modifying internal C-scripts in @PG_C_GROUP.pdl. Modifying core vendor scripts voids system support, causes OS compilation overwrites, and violates software license agreements.
When procuring CEMAT licenses, upgrades, or plant extensions, all package MLFBs and Process Object entitlements must be verified against the official Siemens CEMAT ordering catalog and validated through an authorized Siemens distributor quotation.
Engineer FAQ
Does the CEMAT server license warning stop the physical plant?
No. The warning is a non-blocking notification that prompts the operator, but the underlying PLC control logic and interlocks continue executing.
Do redundant OS Servers require two separate CEMAT Server licenses?
Yes. In a redundant OS configuration, each physical server must possess its own independent CEMAT Server runtime license.
Can a CEMAT V7.0 license run CEMAT V7.1 blocks?
No. CEMAT enforces major and minor version checks; running V7.1 blocks requires a V7.1 license or a valid version upgrade package.
Where are CEMAT license keys stored physically?
License keys are stored in the hidden 'AX NF ZZ' directory on the root of the hard drive and managed via Automation License Manager.