Troubleshoot Missing Tag Data in SIMATIC Process Historian

When Process Historian stops recording tag data, trace the OS-to-PH-Ready-to-historian path before restarting components. Check the historian's operating state, storage and diagnostics, then compare source lifebeat and measured-value transfer timestamps. Siemens documents these checks and the Store & Forward mechanism, but the installation's version and failure details were not supplied. No exact cause or guaranteed restart cure is established; verify new archived samples and any recovered interval separately.

Locate the Break in the Archiving Chain

Distinguish four observations: the OS receives a changing process value, the intended tag is configured for historical collection, PH-Ready transfers it, and Process Historian stores it. An OS Runtime status check is useful, but it does not identify which boundary failed.

The installation's PCS 7, WinCC and Process Historian versions, affected tag scope and exact messages were not supplied. No confirmed reason or successful recovery is established. The checks below use Siemens' December 2021 Process Historian documentation as a diagnostic baseline; confirm the matching dashboard and behavior for the installed release.

Inspect Historian State and Storage

Open the Process Historian Management Console and inspect the server's operating state.
Record the state before attempting a change. In the cited manual, Active archives data, Idle does not, and Locked stops new archiving while allowing stored values to be read.
Open I/O Systems and inspect free space on the relevant drives.
Open Diagnostics and retain messages around the last known recording time.

This separates a stopped or storage-constrained historian from a missing source-data stream. Old values remaining readable does not prove that current samples are still being archived. Do not delete database files to create space. Process Historian manual, dashboards pp. 120–121 and operating states pp. 131–132

Inspect the Affected Data Source

Open the Management Console's Data sources dashboard.
Identify the intended source PC and project, keeping those private identifiers in the local diagnostic record.
Compare Last lifebeat, Last alarm data, Last measured value data and the corresponding configuration timestamps.
Determine whether all sources are stale or only the affected source/tag group.
Compare those observations with the source OS Runtime and actual value history.

The cited manual marks data as stale in blue when no data have been sent for more than 10 minutes. Treat that as a dashboard threshold for this documented edition, not a universal data-loss timeout or proof of a particular network fault.

The dashboard's transfer timestamps need not equal the samples' own timestamps, particularly after an interruption. Manual, Data sources dashboard, pp. 119–120

Check PH-Ready Without Destroying Its Cache

The documented transmission path is OS data to the PH-Ready Store & Forward cache, transfer to Process Historian, storage acknowledgement, and release of acknowledged cache space. During disconnection, pending data can accumulate in the cache within its available resources.

Record the PH-Ready service state and its installed version alongside the historian version. If the fault followed an upgrade, investigate the documented component-version requirements before assuming the OS application alone needs restarting.

Do not delete or reset the cache as a generic repair. Its pending content can be relevant to recovering the missing interval, and the available information does not establish that any cache cleanup is necessary or safe for this case.

Verification

After a documented corrective action, observe new measured-value transfer activity and query actual archived samples for an agreed test tag and time interval. Compare the value and sample timestamp with the OS history.

Verify both continued current recording and the disposition of any missing interval. A running service, refreshed dashboard or successful Runtime restart alone does not prove that historical data were backfilled. Retain any gaps that remain in the recovery record.

Limitations and Operational Precautions

The exact failed component and recovery procedure remain unresolved. The suggestion to restart WinCC is not a confirmed repair and can interrupt operator functions or data collection.

Preserve diagnostic messages, project configuration, database backups and pending cache data before maintenance. Plan any OS or historian restart with operations and the applicable product procedure. Do not promise complete recovery of missing samples without verifying their actual availability.

Engineer FAQ

Does readable old history prove that Process Historian is recording now?
No. The documented Locked state can retain read access while stopping new archiving.

Should WinCC be restarted immediately?
Not on the evidence available. First identify source, transfer and storage state, then use an applicable recovery procedure.

Technical References

Siemens — SIMATIC Process Historian System Manual, December 2021, A5E51393796-AA — Store & Forward transfer, p. 82; Data sources dashboard, pp. 119–120; storage/diagnostic dashboards, pp. 120–121; operating states, pp. 131–132.

Process Historian missing data

Troubleshoot Missing Tag Data in SIMATIC Process Historian