How to Resolve WinCC OS Client Runtime Error 'This Station Has an Inoperable Status' in PCS 7

In SIMATIC PCS 7 (V8.1, V8.2, and V9.x), an OS Client halting with a full-screen grey screen and the error 'This station has an inoperable status. Please inform your service management or restart the computer' occurs when the client's Split Screen Manager (SSM) watchdog detects a total loss of communication with both redundant OS Servers, or when Windows DCOM/RPC security updates block background server polling. Furthermore, this error is frequently provoked by using the WinCC Project Duplicator—which is strictly prohibited in PCS 7. Resolving the fault requires verifying Terminal Bus network routing, configuring a Preferred Server on the client, and reapplying Siemens Security Controller.

Mechanics of the OS Client 'Inoperable Status' Watchdog

In SIMATIC PCS 7 multi-user architectures, OS Clients serve as operator control workstations that display process pictures and trends hosted on redundant OS Servers.

As detailed in Section 5.4.9 of the SIMATIC PCS 7 OS Process Control Manual:
* An OS Client relies on the Split Screen Manager (SSM) and Redundancy Watchdog to supervise connection health to its assigned OS Server pair.
* If the watchdog determines that both OS Server 1 and OS Server 2 are completely unreachable, or if the client runtime encounters a fatal internal graphic desynchronization that renders operator actions unsafe, the system initiates a protective lockdown:
* The entire graphical workspace is suppressed and replaced by a solid grey screen.
* A modal warning appears: 'This station has an inoperable status. Please inform your service management or restart the computer'.
* The only interactive element provided is a red restart button in the bottom right corner.

Root Cause Analysis for Grey Screen Shutdowns

When multiple OS Clients (or specific client workstations) randomly drop into the inoperable status screen, the underlying failure traces to one of several critical network and operating system mechanisms:

1. Terminal Bus Network Disruption / NIC Power Saving

If the client's network adapter drops packets, encounters high latency, or enters Windows power-saving sleep mode, the SSM keep-alive timer (typically 10 to 30 seconds) elapses. Because neither server responds, the client declares an inoperable status.

2. DCOM Security Hardening and Windows Updates

Microsoft security updates altering DCOM RPC authentication levels (such as KB5004442) or un-whitelisted Windows Defender updates can block remote procedure calls between the client and OS Servers. The client's background tag polling engine (CCProjectMgr) encounters RPC access denied exceptions.

3. Missing Preferred Server Assignment

If an OS Client is not configured with a Preferred Server, it randomly toggles between Server 1 and Server 2. During transient network jitter or server archive replication, the client may disconnect from both nodes simultaneously.

The Prohibition of WinCC Project Duplicator in PCS 7

A widespread and dangerous engineering mistake in PCS 7 is attempting to duplicate an OS Server project using the generic WinCC Project Duplicator:

Why Project Duplicator Destroys PCS 7 Redundancy

In Standard WinCC: Project Duplicator is standard practice.
In SIMATIC PCS 7: Project Duplicator is STRICTLY PROHIBITED.
In PCS 7, server redundancy is managed at the SIMATIC Manager multiproject level. The Standby Server is a dedicated WinCC Application (stby) with its own distinct network configuration and server data packages.
Using Project Duplicator copies Master station parameters and computer names onto the Standby Server, destroying the redundant pair's internal GUID relationships and causing connected OS Clients to crash into the inoperable status screen!
Mandatory PCS 7 Method: OS Server projects must be downloaded exclusively via SIMATIC Manager (PLC -> Download).

Step-by-Step Remediation Procedure

To resolve the inoperable status error permanently:

Step 1: Assign Preferred Server on All OS Clients

In SIMATIC Manager Plant View, locate the OS Client project.
Open the WinCC Client project in WinCC Explorer.
In the project tree, right-click Server Data and select Configure....
In the dialog, assign the Preferred Server:
* Set Server 1 as preferred for half the clients, and Server 2 as preferred for the other half (load balancing).
Compile and download the client project.

Step 2: Run Siemens Security Controller on Client and Servers

On each affected OS Client and OS Server, open Security Controller.
Select Repeat Settings; apply all DCOM, Firewall, and User Group rules.
Restart the computers.

Step 3: Disable Network Adapter Power Saving

In Windows Device Manager on each client, open the properties of the Terminal Bus network card.
Switch to the Power Management tab.
Uncheck 'Allow the computer to turn off this device to save power'.

Step 4: Verify Hostname Resolution in `hosts` File

Open C:\Windows\System32\drivers\etc\hosts.
Ensure static IP and hostname entries exist for all OS Servers and Clients to eliminate DNS delays.

OS Client Diagnostic Parameter and Watchdog Reference Matrix

The following table outlines the diagnostic parameters and triggers for the WinCC Client inoperable status:

Parameter / ConditionHealthy ThresholdInoperable Trigger ConditionDiagnostic Log to InspectServer Link Ping< 2 ms latency100% packet loss to both serversC:\Program Files\Siemens\WinCC\Diagnose\WinCC_Sys_01.logSSM Watchdog TimeoutActive keep-aliveNo response for >30 secondsPMDiagnose.log on OS ClientDCOM AuthenticationLevel: Packet IntegrityAccess Denied / RPC ExceptionWindows Event Viewer (System)Preferred ServerExplicitly ConfiguredUnassigned (Floating connection)WinCC Explorer -> Server DataProject GenerationSIMATIC Manager DownloadCreated via Project DuplicatorMultiproject Component View

Enforcing static network settings and preferred servers prevents client watchdog trips.

Verification

To verify that the OS Client stability has been restored:
1. Launch WinCC Runtime on the OS Client.
2. Confirm that process screens load smoothly and faceplates open without delay.
3. In WinCC Explorer, verify that the internal tag @RM_SERVER_NAME points to the designated Preferred Server.
4. Simulate a single server restart on Server 1: confirm that the client switches transparently to Server 2 without showing the grey inoperable screen.
5. When Server 1 returns online, confirm automatic client re-synchronization.

Limitations and Operational Precautions

Clicking the red restart button on the inoperable screen immediately reboots Windows; ensure operators know this action will restart the physical PC.
Never run OS Clients over Wi-Fi or unmanaged office networks; the Terminal Bus must be an isolated, switched Industrial Ethernet infrastructure.
Do not install unverified Windows security rollups on production PCS 7 stations without verifying compatibility in the Siemens Kompatool.
Ensure all OS Clients and Servers belong to the same Windows workgroup or Active Directory domain with synchronized system clocks.

Engineer FAQ

Why does the inoperable status screen provide only a reboot button?

Because the client has lost all communication to automation servers, continuing to display frozen graphic values could cause an operator to take erroneous, dangerous actions. Rebooting forces a clean network re-initialization.

Can I use WinCC Project Duplicator if I only have a standard OS Server pair?

No. In SIMATIC PCS 7, Project Duplicator must never be used. All project downloads must be performed through SIMATIC Manager.

How do I prevent clients from overloading Server 1 after a restart?

Configure half of your clients with Server 1 as their Preferred Server, and the other half with Server 2. This distributes client connection loads evenly across both servers.

Technical References

Related Tags

OS_Client
Inoperable_Status
Grey_Screen
Preferred_Server
Terminal_Bus

6 respuestas

How to Resolve WinCC OS Client Runtime Error 'This Station Has an Inoperable Status' in PCS 7