Correcting Replication Errors Based on Local Replication Misconfiguration

Description

The Historian Server is producing errors related to InSQL Configuration or Main Replication

• Author: James Rochester
• Published: 1/29/2026
• Applies to: Historian 2023 +

Details

When viewing the logger in the OCMC on the Historian server you will observe either of the following errors repeatedly:

"LocalHost: ValidateSecondaryClients: using integrated security but user mismatch, existing user (), token user(NT SERVICE\InSQLConfiguration) [aahClientCommon.cpp, 10014]"

"Main Replication failed to connect to Retrieval through HCAL, error = 174 (User credential mismatch) [CFPHISTORY; ReplicationJobQueueManager.cpp; 1774]"

These errors will lead to your local replication failing as they indicate that Replication is pointed to a Tier 2 Historian or InSight instance which has either been configured improperly or is directing towards an instance for which your user account lacks necessary permissions. 

Resolution:

Add the currently utilized user account to the Windows group aaReplicationUsers on the Tier 1 Historian if you are replicating to Tier 2 and on the Tier 2 Historian if you are replicating from Tier 2 to any cloud storage solution.