Troubleshoot APL Permit and Interlock Popups That Fail on a PCS 7 OS Client

If PCS 7 APL Permit and Interlock popups fail only on an OS client and the output reports invalid plzBlockType from APL_OpenWindow, compare the client's server data and popup/block association with the working OS server. A PCS 7 V9.0 help excerpt quoted in the discussion cautions against assigning a Standard Server to the Text Library unless required by a special application. The thread does not confirm that this setting caused the popup failure.

Reported symptom

An OS client can navigate the main windows and open APL popups, but Permit and Interlock popups do nothing. The output window reports invalid plzBlockType from APL_OpenWindow. The same functions reportedly work when running on the OS server. No APL version, popup block type, package details or complete runtime log is provided.

Review the Text Library server assignment

A reply quotes PCS 7 V9.0 help stating that a Standard Server for archives, pictures, Text Library, user archives and tags is intended only for special applications; absent a specific Siemens instruction, it says to leave the setting at No Standard Server. The original project had a Standard Server assigned to Text Library. Check whether that setting is intentionally required for this project; if not, correct it through the approved engineering process and regenerate/update relevant server data as documented.

Compare client and server runtime data

Clarify whether “works on server” means the OS server runtime itself or the client project physically opened on the server computer. Compare the server packages and server data available to the OS client, including their last update state. Siemens PCS 7 PC Configuration V9.0 documents OS client process-mode behavior and warns that the client can take server data from the Engineering Station if SIMATIC Manager remains open while opening the client project.

Check APL popup associations

Record the exact technological block connected to the Permit/Interlock popup, APL version, faceplate files, and full output-window message. Compare the same popup and block association on the working OS server and failing client; the available source does not identify the required block association or prove that plzBlockType points to a particular connection fault.

Verification

Test the configured client project in process mode and confirm that Permit and Interlock popups open for the intended block and display current status. Verify on the actual client and confirm that package/server-data updates and the Text Library setting do not introduce other runtime faults.

Limitations and Operational Precautions

The thread supplies questions but no confirmed resolution. The quoted Text Library guidance is from a PCS 7 V9.0 context; exact release and special-application requirements must be checked. Do not change server assignments or overwrite client/server packages without an archive and approved test/change plan.

Engineer FAQ

Is the Text Library Standard Server the proven cause of invalid plzBlockType? No. It was a suspect setting identified in the reply, not a demonstrated cause.

Does success on the server prove the client project is correct? No. Server data/package state and the actual client runtime still need separate checking.

Technical References

PCS 7 PC Configuration V9.0, Installation Manual 05/2017, A5E39221378-AA, OS client process-mode notes, p. 156; official Siemens PDF opened and read.
PCS 7 V9.0 Server Data Editor help quoted in the source discussion; no separately accessible direct reference was available during this review, so the No Standard Server guidance remains version/context-specific.