Resolving Process Historian and Information Server Connection Errors After Admin Password Changes

In SIMATIC PCS 7, changing the Windows Administrator password on a server hosting Process Historian (PH) and Information Server (IS) breaks authentication across background services, COM+ components, and SQL Server database roles. While re-running the Information Server Configuration Manager updates the web application, Information Server will still fail to connect to the Historian database until the new password is updated on all underlying Windows services—including 'CCCAPHServer', 'ReportServer' (SSRS), and IIS Application Pools—and database connection credentials are re-established in the IS web administration console.

Architecture of Process Historian and Information Server Authentication

In SIMATIC PCS 7, enterprise reporting and long-term data archiving are managed by two tightly integrated components:
* SIMATIC Process Historian (PH) (6ES7652-0XX08-1XB0):
Runs an enterprise Microsoft SQL Server database storing historical process values, alarms, and batch archives.
* SIMATIC Information Server (IS) (6AV6371-1DH07-5AX0):
A web-based reporting system based on Microsoft SQL Server Reporting Services (SSRS) and Internet Information Services (IIS). It queries the Process Historian SQL database to generate scheduled PDF, Excel, and Word compliance reports.
* The Shared Security Context:
When Process Historian and Information Server are installed on the same server PC (or in a distributed workgroup/domain), they communicate using dedicated Windows user accounts and SQL Server authentication roles (such as SIMATIC HMI, HistorianAdministrators, and ISUser). These service identities maintain cryptographic security tokens across multiple Windows subsystems.

Why Windows Password Changes Break Distributed Historian Connections

When an IT administrator or plant engineer modifies the Windows Administrator password on the server host:

The Mismatched Credential Cascade:
Windows services and COM+ applications configured to log on under the administrator account do not automatically inherit the new password.
The Configuration Manager Trap:
Running the Information Server Configuration Manager (C:\Program Files (x86)\SIEMENS\InformationServer\ConfigurationManager\) with the new password updates the main IS configuration table, but:
1. The background SQL Server Reporting Services (SSRS) engine continues attempting to authenticate with cached, obsolete credentials.
2. The IIS Application Pools (ISAppPool) fail to start, throwing HTTP Error 503: Service Unavailable.
3. The core Historian capture service CCCAPHServer and OS agent services (PH-Ready) fail authentication handshakes, severing SQL data links.

The Interdependency Between CCCAPHServer, SSRS, and IIS AppPools

To resolve database disconnection, engineers must understand which specific components require manual credential updates:

CCCAPHServer (Process Historian Server Service):
The central daemon responsible for maintaining SQL access to the HistorianStorage database. If its logon credentials are out of sync, SQL rejects its queries.
ReportServer (SQL Server Reporting Services):
The reporting execution engine that builds reports on behalf of Information Server. SSRS stores an encrypted database connection string pointing to the Historian database.
IIS Application Pool (ISAppPool):
Hosts the Information Server ASP.NET web portal. If the Windows user password changes, the AppPool crashes immediately upon the first operator HTTP request.
PH-Ready Service on OS Servers:
Runs on all connected WinCC OS servers. It must authenticate with the Historian server using matching credentials to stream historical segments.

Re-Authenticating Information Server with the Historian Database

Even when all Windows services are running, Information Server may still display:
Error: Cannot connect to Historian database

The Internal Data Source Binding:
Inside Information Server, the connection to the Process Historian is registered as a Linked Data Source.
Stored SQL Authentication Tokens:
This data source stores a SQL connection string configured during initial setup. When the Windows account password changes, the stored SQL credential token is invalidated.
Remediation:
The engineer must log into the Information Server web portal as an administrator, navigate to Administration > Data Sources, select the Process Historian data source, re-enter the updated credentials, and test the connection link.

Diagnostic Matrix for Post-Password Change Connection Failures

The following table details common error symptoms following a password reset and their specific corrective actions:

Error SymptomFaulting SubsystemUnderlying Root CauseCorrective ActionIS reports 'Cannot connect to Historian database'Information Server Data SourceStored credentials in IS web admin are obsoleteRe-enter password in IS Web Portal > Administration > Data SourcesHTTP Error 503: Service Unavailable on IS portalIIS Application Pool (ISAppPool)Application Pool identity using old passwordIn IIS Manager, update password for ISAppPool under Advanced SettingsSSRS reports 'Cannot initialize report server'SQL Server Reporting ServicesSSRS service account failed logonIn Reporting Services Config Manager, update service account credentialsOS Servers show 'PH disconnected' in PH-ReadyCCCAPHServer / PH-ReadyMismatched service logon credentialsUpdate password on CCCAPHServer and OS server PH-Ready servicesWindows Event 7000: 'Service failed to log on'Windows Service Control ManagerService set to old passwordIn services.msc, update Log On tab for all Siemens/SQL services

Step-by-Step Recovery Procedure to Restore System Authentication

Follow this verified engineering procedure to restore full connectivity after a password change:

Update Windows Services Logon Credentials:
* Open Windows Services (services.msc) on the Process Historian / IS server.
* Locate the following services:
- CCCAPHServer
- SQL Server (HISTORIAN)
- SQL Server Reporting Services
- SIMATIC Process Historian Ready
- For each service, right-click > Properties > Log On tab.
- Re-enter the updated password in both fields and click Apply.
Update IIS Application Pool Identity:
* Open Internet Information Services (IIS) Manager.
* Expand the server and click Application Pools.
* Select ISAppPool and click Advanced Settings....
* Under Identity, re-enter the account username and new password.
* Recycle the Application Pool.
Update Reporting Services Configuration:
* Launch Reporting Services Configuration Manager.
* Connect to the report server instance.
* Under Service Account, verify the account status and re-enter the password.
* Under Database, verify connection to ReportServer database.
Re-Run Information Server Configuration Manager:
* Run C:\Program Files (x86)\SIEMENS\InformationServer\ConfigurationManager\ConfigurationManager.exe.
* Complete the wizard with the new administrator password.
Re-Establish Database Link in Information Server Web Portal:
* Open a browser and navigate to http://localhost/InformationServer.
* Log in with the updated administrator credentials.
* Navigate to Administration > Data Sources.
* Select the Process Historian database, click Edit, re-enter credentials, and click Test Connection.

Verification

Verify that Process Historian and Information Server connectivity is restored:
1. In the Information Server web portal under Administration > Data Sources, verify that the test connection reports: "Connection to Process Historian database succeeded".
2. Open the Process Historian Management Console (PHMC); verify that dashboard status is Active and that connected OS Clients display green indicators.
3. In Information Server, execute an existing shift report; verify that the report queries the Historian database and generates tables/trends without authorization errors.
4. Open Windows Event Viewer (Application log) and verify that no Event ID 7000 (logon failures) or SQL access denied entries are logged.

Limitations and Operational Precautions

Dedicated Service Accounts: Never use the personal Windows Administrator account for industrial automation services. Best engineering practice establishes a dedicated, unexpiring service account (e.g., SiemensServiceAccount) specifically for Process Historian, SSRS, and WinCC.
Workgroup vs Domain Environments: In workgroup environments, the exact same username and password must exist on all machines (Engineering Station, OS Servers, and Historian). Changing a password on the Historian requires updating the identical user account on all OS servers.
Restarting Services in Proper Sequence: When restarting after credential updates, start components in hierarchical order: 1) SQL Server -> 2) Reporting Services -> 3) CCCAPHServer -> 4) IIS -> 5) OS Server PH-Ready.
Commercial Accuracy: Process Historian (6ES7652-0XX08-1XB0) and Information Server (6AV6371-1DH07-5AX0) licenses are verified through Automation License Manager. Validate software entitlements with an authorized Siemens distributor quotation.

Engineer FAQ

Why didn't running Information Server Configuration Manager fix the database connection?

Configuration Manager configures the web application framework and IIS endpoints, but does not update the underlying Windows service accounts (CCCAPHServer, ReportServer) or the internal web portal data source authentication token.

Can Process Historian and Information Server run under different user accounts?

Yes, provided both accounts belong to the required Siemens user groups (SIMATIC HMI, HistorianAdministrators) and have appropriate read/write permissions on the SQL Server HistorianStorage database.

What should I do if IIS throws HTTP Error 503 after a password change?

An HTTP Error 503 immediately after a password change indicates that the IIS Application Pool identity (ISAppPool) failed to log on due to an invalid password. Update the password in IIS Application Pools > Advanced Settings and start the pool.

Does changing the password cause any historical data loss in Process Historian?

No. The Microsoft SQL Server database files (.mdf and .ldf) remain completely intact. Historical data logging pauses while services are offline, but OS servers buffer data in local circular archives and backfill once connection is restored.