Resolving Named Connection Failures During PCS 7 V6.0 to WinCC V7 Migration

This reference covers the complete resolution path for named connection failures that occur when migrating a PCS 7 V6.0 runtime project to a WinCC V7 environment on fresh PC hardware. The failure mode — an Ethernet-bound named connection not establishing between the WinCC runtime and an S7-400 H-CPU (H-station) — has multiple root causes, each of which must be cleared in sequence. Use the configuration procedure, verification checklist, and troubleshooting matrix to isolate and correct each failure point.

1. Problem Definition: Named Connection Failure After PCS 7 V6.0 to WinCC V7 Migration

The classic failure mode is the following: an operating PCS 7 V6.0 installation is destroyed on its original PC hardware (typically Windows Server 2003 with a SIMATIC NET PC software stack tuned for the WinCC V6 RT environment), and the project artifacts are rebuilt onto a fresh PC running Windows XP SP3 or a 32-bit Windows 7 release. The S7-400 H-CPU stations remain intact and respond normally on the plant Ethernet network, but the WinCC V7 runtime reports the named connection to the AS as failed, down, or in cyclic reconnect, and no process tags update.

The named connection is the symbolic, configuration-driven S7 connection type used by PCS 7 operator stations (OS) to the assigned automation station (AS) over Industrial Ethernet / PROFINET. Unlike the unnamed S7 TCP/IP or S7 ISO-on-TCP connection that the WinCC TCP/IP or ISO channel unit uses, the named connection is not configured by IP address inside WinCC; it is configured by a symbolic connection name in the STEP 7 / SIMATIC Manager project and resolved through the PC station configuration editor and SIMATIC NET at runtime.

Per the Siemens TIA Portal documentation on Configuring a connection via 'Named connections' (Basic Panels through RT Professional), the symbolic connection name and the application name are configured in STEP 7, and the named connection can only be configured for integrated connections. WinCC's "SIMATIC S7 Protocol Suite" channel exposes this configuration through the "Named Connections" channel unit, where the symbolic connection name is mapped to the target WinCC application name.

The Siemens Knowledge Base article on How to configure a "Named Connections" channel unit connection confirms the runtime side: for setting up a logical connection, one of the symbolic connection names listed in the "Connection name" field is assigned to a selected application name in the WinCC Channel Diagnostics.

2. Root Cause Analysis: Why Named Connections Fail After Migration

Five distinct failure modes have been observed on migrated PCS 7 V6.0 → WinCC V7 installations. Each has a different signature in the WinCC Channel Diagnostics tool and a different fix.

3. Prerequisites and Required Software Components

Verify the following component matrix before opening WinCC Explorer. Missing any one component prevents the named connection from resolving at runtime.

4. PC Station Architecture for Named Connections

The named connection traverses three runtime layers. Each layer must be correctly populated for the symbolic connection name to resolve to a live S7 connection.

The application name configured in NetPro must match the slot index assigned in Station Configuration Editor. Typical mappings:

5. Step-by-Step Configuration Procedure

Execute the following sequence in order. Skipping any step breaks the chain.

5.1 Verify SIMATIC NET Installation

1. Open Start -> Programs -> Siemens Automation -> SIMATIC -> SIMATIC NET -> Configuration -> Station Configuration Editor. Confirm the editor opens without error.
2. Open Start -> Programs -> Siemens Automation -> SIMATIC -> SIMATIC NET -> Communication Settings and confirm PG/PC Interface lists PC Station -> Industrial Ethernet -> <your NIC>.
3. Open the Services snap-in (services.msc) and confirm SIMATIC NET OPC Server, S7DOS, and PNIO services are set to Automatic and Started.

5.2 Configure the PC Station in Station Configuration Editor

1. Launch Station Configuration Editor with administrator rights.
2. Add component Slot 1: type WinCC Application (the component labeled "HMI"), index 1.
3. Add component Slot 2: type OPC Server, index 1.
4. Add component Slot 3: type IE General. Click Properties and bind it to the physical NIC that connects to the plant Ethernet. Set the MAC and IP address to match the OS station address defined in the STEP 7 NetPro.

5.3 Generate and Import the XDB File from STEP 7 / SIMATIC Manager

1. On the engineering station, open the migrated STEP 7 project that contains the WinCC OS PC station.
2. In SIMATIC Manager, select the OS PC station object, then Options -> Configure Network (NetPro).
3. Verify the S7 connections from the OS to each AS show symbolic connection names such as AS01_OS, AS02_OS. The "Local ID" column must contain a non-zero value — this is the connection ID referenced by the XDB.
4. Select the OS PC station in NetPro, then Options -> Export Station to XDB. Save as <station_name>.XDB in a path accessible from the runtime PC.
5. Transfer the XDB file to the runtime PC.
6. On the runtime PC, open Station Configuration Editor and select Station -> Import. Browse to the XDB file. The component slots must populate with the same indices exported from STEP 7.
7. Close Station Configuration Editor and confirm the prompt to save changes.

5.4 Configure WinCC Channel for Named Connections

1. Open WinCC Explorer on the runtime PC.
2. Right-click Tag Management -> Add New Driver -> select SIMATIC S7 Protocol Suite.
3. Expand SIMATIC S7 Protocol Suite -> Named Connections.
4. Right-click Named Connections -> New Connection. The Connection Properties dialog opens.
5. In the Connection name dropdown, select the symbolic name exported in the XDB (e.g., AS01_OS). Do not type the name manually — the dropdown is populated only when Station Configuration Editor holds a valid XDB import.
6. Set the application name field. The default WINCC is correct when Slot 1 holds a WinCC Application component.
7. Click OK. Repeat for each AS to which the OS connects.

5.5 Compile the OS Project

1. In WinCC Explorer, right-click the project root and select Rebuild All.
2. Activate the runtime. The connections appear in Tools -> Channel Diagnostics with state transitions from Disconnected -> Establishing -> Connected.

6. WinCC V7 SP2 PowerTag Restriction

Beginning with WinCC V7.0 SP2, the named connection is only released by Siemens for use with the optional PowerTag package. Without PowerTag licensed and activated, the named connection either fails silently on startup or generates error 0x80004005 in Channel Diagnostics with the text "Named connections are not licensed."

The behavior is documented in the WinCC V7.0 SP2 release notes and persists through V7.0 SP3, V7.2, and V7.3 — only the licensing path is consistent. Workarounds for environments that cannot license PowerTag:

1. Switch the connection from the "Named Connections" channel unit to the "TCP/IP" channel unit. This converts the symbolic name to an IP-address-bound S7 connection and removes the PowerTag dependency. The downside is the loss of automatic configuration when AS IP addresses change.
2. Switch to the "ISO Industrial Ethernet" channel unit if the plant network uses ISO Transport. The same IP-vs-symbolic trade-off applies.
3. For H-CPU (S7-400H) targets, replace the named connection with an H-capable S7 connection configured manually with both CPU IP addresses, and enable the "Establish connection to redundant partner" option in WinCC Channel Diagnostics.

7. Network and IP Configuration Verification

Before declaring the configuration complete, validate the network path and the PC station address.

8. Runtime Diagnostic Procedure

Open WinCC Explorer -> Tools -> Channel Diagnostics on the running OS. For each named connection the tool shows the application name, the connection state, and the last error code.

The OPC server diagnostic files at C:\Program Files\Siemens\Automation\SIMATIC_NET\opc2\log\ (default install path) contain a per-connection log with timestamps and ISO transport error codes. The relevant entries use the format OPC: connection <name> state change 1 -> 3 where 1=setup, 2=connected, 3=broken.

9. Troubleshooting Matrix

10. Migration-Specific Caveats for PCS 7 V6.0 Projects

PCS 7 V6.0 originally paired with WinCC V6.0 and STEP 7 V5.3. Migrating forward to WinCC V7 requires the following, all of which touch the named connection path:

• STEP 7 upgrade: The PCS 7 migration wizard runs inside STEP 7 V5.4 or V5.5. The original project is opened in read-only and re-saved under the new version. The PC station object is rewritten with the new S7 connection table format.
• WinCC project upgrade: The migrated WinCC project is opened once with the target WinCC V7 release, which prompts for a project migration. During this migration the WinCC channel assignments are recomputed and the Symbolic Connection list is rebuilt.
• SIMATIC NET upgrade: The PC software stack must be upgraded to a release that matches the target WinCC version. A mixed V6.x SIMATIC NET with a V7 WinCC is unsupported and will not register the OPC server correctly with the WinCC channel.
• PG/PC interface reset: After installing new SIMATIC NET, the PG/PC Interface tool must be reopened and the assignment reset to PC Station -> Industrial Ethernet -> <NIC>. This is the most common root cause of F1 and F2 failure modes.

11. Verification Checklist (Post-Configuration)

Mark each item verified before declaring the named connection operational.

1. Station Configuration Editor shows WinCC Application, OPC Server, and IE General in slots 1, 2, 3 with no warning icons.
2. IE General module is bound to the correct physical NIC, MAC matches the OS PC station object in NetPro.
3. Channel Diagnostics lists every configured AS with state "Connected" within 10 s of WinCC runtime activation.
4. WinCC tag from each AS updates on a forced value change in the AS (test with a discrete output tag).
5. OPC error log at %SIMATIC_NET_HOME%\log\ contains no entries with severity "Error" related to the named connections.
6. WinCC runtime survives a WinCC Explorer -> "Exit WinCC Runtime" -> "Restart WinCC Runtime" cycle and re-establishes all named connections without operator intervention.
7. Redundant AS partner (H-system second CPU) responds on a CPU failover test (only applicable to S7-400H plants).