Correcting Replication Errors Based on Local Replication Misconfiguration
Last updated: March 27th, 2026Description
- Author: James Rochester
- Published: March 27th, 2026
Details:
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.
Give feedback about this article
Recommended articles
[ISS Support Case] Getting Bad Quality in an Object Troubleshooting ABCIP
Created an object in app server and cannot get a good quality read on it. wwClient tried to validate items but adds and item still gets bad quality End device ControlLogix PLC (some tags are working) Tags were previously working / existing system. Work was done on the PLC and then this issue surfaced all point are discrete deployed DDESLC CORE G-2.1 v5.1.0 ABCIP G-2.0 v7
Read More[ISS Support Case] ABCIP connection to 1756L84ES Poor Performance
Direct Email. REF CASE: 8390 and SR 960275396. AVEVA indicated there are some known issues reported by Rockwell related to Firmware version 32.xxx, including v32.013. FAQ 000021344 CompactLogix 5380 v32.014 Release Notes . Per AVEVA's recommendation the client upgraded firmware resulting in even worse performance. "....we had some down time on the production line yesterday, so we took that opportunity to upgrade our controllers to from V32.013 V33.015. That turned out to be *worse*! The data gaps we were reading we much more pronounced. So we reverted back to V32 on the controllers to get it back to the way it was before. I then ran an experiment this morning, turning off all of the HMIs on the line, and then stopping our data collection and OPC server. Turning off the HMIs made a significant impact on the communication (MSG Class 3) utilization. Turning off the data historian made a little impact, and turning off the OPC Server did not affect the utilization at all. I then turned the OPC Server and the data historian back on, and then turned the HMIs back on one at a time. With each HMI, the data gaps increased. At this time, I am seeing a gap of about 0.4-0.5 seconds, occurring regularly every 2 seconds. Im still trying to understand what could be causing this periodic interruption.''
Read More[ISS Support Case] Platform Communication Error on Deployment
GR Platform deploys fine, but cannot deploy to the rest of the remote platforms.
Read More