Resolving SIMATIC BATCH Launch Coordinator Startup Inhibit After SIMATIC Management Console Upgrades

When upgrading a SIMATIC BATCH Server to V9.0 SP3 via the SIMATIC Management Console (SMMC), the Batch Launch Coordinator service may become completely grayed out and inhibited from starting due to a residual setup lock in the Windows Registry. During software installation, the Management Console sets an installation active flag that prevents the Launch Coordinator from launching runtime processes during setup. If this flag is not cleared upon package completion, the trace log reports 'SIMCO Setup is activated --> LaunchCoordinator is stopped'. To resolve this: open the Windows Registry, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Siemens\ManagementConsole, remove the active setup marker, and restart the SIMATIC BATCH Launch Coordinator service.

Executive Summary

Centralized software lifecycle management using the SIMATIC Management Console (SMMC) enables automated, unattended deployment of updates and Service Packs across distributed SIMATIC PCS 7 systems. However, during upgrades of SIMATIC BATCH servers (such as migrating from BATCH V9.0 SP2 UC03 to V9.0 SP3), engineers frequently encounter an operational deadlock where the Batch Launch Coordinator application launches with all control buttons grayed out, refusing to switch into Automatic mode or start the BATCH Server project. Running the standalone DVD setup manually reproduces the identical fault. This article identifies the underlying Registry lock mechanism used by SMMC, details the exact trace log signatures, and provides a verified procedure to release the Launch Coordinator and restore BATCH Server operations.

Architecture and Fundamental Mechanics

SIMATIC Management Console Lockout Architecture, Launch Coordinator Host, and Registry State Mechanics:

Role of the SIMATIC BATCH Launch Coordinator (sblaunchcoordinatorservice32ux):
The Launch Coordinator is a critical Windows system service and tray application that orchestrates SIMATIC BATCH runtime components (Batch Control Server, Communication Server, Recipe Server, and CDV Server).
It manages state synchronization between redundant batch servers and governs transition into 'Automatic' mode when WinCC Runtime activates.
SIMATIC Management Console (SMMC / SIMCO) Installation Lockout Mechanism:
To prevent catastrophic database corruption and race conditions during automated software rollouts, SMMC writes a persistent lock entry into the Windows Registry when initiating an update package.
This flag informs all SIMATIC PCS 7 background services that an automated setup is actively modifying binaries and system components.
In response, the Launch Coordinator host (CBFLaunchCoordinatorHost) purposely shuts down its internal runtime state machine and enters an inhibited state, disabling all GUI buttons ('Start', 'Stop', 'Automatic').
The Post-Upgrade Deadlock Scenario:
If SMMC encounters a communication glitch, an unexpected server reboot, or an installation script timing anomaly during the transition between SP2 UC03 and SP3, the SMMC agent may fail to execute the final cleanup script.
The Windows Registry retains the key indicating setup is active.
Consequently, upon reboot, the Launch Coordinator reads the active setup flag, aborts initialization, and writes the following diagnostic signature to its trace log:
CBFLaunchCoordinatorHost::ConnectToRZM - SIMCO Setup is activated --> LaunchCoordinator is stopped
Re-running the manual DVD installer fails to clear the issue because the DVD installer assumes a management console deployment is still in progress.

Step-by-Step Implementation Procedure

Confirm the Fault Signature via Siemens Diagnostic Tool (SDT) or Trace Logs:
* On the failing BATCH Server, navigate to the diagnostic log directory:
C:\ProgramData\Siemens\Logs\sblaunchcoordinatorservice32ux\trace (or ...\SiemensLogs\Logs\...).
* Open the latest trace log file in a text editor.
* Search for the string: SIMCO Setup is activated --> LaunchCoordinator is stopped.
* If present, confirm that the Launch Coordinator is blocked strictly by the management console setup flag.
Access and Clear the SMMC Setup Flag in Windows Registry:
* Log into the BATCH Server with Windows Administrator credentials.
* Open the Windows Registry Editor (regedit.exe).
* Navigate to the 64-bit redirection node:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Siemens\ManagementConsole
(also check HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Siemens\SIMATIC_BATCH\LaunchCoordinator).
* Locate DWORD or string values indicating active setup (e.g. SetupActive, InstallInProgress, or SIMCO_Setup_State).
* Change the value from 1 to 0, or delete the temporary lock key as directed by Siemens Technical Support.
Restart the Launch Coordinator Service:
* Open Windows Services management console (services.msc).
* Locate SIMATIC BATCH Launch Coordinator Service.
* Right-click and select Restart.
Verify Launch Coordinator Operation in Batch Control Center:
* Open the SIMATIC BATCH Launch Coordinator application from the Windows system tray.
* Confirm that the 'Start', 'Stop', and 'Automatic' buttons are no longer grayed out.
* Switch the Launch Coordinator to Automatic mode.
* Launch WinCC Explorer; activate Runtime and verify that the BATCH Server transitions into active operation.

Verification

Inspect the SIMATIC BATCH Launch Coordinator tray icon; verify it shows a solid green status indicator.
Open the Launch Coordinator dialog; verify that the project name is visible and the status reports 'Running' or 'Ready'.
Open the trace log in ...\sblaunchcoordinatorservice32ux\trace; verify that ConnectToRZM succeeds without setup warnings.
Launch BatchCC on the operator client; confirm that control recipes can be opened, released, and executed normally.

Limitations and Operational Precautions

Editing the Windows Registry incorrectly can cause severe operating system instability; always create a backup of the Registry (File -> Export) before making modifications. Do not clear the setup flag while an actual SMMC deployment or MSI installer task is legitimately in progress, as terminating an active installation mid-stream will corrupt file binaries.

Engineer FAQ

Why are all options grayed out in the Batch Launch Coordinator after upgrade?

Because the SIMATIC Management Console set a registry flag indicating installation was active, which inhibits the Launch Coordinator from starting.

Where is the diagnostic log for the Launch Coordinator located?

In C:\ProgramData\Siemens\Logs\sblaunchcoordinatorservice32ux\trace (or within an SDT diagnostic collection under SiemensLogs).

What exact error appears in the trace log during this lockout?

CBFLaunchCoordinatorHost::ConnectToRZM - SIMCO Setup is activated --> LaunchCoordinator is stopped.

Will reinstalling SIMATIC BATCH from DVD fix this issue?

No, because the manual DVD installer does not clear the external SIMATIC Management Console setup registry key.

What service must be restarted after clearing the registry lock?

The SIMATIC BATCH Launch Coordinator Service in Windows Services (services.msc).

Technical References

20 respuestas

Resolving SIMATIC BATCH Launch Coordinator Startup Inhibit After SIMATIC Management Console Upgrades