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

Why SIMATIC BATCH Fails with 'No Connection' Error During Recipe Release

Why SIMATIC BATCH Fails with 'No Connection' Error During Recipe Release

The error 'Could not release batch: No connection' in SIMATIC BATCH Control Center (BatchCC) occurs when the client station is unable to establish an authenticated, persistent communication channel to the central BATCH Server database services (BFW.exe, BServer.exe) during the release transaction. While recipe browsing relies on cached data, releasing a recipe executes synchronous two-phase commits across TCP Ports 5050/5051 and Windows DCOM. In mixed PC architectures, this fault is frequently triggered by deploying non-industrial consumer operating systems (such as Windows 10 Pro) that lack required Long-Term Servicing Channel (LTSC) industrial networking components, unconfigured firewall ports, or missing client account membership in the server's SIMATIC BATCH Windows user group. To resolve this error, verify operating system compatibility, configure bidirectional firewall exceptions, and synchronize user credentials.

Table of Contents

The Recipe Release Transaction in SIMATIC BATCH

In SIMATIC BATCH, navigating recipes and configuring parameters in BatchCC operates differently than releasing a batch into active production:
* Passive Browsing: When opening BatchCC, the application queries local cached descriptors and reads static recipe tables from the server share (sbdata).
* The Release Transaction: Clicking Release Batch initiates a critical transaction:
1. BatchCC contacts the Batch Server Framework (BFW.exe) via TCP Port 5050.
2. The server queries the Automation Systems (AS) via WinCC to verify that all required equipment units (phases, vessels) are online, idle, and unallocated.
3. The server locks the recipe, generates a unique batch identification number, and writes security audit records.
* The 'No Connection' Fault: If any communication socket between the client, the BATCH server, and the WinCC server drops or experiences authentication latency during this handshake, the release transaction aborts immediately with:
Could not release batch. No connection.

Operating System Incompatibilities: Windows 10 Pro vs. Enterprise LTSC

A frequent root cause in plants deploying commercial off-the-shelf PCs alongside industrial IPCs is operating system selection:
* The Consumer OS Trap: Commercial desktop PCs frequently ship with Windows 10 Pro or Windows 11 Pro.
* Why Windows 10 Pro Fails in PCS 7:
- Siemens explicitly does not release or support PCS 7 or SIMATIC BATCH on Windows 10 Pro.
- Windows 10 Pro enforces background consumer telemetry updates, aggressive DCOM authentication throttling, and dynamic network socket power-saving policies.
- Windows 10 Pro limits inbound and outbound concurrent networking sessions, causing transactional RPC timeouts during batch release.
* The Industrial Baseline: PCS 7 and SIMATIC BATCH require Windows 10 Enterprise LTSC (Long-Term Servicing Channel) (Build 2016 or 2019) or Windows Server 2016/2019, which guarantee stable, unthrottled DCOM and RPC transaction pipelines.

Network Protocol and Firewall Security Requirements

Releasing recipes requires unobstructed bidirectional communication across specific ports:

Port / ProtocolDirectionComponent / ServiceRequired ActionTCP 5050 / 5051Client <-> ServerSIMATIC BATCH Core Services (BFW.exe, BServer.exe)Open inbound and outbound on all firewalls.TCP 135BidirectionalMicrosoft DCOM / RPC Endpoint MapperMandatory for COM object instantiation.TCP 1433Client -> ServerMicrosoft SQL Server (WINCC / BATCH)Open for direct archive database transactions.UDP 5227BidirectionalSimatic Shell Discovery & WatchdogAllow multicast 224.0.2.0 and broadcast.

Method: Step-by-Step Resolution and Connection Recovery

To resolve the 'No Connection' recipe release error:

Step 1: Standardize Operating System Baseline

  1. On the problem workstation, check the Windows edition by running winver.
  2. If the station runs Windows 10 Pro:
    - Back up client project archives.
    - Reimage the station with the certified Windows 10 Enterprise LTSC 2019 operating system.
    - Install the matching PCS 7 V9.1 SP2 OS Client and SIMATIC BATCH Client packages.

Step 2: Configure Local Windows User Groups

  1. On both the BATCH Server and the Client PC, open Computer Management > Local Users and Groups > Groups.
  2. Verify that the operator domain user account belongs to:
    - SIMATIC BATCH
    - SIMATIC HMI
  3. If running in a workgroup rather than an Active Directory domain, ensure identical username and password accounts exist on both the server and client.

Step 3: Configure Windows Defender Firewall Rules

  1. On the BATCH Server and Client stations, open Windows Defender Firewall with Advanced Security.
  2. Under Inbound Rules, create custom rules allowing:
    - Specific TCP Ports: 135, 1433, 5050, 5051.
    - Specific UDP Ports: 5227.
  3. Add program exceptions for:
    - C:\Program Files (x86)\Siemens\SIMATIC BATCH\BFW.exe
    - C:\Program Files (x86)\Siemens\SIMATIC BATCHcc.exe

Step 4: Verify Simatic Shell Binding and Network Adapter

  1. In Windows Explorer, right-click Simatic Shell and select Settings.
  2. Confirm the adapter selected is the physical card connected to the terminal bus.
  3. Confirm that the BATCH Server is visible in the Simatic Shell tree.

Verification

To verify that recipe release operates without connection faults:

  1. Launch BatchCC on the client workstation.
  2. Verify that the bottom status bar confirms: Connected to BATCH Server: [ServerName].
  3. Select a valid Master Recipe and click Create Control Recipe.
  4. In the recipe header, enter a batch name and target unit allocation.
  5. Click Release Batch:
    - Confirm that the batch releases within 1 to 2 seconds without displaying 'No connection' dialogs.
    - Confirm that the batch transitions to the Released state (blue indicator).
  6. In WinCC Runtime, open the Unit Faceplate: confirm that the batch name and recipe status update dynamically on the operator screen.

Limitations and Operational Precautions

  • Do Not Release Batches During Server Backup: Avoid releasing batches while automated SQL Server maintenance or Process Historian database backups are active. Disk I/O spikes can cause transactional timeouts resulting in transient release failures.
  • Unit Allocation Conflicts: If a required equipment phase or vessel is already occupied by another running batch or locked in manual mode, the release transaction will fail with an allocation conflict rather than a connection failure. Verify unit availability before release.
  • Workgroup Password Expiration: In workgroup configurations, if the Windows account password expires on either the server or client, DCOM authentication fails silently. Set workgroup service accounts to 'Password Never Expires'.

Engineer FAQ

Why does BatchCC open normally if there is a connection problem?
Opening BatchCC and viewing recipes requires only read access to shared folders and local cache. Releasing a batch executes active two-way transactional commands with BFW.exe, exposing network and DCOM blocking that passive viewing does not trigger.

Can I run SIMATIC BATCH Client inside a virtual machine (VM)?
Yes. Running BATCH clients inside VMware vSphere or Microsoft Hyper-V virtual machines running Windows 10 Enterprise LTSC is fully supported, provided virtual network adapters use static bridging to the physical terminal bus.

What is the function of the BServer.exe process?
BServer.exe is the master process database daemon responsible for managing recipe synchronization, batch event logging, and transaction rollbacks.

Technical References

  • Siemens Industry Online Support Entry ID 109742323: SIMATIC BATCH Operating Manual
  • SIMATIC BATCH Communication and Installation Manual (Document No. A5E38012658)
  • Siemens Industry Online Support Entry ID 109809264: PCS 7 and SIMATIC BATCH Network Architecture Guidelines

Related Articles

Related Tags

  • https://industrialautomation.net/search?query=simatic-batch
  • https://industrialautomation.net/search?query=batchcc
  • https://industrialautomation.net/search?query=recipe-release
  • https://industrialautomation.net/search?query=network-ports
20 respuestas