[ISS Support Case] Tier 1 Historian High CPU Usage

Last updated: July 9th, 2026

Description

A Tier 1 Historian servers is running at almost 100% constantly. The SQL Server Windows NT (32 bit) service runs around 40-50% and the ArchestrA Historian Storage runs between 30-50% often.

Author: Kevin Modlin
Published: July 9th, 2026

Details:

Product: Historian

Version: 2017

Solution: [Solution is visible below when you're logged in and have a current subscription]

Date Created:	01/13/2022
Case:	80642

Give feedback about this article

Recommended articles

[ISS Support Case] Replication to Insight stopped working for some sites... Address was banned

Had 4 sights that went offline on Insight Created a case which was escalated to L2 and was told a back end fix was applied. Sites just needed a reboot to resolve. Two sites came back online with a reboot, Two did not come back up Both non working sites are running 2017 U3 SP1 TotalSyncQueue items are 0 on both sites, can see replicated tags locally. once site is in Store forward confirmed messages similar to: aahClientCommon component and with text like "OpenConnection to Historian Cloud failed..... address was banned

[ISS Support Case] WonderWare Historian Importing fast data not reflecting correctly

Client reached out as when user performs a fast load CSV import the data is not being added to the History values.

[ISS Support Case] Dev license expired

-Customer is not able to acquire license to run Windowmaker. 5/4/2023: -Customer Did not activate the license properly offline. -Customer is in a Grace Period. -Escalating to AVEVA to Generate Grace Period Code. 5/5/2023: -Requested the Device ID of the Server so that AVEVA can Create a Grace Period Code, Customer DID NOT get back with me.

[ISS Support Case] SQL Server, pre-existing, Redundancy

3/14/2023: -Questions from IT group, New server for standalone application. -SQL server express, less than 5,000 tags, wants to make data redundant. -Already existing SQL Server -Historian on new server, wants to back up data to SQL. -SQL Server Express, Can't manage this locally to the historian. Historian Client Desktop, pull it into an excel. -E-mailed Account Manager.