Troubleshooting SIMATIC BATCH Launch Coordinator and Publisher Service Startup Failures

In SIMATIC BATCH client-server architectures, Launch Coordinator startup failures and publisher service errors occurring after downloading a project from the Engineering Station (ES)—leaving only a .dcf file inside the server's sb8 folder—typically stem from software update mismatches between the ES and BATCH Server or improper deletion of the sb8 runtime directory while services were active. Resolving this issue requires synchronizing component hotfixes across all stations, ensuring Windows user accounts belong to the SIMATIC BATCH and SIMATIC HMI groups, and resetting the BATCH database using the SIMATIC BATCH Launch Coordinator configuration wizard.

SIMATIC BATCH Client-Server Initialization and the sb8 Database

SIMATIC BATCH manages recipe execution and batch records through a client-server architecture centered on the Launch Coordinator (sblaunch.exe) and the Batch Publisher Service (sbpublisher.exe). When an engineer executes Download BATCH from SIMATIC Manager on the ES:
- The system compiles technological recipe phases (IEPH / IEPX) and transfers serialized project data across the network.
- The target BATCH Server receives these files into the project directory sbdata\sb8 (or sbdata\sb6 in legacy systems).
- The Launch Coordinator attaches the BATCH SQL Server database, validates the project configuration file (.dcf), starts the publisher service, and signals readiness to connected Batch Control Center (BCC) clients.

Root Cause Analysis: Component Hotfix Mismatches and sb8 Corruption

Two primary mechanisms trigger the publisher service crash and empty sb8 folder:

Software Update Asymmetry Between ES and Server:
- If the Engineering Station has installed a cumulative update (e.g. SIMATIC BATCH V8.1 SP1 Update 2) while the target BATCH Server remains on base V8.1 SP1, the serialized data structures compiled by the ES cannot be read by the server daemons.
- The publisher service encounters an unhandled deserialization exception on startup and crashes, leaving only the raw communication .dcf file in sb8.
Deleting the sb8 Directory While Services are Active:
- Manually deleting the sb8 folder while background SQL instances or Launch Coordinator threads are registered corrupts Microsoft SQL Server master database attachments, preventing the server from rebuilding the required project database tables.

Step-by-Step Recovery and Service Restoration Workflow

Follow this validated sequence to recover the BATCH Server:

Verify Software Update Parity: In SIMATIC Manager on both ES and BATCH Server, select Help > About > Installed Software; confirm that SIMATIC BATCH versions, Service Packs, and Updates match identically across all machines.
Stop Background Services: Open Windows Services (services.msc) and stop:
- SIMATIC BATCH Launch Coordinator
- SIMATIC BATCH Publisher
- SQL Server (BATCH)
Clean Orphaned Database Attachments:
- Open SQL Server Management Studio and connect to the BATCH SQL instance.
- If old project databases are stuck in 'Recovery Pending' or 'Suspect', detach or drop the orphaned handles.
Re-initialize BATCH Server Settings:
- In the Windows Start menu, run SIMATIC BATCH > Launch Coordinator Settings.
- Re-select the correct local network adapter bound to the Terminal Bus.
- Verify that the local Windows user belongs to local user groups SIMATIC BATCH, SIMATIC HMI, and Administrators.
Re-Download Entire Project from ES:
- On the ES in SIMATIC Manager, open the BATCH configuration dialog.
- Execute Compile Entire Project followed by Download Entire Project to the BATCH Server.
- Start the Launch Coordinator; verify it advances to state 'Ready'.

SIMATIC BATCH Service Diagnostic and Resolution Matrix

The following table details diagnostic checks and corrective actions for SIMATIC BATCH startup errors:

Service / ComponentFailure SymptomProbable CauseCorrective Engineering ActionLaunch CoordinatorHangs in 'Intermediate State' or fails to startNetwork adapter binding or SQL attach faultCheck Terminal Bus NIC in Launch Coordinator Settings; verify SQL serviceBatch Publisher ServiceFails to start; Windows Event Viewer errorBinary schema mismatch from ES downloadMatch BATCH update/hotfix level on ES and Serversb8 Project FolderContains only .dcf file; no databaseDownload aborted due to service lockStop all BATCH services before executing fresh download from ESBatch Control Center (BCC)'Cannot connect to Batch Server'Terminal Bus firewall blocking portsEnsure TCP ports 5000–5010 and SQL ports are open on firewallWindows User RightsAccess denied during service launchUser missing from SIMATIC BATCH groupAdd service account to local Windows SIMATIC BATCH group

Note: In redundant BATCH configurations, both primary and standby servers must have identical software update packages installed.

Verification

Verify SIMATIC BATCH Server recovery:
1. Open the Launch Coordinator window in the Windows notification tray; verify the status icon shows green with status 'Ready' or 'Active'.
2. In Windows Explorer on the BATCH Server, verify that the sbdata\sb8 folder contains full database files (*.mdf, *.ldf) alongside the .dcf file.
3. Open Batch Control Center (BCC) on an operator client; verify that the project connects without timeout dialogs.
4. Open the Recipe Editor; verify that all master recipes and formula categories load cleanly from the server database.

Limitations and Operational Precautions

Essential operational rules for SIMATIC BATCH systems:
- Never manually delete or edit files inside the sbdata or sb8 directories while SIMATIC BATCH services or WinCC Runtime are active.
- Always perform a full project backup using SIMATIC BATCH Backup/Restore utilities before applying any software service packs.
- In virtualized environments (VMware), do not restore snapshots of an active BATCH server without restoring the partner ES and OS servers simultaneously, as recipe revision timestamps will desynchronize.

Engineer FAQ

What does the .dcf file do in the sb8 directory?

The .dcf file (Database Configuration File) stores connection strings, network station names, and database pointers required by BATCH services to locate the local SQL Server instance.

Why did the project work in VMware but fail on the physical server?

The VMware virtual machine possessed an identical, matched set of BATCH hotfixes, whereas the physical server had mismatched updates or corrupted SQL service permissions.

Can I run SIMATIC BATCH on an OS Client station?

Batch Control Center (BCC) and Recipe Editor can run on OS Clients, but the central BATCH Server services must run on a dedicated server or OS Single Station.