Resolving SIMATIC BATCH Error: 'WinCC Alarm Control Cannot Be Used on This Computer'

In SIMATIC BATCH V8.2, encountering the prompt 'WinCC Alarm Control cannot be used on this computer' when launching Batch Control Center (BCC) on a combined BATCH/OS Server indicates that the embedded WinCC Alarm Control ActiveX component cannot initialize its runtime DCOM interface. This occurs when WinCC Runtime is deactivated or in an inconsistent startup phase, when the Windows user account lacks membership in the SIMATIC BATCH and SIMATIC HMI security groups, or when the WinCC Alarm Control OCX file is unregistered. To resolve this, verify that WinCC Runtime is fully active, re-register CCAxAlarmControl.ocx via an elevated command prompt, add the logged-in domain user to local SIMATIC groups, and recompile BATCH OS message links.

WinCC Alarm Control Integration Inside Batch Control Center

SIMATIC BATCH coordinates complex multi-unit recipe execution across ISA-88 process cells. To provide operators with comprehensive visibility during recipe execution, the primary client application—Batch Control Center (BCC)—embeds native WinCC visualization controls. Specifically, the lower pane of the BCC main window hosts the WinCC Alarm Control, allowing operators to view recipe transition alarms, operator prompts, and phase error messages without switching away to WinCC Runtime.

When BCC starts up, it instantiates the WinCC Alarm Control ActiveX/OCX control (CCAxAlarmControl.ocx or CCAlarmControl.ocx) and establishes a local Inter-Process Communication (IPC) link to the WinCC runtime alarm provider (CCAlarmServer.exe). If this COM/DCOM handshake fails, BCC aborts control initialization and displays the fatal prompt: 'WinCC Alarm Control cannot be used on this computer'.

Root Causes: DCOM Permissions, Runtime Startup, and OCX Registration

On a combined BATCH Server and OS Server workstation, three primary configuration defects trigger this error:

WinCC Runtime Inactive or Stalled: The WinCC Alarm Control cannot function as a standalone viewer; it requires the underlying WinCC message logging runtime (ALGRT) to be actively running in memory. If BCC is opened before WinCC Runtime has completed its startup sequence, the connection to the message provider fails.
Missing Local Group Rights: In Active Directory domain environments, the logged-in user must possess explicit permissions to query WinCC and BATCH IPC endpoints. Lacking local Windows security group memberships results in 'Access Denied' DCOM exceptions.
Damaged or Unregistered OCX: After installing operating system patches, PCS 7 updates, or third-party software, the 32-bit COM registry keys pointing to CCAxAlarmControl.ocx may become corrupted or deregistered.

Validating Windows Domain User Group Memberships

To ensure DCOM and Windows security tokens allow cross-application communication:

Open Computer Management (compmgmt.msc) on the BATCH/OS Server.
Navigate to Local Users and Groups -> Groups.
Verify that the active domain user account (or domain user group) is an explicit member of the following mandatory local groups:
- SIMATIC BATCH: Authorizes recipe execution and BCC application control.
- SIMATIC HMI: Authorizes access to WinCC SQL databases, internal tags, and OLE-DB providers.
- SIMATIC NET: Authorizes communication across the Industrial Ethernet and Terminal Bus.
If group memberships were missing, add the account and log off and log back in to generate a refreshed Windows security access token.

Manual Re-Registration of WinCC Alarm Control OCX Binaries

If group permissions are confirmed but the error persists, re-register the WinCC ActiveX controls via an elevated command prompt:

Click Start, type cmd, right-click Command Prompt, and select Run as Administrator.
Navigate to the WinCC binary installation folder:
cd /d "C:\Program Files (x86)\Siemens\WinCC\bin"
Execute the registration command for the Alarm Control:
regsvr32 CCAxAlarmControl.ocx
Also re-register the core WinCC controls:
regsvr32 CCAlarmControl.ocx
regsvr32 CCAlgVSc.ocx
Verify that Windows displays the confirmation dialog: 'DllRegisterServer in CCAxAlarmControl.ocx succeeded'.

Diagnostic Matrix: Batch Control Center Startup and Alarm Control Errors

Use the following matrix to identify and rectify BCC integration faults:

Error Symptom / PromptRoot CauseEngineering Resolution'Alarm Control cannot be used...'WinCC Runtime not active or starting upActivate WinCC Runtime fully before launching Batch Control Center'Alarm Control cannot be used...'Missing local group permissionsAdd domain user to local groups SIMATIC BATCH and SIMATIC HMI'Error 0x80040154 (Class not registered)'CCAxAlarmControl.ocx unregisteredRun regsvr32 CCAxAlarmControl.ocx in elevated Command PromptBCC opens; alarm pane remains blankFilter criteria in BCC blocks all messagesOpen BCC Options, verify message filter settings match OS classesBCC crashes with DCOM access deniedDCOM machine-wide limits too restrictiveOpen dcomcnfg, verify SIMATIC HMI has Local/Remote Launch rights

Step-by-Step Restoration and Integration Workflow

Follow this recovery sequence to restore seamless BATCH and WinCC Alarm integration:

Verify WinCC Runtime: Open WinCC Explorer. Confirm that the project is active (green indicator) and that the Alarm Logging runtime process (CCAlarmServer.exe) is running in Task Manager.
Re-register OCX Controls: Execute regsvr32 CCAxAlarmControl.ocx in an elevated administrator prompt.
Verify Security Groups: Confirm domain user presence in SIMATIC BATCH and SIMATIC HMI local groups.
Compile BATCH OS Messages: In SIMATIC Manager, select the BATCH multiproject container, right-click, and select SIMATIC BATCH -> Compile / Download. Ensure that the OS message generation option is completed without errors.
Launch Batch Control Center: Open BCC; confirm that the interface loads cleanly without warning dialogs and displays live alarms in the bottom pane.

Verification

Confirm that Batch Control Center operates cleanly with WinCC Alarm Control:

Launch Batch Control Center from the desktop or WinCC faceplate.
Verify that BCC opens immediately without displaying 'WinCC Alarm Control cannot be used on this computer'.
In the lower alarm window of BCC, verify that historical and active batch alarms appear with valid timestamps and batch names.
Trigger a test batch recipe; confirm that phase transitions log discrete events into the embedded alarm control in real time.

Limitations and Operational Precautions

Adhere to the following operational precautions:

Startup Order Precedence: Always ensure WinCC Runtime is fully started and stabilized before launching Batch Control Center on combined servers.
Never Modify System OCX Files: Do not attempt to replace WinCC OCX files with DLLs from different PCS 7 versions; version mismatches cause catastrophic runtime memory exceptions.
Domain Group Policy (GPO): Ensure corporate Active Directory GPOs do not overwrite or strip local SIMATIC BATCH user group assignments during periodic group policy refreshes.

Engineer FAQ

Can Batch Control Center run on a machine that does not have WinCC installed?

Standard Batch Control Center client machines require WinCC Client or WinCC Runtime components to host the embedded alarm controls. If running on a dedicated BATCH client, the SIMATIC BATCH Client installation package installs the necessary runtime OCXs.

Does this error affect recipe execution in the controller (AS)?

No. The recipe phases running in the AS controller continue executing normally. The error strictly impacts the visualization of alarms within the Batch Control Center desktop client.

Why must WinCC Runtime be running before opening Batch Control Center?

Because the embedded Alarm Control queries the local WinCC CCAlarmServer process. If runtime is offline, the COM server is unavailable, triggering an initialization timeout.