TN - Hist09112602 - Advanced Debugging of Replication
Last updated: September 11th, 2026Description
- Author: Jamie Jackson
- Published: September 11th, 2026
Details:
- Document Version: 001
- Applies to Version(s): 2023 R2 or later

Description
This article from InSource shows how to collect debug level log information of Historian Replication. This can be useful when facing replication issues where the standard log information is insufficient, especially when replicating to software like PI.
Details
From the Historian side you can set these two components to Trace in the standard AALogger:
- AVEVA.Data.System.Host (Adapter process sending data)
- aahReplication
Also, and I think what you need to do, is set the adapter logs to debug mode, to do so:
First find this folder:
Then open the System_HealthEndpoints.json and set an expiration data for debug.
Once that is saved find the 3 files called x_logging.json
Open all 3 and set the log level to debug:
Once they are set, taskkill this process, it will restart automatically and enable the debug logging:
Then you can view the debug logs here:
_____________________________________________________________________________________________________


Recommended articles
[ISS Support Case] Historian Tag Import problem
Arithmetic overflow error for type int. value = 2147483648.000000 when importing intouch application
Read More[ISS Support Case] Historian missing data
A month ago they changed the network acct utility. Missing data from 9/7 - 10/30, data starting coming in after they re-ran the change network acct utility again. ?Using tiered historian.
Read More[ISS Support Case] Historian Migration
Using TN Hist213 Migration of History Blocks to a New Server but within the configurator, the attempt lags upgraded from 10.0.0.1
Read More