Resolving SIMATIC BATCH Slow Performance, UI Freezes, and Authorization Warnings

In SIMATIC BATCH (V8.2 through V9.1), severe client slowdowns, right-click menu freezes lasting 15 minutes, and warnings stating 'For this functionality, you require the authorization BATCH Server' occur when the Automation License Manager (ALM) on the BATCH Server PC is not configured to accept remote client queries. To resolve this, open Automation License Manager on the BATCH Server PC, navigate to 'File > Settings > Connection', check 'Allow remote connections', select 'immediate restart of service', and verify that the SIMATIC BATCH Server V9.x license is installed and active.

Executive Summary

Following system upgrades or virtual machine migrations in SIMATIC BATCH (such as migrating from PCS 7 V8.0 to V9.0 SP3), automation engineers frequently encounter debilitating performance bottlenecks on Batch Control Center (BatchCC) clients. Upon launching BatchCC, the application takes several minutes to render, the user interface remains unresponsive for up to 15 minutes, and right-click contextual menus fail to display or show only a single 'Find' option.

Periodically, the client halts with the modal dialog: For this functionality, you require the authorization 'BATCH Server'. While engineers typically suspect network bandwidth congestion, domain permission errors, or SQL database corruption, the root cause is licensing communication blockage: the Automation License Manager (ALM) service on the Batch Server is refusing remote RPC connections from client workstations. This guide explains how BatchCC clients query the central server for licenses and provides the immediate resolution procedure in ALM.

Architecture and Fundamental Mechanics

The client-server licensing architecture of SIMATIC BATCH relies on distributed Remote Procedure Calls (RPC) managed by the Siemens Automation License Manager daemon (almsrvx.exe):

Role of the BATCH Server License: The primary operational license (SIMATIC BATCH Server) resides physically on the central BATCH Server PC. BATCH Clients (BatchCC, Recipe Editor) do not require standalone server licenses; instead, they operate as client nodes that dynamically query the BATCH Server to verify that an active, authorized server instance is governing the plant.
The Remote ALM Query Mechanism: When an operator opens BatchCC, right-clicks an element (recipe, formula, material), or creates a new batch, the BatchCC client application initiates a background RPC call across the network to port 4410 (or dynamic DCOM ports) on the BATCH Server to validate authorization tokens.
The 'Allow Remote Connections' Setting in ALM: In default installations of Automation License Manager, the security option 'Allow remote connections' may be disabled or uninitialized. When disabled:
- The ALM daemon on the server rejects or drops incoming remote authorization queries from client PCs.
- The client application pauses execution while waiting for Windows socket connection timeouts (defaulting to multiple minutes per query).
- This causes the BatchCC UI thread to freeze ('Not Responding'). When repeated timeout thresholds expire, BatchCC concludes that no BATCH Server license exists on the network, displaying the warning 'For this functionality, you require the authorization BATCH Server'.
- After roughly 15 minutes, fallback cached tokens allow partial menu rendering, but clicking 'New Batch' immediately restarts the timeout cycle.

Step-by-Step Implementation Procedure

Follow these steps to enable remote license connections and eliminate BatchCC performance freezes:

Access Automation License Manager on the BATCH Server:
- Log on to the physical or virtual BATCH Server PC with local administrative privileges.
- Launch 'Automation License Manager' (ALM) from the desktop shortcut or Start menu.
Enable Remote Connections in ALM Settings:
- In the ALM main menu, select 'File > Settings...'.
- In the settings dialog window, switch to the 'Connection' tab.
- Locate the option: 'Allow remote connections'.
- Check the box adjacent to 'Allow remote connections'.
- Under 'Port', confirm the standard default communication port (4410).
- Select the radio button: 'Immediate restart of service' (or manually restart the Automation License Manager Service via services.msc).
- Click 'Apply' and 'OK'.
Verify Installed BATCH Licenses on Server:
- In ALM on the BATCH Server, expand 'License Keys' > select the drive hosting the licenses (e.g., C:).
- Confirm that the license SIMATIC BATCH Server (matching your exact PCS 7 version, e.g., Version 9.0) is present, valid, and not defective.
- Confirm that valid Process Object (PO) licenses (e.g., SIMATIC BATCH ROP PO / BATCH Unit PO) are installed.
Configure Windows Firewall on BATCH Server:
- In Windows Control Panel, open 'Windows Defender Firewall with Advanced Security'.
- Verify inbound firewall rules for Automation License Manager:
- Allow TCP port 4410 (Inbound).
- Allow executable C:\Program Files (x86)\Common Files\Siemens\Automation License Manager\almapp\almsrvx.exe.
Test BatchCC Client Responsiveness:
- Return to the BATCH Client workstation.
- Close and relaunch Batch Control Center (BatchCC).
- Verify that BatchCC opens within seconds without UI hangs.
- Right-click any recipe, material, or formula node in the project tree: confirm that full contextual menus appear instantly.
- Click 'New Batch': verify that the batch creation wizard opens immediately without authorization warnings.

Verification

In BatchCC on all client stations, confirm that navigating recipe hierarchies and expanding formula trees produces zero UI latency or 'Not Responding' window states.
Create, validate, and release a test batch: verify that no license warning dialogs interrupt the workflow.
In ALM on the BATCH Server, select the SIMATIC BATCH Server license key and select 'View > Log': confirm that client connection timestamps show successful verification handshakes without error codes.
Check the Windows Event Viewer on the Batch Client under Application logs to verify zero DCOM or ALM timeout exceptions.

Limitations and Operational Precautions

Ensuring remote ALM connectivity requires that the BATCH Server and BATCH Clients reside within the same Active Directory domain or have synchronized local user accounts with identical usernames and passwords in a Workgroup environment. Never attempt to transfer active runtime license keys over an unstable wireless connection. Validate all BATCH version upgrade paths, PO counting rules, and official licensing packages with an authorized Siemens distributor or the Siemens Industry Mall.

Engineer FAQ

Why did BatchCC freeze for 15 minutes before menus appeared?

The UI froze because BatchCC was waiting for multiple sequential network socket timeouts while attempting to query the license manager on the server over a blocked remote connection.

Does the BATCH Client PC require its own BATCH Server license?

No. The SIMATIC BATCH Server license resides exclusively on the BATCH Server PC. Clients verify authorization by querying the server remotely.

What port does Automation License Manager use for remote connections?

ALM utilizes TCP port 4410 for remote license verification and management across the network.

Can SIMATIC Logon permissions cause this issue?

While SIMATIC Logon governs user roles and menu permissions, the specific error 'For this functionality, you require the authorization BATCH Server' is strictly an ALM software license check failure.

What happens if BATCH licenses are upgraded without upgrading the software version?

License versions must match or be backwards-compatible with the installed software. A V9.0 BATCH license will authorize V8.x or V9.0 software, but a V8.0 license cannot authorize V9.0 software.