Resolving PH-Ready Error in WinCC OS: 'WinCC Alarm System Not Initialized' (Message 1003071)

The error 'WinCC alarm system not initialized. Could not send system message' (Message ID 1003071) logged by the Process Historian Ready agent (CCCAPHServer.exe) in the Windows Event Log occurs when CCCAPHServer attempts to register its alarm listener before the WinCC Alarm Logging runtime service (ALGRT) has completed startup. In systems with CP 1623 cards, it also indicates network routing conflicts where PH data is mistakenly routed through the CP 1623 NDIS port instead of the dedicated Terminal Bus LAN adapter. To resolve this, ensure Process Historian communicates strictly over the Terminal Bus, verify that Alarm Logging Runtime is enabled in WinCC Computer Startup, and resolve database attachment locks in the WinCC Diagnose logs.

Process Historian Ready (PH-Ready) Architecture and Agent Lifecycle

In SIMATIC PCS 7, WinCC OS Servers do not transfer process archives directly via standard SQL queries; they utilize a specialized background agent called Process Historian Ready (PH-Ready). Installed on every OS Server that archives to Process Historian, the PH-Ready service (CCCAPHServer.exe) acts as an intelligent cache and transport broker.

When WinCC Runtime activates, CCCAPHServer.exe initializes in parallel with the WinCC core services. Its role is to hook into the local WinCC Alarm Logging runtime engine (CCAlarmServer.exe / ALGRT) and Tag Logging runtime engine (CCTagLoggingServer.exe), intercepting committed archive segments and streaming them across the network to the central Process Historian server.

Network Architecture: Terminal Bus (LAN) vs Plant Bus (CP 1623)

A foundational architectural rule in SIMATIC PCS 7 governs the physical separation between control networks and supervisory networks:

Plant Bus (CP 1623 / CP 1613): The CP 1623 communications processor is dedicated exclusively to the Plant Bus, communicating with S7-400H / CPU 410-5H controllers via ISO / S7-REDCONNECT protocols. While the CP 1623 provides an NDIS virtual Ethernet adapter, this adapter must never be used to transmit Process Historian archive traffic.
Terminal Bus (Standard LAN Adapter): Process Historian resides on the Terminal Bus. All communication between WinCC OS Servers and Process Historian must travel across the standard motherboard or PCIe industrial network interface card (NIC) assigned to the Terminal Bus subnet. Configuring the CP 1623 NDIS port on the same IP subnet as the Terminal Bus LAN adapter creates severe IP routing ambiguities, leading to dropped socket connections during runtime startup.

Root Cause Analysis: Event Log Message 1003071 (ALGRT Uninitialized)

The error recorded in the Windows Event Log by CCCAPHServer—'WinCC alarm system not initialized. Could not send system message' (Siemens System Message ID 1003071 / ALGRT:@100%s@:Message System Runtime not initialized)—stems from a race condition or startup crash:

Startup Race Condition: When WinCC Runtime launches, multiple server processes initialize simultaneously. If CCCAPHServer starts up and immediately attempts to send a system status message before the WinCC Alarm Logging runtime service (ALGRT) has opened its message queues, the registration call fails.
Alarm Logging Startup Failure: If the WinCC Alarm Logging service itself fails to start—for example, due to corrupted SQL database segments (AlarmLog.mdf), missing database context, or missing startup entries—CCCAPHServer cannot establish the IPC link, repeatedly logging the error.
Missing Startup List Entry: If 'Alarm Logging Runtime' is unchecked in the WinCC Computer Properties startup list, the alarm system never initializes, permanently blocking CCCAPHServer.

Startup Sequence Synchronization and Computer Properties Configuration

To verify that the WinCC startup pipeline initializes all required subsystems in proper order:

Open WinCC Explorer on the affected OS Server.
In the navigation tree, click Computer, right-click the server name, and select Properties.
Select the Startup tab.
Confirm that the following runtime services are explicitly checked:
- Alarm Logging Runtime (Mandatory for alarm message capturing)
- Tag Logging Runtime (Mandatory for analog/binary trend logging)
- Global Script Runtime (If C/VBS scripts are required)
Ensure that no custom startup applications in the 'Additional Applications' list block execution by running modal dialogs.

Diagnostic Matrix: PH-Ready Communication and Startup Errors

The following matrix outlines troubleshooting steps for PH-Ready errors in WinCC OS:

Error Message / Event IDRoot Cause MechanismCorrective Engineering ActionMsg 1003071: 'Alarm system not initialized'Race condition between CCCAPHServer and ALGRTCycle startup list: uncheck Alarm Logging, run, re-check, runMsg 1003071: 'Alarm system not initialized'Alarm Logging database segment corruptRename/archive corrupt .mdf in ArchiveManager\AlarmLogPH-Ready agent cannot reach PH ServerPH traffic routed through CP 1623 NDISAssign distinct subnets for Plant Bus and Terminal Bus'Error connecting to Historian Storage'PH Server in Maintenance or Locked stateRestore PH Server storage and service health on PH nodeEvent Log: DCOM Error 10016Service account lacks local activation rightsGrant SIMATIC HMI activation rights in dcomcnfg

Step-by-Step Resolution and Component Reset Workflow

Follow this sequence to resolve the initialization lock between PH-Ready and WinCC Alarm Logging:

Separate Subnets: Ensure the CP 1623 Plant Bus IP address and the Terminal Bus LAN IP address reside on entirely separate IP subnets (e.g., Plant Bus: 192.168.1.x, Terminal Bus: 172.16.1.x). Remove any default gateway configured on the CP 1623 NDIS adapter.
Deactivate WinCC Runtime: Exit WinCC Runtime on the OS Server.
Execute Startup Reset Procedure:
- In WinCC Explorer, open Computer Properties -> Startup.
- Uncheck Alarm Logging Runtime (leave Tag Logging checked). Click OK.
- Activate WinCC Runtime. Allow the project to load completely (allowing CCCAPHServer to establish its baseline database context).
- Deactivate WinCC Runtime.
- Return to Computer Properties -> Startup and re-check Alarm Logging Runtime. Click OK.
- Reactivate WinCC Runtime.
Audit Diagnostic Logs: Open C:\Program Files (x86)\Siemens\WinCC\diagnose\WinCC_Sys_01.log. Confirm that ALGRT starts cleanly and CCCAPHServer reports successful initialization.

Verification

Verify error-free operation of the PH-Ready component:

In the Windows Event Viewer, open Windows Logs -> Application. Filter for Source CCCAPHServer.
Confirm that Message 1003071 no longer appears upon WinCC Runtime activation.
Trigger a test alarm in CFC; confirm that the alarm appears in the WinCC Alarm Logging list and transfers to Process Historian.
In Process Historian Management Console (PH-MC), open the OS Server connection list and verify that the OS Server status shows 'Connected' with an active green data throughput indicator.

Limitations and Operational Precautions

Adhere to the following operational precautions:

Never Route PH Through CP 1623: Never configure Process Historian archival communication over CP 1623 cards; the CP 1623 is optimized for deterministic controller polling, not bulk SQL data replication.
Redundant Server Symmetry: Apply the startup list reset procedure identically to both servers in a redundant OS pair.
Avoid Deleting ArchiveManager Folders: Do not delete the ArchiveManager directory to clear alarm errors; use the WinCC reset procedure to preserve historical records.

Engineer FAQ

Why is using the CP 1623 NDIS port for Process Historian traffic problematic?

Because the CP 1623 card is dedicated to real-time S7 communication with controllers on the Plant Bus. Routing high-volume SQL archive traffic across the CP 1623 causes buffer contention and packet drops.

What does Siemens system message 1003071 signify?

Message 1003071 indicates that the WinCC runtime project was activated without the runtime components of Alarm Logging, or that Alarm Logging crashed during startup.