Resolving Missing Station Manager 125 Errors During WinCC OS Client Downloads

The error 'Unable to establish connection to module Stationmanager (Index 125)' when downloading a WinCC OS Client from the Engineering Station (ES) occurs because the engineer improperly selected a hardware/NetPro station download (PLC -> Download) on a client PC Station that does not possess a Station Configuration Editor. Standard OS Clients do not require SIMATIC NET or Station Manager. To resolve this: (1) Do NOT attempt to download hardware configuration to an OS Client; (2) In SIMATIC Manager, right-click the OS Client WinCC project object (not the parent PC Station), select Object Properties -> Target OS and Standby OS Computer, and browse to the network share path (\ClientPC\WinCC_Projects); and (3) Right-click the OS Client object and select Target System -> Download to transfer the WinCC project files via Windows networking.

Executive Summary

In SIMATIC PCS 7 systems, distributed visualization is achieved through OS Clients communicating over the terminal bus to redundant OS Servers. When deploying a new OS Client workstation, engineers follow the PCS 7 setup wizard, selecting 'OS Client', 'Batch Client', and 'SIMATIC Logon'. Consequently, the installer intentionally omits SIMATIC NET PC Software because client nodes do not host direct plant bus controllers. However, upon attempting to commission the client by selecting the PC Station in SIMATIC Manager and initiating a download, the operation abruptly aborts with the diagnostic error: 'Unable to establish connection to module Stationmanager (Index 125)'. Understanding the fundamental architectural division between hardware station downloads and WinCC project file transfers eliminates this commissioning failure.

Architecture and Fundamental Mechanics

The failure mechanism and download architecture of PCS 7 workstations are governed by distinct deployment channels:

The Function of Station Manager (Index 125): On full PC Stations—such as Engineering Stations (ES) and OS Servers—the operating system runs the SIMATIC NET Station Configuration Editor (SCE). The SCE acts as a virtual backplane where Index 125 represents the 'Station Manager' firmware module. The Station Manager receives .xdb database downloads from NetPro, binding physical communication cards (CP1623, IE General) to WinCC applications.
Why OS Clients Lack Station Manager: An OS Client does not participate in S7 plant bus routing. It connects purely across the terminal bus to OS Servers using standard Windows TCP/IP sockets and Simatic Shell. Because an OS Client requires no local S7 connection tables or physical CP card bindings, Siemens intentionally excludes the Station Configuration Editor and Station Manager (Index 125) from the OS Client installation package to minimize footprint and eliminate overhead.
The Root Cause of Error 125: If an engineer right-clicks the top-level SIMATIC PC Station node representing the OS Client in SIMATIC Manager and selects PLC -> Download, or executes Compile and Download Objects with the 'Configuration' box checked, STEP 7 attempts an S7ONLINE hardware download targeting Station Manager at Index 125. Because the service does not exist on the client, the download fails immediately.
The Network Share Transfer Pipeline: An OS Client requires only its WinCC runtime database, graphic pictures, and assigned server data packages. The ES transfers these files entirely through standard Windows Server Message Block (SMB) file sharing, requiring only network reachability and SIMATIC HMI group permissions.

Step-by-Step Implementation Procedure

Commission and download to a new WinCC OS Client using the following standardized procedure:

Prepare the Network Share on the OS Client PC:
- Log into the physical OS Client workstation.
- Create a directory on a non-system drive: e.g., D:\WinCC_Projects (or C:\WinCC_Projects).
- Right-click the folder -> select Properties -> Sharing -> Advanced Sharing.
- Check Share this folder and set the Share Name to WinCC_Projects.
- Click Permissions -> ensure Everyone or the SIMATIC HMI user group is granted Full Control.
- Under the Security tab, verify that SIMATIC HMI has Full Control NTFS permissions.
Configure Simatic Shell on Both Stations:
- On both the ES and the OS Client, open Windows File Explorer -> right-click Simatic Shell -> select Settings.
- Ensure that the primary terminal bus network adapter is selected.
- Verify that both stations are visible in Simatic Shell.
Configure Client Target Path in SIMATIC Manager:
- On the Engineering Station, open SIMATIC Manager Component View.
- Expand the OS Client PC Station -> locate the child object: the WinCC Client project (blue computer icon).
- Right-click the WinCC Client project object -> select Object Properties.
- Open the Target OS and Standby OS Computer tab.
- Click Browse -> navigate over the network to the shared directory: \\ClientPC\WinCC_Projects.
- Select the target .mcp file path and click OK.
Execute WinCC OS Download (Excluding Hardware):
- Right-click the WinCC Client project object (do NOT click the parent PC Station).
- Select Target System -> Download.
- In the download confirmation dialog, verify that only the OS Project is selected.
- Click OK. The ES transfers the client project files directly across the network share without error.

Verification

Verify successful OS Client deployment and runtime startup:

File Transfer Inspection: On the OS Client PC, open D:\WinCC_Projects. Confirm that the WinCC project file (.mcp), subdirectories (GraCS, ServerData), and server packages (*.pck) were transferred successfully.
Runtime Launch: In SIMATIC Manager on the ES, right-click the OS Client object and select Target System -> Activate Runtime (or launch WinCC Runtime directly on the client PC).
Operational Connection Check: Confirm that the client loads process graphics, connects seamlessly to redundant OS Servers, and displays active alarms and process variables without authorization or communication errors.

Limitations and Operational Precautions

Never attempt to manually install SIMATIC NET PC Software or the Station Configuration Editor on an OS Client simply to eliminate Error 125; doing so misconfigures terminal bus routing, consumes unnecessary software resources, and violates standard PCS 7 client architecture guidelines. OS Clients must always remain lightweight, share-based deployment nodes.

Engineer FAQ

Why did STEP 7 report that Station Manager Index 125 is missing?

The ES attempted a hardware configuration / NetPro download to a PC Station that lacks the Station Configuration Editor. OS Clients do not use Station Manager; download only the WinCC OS project via network share.

Do I need to configure a network card (IE General) in HW Config for an OS Client?

In standard PCS 7, an OS Client's PC Station in HW Config contains only a WinCC Client application at Index 1. Adding an IE General card is unnecessary unless explicitly configuring multi-homed routing.

Do I need to create connections in NetPro between OS Servers and OS Clients?

No. NetPro configures S7 plant bus connections to AS controllers. OS Clients communicate with OS Servers over the terminal bus via Simatic Shell, requiring zero NetPro connections.

What user permissions are required for the client network share?

The Windows user account logged into the ES must have administrative rights on the client, and the local SIMATIC HMI group on the client must have Full Control share and NTFS permissions.