C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

Resolving SIMATIC BATCH Recipe Editor Lockout Error 'Object Being Used by Another Application'

Resolving SIMATIC BATCH Recipe Editor Lockout Error 'Object Being Used by Another Application'

In SIMATIC BATCH, attempting to save a master recipe or library operation fails with an error indicating that the BATCH object is being used by another application when concurrent client sessions or dangling database mutex locks maintain exclusive editing claims. When an engineer or client workstation terminates abnormally without cleanly closing the Recipe Editor, the central BATCH database retains the user lock. Resolving this lockout requires verifying active user sessions in Batch Control Center (BatchCC), closing orphaned client instances, restarting BATCH runtime services if mutex locks persist, or saving the recipe under an alternative identifier.

Table of Contents

Concurrency Locking and Object Ownership in SIMATIC BATCH

SIMATIC BATCH provides comprehensive ISA-88 recipe management and batch execution across distributed PCS 7 systems. To guarantee FDA 21 CFR Part 11 electronic record integrity, SIMATIC BATCH enforces strict concurrency control:

  • Object-Level Exclusive Checkout: When an engineer opens a Master Recipe, Library Operation (ROP), or Unit Procedure (RUP) in the Recipe Editor, the BATCH client requests an exclusive write token from the active BATCH Server (bfserverx.exe).
  • Database State Locking: The BATCH server marks the object ID as "Checked Out" in the central SQL database (sbdata) and records the Windows username, client machine name, and process ID.
  • Write Collision Protection: Any concurrent attempt by another client—or a secondary window on the same client—to save, validate, or release the recipe triggers the safety abort:
    SIMATIC BATCH: Recipe Editor Master recipe not created. Error: BATCH object being used and written to or read by another BATCH application.

Root Causes of Persistent Recipe Editor Lockouts

The error frequently manifests even when only one engineer believes they are editing the system. Key root causes include:

  1. Abnormal Client Termination: If the BATCH Recipe Editor crashes, loses network connectivity to the BATCH server, or is forcefully terminated in Windows Task Manager, the checkout lock remains active in the server database.
  2. Concurrent BatchCC and Recipe Editor Sessions: If a recipe is open for structural modification in the Recipe Editor while simultaneously open in Batch Control Center (BatchCC) for recipe release or validation, the BATCH server blocks concurrent writes.
  3. Ghost Sessions on Redundant BATCH Servers: In redundant BATCH server configurations, if server synchronization experiences latency across the Terminal Bus, lock release tokens dispatched by a client may not register simultaneously on the standby node.
  4. Duplicate Object Naming: Attempting to save a new library element using a name that collides with a soft-deleted or uncompiled recipe entity.

Step-by-Step Resolution and Lock Release Procedure

Follow this structured procedure to release stuck BATCH object locks:

Step 1: Check Active Sessions in Batch Control Center (BatchCC)

  1. Open BatchCC as administrator.
  2. In the navigation tree, locate the affected library or recipe category.
  3. Inspect the object icon: A padlock symbol indicates that the object is locked by an active session.
  4. Check the status bar or object properties to identify the locking username and workstation computer name.
  5. If the session belongs to a colleague, have them save and close the Recipe Editor cleanly.

Step 2: Clear Local Client Ghost Processes

  1. On the engineering workstation, close all SIMATIC BATCH applications (Recipe Editor, BatchCC).
  2. Open Windows Task Manager (Ctrl + Shift + Esc).
  3. Under Background Processes, check for orphaned BATCH executables:
    * bfrecx.exe (Recipe Editor)
    * bfccx.exe (BatchCC)
    * bfclientx.exe
  4. If found, select the process and click End Task.
  5. Reopen BatchCC and test if the object has been released.

Step 3: Temporary Save-As Workaround

  1. If urgent recipe changes must be preserved and the original object remains locked:
    * In the Recipe Editor, select File -> Save As....
    * Assign a new temporary name or revision suffix (e.g., ROP_Mixer01_Temp).
    * Complete your engineering work and save the new object.
    * Once server locks are cleared, delete the original locked object or copy the logic back.

Managing BATCH Server Processes and Database Attachments

If the lock persists across all clients, the lock token must be cleared on the BATCH Server:

  1. Verify Plant State: Ensure no critical batches are currently executing on the plant floor before altering server states.
  2. Restart BATCH Applications via BatchCC:
    * On the BATCH Server, open BatchCC.
    * Select Tools -> Terminate BATCH Applications.
    * Wait for all background daemons (bfserverx.exe, bfdatax.exe, bfcdbx.exe) to shut down cleanly.
    * Select Tools -> Start BATCH Applications.
  3. Database Lock Purge:
    * During server startup, the BATCH database engine validates object checkout tokens against active network sessions. Orphaned client locks with dead TCP sockets are automatically purged from the sbdata database tables.
+-------------------------------------------------------------------+
|               SIMATIC BATCH Lockout Resolution Flow               |
+-------------------------------------------------------------------+
|  Recipe Editor reports "Object being used by another application" |
|                             |                                     |
|                             v                                     |
|  1. Terminate orphaned bfrecx.exe / bfccx.exe on Client PCs       |
|                             |                                     |
|                             v                                     |
|  2. If editing urgent: Use "File -> Save As..." with new name     |
|                             |                                     |
|                             v                                     |
|  3. If persistent: Terminate & Restart BATCH Applications in      |
|     BatchCC on BATCH Server (Clears dead session mutexes)         |
|                             |                                     |
|                             v                                     |
|  4. Open Recipe Editor -> Verify clean lock release               |
+-------------------------------------------------------------------+

Verification

Confirm the resolution of BATCH concurrency errors:

  1. Recipe Editor Modification Check:
    * Open the target Master Recipe or Library Operation in the Recipe Editor.
    * Modify a parameter or phase setpoint.
    * Click Save. Confirm that the save completes instantaneously without error dialogs.
  2. Recipe Validation and Release:
    * In the Recipe Editor, select Recipe -> Validate. Confirm zero structural errors.
    * Select Recipe -> Release for testing or Release for production.
    * Verify that the recipe status updates in BatchCC with a green checkmark.

Limitations and Operational Precautions

  • Running Batch Caution: Never terminate BATCH server applications (bfserverx.exe) while active chemical batches are executing steps in automation stations. Doing so interrupts electronic batch recording and can pause phase progression.
  • Avoid Direct SQL Table Modification: Never attempt to manually edit or delete records in the Microsoft SQL Server database sbdata using SQL Management Studio. BATCH databases utilize complex relational triggers; manual edits permanently corrupt project data.
  • Version Synchronization: Ensure that all Engineering Stations and BATCH clients run the identical SIMATIC BATCH version, service pack, and hotfix level.

Engineer FAQ

  • What causes the SIMATIC BATCH error 'BATCH object being used by another application'?
    The central BATCH server maintains an exclusive checkout lock on the recipe or library element, typically caused by an orphaned client process or another open window.
  • How can I save my recipe changes if the original object is locked?
    Use 'File -> Save As...' in the Recipe Editor to save the operation or recipe under a new name, preventing work loss while locks are investigated.
  • What executable corresponds to the SIMATIC BATCH Recipe Editor?
    The Recipe Editor background process is bfrecx.exe.
  • Does restarting the BATCH client PC release database locks?
    Restarting the client terminates local handles, but if the server holds the checkout flag, the BATCH server applications may also need to be restarted.
  • How do I safely restart BATCH server daemons?
    In BatchCC on the BATCH Server, select 'Tools -> Terminate BATCH Applications', wait for completion, then select 'Tools -> Start BATCH Applications'.
  • Can two engineers edit different recipes in SIMATIC BATCH simultaneously?
    Yes, multiple engineers can edit separate recipes concurrently; exclusive locking applies strictly to the specific recipe or library element being edited.
  • Does SIMATIC BATCH require an engineering license to edit recipes?
    Yes, creating and editing recipes in the Recipe Editor requires an active SIMATIC BATCH Recipes engineering license managed via ALM.
  • What is the difference between a Library Operation (ROP) and a Recipe Operation in a master recipe?
    A Library Operation is a reusable class-based template, while a Recipe Operation in a master recipe is an instantiated, parameterized sequence.
  • Where are SIMATIC BATCH event and error logs stored?
    Logs are located in C:\Program Files (x86)\Siemens\BATCH\Log\ or viewed via the BATCH Control Center diagnostic views.
  • Does releasing a recipe require compiling the OS?
    No, recipe creation, modification, and release occur entirely at the SIMATIC BATCH management level and do not require OS or AS compilation.

Technical References

  • Siemens Industry Online Support (SIOS) Portal: SIMATIC BATCH Operating Manual (Entry ID: 109747908).
  • ISA-88.01: Batch Control Part 1 - Models and Terminology.
  • SIMATIC PCS 7 BATCH Engineering Guide, Siemens AG.

Related Articles

Related Tags

PCS 7, SIMATIC BATCH, Recipe Editor, BatchCC, Concurrency Lock, ISA-88, Troubleshooting, Database Lock

20 respuestas