Troubleshoot a PCS 7 Historical Server That Is Not Receiving OS Data

Diagnose the OS-to-Process-Historian transfer path before changing accounts or restarting services. In the documented architecture, PH-Ready transfers long-term OS process values and messages to PH, using a configured destination and transfer filter. This report omits the error image, product versions, and system diagnostics, so it does not establish a specific fault. Check PH-Ready, its PH destination/filter, and PH status using the manuals for the installed release.

Trace the Archive Transfer Path

In a PCS 7/WinCC system, long-term process values and messages are transferred from the OS through PH-Ready to the Process Historian. Siemens' Process Historian 2014 system manual describes the PH-Ready transfer path and its configuration: select the PH server and, for a redundant installation, the standby server on the Server tab, then select the transferred information on the Filter tab. The exact settings and software requirements depend on the installed Process Historian version, which this report does not state.

The source mentions an error shown in a picture, but no image, error text, project version, or resolution is present. Therefore no specific root cause can be diagnosed from the post.

Version-Aware Diagnostic Procedure

Record the PCS 7, WinCC and Process Historian versions/updates, whether the project uses a PH redundant pair, and the exact OS/PH PC-station names. Use the installation and administration manuals for that exact PH release.
On the OS station, verify the PH-Ready component and service are installed/configured as required by that release. Siemens' PH 2020 installation notes state that PH-Ready version must correspond to the Process Historian version and describe MSMQ as an installation prerequisite; do not apply that specific setup instruction to another PH version without checking its own manual.
In the WinCC PH-Ready configuration, verify the configured PH server, redundant standby destination when applicable, and filter selection. These settings determine where PH-Ready sends archive data and what information is transferred.
Check whether the expected long-term tags/messages are configured for transfer on the OS and whether PH records other data sources. Compare the affected source with a working OS station to isolate OS-side versus PH-side symptoms.
Inspect the PH-Ready service and Process Historian status using their version-specific service and management tools. Review Windows and product diagnostics at the failure time. For PH 2020, Siemens documents that PH-Ready stores data in a local Store & Forward Cache before transmitting it to PH; check the cache and available disk space under that version's guidance.
Verify network/name resolution, time synchronization, service identity/group membership, and security configuration only against the requirements documented for the installed release. A forum reply suggesting identical usernames on two PCs in a workgroup is not enough to establish a universal requirement.
After correcting a documented mismatch, confirm that the PH Management view recognizes the source and that expected tag/message data reaches the historian. Preserve the original diagnostic and configuration before changing services or archive settings.

Interpret the Visible Symptom

A stopped PH-Ready service, an unconfigured destination/filter, a PH-side service or database problem, and a communication problem can all interrupt different parts of the transfer chain; the missing screenshot and logs do not identify which case occurred here. If PH-Ready has cached data, its version-specific documentation explains how buffered transfer and cache limits behave. Do not delete or manually edit the cache as a substitute for diagnosing the transfer path.

Verification

Confirm the affected OS server is configured as a PH source, PH-Ready is active and connected to the intended PH destination, and the intended long-term tags/messages are selected. Then verify actual process values or messages appear in PH with expected timestamps and that any redundant PH reaches its documented synchronized state. A running service, visible source entry, or successful configuration wizard alone does not prove the expected data was archived.

Limitations and Operational Precautions

The original error image is absent, and no product versions, exact message, service state, PH assignment, filter configuration, or system logs are supplied. The 2020 and 2021 PH manuals cited below document version-specific behavior; their requirements must not be assumed for an unidentified older release. The forum advice about same usernames and a workgroup is not independently verified for this system.

Do not restart production services, change authentication, clear Store & Forward data, or alter archive assignments without a release-specific procedure and plant-approved maintenance plan. Preserve logs and a recoverable configuration, then escalate unresolved database or transfer errors with the missing diagnostic details.

Engineer FAQ

What component sends OS data to Process Historian? Siemens documents PH-Ready as the transfer component between the OS server and PH; the exact PH-Ready release must match the installed PH system.

Does the reported same-username/workgroup advice apply to every PH installation? The ticket does not establish that. Check the security and service-account requirements in the manual for the installed Process Historian version.

Can this ticket identify why data was not received? No. Its referenced error screenshot and all system-version and diagnostic details are missing, and no resolution is reported.

Technical References

Siemens, SIMATIC Process Historian 2014 System Manual, section 3.3 “Data transfer from PH-Ready to the Process Historian,” document A5E38560565-AA. https://cache.industry.siemens.com/dl/files/440/109738440/att_885702/v1/InformationSystemPRHIenUS_en-US.pdf
Siemens, SIMATIC Process Historian System Manual, 03/2020, section 3.3 “Data transfer from PH-Ready to the Process Historian,” document A5E38560565-AI. https://cache.industry.siemens.com/dl/files/203/109774203/att_1007899/v1/InformationSystemPRHIenUS_en-US.pdf
Siemens, SIMATIC Process Historian System Manual, 12/2021, section 1.2.2.3 “Installing PH-Ready on a PCS 7 OS,” document A5E51393796-AA. https://cache.industry.siemens.com/dl/files/481/109805481/att_1090033/v1/InformationSystemPRHIenUS_en-US.pdf

Related Tags

SIMATIC Process Historian, PH-Ready, PCS 7, WinCC, MSMQ, Store and Forward Cache, archive transfer

Troubleshoot a PCS 7 Historical Server That Is Not Receiving OS Data