Troubleshooting Tag Visibility Between Process Historian and Information Server in Unified PCS 7 Architectures

When Process Historian (PH) and Information Server (IS) 2014 are co-installed on a single PC station in SIMATIC PCS 7 V8.0 SP1 Upd 1, newly archived tags failing to appear in Information Server reporting indicates a local SQL service synchronization stall or missing user security tokens. Because both packages share local resources on a single node, ensure that the Windows service 'SIMATIC Process Historian Server' is in the 'Active' state, verify that the 'Information Server Sync Service' is running, and open the IS web console under 'Administration > Data Sources' to force an immediate catalog rebuild. Also, ensure the Windows user belongs to the local 'Historian Administrators' group.

Executive Summary

In small to mid-sized SIMATIC PCS 7 installations, budget or spatial constraints frequently lead engineering teams to deploy SIMATIC Process Historian (PH) and SIMATIC Information Server (IS) on a single physical SIMATIC IPC workstation. While fully supported by Siemens, running both database-intensive applications on a shared operating system introduces inter-process dependencies and communication contention. A frequent symptom is that newly configured archive tags stream into the Process Historian SQL database, but remain invisible in the Information Server reporting interface. This problem occurs due to stalled synchronization services, database query timeouts, or improper Windows security role assignments on the local server. This guide provides actionable steps to diagnose and repair tag visibility.

Single-Node PH/IS Architecture: Shared Resources and Services

When PH and IS reside on the same server, two distinct Microsoft SQL Server database environments interact:

Process Historian Engine (HISTORIAN Instance): A specialized SQL Server 2008 R2 / 2014 instance configured for high-speed bulk time-series data ingestion and archive segment management.
Information Server Engine (INFOSERVER / SSRS): Operates Microsoft SQL Server Reporting Services (SSRS) and the Information Server web management portal.

The Information Server Sync Service bridges these two environments by querying the HISTORIAN database catalog and caching tag definitions into Information Server's reporting repository. If memory pressure or service stalls interrupt this background link, new tags are never indexed for reporting.

Common Root Causes for Local Tag Synchronization Failures

Three primary technical faults suppress tag visibility in single-node installations:

SQL Memory Contention: If SQL Server memory limits (max server memory) are not capped in SQL Server Management Studio (SSMS), the HISTORIAN instance can consume up to 95% of physical RAM, starving the Information Server web service and causing database query timeouts during catalog synchronization.
Stalled Sync Service: The Windows service Information Server Data Export Service can enter an unhandled timeout state when large batches of new tags are committed simultaneously.
Missing Windows Group Privileges: If the local user executing the reporting web portal is not assigned to the local Windows group Historian Administrators, cross-database queries are denied.

Windows Security Groups and Access Token Requirements

For single-node architectures, verify the following local Windows security groups in Computer Management (compmgmt.msc):

SIMATIC Report Administrators: Grants full administrative control over Information Server data sources and report templates.
Historian Administrators: Grants administrative access to Process Historian database configuration tables.
SIMATIC HMI: Required for WinCC cross-component communications.

Diagnostic Service and Pipeline Comparison

The following table compares the essential Windows services, database instances, and functions in a single-node PH/IS deployment:

Service / Component NameOperating System NameHosting Database InstancePrimary Responsibility in PCS 7Process Historian ServerProcessHistorianServerlocalhost\HISTORIANManages archive segment ingestion and database health.Information Server ServiceISDataServicelocalhost\INFOSERVERExecutes report templates and schedules report generation.SQL Server Reporting ServicesReportServer$INFOSERVERlocalhost\INFOSERVERRenders PDF, Excel, and Word report documents.Data Synchronization LinkISSyncServiceBridge (PH to IS)Synchronizes tag names, units, and plant hierarchy paths.WinCC Data ExchangeCCDataExchangeWinCC OS -> PHStreams archive packets over Terminal Bus to PH.

Step-by-Step Single-Node Synchronization Procedure

Method 1: Capping SQL Server Memory Allocation

Open Microsoft SQL Server Management Studio (SSMS) as Administrator.
Connect to the local Process Historian instance: localhost\HISTORIAN.
Right-click the server instance node and select Properties > Memory.
In a 32 GB RAM server hosting both PH and IS, set Maximum server memory (in MB) for HISTORIAN to 18432 (18 GB).
Connect to the Information Server instance localhost\INFOSERVER and cap its maximum memory to 6144 (6 GB).
Click OK to apply settings without restarting services.

Method 2: Restarting Synchronization Services and Refreshing Data Source

Open Windows Services (services.msc).
Locate and restart the service Information Server Data Service.
Launch Internet Explorer and log into Information Server web console: http://localhost/InformationServer.
Navigate to Administration > Data Sources.
Select the Process Historian data source (pointing to localhost or local server name).
Click Synchronize and verify that the sync status reports success with updated tag counts.

Verification

To verify complete operational integrity on the combined workstation:

Process Historian Active State: Open the Process Historian Management Console. Confirm that the dashboard status indicator displays 'Active' with a green checkmark.
Tag Discovery Test: In Information Server, create a new report using the 'Standard Process Value Report' template. Browse the tag selection hierarchy and confirm that newly added tags appear.
Report Generation Test: Run the report against live archived data. Confirm that the report renders successfully with complete data tables and trend charts.

Limitations and Operational Precautions

Hardware Sizing Constraints: Single-node installations of PH and IS must utilize high-performance IPC hardware (minimum Intel Xeon processor, 32 GB RAM, and dedicated enterprise SSDs configured in RAID 1/RAID 5) to prevent I/O bottlenecks.
Domain Migration Notice: If the workstation is joined to an Active Directory domain, ensure that domain group policies (GPOs) do not overwrite local group memberships for Historian Administrators.
Official Catalog Validation: Validate software licensing quantities (PH Process Objects and IS Reporting Client licenses) against the latest Siemens ST PCS 7 catalog and an authorized Siemens distributor quotation.

Engineer FAQ

Can Process Historian and Information Server share the same Microsoft SQL Server instance?

No. Siemens architecture strictly enforces separate SQL instances (HISTORIAN and INFOSERVER) to prevent schema collisions and decouple reporting queries from real-time archiving.

What happens if SQL memory is not capped on a single-node PH/IS server?

The Process Historian SQL engine will dynamically expand to consume all available physical memory, starving IIS application pools and causing Information Server to crash.

Is it necessary to reboot the PC after synchronizing tags in Information Server?

No. Tag synchronization is an online database metadata update that does not require restarting Windows or cycling the Process Historian server.

Technical References

Related Tags

https://industrialautomation.net/search?query=simatic-pcs7
https://industrialautomation.net/search?query=process-historian
https://industrialautomation.net/search?query=information-server
https://industrialautomation.net/search?query=system-architecture

6 respuestas

Troubleshooting Tag Visibility Between Process Historian and Information Server in Unified PCS 7 Architectures