Resolve a PCS 7 V9.0 OS Web Server License Not Recognized

If PCS 7 V9.0 continues to report a Web Navigator licensing error after a license transfer, first confirm that the correct OS Web Server license is available on the PC configured as the OS Web Server. The V9.0 licensing manual lists OS Web Server licensing for the web-server role and identifies the OS Web Server key as the key for the number of Web clients. The original discussion also reports restarting the Automation License Manager service after transfer as a remedy; treat that as a troubleshooting step, not a guaranteed Siemens procedure.

Confirm the server role and license key

The licensing requirement depends on the configured PC-station role. Siemens' PCS 7 V9.0 licensing manual lists OS Web Server Basic and OS Web Server as web-server license keys; the latter is used for the number of Web clients. The manual also states that a web server and web diagnostics server are used alternately. Confirm which service is configured on the station and which license is required for that configuration.

Check that the license key is present and valid on the computer hosting the PCS 7 OS Web Server, not only on the Engineering Station or an unrelated OS client. The ticket's reply specifically calls for an OS Web Server license on the OS Server PC. Use the V9.0 licensing table and the Web Option documentation for the exact station topology.

Refresh license recognition after transfer

The discussion reports that restarting the Automation License Manager service after transferring the license resolved recognition in the responder's context. Siemens' Automation License Manager manual confirms that some setting changes take effect only after restarting the service or computer, but that passage concerns connection settings, not a universal requirement after every license transfer.

If the correct license is installed on the web-server PC and the error persists, a controlled service restart is a possible diagnostic step:

Coordinate the action with the OS administrator and operations team, since license-management services are part of the configured PC environment.
On the affected PC, use Windows Services to locate the Automation License Manager service and restart it, or restart the PC during an approved maintenance window.
Recheck the license in Automation License Manager and retry the relevant Web Navigator/OS Web Server function.
If the error remains, record its exact text and check the license key type, license validity, station role, and whether the correct server PC holds the license.

The exact service display name and operational impact should be checked against the installed Automation License Manager/PCS 7 version.

Separate license placement from client count

The V9.0 manual distinguishes the OS Web Server Basic key from the OS Web Server key, which is described as the license for the number of Web clients. It also lists web diagnostics as an alternative web-server role. A valid key of the wrong type, or a license located on the wrong computer, may not satisfy the configured role. Compare the actual deployment with the relevant V9.0 manual instead of assuming that any transferred “Web Navigator” license is interchangeable.

Verification

Confirm that the appropriate OS Web Server license appears in Automation License Manager on the host configured for the web server and that it is available for use. Then test the affected client connection and verify that the licensing error has cleared. A license appearing in the manager does not alone prove that the OS web option is correctly installed and configured; if the message persists, capture its full text and review the Web Option setup and licensing requirements for the exact PCS 7 release.

Limitations and Operational Precautions

The ticket does not quote the actual error or identify whether the PC is a single-station OS, a dedicated OS Web Server, or an OS client. The cited license manual is for PCS 7 V9.0, while the Automation License Manager manual is dated 2014. The restart recommendation is reported from the forum reply; opened manufacturer material did not confirm that every post-transfer license-recognition issue requires an ALM service restart. Restart services or PCs only under site operational procedures, and preserve the exact diagnostic text for further troubleshooting.

Engineer FAQ

Where should the OS Web Server license be placed? The ticket reply says to ensure it is on the OS Server PC. Confirm the actual server role and exact key in the PCS 7 V9.0 licensing documentation.

What does the OS Web Server key license? The V9.0 licensing table identifies it as the key for the number of Web clients; it lists OS Web Server Basic separately.

Should I restart Automation License Manager after transferring a key? The forum response recommends it for this reported issue. Treat it as a possible refresh step, not a universal requirement; if necessary, perform it under site change procedures.

Could the wrong web license type cause continued errors? Yes, the V9.0 manual distinguishes web-server license types and says web server and web diagnostics server are alternate roles. Match the key to the configured service.

What if a restart does not clear the error? Record the exact message and verify license presence/validity, the PC station role, web option installation and the correct client-count license.

Technical References

Siemens, Licenses and configuration limits (V9.0), Installation Manual, 05/2017, A5E39222309-AA, §4.3 “Software and license keys for Operator Stations,” pp. 34–36: https://cache.industry.siemens.com/dl/files/549/109746549/att_923991/v1/ps7lic_en-US_en-US.pdf
Siemens, Automation License Manager, Programming and Operating Manual, 09/2014, A5E32921785-AC, §6.15 “Connection tab in the Settings dialog,” p. 100, which documents service/computer restart for changed ALM connection settings: https://cache.industry.siemens.com/dl/files/153/102770153/att_87643/v1/almappxres_en-US.pdf

Resolve a PCS 7 V9.0 OS Web Server License Not Recognized