Diagnosing and Resolving Station Configuration Editor 5% Boot Hangs in PCS 7

A boot freeze at 5% in the SIMATIC Station Configuration Editor on a PCS 7 OS Server typically indicates corrupted station configuration component caches (s7scompx.xml or pnp cache), hung lingering server background processes (s7otbxsx.exe), or network adapter binding deadlocks after an improper system shutdown. Resolve the freeze by booting Windows in Safe Mode or stopping the SIMATIC Station Manager Service, clearing the corrupted cache files in %ProgramData%\Siemens\SIMATIC.S7S\ or executing s7cfg.exe /clear, rebuilding the virtual rack slots in the Station Configurator, and re-importing the station configuration file (*.xdb) generated from HW Config.

Anatomy of the Station Configuration Editor 5% Initialization Deadlock

The SIMATIC Station Configuration Editor (Station Configurator) manages the local PC Station's virtual backplane. During operating system startup, the Station Manager service (s7snpsx.exe / s7otbxsx.exe) executes an initialization sequence represented by the startup progress bar:

0% to 5%: The service parses the local component database (s7scompx.xml), queries installed communication processors (e.g. CP 1623, CP 1613, or IE General), and attempts to bind virtual rack slots to physical hardware drivers.
Deadlock Condition at 5%: If the XML component database is truncated due to a power outage, if hardware MAC addresses have shifted following a RAID card replacement, or if lingering WinCC processes (CCProjectMgr.exe, s7oiehsx.exe) from a crashed session hold mutex locks on the communication subsystem, the driver handshake hangs indefinitely at 5%.

Impact of Power Loss, RAID Restorations, and Ghost Cloning

Industrial servers with redundant RAID arrays that experience sudden hardware crashes frequently suffer this failure upon reboot. Common triggers include:

Improper Image Restoration: Restoring an Acronis or Ghost disk image from partner servers without sanitizing the local computer name and network card bindings leaves the Station Manager attempting to bind to hardware UUIDs that do not exist.
Orphaned Server Processes: Task Manager reveals multiple instances of communication servers (s7otbxsx, CCClient, s7snpsx) spawned concurrently, competing for port locks.
Network Card Binding Order: If Windows alters the network adapter priority order, the Station Configurator may attempt to initialize the Terminal Bus on a Plant Bus driver, causing timeout loops.

Step-by-Step Restoration and Cache Purge Procedure

Execute this recovery procedure to clear the deadlock and restore normal station startup:

Stop Hung SIMATIC Services:
- Boot Windows into Safe Mode or open Windows Services (services.msc).
- Set the following services to Manual temporarily: SIMATIC IEPG Help Service, SIMATIC Station Manager Service.
- Terminate lingering s7otbxsx.exe and s7snpsx.exe tasks in Task Manager.
Clear Corrupted Station Configurator Database:
- Navigate to the directory: C:\ProgramData\Siemens\SIMATIC.S7S\ (or C:\Program Files (x86)\Siemens\Common\s7snpx\ in older PCS 7 versions).
- Delete or rename the cache file s7scompx.xml and temporary .pnp files.
- Open an administrative command prompt and run: s7cfg.exe /clear.
Re-initialize Virtual Rack Slots:
- Restart the server into normal Windows mode.
- Start the Station Configuration Editor manually.
- Verify that the station name matches the exact computer name configured in SIMATIC Manager HW Config.
- Re-add the required components into their designated slots:
- Slot 1: WinCC Application
- Slot 2: CP 1623 (or IE General / CP 1613)
Re-import Station Configuration (*.xdb):
- In SIMATIC Manager on the ES, compile the PC station in HW Config to generate an updated .xdb file.
- In Station Configuration Editor on the server, click Import Station..., select the .xdb file, and confirm.

Station Configuration Editor Diagnostic Phase Matrix

The following table correlates Station Configuration Editor startup percentages with specific subsystems and failure points:

Initialization ProgressUnderlying OperationResponsible ProcessPrimary Failure CauseCorrective Action0% to 5%Component DB & Hardware Scans7snpsx.exe / s7otbxsx.exeCorrupted s7scompx.xml, duplicate tasks, deadlocksClear cache via s7cfg /clear, kill orphan tasks10% to 25%Network Driver Bindings7epatsx.sys / cp16xx.sysNIC MAC mismatch, CP firmware crash, IRQ conflictReinstall CP driver, verify MAC in Station Configurator50% to 75%WinCC Application HandshakeCCProjectMgr.exeWinCC database lock, SQL service not startedRestart SQL Server (WinCC) instance, check DCOM80% to 100%S7 Connection Routing Tabless7oiehsx.exeMismatched NetPro connection tableDownload NetPro connections from ES

[!NOTE]
Commercial Accuracy Notice: The SIMATIC Station Configuration Editor is a system component of the SIMATIC NET PC Software > included with SIMATIC PCS 7. Hardware communication processors such as CP 1623 (6GK1162-3AA00) or CP 1613 (6GK1161-3AA01) > require valid firmware and SIMATIC NET licenses (6GK1704-1CW14-0AA0), but repairing local software component caches > consumes no licenses.

Verification

Confirm that the Station Configuration Editor initializes cleanly:

Clean Boot Progress: Reboot the server. Confirm that the Station Configuration Editor progress bar moves smoothly from 0% to 100% within 15 to 30 seconds without pausing at 5%.
Station Status Indicator: Open the Station Configuration Editor interface. Verify that the station state displays a green checkmark (Status: OK) and that all configured slots indicate RUN.
Network Connection Verification: In SIMATIC Manager on the ES, open NetPro, highlight the PC station, and execute PLC -> Diagnostics/Setting -> Operating Mode. Confirm successful online communication.

Limitations and Operational Precautions

Observe these precautions when maintaining PC stations:

Never Power Down During Startup: Abruptly resetting an industrial PC while the Station Configurator or SQL Server is booting will immediately corrupt local XML caches.
Match Station Name Exactly: The station name in the Station Configuration Editor must be 100% case-identical to the Windows computer name and the PC station name in SIMATIC Manager.
Antivirus Exclusions: Ensure that Siemens-recommended antivirus exclusions are configured for %ProgramData%\Siemens\ to prevent antivirus scanners from locking s7scompx.xml during system boot.

Engineer FAQ

Why does Station Configuration Editor get stuck at 5%?

At 5%, the system initializes the component database and scans physical communication processors. A corrupted cache file, MAC address mismatch, or lingering background processes lock the driver interface.

How do I clear the station configuration without reinstalling PCS 7?

Open an administrative command prompt, navigate to the Siemens bin directory, and run s7cfg.exe /clear. Alternatively, delete s7scompx.xml in %ProgramData%\Siemens\SIMATIC.S7S\.

Can a failed RAID array cause this error?

Yes. Sudden controller crashes or restoring RAID hard drives can result in partially written database files on disk, causing the Station Manager service to crash upon reading them.

Why are there so many server processes running in Task Manager?

When the Station Manager deadlocks, spawned child communication services (s7otbxsx.exe, CCClient.exe) fail to close properly and accumulate on successive restart attempts.