Troubleshooting Named Connection Disconnects on Standby/Partner WinCC OS Servers After Restart

When a restarted partner server in a redundant WinCC OS pair fails to connect to AS tags while the redundant partner communicates normally, the issue typically stems from a mismatch in the Named Connection access point, an uninitialized Station Configuration Editor (SCE), or a corrupted XDB database. To resolve this: (1) Open WinCC Tag Management -> SIMATIC S7 Protocol Suite -> Named Connections -> System Parameters, and verify that the Logical Device Name precisely matches the configured interface (e.g., CP_H1_1: or S7ONLINE); (2) Open Station Configuration Editor and confirm that the PC Station name matches STEP 7 exactly and all components are in RUN; and (3) Use WinCC Channel Diagnosis (WinCCChannelDiagnosis.exe) to inspect the connection state and clear pending driver locks.

Executive Summary

In high-availability SIMATIC PCS 7 environments, redundant WinCC OS Server pairs (Server 1 and Server 2) communicate with fault-tolerant S7-400H controllers using 'Named Connections' over Industrial Ethernet. A critical operational failure occurs when one server is rebooted for routine maintenance and restarts in a degraded state: tags in WinCC Tag Management remain disconnected (status bad/greyed out), while the redundant partner server continues operating normally. Recompiling and downloading the OS from the Engineering Station (ES) often fails to restore communication. This failure typically originates from driver-level access point mismatches, Station Configuration Editor index desynchronization, or SIMATIC NET communication process stalls.

Architecture and Fundamental Mechanics

Named Connections in SIMATIC PCS 7 differ fundamentally from standard TCP/IP communication channels:

Named Connection Architecture: Standard TCP/IP connections bind directly to a hardcoded remote IP address. In contrast, a Named Connection routes through the SIMATIC NET S7 communication layer using a symbolic connection name defined in STEP 7 NetPro. This enables fault-tolerant routing (S7-REDCONNECT), allowing WinCC to switch seamlessly between redundant CP443-1 cards or redundant H-CPU subracks without tearing down the application socket.
Role of the Station Configuration Editor (SCE): The PC Station configuration is exported from STEP 7 as an .XDB database file and imported into the local Station Configuration Editor (Component Configurator). The SCE binds the WinCC Application (Index 1) and physical communication processors (e.g., CP1623 at Index 2 or IE General at Index 3). If the PC Station name in Windows does not match the STEP 7 PC Station name character-for-character, the SCE rejects connection routing.
The Logical Device Name Link: In WinCC Tag Management under SIMATIC S7 Protocol Suite -> Named Connections -> System Parameters -> Unit, the Logical Device Name specifies the access point (e.g., CP_H1_1: or S7ONLINE). A missing trailing colon (:) or an unmapped access point in Windows Set PG/PC Interface breaks the link between WinCC and the SIMATIC NET driver.
Post-Restart Failure Mechanics: When Server 1 restarts, Windows networking services, SIMATIC NET services (s7wncstx.exe), and WinCC startup routines initialize asynchronously. If WinCC Runtime launches before the SIMATIC NET Station Manager finishes binding network interfaces, the Named Connection channel enters an unrecoverable timeout state, displaying disconnected tags.

Step-by-Step Implementation Procedure

Execute the following structured troubleshooting procedure on the affected server:

Inspect Channel Diagnostics:
- On the malfunctioning server, launch WinCCChannelDiagnosis.exe (located in Siemens\WinCC\bin or via WinCC Explorer -> Tools).
- Select SIMATIC S7 Protocol Suite -> Named Connections.
- Inspect the connection status flag and error code (e.g., 0xFFDF 42C2 connection timeout, or Disconnected).
Verify Station Configuration Editor (SCE):
- Open the Station Configuration Editor from the Windows taskbar tray.
- Verify that the station name in the title bar matches the STEP 7 PC Station name exactly.
- Check that all components (Index 1 WinCC Application, Index 2 CP1623/IE General) display status RUN with zero red error icons.
- If disabled or misconfigured, click Station Properties -> rename if necessary, or re-import the .xdb file.
Verify Set PG/PC Interface and Logical Device Name:
- Open Set PG/PC Interface from Windows Control Panel.
- Confirm that the configured access point (e.g., CP_H1_1:) is explicitly mapped to the physical network card adapter (e.g., CP1623(ISO) or TCP/IP -> NIC).
- Open WinCC Explorer on the server. Navigate to Tag Management -> SIMATIC S7 Protocol Suite -> Named Connections.
- Right-click Named Connections, select System Parameters, and open the Unit tab.
- Verify that Logical Device Name matches the exact access point string from PG/PC interface, including any trailing colon (:).
Synchronize via NetPro and Download Configuration:
- On the Engineering Station (ES), open NetPro.
- Select Network -> Save and Compile.
- Select the affected PC Station in NetPro, select PLC -> Download to Current Project -> Selected Station to rewrite the station configuration.
Restart WinCC Runtime:
- Deactivate WinCC Runtime on Server 1.
- Reboot Server 1 cleanly, allowing SIMATIC NET services to start fully before opening WinCC.
- Activate WinCC Runtime. Verify that Named Connections transition to status OK (green).

Verification

Confirm full communication redundancy recovery:

Channel Diagnosis Verification: Open WinCCChannelDiagnosis.exe. Verify that all AS connections under Named Connections report State: Connected with green checkmarks and active telegram counters incrementing.
Tag Quality Inspection: In WinCC Explorer -> Tag Management, inspect active process tags. Confirm that tag values are active and display signal quality code 16#80 (Good).
Redundancy Synchronization: Open @RedundantServerState in WinCC Graphics or Tag Logging. Verify that Server 1 and Server 2 negotiate Master/Standby roles properly, with @PRF_REDUNDANCY_IS_SYNCHRONIZED returning 1.

Limitations and Operational Precautions

Never manually modify individual connection parameters in WinCC Tag Management when using PCS 7; Named Connections must always be generated automatically via OS Compilation from NetPro. Manually altering connection parameters in WinCC Explorer creates configuration divergence that will be overwritten during the next full OS compile.

Engineer FAQ

Why do Named Connections require trailing colons in the Logical Device Name?

In SIMATIC NET, logical access points that represent hardware devices or protocols (like CP_H1_1:) require the trailing colon to distinguish the device handle from a symbolic connection name in the communication driver.

Can I download the PC Station configuration from NetPro while the server is running?

Yes, provided the Station Configuration Editor is online and network connectivity is intact. However, downloading station configuration momentarily resets the communication adapter.

What is the difference between Named Connections and TCP/IP connections in WinCC?

TCP/IP connections require fixed IP addresses and do not support automatic failover across redundant networks. Named Connections use NetPro symbolic routing and S7-REDCONNECT for seamless fault-tolerant failover on S7-400H systems.

Why did Server 2 continue communicating while Server 1 failed?

Server 1 and Server 2 maintain completely independent physical network cards, SIMATIC NET drivers, and SCE configurations. A local driver stall or SCE mismatch on Server 1 does not impair Server 2.

What role does Simatic Shell play in Named Connections?

Simatic Shell manages terminal bus communication between OS servers, clients, and ES. While AS communication uses the plant bus, Simatic Shell must be properly bound for the ES to download OS configurations to the server.