Troubleshoot a BCS Command Error After a SIMATIC BATCH Structure Change
After a SIMATIC BATCH online structure change fails with Error executing the command on the server (BCS), distinguish the normal editing lock from the unresolved server-command failure. Siemens documents that structure editing suspends BatchCC monitoring and control and prevents process-cell updating. Review the permitted changes and collect batch diagnostics before recovery; the error text does not establish that correcting a setpoint, restarting servers or forcing an abort will safely resolve the stuck session.
Table of Contents
- Understand the Locked Editing State
- Check the Change Against the Documented Requirements
- Normal Documented Completion of Structure Change
- Collect Evidence Before Recovery
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Understand the Locked Editing State
The observed sequence is a running batch being held, an online structure change being applied, and BatchCC reporting Error executing the command on the server (BCS). Resume, abort and stop commands are then unavailable. This message alone does not identify an invalid setpoint, a server failure or database corruption.
For SIMATIC BATCH V9.0 SP1, Siemens explains that starting online structure change places the batch in Suspend mode: BatchCC no longer monitors or controls it, and the visualization does not read current process values. Other users cannot edit the affected batch. A process-cell update is also excluded while online structure change is active. These documented restrictions explain why unavailable commands do not, by themselves, establish the cause of a failed apply operation. BATCH manual, chapter 9.8.8
Check the Change Against the Documented Requirements
Use a preserved copy and the exact installed version's documentation to review:
- Whether the batch uses PC-based execution. The V9.0 SP1 workflow excludes recipes with recipe unit procedures executed in the AS.
- Whether the recipe or formula is released for testing and the required structure-change permission is present.
- Whether the proposed deletion includes an active recipe step. The documented restrictions do not permit deleting active steps.
- Whether the edit attempts to change existing parameter data types, unit candidates or process tags, which are excluded from the documented structure-change scope.
Inspect parameter setpoints, equipment/recipe limits and the relevant material assignments for the actual modified elements. Invalid data is a possible validation finding, not a proven explanation for this exact BCS error. Do not assume that every empty material field is invalid without the recipe's applicable configuration rules.
Normal Documented Completion of Structure Change
For an otherwise functioning V9.0 SP1 session, chapter 9.8.8.8 documents this sequence:
- Open the control recipe and make its window active.
- Start editing with Control > Structure change > Start, subject to the documented permissions, recipe state and execution-mode prerequisites.
- Make the permitted changes.
- Finish through Control > Structure change > Accept changes, or reject the pending edits through the corresponding rejection command.
- After editing ends normally, resume a previously paused batch as appropriate to its state.
This describes normal completion, not a recovery command for a session whose BCS apply request has failed. Do not repeat Start or force a state transition when the normal completion commands are unavailable.
Collect Evidence Before Recovery
Record the exact error text, installed PCS 7/BATCH builds, affected batch state, edited recipe elements and whether the structure-change session still appears active. Inspect Extended batch information for related messages and the batch properties' Change Log for recorded structure changes.
Observe the physical process through the site's authorized operating channels: the suspended BatchCC picture is not a live indication of all process behavior. Preserve diagnostic information before a manufacturer-supported recovery. The evidence available here does not establish a safe restart, forced abort, database edit or redundancy switchover that clears this particular failed session.
Verification
Following an applicable recovery, verify that the structure-change session has ended, BatchCC resumes current visualization, permitted batch commands return and the control recipe contains the intended accepted structure. Confirm actual equipment and batch states before resuming.
Check the change log and relevant batch messages. An error dialog disappearing or a client reconnecting does not prove that the recipe changes were committed or that the process is safe to continue.
Limitations and Operational Precautions
The installation's exact version and the detailed BCS failure cause were not supplied. The cited manual explains the normal workflow and restrictions; it does not establish recovery for this exact error.
Do not restart both redundant servers, force database changes or update the process cell as an unverified workaround. Maintain the process in an authorized operating state, preserve the project and batch data, and obtain a recovery instruction applicable to the actual BATCH version and failed transaction state.
Engineer FAQ
Does a missing resume command necessarily mean the batch database is corrupt?
No. Online structure change itself locks editing and suspends BatchCC control; a failed completion still requires separate diagnosis.
Is an out-of-range setpoint a confirmed root cause?
No. It is a useful validation check, but the available evidence does not link it conclusively to this BCS error.
Technical References
- Siemens — SIMATIC BATCH V9.0 SP1 Operating Manual, November 2017, A5E38210537-AB — chapter 9.8.8, pp. 493–498, restrictions, Suspend mode and normal completion; chapter 9.1.4.10, p. 293, Extended batch information.