Resolving Missing Interlock Texts on Specific PCS 7 OS Clients

When interlock descriptive texts on technological faceplates fail to display on a single OS Client while functioning properly on all other clients in a SIMATIC PCS 7 installation—despite having identical graphic picture files (*.pdl)—the root cause is a mismatch in the active WinCC Runtime Language, missing Windows system fonts, or an uninitialized OS Server package. Faceplate interlock strings are retrieved dynamically from the text library according to the client's configured runtime language and regional locale settings; if the faulty client's default language differs or contains empty text records, strings display blank. Resolve this by verifying regional settings and language in WinCC Explorer, synchronizing server packages, and confirming Windows font installations.

Multi-Client Text Rendering and Localization Architecture

In SIMATIC PCS 7 client-server architectures, graphic pictures (*.pdl) deployed on OS Clients do not embed static text strings for technological descriptions. When an operator opens an interlock faceplate (such as an APL Intlk08 or customized Metal Library interlock dialog), the faceplate dynamically queries text strings from the WinCC Text Library (Text Distributor) or reads the block comment and parameter descriptions from the OS Server database over DCOM.

A perplexing diagnostic puzzle occurs when four OS Clients display complete interlock descriptions (e.g., 'Lubrication Oil Pressure Low', 'Emergency Pull Cord Tripped'), but a fifth client displays completely blank text fields, even after copying the entire GraCS directory from a working client. Because the graphic templates are identical, the failure lies in local client runtime localization or communication resolution.

Why Identical PDL Files Can Render Different Text Across Clients

Copying .pdl files fails to resolve the problem because the text data does not live inside the PDL file:

Runtime Language Mismatch: WinCC maintains multi-language text tables indexed by Windows Language IDs (LCID). If the four working clients have their default runtime language set to English (United States) [1033], but the non-working client was installed with English (United Kingdom) [2057] or German [1031], WinCC searches the database for that language index. If texts were never populated for that secondary locale, WinCC returns empty strings.
Outdated OS Server Package: OS Clients query server tags and text libraries via the downloaded Server Data package (*.pck). If the non-working client has a corrupted, locked, or desynchronized server data package, text lookups fail silently.
Missing Windows Fonts: Custom industry libraries (such as the PCS 7 Metal Library) frequently employ specialized TrueType fonts. If the non-working workstation lacks the specific font installed in Windows, text boxes can collapse or render as transparent.

Text Library Language Codes vs Windows Regional Settings

Two distinct language layers must align perfectly on every OS Client:

Windows Regional System Locale: Configured in Windows Control Panel (Region and Language). Governs character encoding, ANSI code pages, and numeric decimal separators.
WinCC Runtime Language: Configured in WinCC Explorer under Computer -> Properties -> Parameters. Governs the active LCID query dispatched to the Text Library and OS Server package.

Comparison of Potential Root Causes on Isolated OS Clients

The table below contrasts the diagnostic indicators and solutions for isolated client text rendering failures.

Potential Root CauseDiagnostic SymptomVerification MethodCorrective ActionWinCC Language MismatchText blank on one PC; healthy on othersCheck WinCC Explorer -> Computer -> ParametersSet identical default runtime language (e.g. English US)Windows System Locale MismatchText corrupt or blankCheck Windows intl.cpl Regional SettingsSet system locale and format to match working clientsCorrupted Server PackageTag values update, but static library texts failRight-click Server Data in WinCC ExplorerDelete server package, re-import, and restart WinCCMissing TrueType FontText box geometry present but emptyCompare C:\Windows\Fonts against working PCInstall missing Siemens Sans / custom library fontDCOM Access PermissionsScript errors in apdiag.exeCheck Windows Event Viewer / DCOM logsRun PCS 7 Security Controller -> Repeat Settings

Step-by-Step Troubleshooting and Rectification Workflow

Follow this step-by-step procedure to resolve missing interlock texts on the isolated client:

Reconcile WinCC Runtime Language Settings:
- On a working client, open WinCC Explorer -> Computer -> right-click computer name -> Properties.
- In the Parameters tab, record the exact values for Language at Runtime and Default Runtime Language.
- Open WinCC Explorer on the non-working client: navigate to the same dialog.
- Ensure both language selections match the working client identically.
Reconcile Windows Regional Settings:
- In Windows Control Panel, open Region (intl.cpl).
- In the Administrative tab, check Language for non-Unicode programs (System Locale).
- Verify that the locale matches the working clients (e.g., English United States). Reboot Windows if changed.
Update and Reload OS Server Data Package:
- In WinCC Explorer on the non-working client, expand Server Data.
- Right-click the server package file (<ServerName>.pck) and select Update.
- If updating fails, delete the package, select Server Data -> Load..., browse to the OS Server share, and re-import the package.
Execute SIMATIC Security Controller:
- Open Start -> Siemens Automation -> Security Controller.
- Click Repeat Settings to ensure all DCOM and registry access rights to remote text servers are verified.

Verification

Verify text display restoration through the following tests:
1. Launch WinCC Runtime on the formerly failing OS Client.
2. Navigate to a process graphic and click the block icon of an interlocked motor or valve to open the faceplate.
3. Switch to the Interlock view: verify that all interlock signal descriptions (e.g., 'Bearing High Temp', 'Low Flow') display clearly.
4. Compare faceplates side-by-side with a working client: confirm that fonts, text alignment, and colors are 100% identical.

Limitations and Operational Precautions

Avoid modifying regional settings or system locales on a live client during plant operations, as changing the system locale forces an immediate Windows operating system reboot. Always schedule client maintenance during shift handovers or maintenance windows. Furthermore, when designing custom industry libraries (such as the Metal Library), always document required TrueType fonts in the plant engineering commissioning manual.

Engineer FAQ

Why did copying the GraCS folder from a working client not fix the problem?

Faceplate text strings are not stored inside graphic PDL files; they are queried dynamically from the Text Library database and server data packages based on the active language ID.

Can I switch the runtime language dynamically from the operator screen?

Yes, if language switching buttons are configured using the standard WinCC function SetLanguage(). However, if the text library lacks translations for that language, texts will render empty.

What tool manages translations across the entire PCS 7 multiproject?

The Text Distributor tool (Options -> Text Distributor in SIMATIC Manager) manages bulk export, translation, and import of all text strings across CFC, SFC, and WinCC.