Troubleshooting Process Historian Not Storing WinCC Tags in SIMATIC PCS 7

When Process Historian (PH) fails to store tags despite an active OS Server connection, the failure typically stems from Process Historian not being in the 'Active' operational state, low hard drive disk capacity, expired Automation License Manager licenses, or unclosed local WinCC archive segments. Resolve this by verifying PH is in the Active state, confirming disk capacity exceeds 10%, checking PH licenses, and reviewing the CC-Historian agent transfer queue.

Diagnostic Overview and Failure Symptoms

In SIMATIC PCS 7 installations (V8.0, V8.1, V8.2, V9.x) configured with an OS Single Station or redundant OS Server pair linked to a dedicated Process Historian (PH) server, plant engineers frequently face a critical archiving stoppage:
* In WinCC Explorer on the OS Server, process variables in Tag Logging are configured with Long-Term Archiving enabled.
* The OS Server tray icon reports that the server is connected to the Process Historian.
* In the Process Historian Management Console, the database appears operational.
* However, historical queries, trends, and reports in SIMATIC Information Server show that no tag values are being written to Process Historian.
* Tag value charts display flatlines or terminate at a historical date, indicating data ingestion has completely frozen.

Because the network link shows connected, engineers often assume communication is functioning properly. In reality, the connection indicator confirms socket connectivity, while internal database ingestion may be suspended due to capacity thresholds, licensing locks, or replication queue deadlocks.

Architecture of WinCC-to-Process Historian Replication

To troubleshoot data flow bottlenecks, examine how process values travel from the controller to long-term storage:

Local Buffering on the WinCC OS Server:
* The OS Server does not stream individual data points across the network directly into SQL database tables.
* Process values are first written to local WinCC Tag Logging segments (Fast and Slow archives stored on the OS Server hard disk).
* The background agent CC-Historian monitors these local segments. When an archive segment closes or reaches its replication buffer limit, the agent streams the compressed package across the terminal bus to the Process Historian.
Process Historian Operational State Machine:
* The PH server engine functions in distinct operational states: Starting, Active, Maintenance, Reorganizing, or Shutdown.
* Tags are stored ONLY when the status is strictly Active.
* If the PH server enters Maintenance (e.g. during database consistency checks) or Standby, incoming data packages from OS servers are acknowledged but cached in the local OS buffer queue without being ingested into the PH master database (HistorianStorage).
Storage Disk Quotas and Safety Throttling:
* Microsoft SQL Server and Process Historian monitor physical disk space continuously.
* If free storage on the database drive or transaction log drive drops below 10% (or less than a critical threshold, typically 10 GB), Process Historian immediately suspends data ingestion to prevent SQL transaction log corruption.
Automation License Manager (ALM) Constraints:
* Process Historian requires two distinct licenses:
- SIMATIC Process Historian Server Basic License
- SIMATIC Process Historian Archive Tags (sized by tag volume, e.g., 1,000, 10,000, or 50,000 archive tags).
- If the number of tags marked for long-term archiving exceeds the installed license count, or if the license has expired, PH enters demo mode and halts historical tag ingestion.

Step-by-Step Diagnostic and Troubleshooting Procedure

1. Verify Process Historian Operational State

Log in to the Process Historian server with administrative credentials.
Open the Process Historian Management Console from the desktop.
Observe the operational state indicator in the dashboard:
* Required State: Active (indicated by a green icon).
* If status shows Maintenance or Error, inspect the System Event Log for database reorganization tasks.
If the service is stuck, open Windows Services (services.msc), locate Process Historian Server Service, and restart it gracefully.

2. Audit Disk Drive Storage Capacity

On the Process Historian server, open Windows Explorer.
Inspect available disk space across all drives:
* OS System Drive (C:)
* Database Data Drive (e.g. D:\PH_Data\)
* Database Log Drive (e.g. L:\PH_Logs\)
If free space is below 10%, Process Historian suspends ingestion.
Execute database backup and segment offloading to external network storage or expand virtual disk volumes.

3. Check Automation License Manager (ALM) Entitlements

On the PH Server, open Automation License Manager.
Verify the presence and validity of:
* SIMATIC Process Historian Server
* Process Historian - Archive Tags (verify total capacity covers all active tags).
Check the ALM message log for license missing or license limit exceeded errors.

4. Inspect Local OS Server CC-Historian Buffer Queue

On the WinCC OS Server, navigate to the WinCC project directory:
<ProjectPath>\ArchiveManager\
Inspect the subfolders for the replication queue. If numerous .mdf/.ldf segment files are accumulating locally, data is trapped on the OS Server because PH is refusing ingestion.
Open Command Prompt and test network latency and port availability to the PH server:
cmd ping <PH-IP-Address> telnet <PH-IP-Address> 1433
Verify TCP Port 1433 (SQL Server) and TCP Port 135 (RPC) are open and unblocked by firewalls.

5. Validate Time Synchronization Integrity

Open Command Prompt on both the OS Server and PH Server.
Execute w32tm /query /status.
Confirm both servers synchronize to the identical NTP master clock. A time discrepancy exceeding several seconds can cause the PH database engine to drop incoming data stamped with invalid future or past timestamps.

Process Historian Component and Status Matrix

Diagnostic ElementHealthy IndicatorFault ConditionConsequenceRemediation ActionPH Console StateActive (Green)Maintenance / StoppedTags rejected / cached locallyRestart PH service; wait for integrity checkDrive Capacity>15% Free Space<10% Free SpaceIngestion suspended automaticallyOffload older segments; expand drive volumeALM LicensingValid & Sufficient TagsMissing / Over CapacitySystem enters demo mode; halts storageInstall required Process Historian PO licensesCC-Historian LinkConnected (Green Tray)Disconnected (Red Tray)OS cannot stream segmentsRun Security Controller on OS and PHNTP SynchronizationOffset < 10 msTime drift > 2 secondsTimestamps rejected as invalidSynchronize all nodes to central NTP master

Verification

In the Process Historian Management Console, confirm the dashboard displays status Active.
In WinCC Explorer on the OS Server, modify a test analog process tag value.
Open Microsoft SQL Server Management Studio on the PH Server.
Connect to HistorianStorage and execute:
sql SELECT TOP 10 * FROM ProcessValueView ORDER BY Timestamp DESC;
Confirm that new records appear with current UTC timestamps matching the modified tag.
Open SIMATIC Information Server; generate an ad-hoc trend and confirm real-time historical data updates continuously.

Limitations and Operational Precautions

Never Shrink Production Databases in Runtime: Avoid running manual SQL DBCC SHRINKDATABASE commands on active HistorianStorage databases during peak logging, as this severely fragments database indexes and spikes CPU utilization.
Segment Retention Configuration: Ensure automatic segment offloading (backup to NAS / SAN) is configured in the PH Management Console to prevent hard drives from reaching the 10% safety cutoff.
Commercial and Licensing Notice: Process Historian archive tags are licensed in cumulative packages (e.g. MLFB 6ES7652-8BX01-0YB0). Sizing must account for all analog, digital, and calculated tags marked for long-term storage. Validate order numbers with an authorized distributor.

Engineer FAQ

Why does the OS Server show 'Connected to PH' if tags aren't storing?

The tray icon indicates that the TCP network connection and CC-Historian handshake succeeded. It does not verify whether the destination database is currently writing incoming data to disk.

Can I recover the tags that were logged while Process Historian was offline?

Yes. As long as the local WinCC OS hard drive has sufficient storage, the OS Server buffers un-transmitted segments in ArchiveManager. Once PH returns to the Active state, the CC-Historian agent automatically transmits the buffered backlog.

What happens if the Process Historian runs completely out of hard disk space?

Microsoft SQL Server will mark the database as SUSPECT or EMERGENCY to prevent file corruption. Ingestion halts completely until disk capacity is freed and the database is recovered.