Resolving SIMATIC Process Historian Segment Backup Failures and Remoting Proxy Errors

In SIMATIC Process Historian (PH), a failure condition where database segment backups cannot be performed, the PH tray icon shows red with 'No connection to Process Historian', and logs report 'Unexpected error occurred connecting to remoting server proxy' is typically caused by disk space starvation or stalled IPC remoting services. When storage volumes drop below safety thresholds (default 10-15% free space), PH locks the server into protective maintenance mode, halting segment backups. To resolve this, free disk space on database and backup partitions, verify PH service account NTFS permissions on target backup shares, and restart the SIMATIC Process Historian Server and SQL Server (HISTORIAN) services.

Process Historian Server Architecture and Protective Locking States

SIMATIC Process Historian (PH) serves as the central, high-capacity long-term archiving system for SIMATIC PCS 7 and WinCC. Operating on Microsoft SQL Server with specialized real-time compression algorithms, PH continuously ingests tag logs, alarm records, and batch recipes from multiple OS Server pairs.

To safeguard database consistency against catastrophic hard drive exhaustion, Process Historian incorporates an automated System State Monitor. When operating normally, PH reports the status Active in the Process Historian Management Console (PH-MC). However, if critical operating parameters are breached, PH shifts automatically into Locked or Maintenance mode. In this defensive state, external client connections are rejected, segment backups fail, and the Windows system tray icon turns solid red displaying 'No connection to Process Historian'.

Disk Space Starvation and Hard Drive Safety Margins

The most common root cause of sudden PH lockups is storage partition exhaustion:

The Safety Threshold: Process Historian enforces hard-coded disk space thresholds across all configured partitions (Operating System C:, Database MDF drive, Transaction Log LDF drive, and Backup Destination drive). By default, if free storage on any database drive drops below 15% or less than 10 GB, PH halts segment creation and suspends automated backups.
Transaction Log Bloating: If SQL Server recovery models or backup maintenance jobs fail, the transaction log file (HISTORIAN_Log.ldf) can swell rapidly, consuming hundreds of gigabytes and pushing the drive past the emergency threshold.
RAM Exhaustion: Process Historian requires significant dedicated physical RAM (minimum 16-32 GB). If Microsoft SQL Server consumes all available memory without a configured ceiling, Windows begins paging aggressively, causing IPC communication timeouts.

The Remoting Server Proxy Architecture in Process Historian

The diagnostic message 'Unexpected error occurred connecting to remoting server proxy' points directly to an internal IPC communication breakdown between PH client interfaces (PH-MC, Information Server) and the core background service:

.NET Remoting and WCF Services: Process Historian uses Microsoft .NET Remoting / Windows Communication Foundation (WCF) hosted inside CCProcessHistorianServer.exe to expose administrative endpoints.
Proxy Disconnect Mechanism: When the underlying SQL Server instance (HISTORIAN) locks up due to memory starvation, or when the PH service enters an unhandled exception state, the remoting proxy port (typically TCP port 5000-5010) closes. Client applications attempting to connect receive a proxy communication error despite physical network pings succeeding.

Auditing Backup Destination Share Permissions and NTFS Access

Segment backup failures frequently occur when target external storage (NAS, SAN, or remote server share) rejects access tokens:

Service Account Identity: The backup transfer engine operates under the security context of the SQL Server (HISTORIAN) service account (typically NT SERVICE\MSSQL$HISTORIAN or a designated domain service account DOMAIN\PH_Admin).
Share and NTFS Permissions: The destination network folder must have both Windows Share permissions (Full Control) and NTFS file system permissions (Modify, Write) explicitly granted to this service account.
Network Disconnects: If the network share disconnects during an ongoing segment backup, PH flags the segment as Corrupted Backup and refuses to initiate subsequent segment transfers until manually acknowledged.

Diagnostic Matrix: Process Historian Service and Segment Backup Failures

Use the following matrix to diagnose and resolve Process Historian failures:

| Error Symptom / Log Output | Underlying Root Cause | Corrective Engineering Action |
|---|---|---|---|
| Tray icon red; 'No connection' | PH Server service stopped or in Locked mode | Free disk space (>15%); restart PH services |
| 'Error connecting to remoting proxy' | IPC remoting channel crashed due to RAM spike | Restart SIMATIC Process Historian Server service |
| Segment backup fails immediately | Target backup share lacks write permissions | Grant MSSQL$HISTORIAN Full Control on backup folder |
| Transaction log fills drive | Uncommitted transactions or missing log backup | Execute SQL transaction log truncation and backup |
| Information Server reports no tags | PH in Maintenance mode; OPC HDA blocked | Restore PH to 'Active' state in PH Management Console |

Step-by-Step Recovery and Service Restoration Workflow

Follow this recovery sequence to restore Process Historian to service:

Check Disk Partitions: Open Windows Explorer on the PH Server. Verify that drive C: and all dedicated database partitions possess at least 20% free space. Clear old temporary files or move obsolete log archives if space is constrained.
Inspect Windows Services: Open services.msc and verify the status of:
- SQL Server (HISTORIAN) (Must be Running)
- SQL Server Agent (HISTORIAN) (Must be Running)
- SIMATIC Process Historian Server (Must be Running)
Open PH Management Console (PH-MC): Launch the console with Administrator rights. Navigate to Dashboard and observe the system state.
Acknowledge and Reset Segment Errors: Under Database -> Segments, locate any segments marked with an error badge. Right-click and select Retry Backup or Verify Segment.
Restart PH Services Gracefully: If the remoting proxy error persists, stop SIMATIC Process Historian Server, wait 30 seconds, restart SQL Server (HISTORIAN), and then restart SIMATIC Process Historian Server.
Verify that the system tray icon returns to green indicating 'Connected'.

Verification

Confirm that Process Historian has returned to full operational readiness:

Confirm that the PH tray icon displays a green checkmark with status 'Process Historian: Active'.
In PH-MC, verify that the active database segment shows status 'Ready' and disk storage graphs show green health bars.
Trigger a manual segment backup test in PH-MC and confirm that the .mdf and .ldf files transfer cleanly to the backup share.
Open SIMATIC Information Server in a web browser; generate a historical tag report and verify that data queries execute without remoting errors.

Limitations and Operational Precautions

Adhere to the following operational precautions:

Never Terminate PH Services Forcefully: Killing CCProcessHistorianServer.exe via Task Manager during an active segment commit can cause SQL database page corruption requiring database restore.
Dedicated Hardware Mandatory: Never co-locate Process Historian with WinCC OS Servers or Domain Controllers; PH demands dedicated server resources.
Backup Drive Speed: Ensure backup target shares possess adequate Gigabit network bandwidth; high latency or packet loss during segment transfers will trigger remoting timeouts.

Engineer FAQ

Why does ping work normally between servers when PH reports no connection?

ICMP ping validates basic network layer connectivity, but Process Historian relies on higher-level .NET Remoting and WCF services on TCP ports 5000-5010. If the service halts, ping succeeds while application communication fails.

Can Process Historian continue logging data if segment backups fail?

PH can continue logging data into the active segment temporarily, but once the active segment reaches its size limit, failure to backup and detach forces PH into a Locked state, halting all further data intake.

How much free disk space is required on Process Historian drives?

Siemens recommends maintaining at least 20% to 25% free disk space on all Process Historian database and backup partitions to prevent automated safety lockouts.