Some content on this site is available only to logged-in subscribers. Contact Us for information on becoming a subscriber.

InSource.Solutions | InSource Training | InSource Client Portal
InSource Solutions Logo
Log In Sign Up
InSource.Solutions InSource Training InSource Client Portal Log In Sign Up
  • Home
  • AVEVA Insight
  • AVEVA Insight Tech Notes

TN - 1500 Insight Data Source is disabled

Last updated: March 4th, 2026

Description

  • Author: Ernest Lee
  • Published: March 4th, 2026

Details:

Description

This Tech Note addresses an issue where an AVEVA Insight data source connected to a Historian Server is disabled. 4This often triggers an email notification to the user. 5

 

Applies to: Historian version 2020 R2 SP1 and newer 6

 

Details

One of the Insight data sources has been disabled. 7The affected data source is connected to a Historian Server. 8Cause

 

Excessive Data Age: The Historian was sending data to Insight that was more than 50 days old. 9This creates behavior similar to a Distributed Denial-of-Service (DDoS) attack by overwhelming the server with excessive traffic. 

 

Licensing Limitations: The Historian is using a Development Studio license, which in this scenario only supports a one-day History duration. 11This license is not intended for production use and causes replication issues and sync queue violations. 121212

 

Resolution

  1. Gather Information: Execute the following query to identify stuck items in the replication sync queue:

SELECT DATEDIFF(ss, ModStartDateTimeUtc, ModEnd Date TimeUtc) AS Dur, Replication SyncRequestKey, Replication TagEntityKey, RequestVersion, ModStartDateTimeUtc, ModEndDate TimeUtc, EarliestExecution DateTimeUtc, ExecuteState
 

FROM Replication SyncRequestinfo
 

ORDER BY ModStartDate TimeUtc

 

2. Verify Specific Tags: Using the results from the first query, replace the placeholders below to investigate specific tags and history ranges: 

Select * from Replication TagEntity where Replication Tag EntityKey = <Enter key here>


Select * from History where Tagname = 'Enter tagname here' and DateTime >= '<Enter ModStartDateTimeUtc>' and DateTime <= '<Enter ModEndDateTimeUtc>' and wwTimeZone = 'UTC'

 

3. Clear Sync Queue: To resolve stuck items and license violations (such as QD 33), you must clear the queue. 17

Step A: Shut down, back up, and clear the Replication StoreForward folder. 

Step B: Run the following query to truncate the table: 19

TRUNCATE TABLE ReplicationSyncRequest

4. Re-enable:22

Contact AVEVA support to re-enable the data source. 23

 

insight tn
Give feedback about this article

Recommended articles

[ISS Support Case] No Data In A Deployed OMI Application

Got 3 servers 1 gr 1 AOS 1 IO developed application on GR server tests view apps and OMI app is working. On AOS server and open application OMI screen appears Gone to object viewer sees PLC objects (NOT in OMI application) In SMC Platform an engine running on scan. LM 4.0.1 OI 2023R2

Read More

[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.

Read More

[ISS Support Case] Aveva Historian Data retrieval bug

Client has 2 user accounts that have access to Historian Server. Client has no problem viewing the trend data in account 1, but when adding the same tag to trend on account 2, the tag flatlines. Queried data appears correct. This seems to only affect analog tags.

Read More
Support Icon

CONTACT SUPPORT

How to reach us

10800 Midlothian Turnpike Tpke, Suite 209, Richmond, VA 23235

1.877.INSOURCE

Technical Support - 1.888.691.3858

Contact Us

  • InSource Solutions
  • InSource Training
  • InSource Client Portal
  • Log In
InSource Solutions Logo

© 2026 InSource Solutions. All Rights Reserved.

Knowledge Base Software powered by Helpjuice

Expand