Aveva Insight Data Source is Disabled

Last updated: June 30th, 2025

Description

Author: Ernest Lee
Published: June 30th, 2025

Details:

If you receive the email below Aveva has blocked uploads to Insight.

Steps needed to be performed prior to contacting Technical Support:

Shutdown/Disable the Historian and execute the query below in SQL.

SQL Query executed:

SELECT * FROM ReplicationSyncRequest

ORDER BY ModStartDateTimeUtc

SELECT * INTO ReplicationSyncRequestBackUp

FROM ReplicationSyncRequest

SELECT * FROM ReplicationSyncRequest

WHERE ModStartDateTimeUtc < '2025-01-01'

DELETE FROM ReplicationSyncRequest

WHERE ModStartDateTimeUtc < ‘2025-01-01’

2. Move the content of the 2 folders in Historian Store/Forward to another location.

3. Use the Replication Backfill utility located at c:\Program Files (x86)\Wonderware\Historian\x64, file name is aahBackfillUI.exe.

4. You can try backfilling data for a couple of days and set the “Time increment (in hours) to 1”

5. The recommendation is to start with the most recent dates and work backwards to the oldest.

Give feedback about this article

Recommended articles

[ISS Support Case] Some Discrete tags collected from Cogent Data Hub in Historian are not working

Has a historian collecting cogent datahub (OPC) data. Some Discrete tags not working / being added roughly 20 or so. Getting an error in the Cogent datahub (sounds like a cogent data hub issue). Remote support is possible, has availability until 2PM today or any time Monday. 2020 R2 Sp1 P01 Allen Bradley PLC -> Top Server -> Cogent Data Hub -> Historian

[ISS Support Case] Historian data not showing

No Historian data is displaying for any tags prior to 5/8 at about 11:00 AM. Found no errors in the SMC log or Windows System log from 5/8 at midnight through 5/10 at 11:59 PM. There was a Historian warning in the Windows App log on 5/9 at 1:00 AM "Null value / quality mismatch - value / quality is overwritten to conform with OPC specification". No events were known to have happened on 5/8 that would have caused this issue. Have requested a reboot of our Historian server at 4:30 PM this afternoon to see if the problem would be resolved by a reboot. Would just like to check and see if there is any other investigation that could be performed or any other remedy that we might be able to perform to resolve the issue in lieu of a Historian server reboot.

[ISS Support Case] Historian Will Not Start After A Reboot

Have 2016 Windows Server Historian 2017 running on it Restarted Stopped Restarted Last update 4.23.23 17.018000 (2017) On a restart gets to the point of a MedataServer (message) doesnt go further.