AVEVA Historian Support Cases

[ISS Support Case] Historian loses connection after shutting down

If the historian is shut down and disabled then re-enabled it doesn't connect to tags that haven't changed. Reboot re-establishes connection.

[ISS Support Case] Trying to access old history blocks

They have a very old system they're trying to open a trend or see the data, but they don't see a trend program and can't figure out how to open the file. They believe they have the data, but it's running in demo mode and won't show data. This is an offline PC and they want to avoid putting it online, so we can't do a screen share.

[ISS Support Case] Trend SQL Login Failure

Client reached out due to receiving time out error message when logging into SQL to View Trends remotely on Development node.

[ISS Support Case] Wanting to pull 9 months of historized data

-Customer is wanting Historized data from the last 9 months in a .CSV file. Or in SQL. and wants to know the best practices.

[ISS Support Case] Acquisition Type not showing for Intouch Application.

9/11/2024: -23.1.001 -Imported runtime data base from older version (does not know the version) to new version. -Acquisition Intouch View. -Application Server. -OCMC: -Did it to most tag's but, not all. 9/12/2024: -TEAMS MEETING 10:30 A.M EST. -Process of Importing database (tagname) was a little off. -Used Historian Import/Export tool. Worked properly even after reboot, data acquisition stayed the same. -Believe the Tag ID to Tagname was being manipulated during the previous process, which made the tag's in the OCMC default to a different Acquisition.

[ISS Support Case] Remote Alarming not working.

Alarm history is working. -Alarm Summary, using query Intouch. works fine but when pointing to remote node. This does not work/does not connect. -Say's attempting to connect. -Almost sounds like it cannot resolve the node name.

[ISS Support Case] ABCIP running in demo mode

backup was running fine

[ISS Support Case] Historian 2023 R2 Software Request

Client reached out initially to inquire about whether Historian 2017 Update 1 Sp1 is compatible with windows 11.

[ISS Support Case] Historian Query Failure

A portion of History blocks were automatically deleted by the system due to running out of space. Those blocks ended up in the NAS (alternative data location) recycle bin and have been restored. The Historian shows the files in the circular drive, but does not query past the date of the restored files. Client has attempted this with "Query", "Trend" and the Web client, all have the same results.

[ISS Support Case] Historian Failing to Historize Tags

Client reached out as none of the tags in the project are being Historized.

[ISS Support Case] Historian Database Retrieval UTC

Client reached out looking for guidance of querying Historian data in both UTC and local time.

[ISS Support Case] Trying to retrieve historical data from an alternate drive

they need to retrieve old historical data on an external drive and it takes too long to manually transfer the data

[ISS Support Case] Historian Installation

Client reached out requesting a copy of Historian installation.

[ISS Support Case] Unable to Connect to Logger

Client reached out initially due to issue with Historian, but user was unable to open logger receiving the following error message: "Unable to connect to logger on 'Hostname'. If running on Windows Server 2003 SP1 or Windows XP SP2, verify that you have run the OS configuration Utility to ensure correct services login. This may have been caused by the logger Service having been shutdown possibly by a product being installed. The Microsoft Windows Data Execution Prevention (DEP) feature may also cause the problem. To disable DEP, add '/noexecute=AlwaysOff' to the Boot.ini file, then reboot."

[ISS Support Case] SQL login

Unable to login as SQL user

[ISS Support Case] Can you adjust how many decimal places are displayed in Historian Web Client (on-premise Insight)

Do you know if there is a way for me to change the decimal point place in analog tags in Historian? In the picture, you can see that the value is 1554 degrees C, but I would like to display it as 155.4 degrees C.

[ISS Support Case] Nodes Failing to Connect to Historian

Client reached out as nodes within Galaxy were failing to connect to the Historian with the following error message: "OI.: Failed to connect to Historian at :32565 - error = 164 (Communication Error) - Grpc.Core.RpcException: Status(StatusCode="Unavailable", Detail="Error starting gRPC call."

[ISS Support Case] Historian Getting Tag Count Violation

recieved flex licensing switched to flex licensing - grabbing 5k tags Historian grabbed 500 out of 10000 tags. Central license server

[ISS Support Case] installing historian client trend

Historian Client installation issue

[ISS Support Case] Historian TagRename Utility General Info - Best Practices

ref 88093: Eventually the current IDAS data source is going to go away. Seeking any details on Tag Rename Utility to rename Tags once the TopServer Goes Away.

[ISS Support Case] new topic not communicating

created a new topic and tags created do not communicate

[ISS Support Case] AVEVA Historian

Client reached out as when user was attempting to configure Historian server he was receiving the following error: "Failed to Connect to SQL Server: Provided SQL login does not have 'SYSADMIN' privileges"

[ISS Support Case] Querying Historian General Inquiry

Want to query historian Where do I find table information. how do you access archived tables. Want to be able to use data in HMI

[ISS Support Case] historian tag not reading

Trying to configure the 32 tag Historian and it is not starting the Historian Client Access Point.

[ISS Support Case] Historian Migration/Configuration

Client reached out as he was migrating his Historian Database to a new server.

[ISS Support Case] Historian Cannot Access SQL Server when logged in with Specific Users

Client reached out because when using any user other than Administrator user was unable to connect to SQL Database through Historian.

[ISS Support Case] Historian Data Storage\Rate Change question

Client reached out as he has several tags with engineering units set to near 200 million. User wants to ensure that all changes to this tag data are stored regardless of numerical significance.

[ISS Support Case] historian events/clock 3 hours behind

[ISS Support Case] SQL Server Connection Failure

Client reached as when user was attempting to launch Historian Trends and connect to SQL he would receive the following error: "Connection Failure. Unable to reach INSQL/Historian server, make that INSQL/Historian server is Running" This was locally on the Historian server itself.

[ISS Support Case] Setting Up Historian To Collect Data From PLCs

I have installed my historian software but was wondering if there are any guides or videos for setting up the historian to collect data for PLCs. I have found some 8 year old videos on YouTube and on forums but they are too outdated for the current drivers and historian it seems. Do you happen to have anything that is for the current gen historian?

[ISS Support Case] Historian Database Query Failure

Client reached out as when user was attempting to query the runtime database the query would execute indefinitely and never finish unless stopped manually. The query is being performed locally on the historian server. This is after migrating from 2017 to 2023 R2 P01.

[ISS Support Case] Historian not acquiring license

Issue started shortly after committing changes to add new tags. Found Hist was showing disconnected in OCMC. Not responding to any commands or loading status page. All services running, RPC service running, SQL service running. Able to log into SSMS and access db. Restarted server, communications restored. Verified license acquired and data historizing as expected.

[ISS Support Case] Engines Failing to Historize Data

Client reached out because no data was being historized from deployed engines.

[ISS Support Case] Adding New Application to 2023 Historian Undetermined Issue

recently had someone on site who updated from 2020 Historian to 2023 in process of adding more tags client noticed there is no previous applications listed.

[ISS Support Case] Historian not connecting to most engines

Initially had tag count violation - reduced tags below limit but still had issues. Found errors in logs about circular buffer overflow. Circular storage was configured for 500MB deletion threshold and unlimited max size/age. 180GB free space on history block storage drive, but messages show it still checking against the deletion threshold

[ISS Support Case] IDAS Tag Historization Failure

Client reached out due to loss in Trend data for IDAS tags. When reviewing logs observed the following error: "IDAS new node config version 002121E620652AEE differs from recalculated version 002121E6D8E7460D. Corrupted configuration saved to C:\ProgramData\Archestra\Historian\IDAS\Support\idascfg_CYTPENPWSQL01_2_backup_corrupted_479.dat [CYTPENPWSQL01; IdasServer.cpp; 515]"

[ISS Support Case] Arithmetic overflow error on tag import

[ISS Support Case] Cannot connect to the historian

After tag reimport, the historian keeps disconnecting/reconnecting

[ISS Support Case] Remote Trend Clients Suddenly Stopped Working

Trend clients were suddenly unable to connect to Historian.

[ISS Support Case] Com driver for SI direct, wont let him run more than one driver at a time

The redundant license pair seems to be going into grace period

[ISS Support Case] Historian Client Connection Issue's.

12/7/2023: -Historian Server, engineering station that has the Historian Client. -BMS terminal Server.

[ISS Support Case] Aveva Historian with Edge Validating Historical Data

I'd be interested in learning some quick and easy sanity checks for determining if live data is being historicized after our upgrade. Something along the lines of browsing live OPC data in Kepware or PI to determine if the historian "sees" the tags, and then doing some trends to be sure they're being recorded. -Also, I think I'll need some fresh demo licenses for Historian 2023 and Edge 2020 for January 2023

[ISS Support Case] Historian SQL Error

Client called in due to historian throwing errors when trying to query the database. The error message stated: "The time of the point for the specific stream is outside the required cycle."

[ISS Support Case] Running out of available space

1/17/2024: -Historian running out of available space.

[ISS Support Case] Tags no longer historizing

tags are no longer historizing only tags that are related to the tags as water pressure systems after a power outage. no active data 2014R2 SP 1

[ISS Support Case] Historian Missing Tags

Client called in due to noticing they were missing around 37,000 tags and only had around 7,000 showing in system since yesterday afternoon. When inquiring about any recent changes client stated that they were attempting a bulk import yesterday when they received an error. They are unsure of the exact error but client stated it was something along the lines of "Cannot reserve the .LOK file." They believed the error was due to a lack of space/memory or too many nodes in the importer so they deleted 10-15 of the nodes which I believe were tied to the missing 37,000 tags. Attempted to query some of the missing tags using query and no data was returned for tags for live or historical values. Believe that nodes will be need to be readded to import tags or possible backup restoration on system?

[ISS Support Case] Does Historian require JAVA?

Quick confirmation question on Oracle Java on Historian servers. Are the following Java versions needed, and if so licensed under Historian License Java Platform (Public) 8 Standard Java(TM) Platform SE 8, Java(TM) Platform SE 8 U202 Java(TM) Platform SE 8 U202, Java(TM) Platform SE 8 If Java is needed, do you think if we could use some other version such as Azul Zulu?

[ISS Support Case] Historian trend not seeing data

Had restored runtime database after missing some tags. License wasn't working originally, got that fixed. Diagnostics showing tags are green and reading. Pulling from MBTCP. Added test tag.

[ISS Support Case] Historian Low Disk Space

Client called in due to disk space on Historian server nearing maximum volume. Advised client on how to setup automatic backup/deletion or alternate storage paths for history blocks. Provided client with Tech Note: ISS-TN024

[ISS Support Case] Deleting Unused MDAS Historian Tags

Client called in because they were updating there system and they were over there tag allowance by five tags. User wanted to delete old unused tags from system and wanted to confirm the procedure. Advised user of the follow and provided documentation with these steps as well: If you need to delete Historian tags to keep them under the number of licensed tags, complete the following steps: Uncheck the historization of those corresponding AppServer attributes. Redeploy these attributes. Delete Historian tags. Commit the changes from Historian.

[ISS Support Case] Tag import doesn't want to work

Cannot create appedit.lok but there is not one in there.

[ISS Support Case] Values not changing in Trend

Galaxy is not updating historical values. He sees them in MDAS and they are there but in Trend they never change. 2017 p03

[ISS Support Case] Historian Client Failure to Acquire License

Client called in due to Historian Client 2023 failing to acquire license and going into Demo mode on two nodes. Client has 2017 Historian client license installed currently. Client was previously using Historian 2017, but the new PC's are windows 11 and therefore incompatible.

[ISS Support Case] Tag Violation Error

Client called in as they were receiving Tag count Violation error in Historian while they were significantly under tag count. Error could be cleared by restarting server or refreshing the license manager would clear the error.

[ISS Support Case] Error using Archesta Bulk Import Utility

Client called in as they were trying to add alarm attribute to existing templates using Archesta Bulk Importer and were receiving duplicate errors.

[ISS Support Case] How to Monitor the Historian Status From an Application

Direct Email: Wed also like to add some way of monitoring the Historian status in our application. Right now we dont get any alerts or indication when the Historian stops.

[ISS Support Case] IDAS Connections Counter Incrementing - Topic Timeout

We have several connections to an AVEVA Historian through OPCUA . We have a system on site that's a wonderware product and we connected it directly into AVEVA Historian. The data is largely okay, but the connection is spotty and each time the connection dissconnects and reconnects, or if we reinit the topic, the connections value increments. I've attached an image here.

[ISS Support Case] Historian (Aveva platform) Install issue

When installing the 2023 R2 update on some systems, I get an error about needing Net Core 6 installed. I checked the installed runtimes and sdks (dotnet --list-sdks and dotnet --list-runtimes) and versions of 6 are installed. I downloaded and installed the 6.0.27 DSK and the Hosting Bundle, but I still get the error. I've been able to install on some machines, but not others.

[ISS Support Case] Applied Unlimited Historian licenses SMC still showing inaccurate tag count

We purchased a few licenses: for the additional Historian Clients users and Unlimited Historian tags. I have added them to the license manager software and can see them activated. When I go to the SMC status, I still see old value for the number of licensed tags (please see picture attached) Have two license AVEVA MES AVEVA Historian license is for Unlimited Historian and two more uses for Historian client. got licenses put them on the server (activated) Accessing historian

[ISS Support Case] Tag stops historizing if UAExpert not using it

We have a tag (called heartbeat) which reads/records the minute wall clock value in our controllers. This is used to monitor the connectivity from the asset to the historian. One of these stops updating unless we're also monitoring the tag via UAExpert. The moment we stop monitoring via UAExpert, the tags flatlines.

[ISS Support Case] Historian crash caused data retreival issues

After an unexpected crash of the historian server the data displayed by the historian client is inconsistent, depending on time window and dates. Data is displayed when looking at small windows, but disappears when zooming out. A previous ticket was submitted and the technician had us set the topics to include late data which helped, but we do not want our tags to be collecting in Delta mode so this is not a permanent fix.

[ISS Support Case] Historian

After updating to 2023 R2 ( and enterprise Licensing 4.0.1), The historian is pulling or using 32 Count tag license. The machine has the Licensing server installed and the Configurator points to it. I have tried setting the Machine as having a reserved license, but so far, it still uses the 32 count.

[ISS Support Case] stream live data, IDAS tags

[ISS Support Case] Advanced SMC Log Flags & Filtering How To

Uninstallation Error Needs Log Export guidance not familiar with accessing log files. Filtering and exporting etc.

[ISS Support Case] Backing Up Historian How To

Encountered Uninstallation Error Needs Backing up Historian Guidance.

[ISS Support Case] Uninstalling System Platform 2020 Versions

Uninstallation Error performed from control panel. Needs Uninstallation TN (including batch files)

[ISS Support Case] Unable login to the DB

Unable login to the DB using Hist Client

[ISS Support Case] Backing Up Historian How To

Ref case 86600 May have messed up one of our servers getting SMC - OCMC not found post machine rename. Research indicates this may result in an OS reset needs instruction on backing up Historian. Can you send some instructions on how to do this?

[ISS Support Case] License violation

We noticed that the trend was not working and checked the error log please see the attached file.

[ISS Support Case] Newley added Topic is not acquiring Data

Historian added a new topic (configured, matching PLC, Topic not connecting (reinitialize had no impact) 2014 R2 Sp1

[ISS Support Case] Validating Suitelink Communication wwClient

Would like some instruction needs to validate data sources are working.

[ISS Support Case] Event Block Storage Access

[ISS Support Case] Historian Status Tag Count Window

Direct email: I'm never sure how to read the Historian tag count window. What is: License tag count - ? Allocated tag count license - ? Total tags defined - I understand this one Tags requiring a license - I understand this one Total tag count available - ? If I'm reading this right, I only have 4 tags available on my license?

[ISS Support Case] Failed to export CSV using Hist data wizard

While exporting data from the graph as CSV file using the Hist data wizard. When selecting save the application doesn't save or display any errors

[ISS Support Case] Historian v2023 p03 - sql login is invalid

He restarts the historian, sql login is invalid. He is logged in to computer using local admin account. ---- Advised caller to make sure the account he is logged in under is in aapowerusers group.

[ISS Support Case] Trend Intermittently Missing Data

Client called in because when viewing Trends the data for all tags is intermittently missing at the same time.

[ISS Support Case] PCS.IdentityManager.Host

Our IT department would like more information on the requirement for PCS.IdentityManager.Host, it's requirement on the system, the possibility of removing it and, if so how. Port 1900 was discovered on firewall logs and led to this https://docs.aveva.com/bundle/system-platform-deployment-guide/page/686254.html.

[ISS Support Case] Tier 2 Historian Error

Retrieval waiting period 2 tier 1 hist and 2 tier 2 AAH retrieval (unknown data type) Scheduled tasks importing data from usga

[ISS Support Case] Historian Stopped Collected Data

2023 p02 Stopped Collecting Data around the 31st. In SMC seeing : Auto Summary Storage failed to move 2 aged history blocks from Circular to Alternate Domain Environment

[ISS Support Case] Historian Client Applications Do Not Display Data

Can not retrieve data from Historian. dont know why. History in SSMS? Trend or Query, Cant see past yesterday Lots of Errors in log viewer Trend and Query display the issue. SSMS (not seeing data for the time period either) Not sure when this started first noticed the issue yesterday at 12PM (logs littered with errors) No historical data for any of those tags, and I looked before and there was information. Previously working and stopped affecting more than one user, Unable to see any data before 12 something yesterday

[ISS Support Case] Historian Tag Count Violation

Client called in because in the Operations Control management console he was seeing tag count violation for the Historian.

[ISS Support Case] Historian Data Varies

Historian queried data is different than the Live data and the live data and the trend flat lines. Copied circular data directly from the duplicated machine more data with same dates and times is overflow alternate/overflow data

[ISS Support Case] No Alarms List

There is no alarm list or event list data, it is possible that some additional configuration should be done with the historian server or that this problem is recent, I also noticed that once a week or every two weeks the operator should restart the historian server because the trends screen is stopped.

[ISS Support Case] Historian Unlimited Licensing Issue Undetermined

Client is supposed to have an unlimited license but historian only acquired a 50,000 tag license.

[ISS Support Case] Historian Stuck in Store Forward.

4/23/2024: -Historian is stuck in store and Forward state. After a Reboot. -80 gigs, 20 gigs available.

[ISS Support Case] Inisght Trend data has no history

Omi view app real-time trend for 2 pins they can't see 75 mins of data like the others Trend retry count key Data is in the trend client be havior is similar to if the app were looking at it's self

[ISS Support Case] Historian Trend Showing data irregularly.

4/24/2024: -Trend will flatline but, later the data will show on the graph as good.

[ISS Support Case] Historian Client not Trending New MDAS Tags.

4/29/2024: -New Tag's not showing in historian Client. -Manually added Tag's, 5 or 6 new tag's. -Most Tag's are Analog Tag's. -Maybe two Discrete Tag's. -Data inside IDE. -TagCount Violation, License. 12,000, 12,219.

[ISS Support Case] All tags showing Null value in Trends

Client reached out due to all tags being acquired from OPC server are showing as null. When viewing the tags on OPC server they appear to be functioning correctly.

[ISS Support Case] Historian 2020 Migration Guidance

Going to a new virtual server OS 2022 Interested in recreating our historian server at 2020 so it matches all of the other nodes in the galaxy. Needs guidence on migrating data. Install Server Software Migrate Data No time crunch, objective to get this leave existing infrastructure in place. Dedicated tag server serving 80 - 90 tags Will also be running Factory Talk Asset Manager Also (plan is to get Historian up, running etc). Old server killed Address Rockwell 'stuff' 3-5 day Rockwell support

[ISS Support Case] Historian not seeing license and tag count hasnt changed

[ISS Support Case] Unable to delete a replication server

Client reached out due to receiving the following error when attempting to delete replication server : "Invalid Value. Cannot delete Replication Server having Replication tag(s)"

[ISS Support Case] Cannot connect to History Blocks

Client reached as when user was testing connection to History blocks in Alarm configuration he was receiving the following error message: "Connection to History Blocks Data Storage failed on Server (Server Name)"

[ISS Support Case] Historian upgrade to 2020

Customer has intouch 2020 installed but i advised he install historian server 2020 r2 sp1 as it is compatible with his OS which is 2022.

[ISS Support Case] Historian Installation Failure

Client reached out as when he was trying to Install Historian 2020 R2 Sp1 he was receiving an error message stating: "Unsupported Operating System detected." After confirming the OS was compatible in technology matrix tried running Install in compatibility mode. The install got further this time but then failed with the following error message: "Prerequisite failed to install because of the following: "Install cannot continue. If you have an unsupported version of SQL Server already installed on this computer, please upgrade it to a supported version. Alternatively uninstall SQL Server and rerun this set Setup again to automatically install and use SQL Server Express" This node is a VM using a possibly unsupported virtualization software according to the "Virtualization and Fault-tolerant Environment Environment Compatibility:

[ISS Support Case] Historian stop showing real time data

Client reached out due to when viewing Trends all tag data is intermittently missing at the same time.

[ISS Support Case] Historian not connecting to SMS

Client reached out due to when trying to configure the Historian server to connect to the existing System management server he was receiving the following failure/error message: "Failed to configure the device Check Archestra logger for more information." The logs showed an error message stating: "Please unregister the device"

[ISS Support Case] Database keeps deleting data

InSQL database keeps wiping data every 2-3 minutes check to see if history blocks are being created (it might be returning the data from memory and not actually storing it to history blocks)

[ISS Support Case] Unable to View Historical Alarms in InTouch

Client reached out to receiving the following error when querying SQL database: "OLE DB Provider "INSQL" for linked server "INSQL" returned message "Event History no longer support queries that do not provide time." Client was also unable to view Historical alarms in HMI.

[ISS Support Case] Historian Tag Count Violation

Client reached out due to Historian showing tag count violation while Historian license with higher than utilized tag count is reserved to the Historian server.

[ISS Support Case] Historian server (DAQTF) is not maintaining historical data

[ISS Support Case] siemens cant connect topics// PLC says disconnect

[ISS Support Case] Why is the diagnostic tool showing 4 hours ahead of the server and PLC time?

[ISS Support Case] New PLC's added, no data being received.

6/28/2024: -Added new PLC'S. -ABCIP. -Topic Search Failed. 7/1/2024: -Topic's K3 and K7 not showing data. Also not showing up in the device groups. -No Encrypted suitlink communication. -Created a backplane for new ABCIP connection, then added a logix connection, inside SMC, created new Device group from Logix connection, started to receive data.

[ISS Support Case] unable to shut down historian

[ISS Support Case] License issue during a migration

Doing a migration from windows server 2008 to Server 2022. Cannot find a license on the idas computer using a 2014 invensys license manager. Trying to connect a 2020 historian to an idas server running 2014, does he need to upgrade 2014?

[ISS Support Case] Cannot edit historian directories in configurator

new install, cannot change directories for historian

[ISS Support Case] Tag Import fails. Shuts Down the OCMC

Tag dump fails through import wizard and shuts the OCMC down. -2.72 Meg Tagname.x file path size. -cannot create appedit.lok -Tag Import Wizard-InTouch Node Information is where this fails. -After pointing to the file path, the import fails with the error above appedit.lok. -Cleared the appedit.lok error message. -Import still shuts down the OCMC. -2 Servers;

[ISS Support Case] Missing Historian Data after Migration

Running TN1047 caused some issues. I suspect it's because I moved history blocks around while migrating. I have a flatline in InSight during the time I had the Historian down, and now I have an unstoppable flood of warnings in the OCMC on the Historian. Any idea how I can fix that?

[ISS Support Case] Old Historian data missing after upgrade

Intouch 2014 to SP 2023p3 Historian not showing all data Copied history blocks, ran tag rename utility Conversion was done in Dec 2023, data gaps start appearing as recently as July 2023 and earlier History block sizes match Hist query shows same results as trend Old system is still accessible, does not show these gaps

[ISS Support Case] Historian add-in stopped working

[ISS Support Case] Historian Store Forward Error

Client reached out due to repeated store forward ViewEngine related warnings in the logger stating the following: "ViewEngine.Event.: LoadTagMetadataFromSF: failed to get history block metadata status: error = 51 (Unknown client) [SFConnection.cpp, 721]"

[ISS Support Case] Main Replication failed add non-streamed value to HCAL...Error 127

Any idea on this error on the same historian? Main Replication failed add non-streamed value to HCAL: destination tagid F01A2055-559F-4223-9D67-B154C8F0602D: error = 127 (Tag not found) [WWHIST2201; aahReplicationServer.cpp; 2195]

[ISS Support Case] Historian Disabled

Client reached out due to Historian being in disabled status.

[ISS Support Case] Looking for assistance in getting InTouch to communicate with Historian

This was working previously and InTouch has been moved to a different machine.

[ISS Support Case] Historian classic event tag not sending emails

Historian - email alerts issue. 2023

[ISS Support Case] Historian not showing new data after shutdown/enable

I shutdown/disabled Historian, deleted some one data in Circular, and allowed Historian to run again. I'm not getting any new data showing, though acquisition is showing new data being collected. All of the old data is still there. I tried deleting index-history.dat from \Historian\Data\DataIndex and having it regenerate and I tried dropping new Taginfo.dat and Taginfo-tagid.idx into an existing cyclical subfolder, to no avail :(

[ISS Support Case] Historian taking long time to load and can't

HIstorina loading slow

[ISS Support Case] Historian IDAS issue with opc ua

Historian - connection to a new machine. 2017 U3 Patch 01 He added an OPC UA connection. DCOM event id 10016

[ISS Support Case] Historian SQL Query Issue

A previously functional SQL query has stopped working and instead returns the following error: OLE DB provider "INSQL" for linked server "INSQL" returned message "HCAL reported an error status. See the Historian error log for details". Msg 7330, Level 16, State 2, Line 2 Cannot fetch a row from OLE DB provider "INSQL" for linked server "INSQL". Completion time: 2023-04-03T08:57:16.8312946-04:00

[ISS Support Case] Question Regarding Historian License

Will acquiring a tier 2 feature license on a Historian prevent the Historian from Historizing on the Tier 1 level

[ISS Support Case] Historian import

Importing data from old blocks into new ones. Is there a utility for this?

[ISS Support Case] Historian Migration

New HW/SW for 2020R2SP1P01 Historian. Cannot successfully migrate Runtime DB from Historian 2014. Before setting up a lab 2014 and upgrading to 2020R2SP1P, I would like to verify a direct import is not possible. I've run the User and NodeName scripts and they appear successful. SMC errors include invalid object names for "dbo.TagExtendedPropertyInfo" and "dbo.SearchMethodSyncRequest".

[ISS Support Case] Remove a Redundant Engine From Store Forward

Get redundant engine out of store forward without redeploying

[ISS Support Case] alarm report showing N/A

not pointed to the database.

[ISS Support Case] Accessing Previously deleted History blocks

Have a Historian with HB deleted but now they are being audited. Can HB be restored without the need for stopping / starting Historian?

[ISS Support Case] Historian Client to Historian Not Working

Existing machine was previously working now today will not connect. Domain Tools > Server unable to reach insql make sure the server is running. Firewall disabled Using SQL authentication.

[ISS Support Case] Arithmetic overflow error

ERROR BELOW. Description: Invalid Value. The statement has been terminated. Arithmetic overflow error for type int, value = 214748648.000000. Changed database context to 'Holding'.

[ISS Support Case] Historian

Added Historian Server, however I get an error message

[ISS Support Case] Objects / Engines Configured to Historize Are NOT Listed In Data Acquisition (SMC)

The objects are deployed everything looks good. Gets errors (undetermined) when trying to access historical data from SMS or Historian client application. QualityDetail : 10 Communication loss 4106 Communication loss, partial cycle

[ISS Support Case] Unable to Edit Historian Properties

User is unable to create tags and modify Historian database. SMC logs "Failed user log in "no username " "

[ISS Support Case] Getting error messages regarding local replication

Getting a message: aahstorage failed to initialize metadata. Version 2023 Patch 2

[ISS Support Case] Historian MDAS Issue When Deploying To A Remote Server

Was told to change Historian We have an app engine in the app engine (enable storage to Historian) Provide the Server Name where Historian is and try to deploy (should be storing) Getting some errors Open connection authentication failed

[ISS Support Case] Failure to install Historian

Aveva Watchdog(watchdog_service) failed to start. Verify that you have sufficient privileges to start system services.

[ISS Support Case] Question Regarding Renaming MDAS Tags

User guides states that everything in the galaxy must be undeployed in order to rename tags. Which will cause downtime. Would like to confirm with Aveva

[ISS Support Case] Older Version Of Tag Rename Utility

Requesting older version of TagRename Utility

[ISS Support Case] Manually configured IDAS in Historian is not pulling in values

Manually configured IDAS in Historian is not pulling in values.

[ISS Support Case] Gallexy Dump

Alarm information is live on the Dev sytem.

[ISS Support Case] Historian stops updating requiring a restart

Historian stops updating requiring a restart. This has been happening frequently for the last couple of months.

[ISS Support Case] Tier-2 Historian is down

This is a Tier-2 historian that receives data from Tier-1 Historians and also pushes data to InSight. Version: 2023 Patch 1

[ISS Support Case] Historian Occasionally Stores Bad Values For Real Tags

I've been noticing on the historian data collection for our GE IDAS will hang or store a garbage value. Issue is affecting real tags for the most part. For example has 8 ovens with temps that typically float around 1800 but is occasionally stored at 65,000. Can also happen on slow changing tags like setpoints. Topics are set to no timeout. Historian is 2020 R2 ver 20.1.000 Using CDP 2023 7.4 OI /data source is installed on the same system as the Historian Using GESRTP issue only seems to be affecting GE connection. PLC VersaMax - firmware 2.34 A restart typically resolves for a couple of weeks Stop Start of GESRTP resolves for a couple of hours

[ISS Support Case] unable to add server setting up trend

trend client on a remote machine trying to add a server Server Configuration Logon dialouge box unable to reach , SQL server

[ISS Support Case] Some historian values are not getting data

Had them reindex the data but still no luck.

[ISS Support Case] Historian tag export

How to modify the historian tag export txt file in excel and back to a txt.

[ISS Support Case] Historian Migration Guidance

This machine will act as a flex license server for a couple HMI panels running Aveva Edge (2020) as well; those HMI Panels are also part of this upgrade project. The new Server2022 VM is built, and I have also created a dummy Server2022 VM on my laptop to experiment with as well. I have the System Platform Installation Guide manual, as well as a few other items, although I havent read every last bit of it. A couple quick questions Im running into at the start of the process on my dummy VM: Question: In terms of migrating the configuration of the old Historian to the new VM, I noticed that there is a configuration export tool that generates a text file on the legacy (WW Historian 2017) machine. I have also taken the step of creating a .bak backup of each WW Historian Database (Holding and Runtime) as well. Is it preferable to restore those databases into the new SQL Server Express? Or is it better to use the import tool when attempting to migrate to the new system?

[ISS Support Case] Uninstalling AVEVA System Platform

Ref case 85899, new to the product, set up VM for testing. Seeking uninstall guidance.

[ISS Support Case] Compile error in hidden module: RegistryFunctions

Client sent a direct email. We uninstalled the office 64-bit version and reinstalled the 32-bit version. Excel currently wants to run the Historian add-in, but were seeing these errors and not sure where theyre coming from with the Historian. Any thoughts on what were missing? Error popup: Compile error in hidden module: RegistryFunctions. This error commonly occurs when code is incompatible with The version. Platform, or architecture of this application. Click Help for information on how to correct this error.

[ISS Support Case] License

After migrating from 8.1 to 2017 the customer wanted to know the license activation process for system platform and and Aveva edge

[ISS Support Case] Historian disconnecting.

12/20/2023: -Historian is disconnecting. -Customer sending Log's. -No data on the trends.

[ISS Support Case] No Data In Tag Until Restart

After adding a tag to Historian via Configuration editor, the data from the tag doesnt appear in trend until after restarting the Historian

[ISS Support Case] Is there a way to delete data from the Historian

The client is running a report and needs to remove one anamalous data entry for a discrete bit.

[ISS Support Case] Historian not showing data

No data is showing up in Historian for new tags.

[ISS Support Case] Migrating Historian to 2020 not seeing tags in Config Export.

Question about configuration export historian configuration. Doesnt show the tags or IO servers in the export list. Working on an upgrade of the Historian.

[ISS Support Case] Historian Showing Disconnected in SMC

Historian management console showing "disconnected" and "please wait" repeatedly

[ISS Support Case] Switched Historian and Lost Remote IDAS

cutting over from 2008 historian moving to new historian 2020 changed ip of new historian to that of the old historian. things working for IDAS tags have 3 remote systems (remote idas is impacted) IDAS tags stopped when the old was shut down and ip address changed moved idas topics to the 'normal server' (should like hierarchy was adjusted in SMC) Trends just basically stopped. please update historian properties

[ISS Support Case] Seeing Message In SMC Please update Historian Server properties with valid credentials

Cutting over from 2008 historian moving to new historian changed ip of new historian to that of the old historian. things working for IDAS tags Seeing the message frequently,

[ISS Support Case] Looking to address a security vulnerability Seeking Elaboration on Elasticsearch & JRE

Trying to open a help desk ticket to address a security vulnerability. Wonderware 2017 R2 running on Windows Server 2016. The findings are phlwwtp03.usmint.etreas.govUNKNOWN\PHLWWTP03 Plugin Output: Path : D:\Program Files (x86)\Wonderware\HistorianSearch\elasticsearch-6.7.0\bin\elasticsearch-sql-cli-6.7.0.jar Installed version : 2.11.1 Fixed version : 2.12.4 TA does not address .jar, confirms they are using Insight on prem - in the bin directory there is a SQL jar file within there there is a library that is referencing Plugin Output: Path : D:\Program Files (x86)\Wonderware\HistorianSearch\jre1.8.0_202-x64\ Installed version : 1.8.0_202 Fixed version : Upgrade to version 8.0.351 or greater

[ISS Support Case] Unable to connect Historian

Can only connect historian on one server

[ISS Support Case] 2023 License Backward Compatibility

Direct email : Last December, we changed our license and support agreements to a Flex Agreement, encompassing SCADA, Historian, Reporting, and InSight + redundancies everywhere. The licenses provided by the Flex Portal are, obviously, for the latest versions of each application. The problem is that when I try to apply the 2023 license to the Historian, it does not use it. I did not remove the 2020 R2 license from the server. This is what I did for testing purposes: 1. Opened the Enterprise License Manager 2. Installed the Flex License 3. Reserved the Historian 2020 R2 license to another device 4. Forced a License Refresh on the SMC When I did that, it did not capture the Flex license. I have no grace period licenses available. Would you be able to confirm that the Flex License is retro compatible with other versions?

[ISS Support Case] How to Manually release / acquire a License

Direct email: When I try to apply a 2023 license to the Historian, it does not use it.

[ISS Support Case] How to configure auto delete old History blocks

Running out of server space and on the Historian server is managing our history blocks. Looking for an automatic delete 7 or 8 years should be good we are 2014 R2 SP1 11.6.19102 Right now the the original data is in the circular folder it's also pushing some files to an alternate folder in a partition of the drive. It's the alternate folder where the HB need to be deleted.

[ISS Support Case] Limiting Historical Trend Client Connections

Have 17 Historian Client licenses. Have the Historian Client installed on probably 70 PCs. Understand that our Historian Client license usage is based on concurrent uses up to 17. Would like to know if there is a way to terminate sessions after some period of inactivity. I'm concerned about users who might start a trend or query and keep it open at all times even though they are not using the session.

[ISS Support Case] Historian services not starting after reboot

Historian running on vm 2017.0.18.Configurator message: Unable to connect to database. There is only sysadmin account in SQL which is the SA account but the password is not working. There are 2 other AD accounts in SQL but they are not sysadmins.

[ISS Support Case] Message in logger Data rate is too high. Reduce history block duration

Direct email : Ive been restarting the historian whenever I hear that it stopped. Recently, I noticed a message in the SMC logger that I didnt notice before. Component is aahstorage and the message is Main Storage: Incorrect configuration of history block duration. Data rate is too high. Reduce history block duration. Ive reduced the history block duration from 24 hrs to 12 hrs and now to 4 hrs, but Im still getting this warning message, and the failures continue. Is there anything in your knowledge base on this? 2012 R2 P02

[ISS Support Case] Tracking IO for a Super Tag

Super tag was added to Historian but is not displaying data in client applications.

[ISS Support Case] Historian Server Upgrade Questions

Almost ready to replace an old Wonderware 2014 Historian with a new Historian running System Platform 2020 R2 SP1 on a Windows 2019 VM. The new SP Historian server has been running for the past couple of months and collecting data. Would like to copy all history blocks from the 2014 Historian to the new Historian. Should I delete all history block folders on the new Historian and copy over all history block folders from the old Historian or do I only need to copy over the history block folders that do not currently exist on the new Historian? Need to make sure that we are keeping all of our historical data intact. Have been following https://3777554.extforms.netsuite.com/app/site/crm/externalcasepage.nl/compid.3777554/.f?formid=6&h=AACffht_vbqCKdcsKDfLP4IS_S5lgzIuuAQ&redirect_count=1&did_javascript_redirect=T as a guide. Also, have one Historian Enterprise 25K Tag license and one Historian Local 25K Tag license for a Backup Historian. After retirement of our old Historian and conversion to the new Historian, I will be standing up the Backup Local Historian. Since the Historian software will be exactly the same on the Backup Local History as on the primary Historian, will the Backup Local Historian know to use the available Historian Local 25K Tag license?

[ISS Support Case] License Tag Count Violation

Historian stopped trending due to a license count violation

[ISS Support Case] Data is no longer connecting in the Historian

This was working previously but has now stopped working for all servers.

[ISS Support Case] Enable history on Field Attribute Gets Adding Primitive Causes Name Conflict

ArchestrA IDE Pop Up Message: .Historized: Adding primitive causes name conflict,

[ISS Support Case] Questions Around Outlook Client in Historian

Users have concerns and questions regarding the Historian Microsoft outlook client in order to send emails

[ISS Support Case] Historian resources spiked, VM crashed

1. 7 VM running Aveva - on 1/24 historian resources spiked. Occurred between 4-5pm. 2. 2012 upgrade to 2020 r2 sp1

[ISS Support Case] Lost SA account

[ISS Support Case] Not receiving event tag alerts Reconfiguring Database Mail

Triggered event tag alerts are not being received. The alerts are writing to the SQL Server table EventHistory in the Runtime database, but are just not getting to the intended recipients. Manually running the contents of the Action Query from the triggered event tag within a SQL query are successfully received by the intended recipients. Have restarted the AVEVA Historian Event System service, but that does not resolve the issue. sysmail_log not creating a db mail process when the wonderware events are fired.

[ISS Support Case] Historian 64-bit Excel addin not working

1. When I first load the AVEVA Historian Excel addin, I get the following error message... "WebView Stop On Load" 2. When I type in Tag Search area, no tags populate/show up 3. When I try to do a "Periodic Numeric", I get an "Error: Status code undefined returned" message. IE Enhanced Security is turned off, so this isn't the issue. Please see the attached zipped screen shots.

[ISS Support Case] Historian Client Web "Insight couldn't retrieve data" Error

client web is not returning pens. "Insight couldn't retrieve data" error

[ISS Support Case] Problem connecting to InSight from Historian

The client is trying to replicate Historian data to InSight and the connection is failing.

[ISS Support Case] Unable to Reinitialize Topics: The User ID entered is not authorized to execute commands on this Historian

We connect to a TopServer OPC as an IDAS. Last night I had to reinitialize the OPC server and I noticed this morning, all the Topics to this server are Disconnected. When I right click one of them and select reinitialize, I get the message, The User ID entered is not authorized to execute commands on this Historian.

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

[ISS Support Case] A contiguous set of history blocks will not return data

A contiguous set of history blocks will not return data

[ISS Support Case] Seeking Information for an Historian Project

Seeking information for a Historian project. Replacing Historian 1. Maybe theres a server migration document that you can share? Any information would be helpful as someone new to the system. 2. What level of service do we have? (primary, standard, premium, elite) 3. Is there an online CF support website?

[ISS Support Case] Historian 2020R2 won't upgrade old Runtime backup

We have a backup of Runtime database from v2014R2 and the Configurator on new v2020R2 SP1 P01 install will not update the database. Logs show that it is skipping the historian configuration. Tried to also step upgrade 2014R2 > 2017U3 > 2020R2. The first step works but the v2020R2 upgrade fails. Is there a hotfix out there for this? The system is close to being deployed and cutover so we need assistance as soon as possible.

[ISS Support Case] Trends are not showing up on production server

It works from the Historian server but not from the remote production server.

[ISS Support Case] KB5004442 - patch DCOM Hardening Inquiry

We want to know for Security reasons when will a hotfix/patch will be available for Wonderware 2020 R2 to allow the latest Microsoft patch KB5004442 that prevents OPC DA from working properly. We are in need of keeping our Server up to date on patches but this preventing us from moving forward.

[ISS Support Case] Null Values From Static Tags

At around 6pm daily, tags that are slow to change/ dont change at all start reporting null values. Redeploying fixes the behavior

[ISS Support Case] History Block Creation Time

Historian would create new history blocks at 1:00am and the new version creates history blocks at 12:00am. How to I set the new Historian to create history blocks at 1:00 am

[ISS Support Case] Updating bad data that's been historized

Got a historian tag with bad data sent it. The issue is suppressing averages. Would like to updated the data to a different value for an 8 hour period. Version (20.1.100)

[ISS Support Case] Changing Tag References

In AVEVA we are trying to change how some of the tags are being referenced. Wed like to change the F10_C3_TQ reference to what is now as F10_C2_TQ, and F10_C2_TQ to what is referenced as F10_C1_TQ. Ive drawn a small diagram below to try and illustrate the intent. The current situation is slightly more involved as there are more tags, but this is the basic idea. C1 <- C2 <- C3

[ISS Support Case] Help Retrieving information from Historian

We need help with retrieving information from SCADA Historian about a few alarms.

[ISS Support Case] Question about data loss RSLinx Service Keeps Stopping

We have been having issues for a while now with our Wonderware Network, sometimes like after a power outage, etc we have to login to our Virtual Comm Servers and reboot them because of the lost data points then we tried to setup the servers to automatically reboot, which didnt work and we currently have a technician that will reboot the servers one day a week but we had an issue where one of the techs clicked on shutdown and we had to wait for IT dept so what I am asking you is there a way to keep the tags refreshed in the rslinx service to avoid having to reboot? We lost all of the data from historian for a chart recorder for a month. Please let me know if you need any more information. lost power lost power on a chart recorder which a is a tag in rslinx 17.3.100

[ISS Support Case] Store Forward Script

Can you script store forward to reinitialize a connection

[ISS Support Case] Archestra trend pen is blank

No data coming in to historian.

[ISS Support Case] Active Factory tag recording

Engineer within our group created a new tag on our new Historian server. Tag value is being reported through wwclient and in diagnostics of SMC, but is not recording tag data in Trend or Query. Have restarted the DA service and tag is still not recording in AF. Cannot figure out why.

[ISS Support Case] Historian is displaying a Question Mark

In the SMC missing management portion, it seems to be hit or miss. The Historian is displaying a question mark.

[ISS Support Case] Trend has no data, tag picker is empty

Historian connection problem. He is trying to look at tags.

[ISS Support Case] Replication failing with logger error "Retrieval waiting period..."(See case description for complete error)

Replication failing with logger error : Retrieval waiting period of 00.05.00.000 for response is expired for storage id: 00000000.0000.0000.0000.00000000 named pipe aahStorageEngine\Console on localhost QID 1140967, error = 76 (Timeout) [RALWWT2HIS05; AsyncDataCacheSource.cpp; 624]

[ISS Support Case] Configuring Insight Publisher Results in Invalid Value Error

Walks through the publisher Wizard and when selecting Finish gets a pop up error: Invalid Value. The statement has been terminated. String or binary data would be truncated.

[ISS Support Case] Historian Validation screen not supported

3/14/2023: 2017 update 3 SP1 -Historian Set-up -Programfilex86, validation screen, .dll not supported.

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

[ISS Support Case] Historian Installation, Agreement grey

3/15/2023: -Customer is trying to install historian , license agreement is greyed out.

[ISS Support Case] InSQL

I think customer is running InSQL 8.0. This from lic file... #WW Historian - Standard, 25K Tag|WW Historian - Standard, 25K Tag|P/N 17-0472|#Serial Number 1062168 FEATURE Historian_Tagcount Wonderware 9.000 1-jan-00 0 CD6AA90DF8B29AEE9E44 FEATURE InSQLServer_8_Tagcount Wonderware 8.000 1-jan-00 0 1D9A497DC4BA17C0F8CF \ Is it possible to upgrade to current version and use the old data?

[ISS Support Case] Historian - 1 node is not communicating.

He imported the tags but is not getting any data. Node is running intouch 7.1 2020 r2 sp1

[ISS Support Case] Local Historian configuration

Attempting to follow https://softwaresupportsp.aveva.com/#/okmimarticle/docid/tn000022770 to create a Backup Local Historian. Have backed up Runtime db off of Main Historian and restored to Backup Local Historian in SQL Server. Signing into SQL Server on Local Historian as a sysadmin. Get to step 13 in the document and get attached errors when attempting to perform that step. Noticed that none of the local user accounts existed within Security Logins, but thought that the script would be creating those. Do not understand why I'm getting the errors or what to do to fix the issue.

[ISS Support Case] Alarm Comments Arent Being Captured

As of late week, alarm comments arent being captured in the A2ALMB data base. The comment field just states "Lost alarm communication to xxxx"

[ISS Support Case] How to Offline License Activation Historian Client

May be facing an OS reset and hasn't gone through the offline process directly yet, confirmed node is not connected to the internet.

[ISS Support Case] Historian Upgrade

[ISS Support Case] Historian Trend server configuration

Attempting to logon to the server created in the Trend Server Connection server list of a Backup Local Historian. Get the attached error message when attempting to perform the logon. Found https://softwaresupportsp.aveva.com/#/okmimarticle/docid/tn000022756 that is a fix for the issue that was encountered. Attempting to follow the instructions in the TN article. Step 2 in the section "Using the SQL Server Management Console" says to locate the dbo.aaManualTagInsert Stored Procedure. That store procedure is not present in SQL Server of the Backup Local Historian. Many other dbo.aaxxxx stored procedures are present. Unsure why the aaManualTagInsert procedure is not present or how to resolve the issue.

[ISS Support Case] Remote IDAS service stops

Remote IDAS was installed and configured on Wonderware Runtime workstation following https://softwaresupportsp.aveva.com/#/okmimarticle/docid/tn000023017. IDAS was configured on Historian server. Appropriate I/O Servers and Topics were moved to the new IDAS on the server. Wonderware Historian Data Acquisition service starts on the Runtime workstation, but then stops. Historian server shows that "Data acquisition on IP address" is stopped. Windows System log on Runtime workstation shows error 7003, "Wonderware NetDDE Helper service depends on the following server: NetDDE". There is no NetDDE service on the Runtime workstation. According to Microsoft NetDDE is no longer supported. Remote IDAS is currently running on other Windows 10 Wonderware Runtime workstations where a NetDDE service does not appear to exist. Unsure how to resolve this issue. Have attached SMC log from Historian server that references the error.

[ISS Support Case] Change Historian Data Path Folder to D Drive

What is the procedure to change the Data Path for the Historian Circular Folder, currently is on C:\Historian and we want to change that to D:\Historian since this drive have more space

[ISS Support Case] Historian Migration Question

We are moving the current Historian v2020 to a new server and upgrading to v2023. I plan to install Historian 2023 on the new Historian and then replace the runtime database with the runtime database from the current historian and re-running the configurator. I know in previous versions a script needed to be run following this procedure but I cannot find anything for moving from 2020 to 2023. Is there a script that needs to be run on the new server after restoring the runtime database?

[ISS Support Case] Historian Database Import Utility - New Sections - Extended Properties

Need some guidance on using the Historian database export/import tool. There are sections in the export I am not familiar with. what they are used for. :(TagHistory)TagName :(StructureTag)TagName :(AutoStructureTag)TagName :(ReplicationTagEntity)DestinationTagName :(AutoTagHistory)TagName Also, when exporting and reimporting to make changes to tag information; should the tagID be deleted? For example I am exporting the entire database and changing the computer name of all topics and tags and then importing the information

[ISS Support Case] Server has question mark

client is unable to see server settings and information due to the question mark on the server.

[ISS Support Case] Backup of Historian Server

We are having a problem with the backup of our Historian server. Other functions of the Historian server are working as expected. The backup vender is recommending the below fix: To troubleshoot the issue please perform the following: - restart following services in this sequence: 1. COM+ Event System. 2. COM+ System Application Service. This may not be started (if not, start it). 3. Distributed Transaction Coordinator Service. 4. Volume Shadow Copy Service. 5. SQL Server VSS Writer. Would restart of any of the above services impact recording of tag data or any of the other main functions of the Historian server?

[ISS Support Case] Unable to Install Remote IDAS

New Historian Install, getting the following error on the remote IDAS when historian starts up. IDAS never starts. FCSCADAHIST:aahCfgSvc(23.0.000):15284: HistoryService::EstablishConnection: error = 172 (Not in requested group) aahClientAccessPoint::CServerNode::ValidateIntegratedCredential: Authentication failed; user SCADA\FCSCADAHIST$ is not a member of one of these groups: aaAdministrators, aaPowerUsers, aaReplicationUsers, component = aahClientAccessPoint::CServerNode::ValidateIntegratedCredential [HistoryService.cpp, 288] [ServerLog.h, 317]

[ISS Support Case] Remote IDAS service stops

Installed Remote IDAS and WSP2014SP1_Patch02 on a server that has FSGateway installed and needs to cache tag data in the event that the server disconnects from the Historian server. Followed the instructions in AVEVA TN000023017 to perform the install. Have rebooted the server where Remote IDAS is installed. The Historian Data Acquisition service starts, but then stops. The Windows system event log shows the service starting, but the service stops shortly after starting. An error is registered in the system log "The Wonderware NetDDE Helper service depends on the following service:NetDDE. This service might not be installed" (other workstations where Remote IDAS is installed do not get this NetDDE error). One issue to note about this system is that it requires the adjustment for daylight savings time to be turned off. So, the system time on the server where Remote IDAS is installed is one hour behind the current time. Can I assume that the time on the server would need to agree with the time on the Historian Server for the Remote IDAS that was installed to work? If Remote IDAS can still operate with daylight savings time turned off, what might need to happen to resolve the issue with the Historian Data Acquisition service turning off?

[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] Historian Client Lost Connection to Historian Post Server (ESXI) Upgrade

Historian client (.NET control) has lost connection to Historian Server. Happened after servers were shut down and restarted (ESXI upgrade from 5.0 - 7.0) not sure what settings need to look at. Domain Existing installation

[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] Using wwClient to Read Values Across OI, InTouch and Historian

Would like a walkthrough.

[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 not able to start.

Some services not starting

[ISS Support Case] Stuck in SF

standalone serve

[ISS Support Case] Question about OPC UA server issue

Behavior is erratic. 5 ms hiccups every so often as opposed to the usual of around 1 second between storage points. The data source here is OPC UA through OI Gateway

[ISS Support Case] Engineering units not counted correctly

Flow rate is larger than expected. The integral deviser has a value of 1 instead of 60 engineering unit table(updated). Used the query tool to check the interval value is 60(deviser of 60) getting it back in gallons per second but getting gallons per minute. looking in the query tool and seeing the value is not being counted correctly the 2017 historian retrieval PDF page 194 & page 62 2017 update3 SP1 P01

[ISS Support Case] Licenses Are Currently In Use Message

deactivated licenses (offline) Uninstalled / reinstalled product, but is receiving the license is currently in use message.

[ISS Support Case] Validating Microsoft Updates

Running Historian 2020 R2. IT is pushing out some updates, would like to validate they wont have any negative impact.

[ISS Support Case] Disabling IPv6- Supported In 2020

I see in your TN AppSvr300 that IPv6 was not supported by Wonderware products as recently as your update to this article in Jun-2020. Is that still the case? We are currently running AVEVA Historian and Client Historian 2020 R2 SP1 and Wonderware 2014 for Dev Studio and InTouch Runtime. We are not using IPv6, but have not disabled it. We are not experiencing any known issues with AVEVA products on workstations or servers, but we are considering the possibility of disabling IPv6 to reduce network traffic that has been detected as IPv6. Given our current environment is your recommendation to still disabled IPv6? Just wanted to make sure that this is still your position on IPv6.

[ISS Support Case] 2017 License Manger Issue

Initially, the historian server showed invalid tag count error. Looked at license manager and all looked ok. Thought I would try to reinstall the license, so tried to deactivate the server license - all I get is error message sayin in cannot connect to license server on port 55555. Now I show no licenses activated and unable to activate any becuase it cannot connect to license server.

[ISS Support Case] Historian License not activating

We had to restart our historian server and it lost it's license information. When trying to activate through the Enterprise License Manager the connecting either times out or we get an error

[ISS Support Case] Historian Client Installation Error.

Historian Client Error: AVEVA SP 2023 installation, cannot Install Prerequisites for SQL.

[ISS Support Case] Communication Failure after update

After updates communication to the historian failed.

[ISS Support Case] Unknown Historian error

I'm seeing an unknown error in SMC logs on the historian. I've tried undeploying the objects referenced in the logs (undeployed from the Galaxy I mean), and the error still persists.

[ISS Support Case] Fastest Historian Storage

What is the fastest storage period for a discrete value that can be accomplished using a historized attribute in a galaxy object? What is the fastest storage period of a classic discrete tag?

[ISS Support Case] Moving History Blocks from old Server to new Server

What is the recommended procedure for moving history blocks from a Historian version 11,0,002,00 to a Historian version 23,0,000,000. The new Historian has approximately 10 tags that aren't in the old historian, and we don't want the process to delete the data for those 10 new tags.

[ISS Support Case] Historian Migration How To 11.0 - 23.0

The old Historian is still in production. Basically, the client is running both App Server 2012 R2 and System Platform 2023 at the same time. Everything is replicated, both the hardware and software. The last step is to get the new Historian to read all the data from the old Historian so that the old Historian (and all the App Server 2012 R2 hardware and software) can be decommissioned. The new Historian does have a few more tags, than the old one, but we dont have to worry about them because I can run a query on those few tags before migrating the old historian data to the new historian. I tried shutting down the new Historian, deleting all the history blocks, copying the history blocks from the old historian, then restarting the Historian. This almost works, however, the data is spotty nulls occur in places in time they shouldnt, for example. Since just copying the history blocks from the old to new didn't work, I attempted the method shown here https://knowledge.insourcess.com/Operational_Efficiency/Historian/Implement_and_Support/Support_Tickets/Installation_and_Configuration/Installation_and_Configuration14/68223_-_Unable_to_see_data_in_imported_History_Blocks I made a backup of the Runtime and Holding database one the old Historian, copied them to the new Historian, and then attempted to restore them to the new Historian. I detached the Runtime database on the new Historian and selected Restore data base, then pointed to the Runtime data from old Historian. However, I received an error message that the Runtime database cant be restored because it is being used by the Runtime 11 database. See attached screenshot. What should my next steps be?

[ISS Support Case] Historian - cannot commit changes

Historian commit changes error message: This is a new historian setup as a T1 and they are adding topics. 20.1.100

[ISS Support Case] Alarm Client Showing 0 0f 0 Historical Alarms & Events

Alarm Client connects to historian however shows 0 of 0 when configured for historical alarm and events. I can go to SQL Server Management studio and go to the Runtime database and show top 1000 rows of the HistoricalAlarmEvents2 view (by adding the EventStampUTC modifier) and i get entries however I can't seem to have them populate in the Alarm Client.

[ISS Support Case] How to rebuild Historian Search Index

How does one rebuild the index? Thx,

[ISS Support Case] Historian Client 2023 -> Historian 2014 R2 SP1 Not Working

11.6.08001 Server 2014 R2 2012 R2 (domain) Historian Client is 2023 Windows 11 (workgroup) Add Server - Logon > Error One or more database objects required for proper operation is missing, and cannot be installed under the permission granted to the current user. Log on as an empowered user to install missing objects Tried by name and IP address

[ISS Support Case] Historian Showing Tag Count Violation Core Service Stuck Stopping

Historian is showing license violation, License manager CORE service is stuck stopping.

[ISS Support Case] Historian Inquire cant login, excel add in, asking for OS for compat

[ISS Support Case] lost communications on engines/platforms.

Showing null on static tags. Hotfix's were applied.

[ISS Support Case] After a failover objects are stuck running on back up - Unable to Fail Back

Site is indicating after a failover they are not able to fail back. Currently stuck running on AOS2. In SMC getting : Partner Status Standby not available 2020 R2 P01

[ISS Support Case] What's the difference between Value and vValue

Direct email: When querying results getting NULLS for Value Column . What's the difference between Value and vValue

[ISS Support Case] How To Monitor Status Of Historian

DIRECT email: After a recent Store Forward event the client would like to know how can we be notified of Historian disconnect / Store Forward status?

[ISS Support Case] Data Acquisition Module not starting Post Migration Error=127

Migration to Wonderware Historian Data Acquisition Module not starting Error = 172 2020 R2SP1 to 2023 P02 Domain

[ISS Support Case] Problem with Historian

Some tags are not getting values stored in the Historian.

[ISS Support Case] Error when Importing new tags

When importing tags within the IDE the DB load fails with a check the logger message in a dialog box. The message that is displayed in the log is: "Must start line with a tagname, or :keyword"

[ISS Support Case] Enable Late Data option store-and-forward

How do you configure/enable the late data option when the primary IO driver is down? Where do I set the path and enable this configuration? Does that need to manually configure or just enable the option?

[ISS Support Case] Historian Migration Information Request.

Im working on a historian migration from 2017 U2 to 2023 P02. A few questions: I seem to recall a tech note or instructions on how to move over the DB from SQL to keep all the configurations intact, but I cannot locate it in my archives nor find it at AVEVA or InSource. Do you recall something like that, can you put hands on it, and can you get me a copy? Are there any other pitfalls/support docs I should know about? Are there any special install instructions when installing Historian client on a true Terminal Server?

[ISS Support Case] Historian replication not working

Not able to test the connection.

[ISS Support Case] Trend intervals

Timing is off in the trend displays in random intervals. Customer is only able to see data in the trend when using the interval cyclic and though he has it set to update every minute the data comes in every hour.

[ISS Support Case] Null values in the historian

Several tags across different plcs are storing null values for a couple hours at a time, a couple of times per day logs are showing connection issues to the sql database

[ISS Support Case] Service account getting locked on T2 historian

The T2 historian was locking out the service account. Why was this locking out without anyone active on the box? We found it because we kept getting licensing errors on the GR node when trying to open WindowMaker.

[ISS Support Case] Replication Failure

We have a Historian Tier 1 server (logs attached server) that historizes data and replicates to PI server using Aveva Replication method. Currently we do have a different replication method which is in production working fine now. That replication is from Tier1 Historian (not the same server with logs attached) to Tier 2 Historian, from that Tier 2 Historian to PI server using OCPI replication method.

[ISS Support Case] Historian Tread missing data

Historian Trend missing data.

[ISS Support Case] Historian export utility fails to export tags

Historian export utility fails to export filtered tags no matter the data type

[ISS Support Case] Historian data not storing properly

They have multiple PLCs and are expecting the data coming in to be roughly the same, but the most recent historian is showing mostly flat lines as data points. It appears to be updating slowly and when restarting the historian, it takes much longer to start than it should, staying stuck in "IDAS offline" for several minutes.

[ISS Support Case] lost connection on xmas no data

[ISS Support Case] Historian & SQL Connection Failure

Client reached out due to failure to connect to Historian on remote node using Historian Trend and also on Historian Server locally. User was receiving an error message stating that system is unable to connect to SQL server. This was due to both the runtime and holding databases being in pending recovery status.

[ISS Support Case] OPC Tag Added To Historian Not Displaying Data

Tag OPC tag cannot get that thing to pull into the historian. Tried for 2 days. Straight to Historian Data Source Software Toolbox Top Server Already pulling tags from this already. Add a tag that is existing. LIVE ?? Remote Support Possible.

[ISS Support Case] Is Quality Detail 44 Bad

...found a recording that shows how to add a tag. It is working and I am getting the data but I am concerned by the Quality String Pipe Reconnect / Quality Detail 44

[ISS Support Case] Historian Client Connection Suddenly Stopped Working

Historian Connections. Windows 11 PC's that had Historian Client installed. About a month ago they stopped being able to talk to historian. Can connect to it from other servers (2019 and 2022 server) 2 Win 11 machines, fail with generic cant find Historian message.

[ISS Support Case] Historian SQL Connection Failure

Client reached as when user was attempting to view Trends remotely or locally on the Historian they would receive an error stating the connection to the SQL DB has failed.

[ISS Support Case] Disconnected from SQL Server

Client reached out due to user locating this error in the logger from component aaTrendDataSetProvider. The user was having issues with Trends which led them to review the logger. "aaTrendDataSetProvider The configured InSQL server is either Disconnnected from Network or in ShutDown/Disable state"

[ISS Support Case] Aveva not connecting to cloud

No sync backlog or visible errors in logs

[ISS Support Case] Historian filling up the hard drive

Circular storage had over 500GB of data

[ISS Support Case] Historian Client Trend Suddenly Stopped Working

Have Historian 2023 R2 not able to trend any data. Checked Historan LIVE table? (no) Confirmed data is visualized in intouch HMI managed applications and currently working. See's a value LIVE Sees value Historical Values. Been working on historian all day - rebuild index. - HB are there - Shut down and disabled started back up. - Restarted VM - Not able to see data in trend standalone application. Existing system stopped working RB on the trend license status license status (30 demo) copying 5 years of data across the network no way around this. HB are being copied directly to alternate location no way around that

[ISS Support Case] Migrating Historian From 2014 R2 - MDAS Configurations Inquiry

trying to migrate historian date from 2014 R2 application to 2023 R2 Sp1. Looking at a list of MDAS tags and is hoping to export these so they don't have to be manually created. Have almost everything done.

[ISS Support Case] Historian Email & Text How To SQL Database Mail

1yr and a half ago guy i worked with set up historian We have two new PC's historian on one and DEV on another. No SMS needs to move data to a spread sheet (assuming it's coming from historian) and set an email trigger. Objective to email and text 2023 SP ? One video I've seen SYSEM Monitor Alert EMAIL Server now have 2017 no SMS two different plants each plant have 4-5 clients. What I do is just kept with the current process Test in dev If works Move to production Delete the old one (places in a path)

[ISS Support Case] XL Reporter report Generation Failure

Client reached out as user has configured a report in XL reporter that should be recording the start/stop time and running duration of pumps. The report is producing mostly 0's for these values. It turns out that at the end of each scan cycle the system was recording the last reported value which would generally be an end value which led to the report being generated with many end values without start values. Each of these corresponds to the end of a scan period.

[ISS Support Case] Citect to Historian Connector Failure

Client reached out as when user was attempting to configure backfilling historical data from Trends into the Citect historian an error occurred and the connection is now showing invalid/old values.

[ISS Support Case] Historian disconnecting/reconnecting issue

1. contstantly connecting and disconnecting. 2. Status says 3. if they reboot it will work for less than a day 4. All issues started after working on upgrading license server to 4.1.01. 5. Its failing the license check because of a missing feature ( -------------------------------

[ISS Support Case] Historian Replication Configuration Issue Undetermined

two installs of Historian trying to replicate. getting an error defining the replication server on tier 1. Can connect from what will be Tier 2 to the Tier 1 but not vice versa. Where do I define the replication?

[ISS Support Case] Alarm History Migration: Importing Alarm DB Logger Data into Historian

Planning an upgrade from Application Server 2020 to 2023. In version 2020, we used Alarm DB Logger. When we upgrade to 2023 and use the new Historize method so alarm history is in Historian, is there a way to import the old Alarm history?

[ISS Support Case] Historian License Acquisition Failure

Client reached out as the Historian was showing a license tag count violation and there was an error message in the logger indicating the license product service was failing to communicate with the Historian.

[ISS Support Case] Historian Trend Gaps in Data

Client reached out due to the Historian showing gaps in data overnight from midnight until 4 am.

[ISS Support Case] Do State Alarms Contribute to the Licensed Tag Count in Historian?

Do state alarms count against the licensed Tag Count In Historian?

[ISS Support Case] SQL server not able to connect.

[ISS Support Case] Historian Account Mapping Issue

Client reached out as when trying to access the the WWALM DB with read only permissions through Intouch they would receive the following error: is not authorized to retrieve events. Because user is not a member of the groups: aaAdministrators or aaPowerUsers or aaUsers. "

[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

[ISS Support Case] notifications of hard drive capacity

deleting data wants a sample code that will let him know when HDD is full periodically

[ISS Support Case] How to Back Up Restore Historian Runtime

Applying 000034301 Migrating Older Historian Runtime Database to Historian 2017, 2020 or 2023 Questions regarding Back up restore Runtime best practices.

[ISS Support Case] Post Migration Not Seeing Old History

Moved Historian circular blocks to the new system. Can open existing trend files but it's linked to the old historian. I dont see any where to update this. Original 2023.

[ISS Support Case] Historian SDK License Requirements

Direct email: We might look at the Historian SDK in the future. Do you know if there is a charge or license requirement to use the Historian SDK?

[ISS Support Case] Unable to connect to Historian

[ISS Support Case] Vulnerability 'Log4Shell' in Apache Log4j

Which AVEVA products are affected by critical vulnerability 'Log4Shell' in Apache Log4j (CVE-2021-44228)?

[ISS Support Case] Please update Historian Server With Valid Credentials

Please reference case # 88076. During the troubleshooting process the client observed the following message being logged and would like to know where these credentials are updated.

[ISS Support Case] Historian - Not Collecting Data

Since April 10, 2025, no new data was being collected in Historian for a large majority of the tags (anything coming from the Local IDAS). The data for all tags was flatlined.

[ISS Support Case] Historian - Installing w/ Multiple Versions of SQL

[ISS Support Case] Upgraded Historian Tags Changed From IDAS to MDAS

Upgraded Historian from 2017 U2 to 2023 R2 , somehow it's changed all my tags over to application server. It's all Gone. Why did it switch to application server 21H2

[ISS Support Case] HIL2 DC3 HIstorian memory maxed

aahEventStorage keeps leaking memory. Found known issue in this version, fixed in P01.

[ISS Support Case] MDAS stopped updating

MDAS stopped updating on April 2: Historian Client displays Null values for certain tags, despite confirmed SuiteLink connectivity through WWClient. Data does not appear to be logged or visible in trends. Troubleshooting Steps Performed Verified WWClient Connectivity Confirmed successful SuiteLink connection to the IO Server (MDAS). Tested tags via WWClient connection succeeded. However, observed that values were not updating as expected, or returned with poor quality. Historian Reindexing Followed the official procedure (InSource Tech Note) to reindex Historian: Shut down and disabled Historian. Deleted contents of the following directories: D:\Historian\Data\SearchIndex\files D:\Historian\Data\Logs\SearchIndex D:\ProgramData\ArchestrA\HistorianSearch\Logs Re-ran Historian Configurator with Reindex selected. Restarted Historian service. Ran Change Network Account and OS Configuration Utility Executed tool to ensure proper DCOM permissions and service account configuration. Validated results and confirmed account consistency across services. Verified Time Sync Configuration Time Sync parameter on IO Server is set to 1, meaning timestamps are sourced from the PLC/device. Identified potential for timestamp mismatch if PLC time is unsynchronized. Recommended temporarily setting Time Sync = 0 to force server time for debugging. Historian Tag Quality Verification Since the Excel Add-In is not in use, may need to query tag values directly via SQL in SSMS: query: SELECT TOP 100 DateTime, Value, QualityDetail FROM Runtime.dbo.History WHERE TagName = 'SampleTag' ORDER BY DateTime DESC; Analysis of QualityDetail column ongoing to determine whether Historian is rejecting values due to poor quality (e.g., 0x00, 0x40). IO Server and Data Flow Checks Confirmed IO Server service is running. Verified that data is configured to collect from the appropriate source. Reviewed tag configuration in Historian Admin (scan rate, deadband, collection status).

[ISS Support Case] Historian - Tag Count Violation

[ISS Support Case] Historian License Tag Count

Customer has a 5K tag license but noticed that Historian is only showing 500 Allocated Tags.

[ISS Support Case] 68GB worth of data created by SSM

sentinel system monitor simhost service account 163533 files 68GB 3/2021 - 12/2022

[ISS Support Case] grabbing wrong license

historian grabbing incorrect license count

[ISS Support Case] Historian - Upgrade

Customer planning to do a WW upgrade. Regarding Historian and licensing they are trying to make a seamless transition. They have 2 Historians right now.

[ISS Support Case] Replication Failure for specific tag

Error Message: Main Replication failed add non-streamed value to HCAL: destination tagid CD2FAE2B-*-*-*-*: error = 127 (Tag not found) in historian. I searched for this tag id in both Tag and ReplicationTagEntity tables and could not locate.

[ISS Support Case] Issue with Historian Web Interface

When zooming in, the trend line disappears.

[ISS Support Case] Backfilling Historical Data

Client reached out looking for guidance on backfilling missing Historical data after standing up an upgraded Historian server.

[ISS Support Case] Questions on installing historian and sql

they want to know the necessary configuration for sql server when installing it before installing historian

[ISS Support Case] Cannot connect to historian server

new installation able to ping the server logon warnings in the logger

[ISS Support Case] Migrating Historian Data

Client reached out looking for guidance on migrating or importing old Historical data to a new Historian server.

[ISS Support Case] Tier 2 historian replication backfil data

Client reached out inquiring about backfilling data on the Tier 2 Historian for a tag that recently began being replicated.

[ISS Support Case] Where are Dashboards Saved In Historian Client Web - Open aaTrend Files

Historian Client Web Just got the 2023 Version If I have a .aaTrend File with Client Web When creating Trend files what is the file path where they are being saved. Are they actual files saved on the machine what's the default file path. Classic vs Modern look Classic Create Browse Modern Look Create Browse -

[ISS Support Case] Installer not recognizing existing historian installation

They have installed SQL Server 2022, but the historian installation wants to install it over top

[ISS Support Case] Historian Security Update

Is KB5058721 supported with Historian 2023 R2?

[ISS Support Case] Historian Data Importer Failure

Client reached out as when attempting to import any CSV data into the Historian data importer it fails with the same error message: "Error processing the file. Error in line number 2. Unsupported delimiter." This was tested with multiple unique CSV's exported from both Query and Trend.

[ISS Support Case] wwClient Guidance Supporting Doc Request

ref: 98843 requested meeting recording Requested wwClient walkthrough and supporting documents. - OI validate - Historian validate aaHOISvrSvc

[ISS Support Case] Configuring Store Forward Detail Request

Reference case 98835 Client mentioned on a teams that currently they loose data during incidents. Store & Forward is not configured. Requested information on

[ISS Support Case] Migrating Historian Server

Client reached out requesting guidance on migrating the Historian database from a server running Historian 2020 R2 to a new server running Historian 2023 R2.

[ISS Support Case] Tier 2 Historian backfilling Replication Data

Client reached out requesting guidance backfilling data on the Tier 2 Historian for a tag that recently began being replicated.

[ISS Support Case] Antivirus and Firewall Documentation

Looking for documentation on Antivirus exceptions that need to be in place and Firewall documentation showing what ports are used.

[ISS Support Case] Historian Tier-1 to Tier-2 Replication

After importing Historian replication info and deleting all the old server replication tags, unable to delete the old replication server. Still says replication tags exist on the server.

[ISS Support Case] Elasticsearch CVE question

Elasticsearch getting flagged as a vulnerability.

[ISS Support Case] Historian - Power Outage

Issue with Historian database for AVEVA Edge. They had a power outage and their Trends are showing as blank. In the Historian folder it is recording the data. They did try changing the timeframe around and it only showed data before August 10.

[ISS Support Case] Historian Connection

Client is having an issue acquiring data from the Historian. Attempts to "drop database" and configure from configurator result in error. Data acquisition section of Historian is showing data is being acquired from the wrong node. Client is not able to access data in Historian Trend or via SQL Query. Viewing the runtime database in SSMS does not show the database tables so there appears to be an issue with the runtime database.

[ISS Support Case] Historian - Questions on SQL

Customer asked if on the Historian, there's supposed to be a GR db folder? Had some other SQL related and user/group related questions.

[ISS Support Case] Restore Historian

Import previous historian and restore it

[ISS Support Case] Historian In Stopped State

Historian seems to have stopped storing data. In the SMC, a few of the Historian Modules, including Storage, are showing in a STOPPED state.

[ISS Support Case] Cannot Retrieve Data From Historian

Historian is up and running, all modules show Started and Data Acquisition shows it is receiving values. With all of that, we are unable to retrieve any values other than System Tags from the Historian.

[ISS Support Case] Historian stopped logging data after adding IDAS data source

Client is seeing the following errors in Historian: AddValuesfromSre failed to add value tagid. storeforward not enabled.

[ISS Support Case] Historian disconnected

They had a service (aahcfgsvc) that was unable to start yesterday and after rebooting it says disconnected Cannot configure search index "Object reference not set to an instance of an object"

[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] Historian Trends Missing Data

Client reached as when viewing InSight based on Tier 1 Historian datasource there is a gap in the data over a few hours. (Flat lines) This gap is not present when viewing the data within Historian Trend or Query.

[ISS Support Case] History Cannot Be Retrieved After Migration

After migrating Historian from 2020 to 2023 R2, following the migration tech notes, no historical data is being retrieved. NEW data seems to be coming in fine.

[ISS Support Case] InSight Missing Data

Client reached as when viewing InSight based on Tier 1 Historian data source there is a gap in the data over a few hours. (Flat lines)

[ISS Support Case] Historian Not Importing LGH Data

Historian is flat lining new data every day. The way the customer recovers from this is to wait until the next day, shutdown and disable Historian, delete the History Block for the previous day and then import LGH data from their InTouch app into Historian. When that works, then the data shows correctly in Historian. But then the current day's data is still flat lined.

[ISS Support Case] Historian Showing Gaps in Data

Client reached out as after store forward events the data is not properly being loaded into the Historian resulting in gaps in data.

[ISS Support Case] SQL upgrade questions

Historian install, upgrading to Flex license. SQL configuration questions

[ISS Support Case] Some Users Are Unable to Add Replication Tags

Chat request: I'm unable to add new replication tags on one of our historian servers with certain users

[ISS Support Case] unable to log into the historian

newly created user cannot log in to the historian

[ISS Support Case] Updated Demo License Request

Have a situation getting demo licenses. Expires every month. New to this role, calling to get updated licenses. has Historian Historian Client InTouch ITME Described intermittent outages in historical data from a particular PLC, Any guidance? (need more detail mentioned wwClient). Client recalled a vendor who indicated there was some work to be done at the communication driver level in regards to this. - wwClient Seeking any information to assist with getting up to speed with the product. - eLearning

[ISS Support Case] high cpu usage on the historian

CPU showing 100% utilization at all times across three main tasks aaIndexSvc.exe aahStorage.exe aahRetrieval.exe

[ISS Support Case] How to Connect Excel (Add In) to Historian

Direct Email: I recently installed Aveva on a new computer and all is working fine but I would like to connect the historian on Excel sheet to pull data from Aveva points. Can you please provide me instructions or support, we have two other computers that have the Historian add in working on them just not sure how to get it to connect with my new computer.

[ISS Support Case] Intermittent historical data acquisition issue wwClient General Guidance

ref case 98483 Client described occasionally having issue with historical tag data. Currently onboarding seeking general troubleshooting guidance and any training resources available.

[ISS Support Case] How to Historize Data from a Data Table

2020 R2 SP1 Data is in a Table in SQL server 12 tags not sure how to get them historized integers coming from a SQL server. Numbers 1-6 not sure on meaning just yet.

[ISS Support Case] Frozen Data in Reports from 12:00AM to 7:00AM Affecting Both New and Old Systems

would like to revisit 97874. Having some issues with my Historian. Running InTouch 2023 R2 It seems like whenever the day rolls over and the new circular file is being created. Trends are unavailable for 6 hours period. On the trends everything is paused until the next days Historical data file is created. around 1:30 will see data again until the following day. Client runs ARFO which confirms the existence of an issue when pulling data during the 'frozen data' period. Data coming from a Managed intouch application using LGH files MDAS Tags pushing data to Historian (using history block's) Historian Trend .NET control Historian Trend Standalone application issue affecting multiple controllers From midnight - 6AM there are times where there is a blip of 15-20 minutes where the data is accessible but it goes away until after 12:30 PM

[ISS Support Case] Historian Remote IDAS Configurator

After installing the Remote IDAS Component on a machine, the Configurator popped up asking for a username and password. Customer believes that they may want to change the user designated here in the future but is not sure how to relaunch this Configurator. Currently, the Configurator he is looking at with the Historian part contains ONLY that. Going to Start > AVEVA > Configurator opens a separate instance of the Configurator and is MISSING the Historian configuration section.

[ISS Support Case] Historian login issue, windows integrated

Computers were wiped after a change in company. He tries to login to Historian and gets an error message. Caller and another person are having issues logging in to Historian He is not sure if he can login to sql.

[ISS Support Case] Historian Remote IDAS Setup

The IDAS is showing up as offline.

[ISS Support Case] Historian stuck in store and forward after moving the advanced historian

They moved their advanced historian outside the network during production and now their tier 1 historians are stuck in store and forward. They are concerned that they will have orphaned data if they stop and start the historian after updating. tested connection over the replication port through powershell, and it shows a good connection

[ISS Support Case] Data Flat Lining Occasionally

Almost, if not, daily, Historian is showing a flat line for data usually starting around midnight and ending somewhere around 7 AM. The next day, this same data that was flat lined will show correctly and the CURRENT day's data from midnight to about 7 or so will be flat lined.

[ISS Support Case] Filling in missing data on tier-2 historian,

Client is upgrading old tier-1 historian from 2014 R2 SP1 to 2023 P03. The old Tier-1 had an issue where the server lost some amount of data and did not replicate to tier-2. Client has the new tier-1 running side by side and this missing data is on new tier-1. Client is seeking best strategy to get consistent data up to tier 2 and get everything filled in on new system. Client has attempted to export data via SQL Query and import via fast load but getting error: "Importing data for tier 2 tags not allowed".

[ISS Support Case] Historian - Data

Good, morning We have a windows server 2025 edition running Aveva Historian 2023 R2 Sp1 23.1.100 and for some reason randomly it stop recording any data. A reboot seems to fix the issue but from the time the issue starts until reboot all data is lost. I have attached the historian logs from our most recent data loss can you help get this fixed, hard to rely on data that is nonexistent.

[ISS Support Case] New Historian Tags Not Collecting Data

Newly created tags in Historian are showing as NULLs in Trend.

[ISS Support Case] Historian Upgrade Inquiry

Client reached out looking for guidance on upgrading Historian 2014 R2 to 2023 R2.

[ISS Support Case] Trends Flat Line from Midnight to Around 6 AM

Historian 2023 R2 Customer has data that they are looking at for the day. Sometimes, the trend will show a flat line from midnight until a later point (6 or 6:30 AM). Eventually, that data will come back. If they look at it the next day, the data will be there.

[ISS Support Case] Historian Upgrade Failure

Client reached out as when attempted to update to intermediary step of System Platform 2017 as part of the overall upgrade from 2014 R2 SP1 to 2023 R2 the upgrade would fail with the following error message: "You must uninstall the following products before setup can continue: Wonderware InTouch 2014 R2 P01 or Older"

[ISS Support Case] Historian Missing Data

The client reached out as the Historian was showing missing data for a few hours, but the connection to the PLC from the remote IDAS was actually corrupt.

[ISS Support Case] Enabling Historian Excel Add-In

Client is seeking assistance adding Excel add-in to historian.

[ISS Support Case] System Management Server Configuration Failure

Client reached out as after setting up a new System when attempting to configure System Management server to connect to existing SMS on the Historian server it failed.

[ISS Support Case] InTouch LGH File Import Failure

Client reached out as when Importing Data from an InTouch History File the data does not seem to be created in the History blocks. This is after a migration from 2014 R2 SP1. The process completes without error but no new data is inserted/created.

[ISS Support Case] Replication Failure

Client reached out as after configuring simple replication from the Tier 1 Historian to the PI Server the replication was failing.

[ISS Support Case] Replication Stuck in StoreForward After Upgrade

After upgrading a Tier-1 Historian to 2023 R2 SP1, it is no longer connecting to a Tier-2 Historian (2017 Update 2) and is stuck in StoreForward.

[ISS Support Case] Unable to reach historian server

Make sure historian is running message

[ISS Support Case] Historian has stopped recording data

The client's Historian has suddenly stopped recording data for all tags. Client has not taken any troubleshooting steps thus far aside from restarting Historian services and reinitialize IO topics. Machine is also the IO server. Client is not experiencing any communication issues. Client is not able to reboot machine as it is in production. Everything is showing green under status. Data Acquisition is showing red. 2023 R2 SP1

[ISS Support Case] Historian License

Even though a 5K Historian Tag license is installed, the OCMC still shows a tag limit of 32 and is coming up with a license violation.

[ISS Support Case] Historian Showing Tag Count Violation

After moving a VM from one host to another, Historian has stopped getting its license. It shows a Tag Count Violation in the OCMC and shows an allocated tag count of 32.

[ISS Support Case] Excel Add on

Not able to add it. Possible wrong syntax.

[ISS Support Case] Client Access point will not start

.Net not installed correctly. Error in event viewer.

[ISS Support Case] How to Setup Historian Client Web

Customer wants to know how to setup and configure Historian Client Web and if it requires additional licensing to use.

[ISS Support Case] Not seeing any data update to InSight

This was previously working

[ISS Support Case] InTouch HMI Failing to Historize

Client reached out as after migrating an InTouch application the tags within the HMI application are failing to Historize.

[ISS Support Case] Tag count violation after reboot - Historian

Client was getting a "tag count violation" in the Historian after a monthly scheduled server reboot. Historian was grabbing the incorrect license.

[ISS Support Case] Historian not replicating to PI

This used to work fine but after using the backfill utility in June, it's been stuck in store and forward. Local Historian works fine Replication to Insight works fine as well 15 other Historians are replicating to the PI server just fine The connection to the PI replication server says it's a successful connection "Storage not read to receive data" in the logs

[ISS Support Case] Historian SQL

Found SMS was not configured - set to no SMS to match other nodes. Found Historian was configured for regular SQL instance, was missing the \sqlexpress since they are using express. OS error when trying to configure Hist, unable to create the mdf due to access denied. Verified logged in user and CNA user both local admins and gave local admins full control over the sql folder/subfolder, no change.

[ISS Support Case] Tier 1 Historian Logger Error and Warning Messages

One of our tier 1 historians is constantly logging the following two errors: 1) 5172113 1/31/2025 3:13:04 PM 10912 3028 Error aahRetrieval Retrieval waiting period of 00:05:00.000 for response is expired for storage id: 00000000-0000-0000-0000-000000000000 named pipe aahStorageEngine\console on localhost QID 11266, queue state currently is not in queue, size 0 (false), time 2025/01/31 15:13:0... 2) Main Replication failed add non-streamed value to HCAL: destination tagid 37ACDFBD-5BFB-442B-BDC2-3CC3ED72A621: error = 127 (Tag not found) [WHIST2201; aahReplicationServer.cpp; 2195] Needing some assistance to figure out how to clear these up.

[ISS Support Case] Creating new IDAS

IDAS not starting/in a stopped state.

[ISS Support Case] PI System Management tool question

It sounds like he needs assistance pushing Historian data to PI.

[ISS Support Case] IDAS Tags Removed when Historian is restarted

The client reached out as the Historian IDAS tags seem to disappear from all three topics when the Historian is restarted. The user has saved an export and is manually importing them each time this happens.

[ISS Support Case] Historian Replication Inquiry

Client reached out inquiring about whether they could replicate tags from one Tier 1 Historian to another Tier 1 Historian.

[ISS Support Case] PCS.Discovery.local warnings

Client reached out due to repeated warnings in the logger from component PCS.Discovery.Local: "this listen URI 'net.tcp:///ABService/InTouchDataV3Service' of Discovery Entry)" These warnings do not seem to be affecting operation at this time.

[ISS Support Case] Tier 1 and tier 2 replication not working

[ISS Support Case] Tag Data SQL Query Inquiry

Client reached out looking for direction on querying tag data from the Historian DB.

[ISS Support Case] Historian SQL Connection Failure

The client reached out as when user was attempting to view Trends within Trend client the SQL connection was rejected.

[ISS Support Case] Historian systimesec not updating

Not updating in Intouch view. Queried value in runtime.dbo.live view, systime tags showing days old values. Status in OCMC shows all good, correct time values. Nothing in Event Viewer or OCMC logs for the time values stopped updating. Historian taking an abnormal amount of time to shutdown, client opted for reboot instead.

[ISS Support Case] Historian IO Address Replication

We have one site that we are migrating users to use the Tier II historian. These particular users are used to searching based on IO address field. We are curious if there is a way to replicate that to the Tier II as well. Instead of the defaulting to the local MDAS/IDAS value. I can supply some screenshots for further clarification as well.

[ISS Support Case] Historian Store Forward Error

Client reached out due to the following error being repeated in the logger: "Store/forward Storage(C:\Historian\StoreForward\LocalAutoSummaryReplication) failed to load file C:\Historian\StoreForward\LocalAutoSummaryReplication\A000000_001\taginfo.dat, error = 18 (Invalid file identifier) fileid read requested returned 0 instead of 21587 [Historian Hostname; HistoryBlockMetadataServer.cpp; 447]"

[ISS Support Case] sql reporting services doesn't exist

trying to configure Alert Email service and they get the message that sql reporting services doesn't exist and they cannot get it to work The Historian event tags are not recognizing their email program eM Client which is set as the default email program.

[ISS Support Case] Historian - Upgrade

[ISS Support Case] Historian login issues

They want to be able to log in with a sql account using multiple InTouch scripts but are unable to log in with anything but windows authentication

[ISS Support Case] Historian not seeing a license

On 4/18, Historian stopped recognizing the license. Now it is not seeing a .loc license either. Issue occurred after installing hotfix below. ------------------ AVEVA Enterprise License Server and Licensing Platform 4.1.0 Hot Fix for IMS 3712176 release Resolved Issues: 3712176 - Wrong feature is requested and acquired when reservation is checked out Solution: 3712176 - Modified the license acquisition flow to first check the checkout store for a checked-out license; if unavailable, it now verifies the license status on the server and retrieves it (if status showing as checked-out) to the checkout store before proceeding with license acquisition.

[ISS Support Case] Histroian Failed to get idas configuration version

2014R2 data aquisitions idas Issue Summary: After migrating the Historian Runtime database to AVEVA Historian 2017 Update 3 SP1, the Industrial Data Acquisition Service (IDAS) fails to start, with logs showing the error: "Failed to get IDAS configuration version."

[ISS Support Case] Historian issue

Auto summary messages causing errors in logger.

[ISS Support Case] HIstorian going into demo mode

License not able to grab.

[ISS Support Case] tag count showing 500 when he has 2000

The license still not good, tired of getting demos

[ISS Support Case] Local Tier-1 Historian not replicating all tags to Tier-2 Historian

Client has set up replication on five local tier 1 historians to replicate to tier 2 historian. 4 of them are replicating correctly, but one is only replicating 185 out of 4500 tags. Replication was configured the same on all Historians. Nothing noticeably different

[ISS Support Case] Compatibility questions

They wanted to know if a certain update was compatible with their version of system platform

[ISS Support Case] Tier-1 and Tier-2 Historian data appears to be different

Client is migrating from 2017 U3 SP1 P01 to System Platform 2023 R2. The old and new systems are currently running in parallel. Client has configured seven tier-1 historians to replicate to a tier 2 historian via simple replication. Client is currently getting incorrect tag/object reference data on the tier-2 Historian. All tier-1 historian information appears correct.

[ISS Support Case] Post Tag renaming utility Not Able To Query

Did some tag renaming this morning, I was able to shut down the historian. I thought i did the tag renaming correctly after that whole process the historian is not querying anything at present. Virtual Machine see some error stuff that started yesterday. Tag renaming around 8:50 thought it completed successfully. Value started saying NULL before the tag renaming took place around 8:20 AM

[ISS Support Case] Excel 64 bit work on 2023R2SP1

[ISS Support Case] Historian - Error when running SQL Script

Customer was trying to take data from Historian, manipulate it, and re-insert it back into the DB.

[ISS Support Case] Alarms not historized

they are historizing everything else correctly and have it set up the same way but alarms will not historize

[ISS Support Case] Historian Migration - Data Path and History Block Path

Customer is working on migrating a Historian to 2023. He ran through the queries from https://softwaresupportsp.aveva.com/#/knowledgebase/details/000034301?lang=en_us. They store their data on the E: Drive, but the Database Path and Data Path in the Configurator still show as C:

[ISS Support Case] Historian license only showing 32 Tags

Client is having an issue connecting to the license server after renaming the license server.

[ISS Support Case] Replication Issue Undetermined Stuck In SF

Looks like the data stopped replicating around 05/07/2025 @ 3PM. Logs Replication Status stuck in store forward. Test Connection in the replication work fine. Stuck in store forward.

[ISS Support Case] Historian Error

Client reached out due to the following error being repeated in the logger and flat lines being shown in data retrieval: "Main Storage Exception caught: error = 33 (Invalid snapshot signature) file = D:\Historian\Data\Circular\A250311_001\original.dat, component = Storage, et = {0 1 3 5 7 8 9} [HUNWWHIS01; Dispatcher.cpp; 3752]" The Historian appears to be in valid running status.

[ISS Support Case] Historian Migration

Client reached out looking for guidance on migrating History blocks and runtime database to a new Historian node.

[ISS Support Case] Tags not historizing after network switch change

Some tags reporting null in hist. Data flowing to Intouch. Most tags from the same PLC are historizing. Restarted ABCIP - no change. All tags not working are on 1 engine. Redundant setup, backup shut down for unrelated issues since before issue began. Undeployed/redeployed engine - no change. Verified data acquisition all green with a rate. Reindexed search - no change. Now all data from engine is not reporting to HMI. Restarted ABCIP - no change, see values changing in SMC.

[ISS Support Case] Historian Migration Inquiry

Client reached out looking for guidance on migrating History blocks and runtime database to a new Historian node.(Moving from a physical machine to a VM)

[ISS Support Case] Need Help Optimizing Overflow Data on Historian

Going to clarify with Aveva on seeing what are best practices for this.

[ISS Support Case] Error message

Question about repeating message in logs. Confirmed no issues with the system. Confirmed data storage and retrieval working as expected.

[ISS Support Case] Data in Old History blocks is not available

Upgrading a Historian The history blocks copied from 2017 U3 to 2023 See's HB Reindex HB Gone in Data Index folder. AIHistory Column is 1 for all the Analogs. Stood historian up last Tuesday. 4th location at this plant. This is the anomaly other 3 are working.. Selected main partition and selected rebuild index Shut Down and disabled historian Cleared index manually. Set AI History to one.

[ISS Support Case] Looking for guides or Tech notes on how to enable store forward

[ISS Support Case] Historian Missing Data

Client reached out as the Historian is missing data for an 8 hour period. (showing flat lines) When reviewing the logs observed the following error messages: IDAS Topic connecting (topic name; handle) CYTPENPWSQL01; \\FLPE-P-HDC.DANAHER.ORG\DASABTCP|HDC-5F:367707304 [CYTPENPWSQL01; IOServer.cpp; 353] Data reception timeout: reconnecting (topic name) (CYTPENPWSQL01; \\10.3.77.59\DASMBTCP|TCU) [CYTPENPWSQL01; StorageNode.cpp; 865]

[ISS Support Case] Historian Grabbing Dev License

Historian is grabbing a development license (500 tags) rather than the actual Historian license from the License Server node.

[ISS Support Case] Connection to historian does not work for all users

this has not worked before connection to history blocks data storage failed on server: server name works for some users but not all

[ISS Support Case] Historian 2023 Summary Query

They have a server in a different time zone than their client and are trying to retrieve 24 hours of data in a query.

[ISS Support Case] Tag Event Emails Not Sending

Client reached out as Tag Event Emails configured within Historian stopped working without any warning or error.

[ISS Support Case] Import Tags into Historian

Customer has an existing 10.0.100 Historian that he wants to bring some new tags into. Needs the import process and only bringing in a certain subset of tags from the app, not everything. When trying an import, received an error saying that Transaction Log for the Database Runtime is full.

[ISS Support Case] Replication not working to PI Server

It was working for several months, but stopped working properly sometime in June Status is unknown after shutdown/disable and enable/allow to run. They don't think they've made any changes The PI side gets the handshake from the Historian before the connection immediately drops

[ISS Support Case] Missing Historical Data

After migrating the Database there seems to be Historical data missing when viewing it in Trends and and null values for those same dates within Query.

[ISS Support Case] Historian - Security Vulnerability

They have another software on the same server as a Historian. They wanted remediation plan with Historian to upgrade. There are 2 vulnerabilities with Windows Server 2012. Sentinel LDK License Manager has the vulnerability in it.

[ISS Support Case] Checking if Data Acquisition is working

[ISS Support Case] Historian Client - Missing Data After Upgrade

Customer took a 2012 historian and upgraded it on new machines to 2020 R2 SP1. Everything is up and running, but there's about 11 days of missing data from this month on the new server. But the data is in the old server.

[ISS Support Case] Historian 2023 Two Hour Static Data

Client reached out as they were intermittent gaps in the Trend and Query data. Flat lines or static values depending on where the data was viewed.

[ISS Support Case] Historian Configuration Service Won't Start

After upgrading from Historian 2020 R2 to 2023 R2 SP1 P01 (single node, in-place upgrade), Historian Configuration Service will no longer start and Historian is stuck in a Disabled state.

[ISS Support Case] ERROR: Folder does not exist (D:\Historian\Data\DataImport\FastLoad) [DBIVTK02; InsertFastLoad.cpp; 200]

Client reached out as the following errors are repeated in the logger after migrating the Historian database from one Historian server to another: ERROR: Cannot create notification event for folder (D:\Historian\Data\DataImport, 21, The device is not ready.) [DBIVTK02; insertcsv.cpp; 1685] "ERROR: Folder does not exist (D:\Historian\Data\DataImport\FastLoad) [DBIVTK02; InsertFastLoad.cpp; 200] " This directory does not exist on the new Historian server.

[ISS Support Case] Attempt to contact the License Server to refresh product license has failed

On the Historian machine (also houses the GR), a warning appears every three to four hours: Attempt to contact the License Server to refresh product license It then calls out the Historian license. In the OCMC Historian Status, nothing changes there. It still shows as licensed and has not failed.

[ISS Support Case] Units & Description For Historian Tags Missing SRC ITME

Have a senior chemist who gets into the historian. He noted some of the trend tags do not have units or descriptions entered. Hoping to get some guidance on this Using Trend Sees no description Sees no units ITME 8.1looked at project tags. - confirmed sees neither a unit or description

[ISS Support Case] SQL Historian v17.2

Question about memory limits

[ISS Support Case] Historian - Questions

Customer had two questions: 1) What OS does 2014 R2 SP1 work with. 2) What version of Excel is compatible for the add in.

[ISS Support Case] Historian - No Data

They are trying to set up a System Platform 2023 R2 SP1 environment. He's done a handful already. This is going to eventually take over for a 2023 base system. As he's testing, the Historian doesn't want to talk to the AOS servers. If he looks at Log Viewer on the AOS, they all say failed to connect to Historian, certificate not found.

[ISS Support Case] Historian Server - Delete Unused Tags

Is there any way to know if there are data tags that are either not used or not queried. I am looking at cleaning up the Historian tags we have collected that are not used.

[ISS Support Case] Historian - Questions About New System

If we would like to go with Windows server 2022 version on a new Historian server, what would you recommend on server specs like CPU, RAM, Hard Drive space, etc.? what version of Historian would you like to recommend? We do need Excel to work with Historian and generate report from process data recorded in Historian. What excel version will that be? Thanks!

[ISS Support Case] Historian Tag Import Failure

I am upgrading a Historian and combining two together. I have removed one of them and am trying to Import the node on a different machine. I have deleted all the tags and everything related to the Old node, but during Import it keeps failing and says "Error occurred during import. The name already exists in this group. The group will not be created." I have no idea what "group" it is talking about.

[ISS Support Case] Trends not working on 1 machine.

[ISS Support Case] Historian Migration Tech Note Clarifications

In TN 000034301 - Migrating Older Historian Runtime Database to Historian 2017, 2020 or 2023, when updating the Storage Locations, it mentions that AutoSummaryData and MAIN Data paths need to be different. Wondering what the AutoSummaryData vs Main data paths are. In that same section, it gives examples of paths for each storage location and says to replace "x" with the appropriate Drive letter for your system. But two of the examples have "C" in them instead of "x"

[ISS Support Case] Historian not collecting data after migration

migrating from 2014 to 2023R2 They can't get the data from the topics into the historian, but they can see it in InTouch just fine.

[ISS Support Case] Configuration Service Failed to Connect to HCAP on Node Error=242

Customer has a GR/Historian node and a remote node. On the GR, it is throwing a warning: "Configuration service failed to connect HCAP on *remote node* error = 242"

[ISS Support Case] Unable to Start Historian Client Access Point

Client reached out as Historian Client access point was showing as stopped in the Historian status tab in the Operations Control Management Console. The following error was also observed in the logger: "CRITICAL: Unable to start Client access point [Iocal server name]; aahCfgSvc.cpp; 3775]" When attempting to start the service manually it would fail with error 1053.

[ISS Support Case] Invalid Historian Registration Login Credentials

Client reached out due to the following error in the logs on the Tier 2 Historian: "9356206 9/30/2025 10:18:48 AM 5480 9880 Warning aahCfgSvc Please update Historian Server properties with valid credentials (on client computer) (hostname) [hostname]; Status.cpp; 640]"

[ISS Support Case] No Values From Historian

Unable to connect Aveva Historian to Citect application. Citect 2018 Historian 2020 Citect connection status for both citect and destination is showing connected.

[ISS Support Case] Tier 2 Historian Shuts Down Randomly

Since October, randomly the Tier 2 Historian will turn itself off about every two weeks. SMC Error states "Data packet was rejected and lost"

[ISS Support Case] 2020R2P01 Historian Client Web UI Lags Unresponsive

Frequently see this "Page Unresponsive" error on Aveva Client Web. What's the problem? Client Windows 10 Using Chrome New Install *Video 12/08/2019 - 1/06/20 (5:00) Client Web slight delays updating UI (6:10 - 7:56) delays updating UI (8:10 - 10:00) Client Web Last 30 Days unresponsive *SMC Logs (1.6.22 5:26 PM 5:29PM)

[ISS Support Case] SMC Reporting Historian Errors

The following 2 errors started and are repeating every 5-6 minutes. 9925911 1/4/2022 10:21:45 AM 13148 30560 Error aahStorage Main Storage exception caught: error = 28 (Invalid argument) invalid time offset size, et = {0 1 3 5 7 8 9} [VA03YWVDB0100; QueryServer.cpp; 1176] 9925912 1/4/2022 10:21:45 AM 9448 12640 Error aahRetrieval Retrieval failed to call NextQueryValues for QID 134101748, error = 28 (Invalid argument) invalid time offset size [VA03YWVDB0100; AsyncDataCacheSource.cpp; 353]

[ISS Support Case] Tier 2 flat line from 1 Tier 1

Tier 2 flat line from 1 Tier 1 version on both is 11,6,19102,000 Replication - Replication Problem?

[ISS Support Case] AVEVA Management Console OPC UA Configuration

three separate networks with Siemens Controllers wants to start pulling tags to the Historian Im currently using the Siemens OPC UA and OPC DA on another machine using some reporting software that we have been using within the organization for quite sometime. I want to utilize the OPC to gather data on the Wonderware Historian Software, but Im scratching my head a bit because I dont want to have to add a bunch of network cards to the machine to get my data from the various Processors throughout. Do you have any documentation on setting up a Siemens OPC Server Instance within the Aveva Management Console. If you need better details on what Im trying to accomplish give me a shout at one of the numbers below. This is a WINCC SCADA system that Im trying to connection to the Historian that we have onsite.

[ISS Support Case] Historian 2017 17.3.100

aahcore unable to connect to sql server failed to make a connection to configuration db

[ISS Support Case] Tier 1 Historian High CPU Usage

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.

[ISS Support Case] T2 not replicating and showing null when trying to trend tags

Similar 80599

[ISS Support Case] Unable to Access Historian

Cant expand the Historian option in the System Management Console

[ISS Support Case] Historian Showing as Unlicensed

Licensing issue with Historian upgraded license to XML In SMC license status tag count violation (32 licensed) Pulled up license manager has 5 concurrent licenses licensed locally

[ISS Support Case] Historian Client Unable To Add Server In Server List Configuration

Under Server List Configuration Failed to connect: Unable to reach INSQL/Historian server, make sure that INSQL/Historian server is running

[ISS Support Case] Looking for help restoring a runtime backup.

The client has recently upgraded and is looking for assistance restoring a backup Runtime database.

[ISS Support Case] Questions on migrating Historian and the Runtime database

Questions on migrating Historian and the Runtime database

[ISS Support Case] cant see values in historian

cant see values in historian quality = 0 and only 4 tags are returned on live other than sys tags - total tag count used is 404

[ISS Support Case] Reacquire Historian License

User deactivated their development license and was concerned about the Historian no longer running

[ISS Support Case] unable to connect historian client to historian

Problem was Historian Configuration Service died and start service or reboot takes care of ole db provider for linked server see No 11143, 11214, 11416, 11517 in smc logs for 1/28 version client 20.1.001 Sat Morn clients kicked off Server Connection for Hist Client 1/22 2020 and 2019 Server OS, client nodes Windows 10 Sat 1/22 clients kicked off historian 6:30AM 1/28 client connect problems and flat line

[ISS Support Case] Historian query and key

When copying back history blocks that were archived off of a Historian does the Historian process have to be shut down? I have two years worth that I need to copy back the query. Also, what is the data base key for tags. The tagname itself or is there a number ID somewhere.

[ISS Support Case] Historian query and key

When copying back history blocks that were archived off of a Historian does the Historian process have to be shut down? I have two years worth that I need to copy back the query. Also, what is the data base key for tags. The tagname itself or is there a number ID somewhere.

[ISS Support Case] Monitoring End device Runtime Hours

Question; Is there some way to query historian and get runtime hours each day for an end device? Described having end devices via IDAS Would like to query via SSMS

[ISS Support Case] Monitoring End device Runtime Hours

Question; Is there some way to query historian and get runtime hours each day for an end device? Described having end devices via IDAS Would like to query via SSMS

[ISS Support Case] Historian trends seem to freeze/flat line after a while.

[ISS Support Case] slow retrieval from Historical Trend

something happened 1/28/2022 20.1.001 Historian version on Windows 2016 2020R2 P1 on windows 10 20H2 old 2014 running on server 2012 and sql 2012 new 2020 running on 2016 and sql 2019 see cust logs in box

[ISS Support Case] Historian Client Unable To Establish A Connection

The Historian is not responding to clients. Logs on to Historian and it's running collecting data. System is sluggish aahGateway.exe high CPU (82%) HC client are rejected with server unavailable message

[ISS Support Case] Historian Client Unable To Establish A Connection

The Historian is not responding to clients. Logs on to Historian and it's running collecting data. System is sluggish aahGateway.exe high CPU (82%) HC client are rejected with server unavailable message

[ISS Support Case] Log4j Vulnerability

Rapid7 is showing these 4 vulnerabilities on the 2 Wonderware servers in Magnolia Apache Log4j Core: CVE-2021-44228: JNDI support has not restricted what names could be resolved allowing remote code execution Apache Log4j Core: CVE-2021-44832: Apache Log4j2 Remote Code Execution Apache Log4j Core: CVE-2021-45046: Apache Log4j2 Thread Context Lookup Pattern vulnerable to remote code execution in certain non-default configurations Apache Log4j Core: CVE-2021-45105: Apache Log4j2 does not always protect from infinite recursion in lookup evaluation The file locations are as below 10.25.16.82 am112v1582 Microsoft Windows Server 2016 Standard Edition 1607 AM112 - Mills - Magnolia - Process Network 1/26/2022 Vulnerable software installed: Apache Log4j Core 2.11.1 (C:\Program Files (x86)\Wonderware\HistorianSearch\elasticsearch-6.7.0\lib\log4j-core-2.11.1.jar) 10.25.16.75 am112v1575.cmc.com Microsoft Windows Server 2016 Standard Edition 1607 AM112 - Mills - Magnolia - Process Network 1/24/2022 Vulnerable software installed: Apache Log4j Core 2.11.1 (C:\Program Files (x86)\Wonderware\HistorianSearch\elasticsearch-6.7.0\lib\log4j-core-2.11.1.jar) I heard from Nancy and Shane recently that you upgraded the Wonderware in Magnolia to fix the Button sticking issues. Can you please take a look at this sometime and see if it is possible to upgrade the Log4j for Wonderware if it is needed. We certainly do not want to interrupt operations.

[ISS Support Case] Log4j Vulnerability

Rapid7 is showing these 4 vulnerabilities on the 2 Wonderware servers in Magnolia Apache Log4j Core: CVE-2021-44228: JNDI support has not restricted what names could be resolved allowing remote code execution Apache Log4j Core: CVE-2021-44832: Apache Log4j2 Remote Code Execution Apache Log4j Core: CVE-2021-45046: Apache Log4j2 Thread Context Lookup Pattern vulnerable to remote code execution in certain non-default configurations Apache Log4j Core: CVE-2021-45105: Apache Log4j2 does not always protect from infinite recursion in lookup evaluation The file locations are as below 10.25.16.82 am112v1582 Microsoft Windows Server 2016 Standard Edition 1607 AM112 - Mills - Magnolia - Process Network 1/26/2022 Vulnerable software installed: Apache Log4j Core 2.11.1 (C:\Program Files (x86)\Wonderware\HistorianSearch\elasticsearch-6.7.0\lib\log4j-core-2.11.1.jar) 10.25.16.75 am112v1575.cmc.com Microsoft Windows Server 2016 Standard Edition 1607 AM112 - Mills - Magnolia - Process Network 1/24/2022 Vulnerable software installed: Apache Log4j Core 2.11.1 (C:\Program Files (x86)\Wonderware\HistorianSearch\elasticsearch-6.7.0\lib\log4j-core-2.11.1.jar) I heard from Nancy and Shane recently that you upgraded the Wonderware in Magnolia to fix the Button sticking issues. Can you please take a look at this sometime and see if it is possible to upgrade the Log4j for Wonderware if it is needed. We certainly do not want to interrupt operations.

[ISS Support Case] data from old historian to new historian

he turned off data collection for the nodes bringing data on the new historian and the old historian now needs to move the data over to the new historian for those 7 opc clients If only he had left data collection on for the other nodes on the old Historian the History blocks there would be full.

[ISS Support Case] data from old historian to new historian

he turned off data collection for the nodes bringing data on the new historian and the old historian now needs to move the data over to the new historian for those 7 opc clients If only he had left data collection on for the other nodes on the old Historian the History blocks there would be full.

[ISS Support Case] Options For Alert or Action On OI Downtime Event

Recently had an issue where a disconnect of OI.Gateway resulted in aahGateway consuming system resources and locking out Historian Clients. Discovered they are not covered in a scenario where a node goes down due to a weather event causing a power outage on one (or more) assets. This happens infrequently but it does happen. How do I safeguard the historian for other users in the event one asset goes down after hours and theres no on available to Deactivate the OI.Gateway

[ISS Support Case] Options For Alert or Action On OI Downtime Event

Recently had an issue where a disconnect of OI.Gateway resulted in aahGateway consuming system resources and locking out Historian Clients. Discovered they are not covered in a scenario where a node goes down due to a weather event causing a power outage on one (or more) assets. This happens infrequently but it does happen. How do I safeguard the historian for other users in the event one asset goes down after hours and theres no on available to Deactivate the OI.Gateway

[ISS Support Case] user cant create tags in historian

version 17,0,18000000000

[ISS Support Case] user cant create tags in historian

version 17,0,18000000000

[ISS Support Case] Historian 2017 can not aquire license

Historian 2017 can not aquire license

[ISS Support Case] Historian Configuration Import Resulted in Error

Following TN1048 had difficulties networking older historian, so decided to move to 2020. Exported configs from 2014 R2 SP1 system (either to a USB or team viewer cant recall) Now trying to import configuration in 2020 R2 P01. During the import started getting 'a lot of errors' (like each tag could not be imported) SMC: The following query did not succeed: . SQL Server reported the following error(s): TagHistory being imported is an active tag (update failed) Now historian modules are in a mixed state (some stopped some started) Now getting message : Circular storage location could not be accessed

[ISS Support Case] Historian Configuration Import Resulted in Error

Following TN1048 had difficulties networking older historian, so decided to move to 2020. Exported configs from 2014 R2 SP1 system (either to a USB or team viewer cant recall) Now trying to import configuration in 2020 R2 P01. During the import started getting 'a lot of errors' (like each tag could not be imported) SMC: The following query did not succeed: . SQL Server reported the following error(s): TagHistory being imported is an active tag (update failed) Now historian modules are in a mixed state (some stopped some started) Now getting message : Circular storage location could not be accessed

[ISS Support Case] Historian License Violation

That AVEVA Development Studio 2020 Large 5K/3K/500 with sn 2138116 and Activation ID HLO4-KKTE-4E0Q-CF41 The tag break down is: 5K App Server Tags 3K InTouch Tags 500 Historian Tags

[ISS Support Case] Not able to trend a value on a Tier-2 Historian

The value comes in correctly on the Tier-1 but not the Tier-2

[ISS Support Case] Not able to trend a value on a Tier-2 Historian

The value comes in correctly on the Tier-1 but not the Tier-2

[ISS Support Case] Question about licensing and use of demo to enable project transfer

Question about licensing and use of demo to enable project transfer

[ISS Support Case] Question About TN 23173

The tech note states to undeploy the galaxy. SI wanted to know if he could attempt this while the site was running

[ISS Support Case] Historian stopped collecting

he rebooted came back 2020R2 P1 went down 2/20/2022 4:41PM until restart server at 8PM

[ISS Support Case] Historian load options

2 questions: multiple tags ---yes--- opc value TN00032881 Historian QualityDetail https://softwaresupportsp.aveva.com/#/okmimarticle/docid/tn000032881 layout format for the CSV file is Page 155 of the manual: Insource does have a overview of the load of a csv file into the Historian - TN Hist279 How to get CSV data into the Wonderware Historian https://knowledge.insourcess.com/?title=Operational_Efficiency/Historian/Maximize_%26_Optimize/TN_Hist279_How_to_get_CSV_data_into_the_Wonderware_Historian Page 154 discusses the Predefined CSV File Import Folders: By default, import folders are created in the main AVEVA Historian data folder when the product is installed. For example, if you specified D:\Historian\DATA\Circular as the circular data folder, the CSV data import folder is D:\Historian\DATA\DataImport,. Important: If you leave the data import path at the default location (on the drive hosting the circular data folder), placing large CSV files in a data import folder may prompt the AVEVA Historian disk management subsystem to immediately start moving or deleting history blocks to maintain the configured amount of required free space on the disk. It is highly recommended to change the data import folder to a different drive than your circular storage. The different import folders are described in the following table: Import Folder Description \DataImport Used for normal CSV import files. \FastLoad Used for "fast load" CSV import files. Files in this folder are processed one at a time, in the order that they appear in Windows Explorer as you are viewing the folder contents. \Manual Used by MDAS for tags. If the amount of data spans multiple 64 KB chunks, files are collected in the \Support subdirectory until all of the data is received. The files are then copied to the \Manual folder for inclusion into history.

[ISS Support Case] older version historian upgrade

going to 2017 or 2020

[ISS Support Case] older version historian upgrade

going to 2017 or 2020

[ISS Support Case] OLE-DB Provider Doesnt Start

OLE- DB Provider doesnt start in the Historian management console

[ISS Support Case] OLE-DB Provider Doesnt Start

OLE- DB Provider doesnt start in the Historian management console

[ISS Support Case] Historian Stops Collecting Data

Errors in historian might be causing gaps in data

[ISS Support Case] 2020 Historian data storage issue

The 2020 R2 Historian is storing a null when an DA server goes offline and then when it comes back online, if the tag does not change from the value prior to the null, it does not insert the current value and the null stays until the value changes. For a setpoint this caused a 5 day gap in the value on the Active Factory trend due to the null being stored. See notes below: Please respond by email., i work part time, remotely from pacific time zone. 2020 R2 SP1 Historian Tagname DateTime Value vValue StartDateTime 1601G-TE-105.2_SP 3/19/2022 8:15:19 AM 209.6 209.59999999999999 3/19/2022 8:15:19 AM 1601G-TE-105.2_SP 3/19/2022 12:40:44 PM (null) (null) 3/19/2022 12:40:44 PM 1601G-TE-105.2_SP 3/23/2022 8:51:38 AM 209.5 209.5 3/23/2022 8:51:38 AM 1601G-TE-105.2_SP 3/23/2022 8:51:43 AM 209.6 209.59999999999999 3/23/2022 8:51:43 AM 2014 R2 SP1 Historian Tagname DateTime Value vValue StartDateTime 1601G-TE-105.2_SP 3/19/2022 8:15:19 AM 209.6 209.59999999999999 3/19/2022 8:15:19 AM 1601G-TE-105.2_SP 3/23/2022 8:51:38 AM 209.5 209.5 3/23/2022 8:51:38 AM 1601G-TE-105.2_SP 3/23/2022 8:51:43 AM 209.6 209.59999999999999 3/23/2022 8:51:43 AM The above are delta retrievals via 2014 Active Factory Web Query. Both Historians are configured for Delta storage with a time deadband of 1000 ms and both historians point to the same remote DA server (DASMBTCP). The tag is a setpoint which rarely changes. There was some issue with the remote DA server machine, and it wasnt until the setpoint was manually adjusted did the 2020 Historian record the new value to replace the stored null. Is there any way to ignore nulls on an Active Factory trend retrieval? Why does 2020 R2 SP1 Historian insert the null compared to the 2014 Historian?

[ISS Support Case] IDAS overflow recovery

version historian 20,1,001,000 version of fsgateway 3.0.200 version is mature support toolkit version 7,2,1,14 os for fsgateway nodes is server 2008 In qualitymap table quality 20 IDAS overflow recovery In OPCQalityMap 20 Bad,Last known Value Suitelink stream communication failure receiving from aahidas connection for fsgateway went away app closed connection see also case 80339 see aveva case SR960148342 1. Run SSMS and execute the following query against the Runtime database (where ls starts with lowercase L): update StorageShard set CmdExtArgs='-ls' where ShardName = 'Main'; 2. Create a registry DWORD (32-bit) value with Name 'ForceValueOnReconnect' and set it to 1 under location below for 32 bit OS. HKEY_LOCAL_MACHINE\SOFTWARE\ArchestrA\Historian\Programs\aahClient and for 64 Bit OS. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ArchestrA\Historian\Programs\aahClient And the values started updating

[ISS Support Case] 32 bit to 64 bit sql server install

going from 2017 to 2020 Historian (that is 32bit to 64bit)

[ISS Support Case] Historical Alarms going down

Historical Alarms go down every week or so. Restarting the Historian fixes it temporarily. They have a separate, independent Historian that collects the same information that doesn't have this issue.

[ISS Support Case] Historian Data not accurate on a pump

Scaling seems to be off is what I am guessing?

[ISS Support Case] Missing History After Migrating to 2020 R2 SP1

Followed Migration steps and is unable to access history after the upgrade. Client described restoring runtime and holding DB in step 6 displayed an error, although the databases were visible in SQL after acknowledging the error.

[ISS Support Case] Tier 1 Not Replicating to Tier 2

Total Sync queue numbers rising, which may indicate that the Tier 1 and 2 Historians arent communicating properly

[ISS Support Case] 24 hour of 2017 Historian Data with Dev license

Development license is being used as a Historian - the base Historian Server is limited to 24 Hour data retrieval. And needs current license(s) for Historian Client

[ISS Support Case] Historian down for several days hindering production

Historian down for several days hindering production. After a system failure, Historian showing flat lines in all trends. A machine which may host IO servers has a failed hard drive. Verison == TBD

[ISS Support Case] How to force a Historian to acquire the desired license

It appears to be grabbing a license with a lower tagcount than needed.

[ISS Support Case] Some History blocks are not being read

Some History blocks do not appear to be getting read after copying to a new Historian

[ISS Support Case] IDAS is stopped when restarting

[ISS Support Case] Sorry you don't have permission to access this site

When trying to connect to Historian Client web it says access denied. Sorry you don't have permission to access this account currently.

[ISS Support Case] HIstorian replication issue

Insight having a problem or bug where the replication is stuck in store forward and wont release the data back to the cloud. Aveva devs working on a fix at the moment.

[ISS Support Case] Historian 2020 Data Gaps Post Migration

Historian 2014 R2 SP1 got a new server Historian 2020 R2 P01 everything is talking to the tag server used tag import export to import tags to new historian updated IDAS moved circular files there are data gaps of a day here and there but on the 2017 system they are not present.

[ISS Support Case] Historian 2020 cant acquire license

Historian grabbed a 500 tag count Dev/they deactivated that, then it found a 500 tag flex rebooted 3 times sn 1242130 is a 2017 version license

[ISS Support Case] Unable to Complete Historian Install

Site wants to use a remote SQL instance to support the local Historian install

[ISS Support Case] Getting errors on Historian

A network switch shutdown the server on April 6th

[ISS Support Case] SQL server ODBC cannot connect

upgraded sql server versions on the machine and unable to connect. When testing the connection, we get a SSL error. Screenshots in box. SQL 2019 with system platform 2014.

[ISS Support Case] Unable to Start Historian

Historian wont start after being migrated from 2020 to 2020 on a new machine

[ISS Support Case] Seeking documentation for upgrading to 2020 R2SP1

Ref case : 81494 suggested to update to the newest version (2020 R2 SP1) Has 4 servers 3 @ 2017 U 3 Sp1 1 @ 2017 U1 Seeking any documentation surrounding an upgrade

[ISS Support Case] Unable to Connect to Historian

Trend client unable to connect to Historian after reboot. "Unable to reach INSQL/Historian server. make sure that the INSQL/Historian server is running."

[ISS Support Case] License Violation in Historian

License Tag count exceeds license

[ISS Support Case] Historian groups not showing up

[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] Historian Replication Stopped Working

A Microsoft update was applied on a Tier 2 Historian. Currently have 4 tier1 replicating to tier 2 3 out of 4 are replicating with no issue 1 shows it's replicating but not seeing any tags - no errors or warnings - not in store forward restarted Historian Shut down and disabled / enabled restarted aahServices from Powershell Microsoft update applied was validated against security central

[ISS Support Case] Trigger Email when Data Stops collecting for a Tag

Objective On a tier 2 would like to detect when data stops collecting for a particular tag. When this event occurs would like to get an email notification about the missing or flat data (start with a single tag)

[ISS Support Case] Historian not collecting Data

Tags from an app engine are not historizing

[ISS Support Case] View Data From a Previous Historian Installation

Calling about WSP Historian upgraded from 2017 N to 2020 R2 SP1 When they made the move they started with a new data base new data. Would like to be able to see some data from the previous system. The old system is unlicensed. Moved HB to folder

[ISS Support Case] INSQL issue

Max Value needs to be adjusted but for all tags at once? Is this possible? System version: 2020

[ISS Support Case] Extended Property Not Working As Expected

An extended property searched for via Historian Client web returns nothing. Per the Historian Admin (excerpt attached) this custom property is searchable. Entering the extended property value in the search bar returned nothing. Please help me understand how to have search Historian Client Web search and return matches on custom properties. I am confused on the use of the location extended property. Is that reserved for something in particular or can It be used for anything? Would like to list the controller address/tag somewhere so my technicians can see the actual controller tag and not just the alias. Alias is good for the engineers but not so good for the techs.

[ISS Support Case] Redefining historized tag type

I inadvertently created tags to be historized as analog which should have been digital. What's the best practice in correcting this

[ISS Support Case] Update Query/Stored Procedure.

How to update the Engineeing Units for a tag using a SQL Query

[ISS Support Case] Disable Insight Replication

Wants to disable replication to insight due to an issue that Aveva isnt going to hotfix on the version of Historian being used

[ISS Support Case] IDAS Disconnects Every Few Seconds

IDAS topic connection from a local OI.ABCIP 2020 R2 disconnects and reconnects every 7-10 seconds or so

[ISS Support Case] Data stopped being historized

I am not seeing the historized tags in the historian server. The historian is in a different machine than the The data acquisition says its acquiring data but we have communication loss on the query Blue Heron Tampa Water

[ISS Support Case] Upgrade Historian 2014 R2 SP1 to 2020 R2

Documentation on an in place upgrade of Historian

[ISS Support Case] Historian is disabled

The Historian is disabled and the client is unable to get it started.

[ISS Support Case] 4 areas are not receiving data on one Historian

The client has redundant HIstorians, one of them is getting the data but not the other

[ISS Support Case] Historian won't start post upgrade to 2020 R2 SP1

System Platform 2020 R2 was installed on a system a couple weeks ago (running on a dev server). Recently called in an was made aware 2020 R2 SP1 was out and the suggestion was to upgrade - ref case 81933 [Update] I upgraded to SP1 and it killed the Historian. Did I miss something? Its looking for SQL (which is running) and rights. It was working under the original installation

[ISS Support Case] Historian Server Stuck Loading Post Migration Bad SQL Login

Runtime database was restored but the historian will not enable. Getting Bad SQL Login.

[ISS Support Case] Frequent SuiteLink suspend/resumes and corresponding flat lines in Historian data

Frequent SuiteLink suspend/resumes and corresponding flat lines in Historian data

[ISS Support Case] Remote IDAS to 2 Historians

I need to install a remote IDAS on an Intouch HMI 2014 R2 node and have it provide data to both a 2014 R2 historian and a 2020 R2 SP1 historian. Is this possible? The 2014 historian will be decommissioned in July but I'd like to have the remote IDAS connect to both historians during the switchover. Also the upgrade to the HMI from 2014 R2 to 2020 R2 will likely not occur until later this year so I'd like to use the 2014 remote IDAS with the 2020 R2 historian if that is possible. I did install a test remote idas on the server i use for the 2014 Intouch development and WIS and could get it connected and configured to the 2014 historian. If i try and use it on the 2020 historian it appears to want to configure the remote idas again an not use the configuration from the 2014 settings.

[ISS Support Case] Historian SysPerfAvailableMBytes Tag Incorrect

System monitoring tag SysPerfAvailableMBytes is giving incorrect data and seems to often get stuck at "4096" when the actual value is around 5400. Interestingly, SysPerfAvailableBytes is accurate once you do the math to add back in 4,294,967,296 per the manual. Not a high priority ticket, but this is something we use to get e-mail alerts every time a server is low on memory and this has been throwing many false alarms recently.

[ISS Support Case] T2 Historian has stopped storing data with tag count violation reported in Status.

T2 Historian has stopped storing data with tag count violation reported in Status.

[ISS Support Case] Fast Load not completing

[ISS Support Case] Will Upgrading Historian Affect Available Disk Space on External Drive

Currently have a 6TB HDD (5gigs free) Previously encountered a scenario where upgrading the product consumed some disk space temporarily and hosed the system. Trying to confirm if the available free space will be consumed in anyway during the upgrade.

[ISS Support Case] Identifying Historian Partner

Not sure if the Historians are redundant partner or a synchronized pair. Objective is to identify the process for decoupling permanently. Need to be done during this upgrade.

[ISS Support Case] Missing Historian Data Post 2020 R2 SP1 Upgrade

I have missing data in the Historian database. I have the History blocks, but the data is missing from 6/23/22 back. This happened after upgrading to System Platform 2020 R2 SP1. 2017 2020 R2 P01 -> 2020 R2 SP1 Upgrade was done on the 20th

[ISS Support Case] Manually Installed SQL but Historian does not recognize it

Finished development Install Trying to install SQL before installing AVEVA SQLServer Express (installed fine) was able to log on fine Installed Historian (did not install install SQL according to AVEVA TN

[ISS Support Case] missing NT SERVICE (virtual) users

Don't attempt to call my office phone number. Email is the easiest way to reach me. Thanks. According to TN_WW241_NT_Services_that_must_not_be_excluded_from_the_Administrators_group Certain virtual accounts must not be deleted from the box in order to have a stable system. On our various Historian boxes, I see that the following user is referenced in the local Administrators group, but does not exist as local user: NT SERVICE\aaPim. Likewise, on the servers that our OI Server runs on, the following 3 accounts are referenced in the local Administrators group, but do not exist as local users: NT SERVICE\aaPim, NT SERVICE\adpHostSrv, NT SERVICE\simHostSrv. Numerous of these types of orphaned account entries exist in the aaAdministrators group on our Historian boxes as well. I'm wondering how everything can continue to run with these local accounts missing? What are your recommendations? The whole reason I'm researching this is because of a couple of failures (that required reboots) in one of our OI Server boxes -- the that now appears to be because of that box needing to be re-joined to the domain.

[ISS Support Case] Historian Compatibility Information

Wanted to check OS compatibility for the latest Historian version

[ISS Support Case] SysDrv looking at old machine name

[ISS Support Case] Error Calling SPROC from Python

Experiencing an issue calling SPROC. Received information for programmatically loading data to Temp table then to Historian table. Having issue firing SPROC from a python application. Error message ProgrammingError: ('42000', '[42000] [Microsoft][ODBC SQL Server Driver][SQL Server]The requested operation could not be performed because OLE DB provider "INSQL" for linked server "INSQL" does not support the required transaction interface. (7390) (SQLExecDirectW)') - loads in temp table no issue - calling SPROC from python gets error Using PY notebook Remote system interfacing with Historian Query works from SSMS - not tested locally - not tested any other SPROC

[ISS Support Case] Historian Server upgrade

Is a license for SQL Server Standard still included with the 2020 System Platform? If so, how do I get the SQL Server Standard version? If not and I do not want to run SQL Express, do I need to supply my own SQL Server Standard?

[ISS Support Case] Repeating Missed detection interval messages in SMC Historian - 20.1 SP1

Warning shown on logger about 20 times per hour for missed detection interval. There are 3 different threads listed. This has been going on for awhile and the 2017 historian has some of these errors as well, but they are much less frequent (1-2 per hour) Warnings from logger shown below: 18413823 7/19/2022 10:50:45 AM 15824 5700 Warning aahEventSvc Main EventService: Missed detection interval [VA03YWVDB0100; D:\ADOBuild2\2\s\src\Event\aahEventSvc\PoolDetectorThrd.cpp; 323] 18413824 7/19/2022 10:53:30 AM 15824 15952 Warning aahEventSvc Main EventService: Missed detection interval [VA03YWVDB0100; D:\ADOBuild2\2\s\src\Event\aahEventSvc\PoolDetectorThrd.cpp; 323] 18413825 7/19/2022 10:55:46 AM 15824 15964 Warning aahEventSvc Main EventService: Missed detection interval [VA03YWVDB0100; D:\ADOBuild2\2\s\src\Event\aahEventSvc\PoolDetectorThrd.cpp; 323] Would this be 3 of the same event tags or could it be any event tag? There are 77 event tags in the historian. I work part time from the west coast, so email replies would be the best way to get in touch.

[ISS Support Case] Problems with Historian

Memory errors along with configuration errors. Unable to switch to primary historian

[ISS Support Case] Customization of Aveva Historian Client Trend 'Tags pane'

Is the tags pane configurable. IOW, can one omit the tag I/O address and Source Tag columns (which are empty in our case) and instead show the units and/or other Custom fields? How would one change this?

[ISS Support Case] Failed to retrieve information from the FS A2 Development license

Could not open IDE on Galaxy or any InTouch apps in Window maker. was getting the message about FS A2 Development license - that it either expired or not available. Rebooted license server - that seem to have resolved the issue. Please look at the log and advise the cause .

[ISS Support Case] Migrated historian not picking up data

Tag count violation

[ISS Support Case] Fast Load CSV Import Questions

Direct email: how picky is the encoding identifier for a Fast Load CSV import to Historian? If you save from Excel as CSV, the encoding is UTF-8. Do I just set it to UNICODE as shown below?

[ISS Support Case] Historian values inaccurate before reset

graph showing different values before the tag resets at 6AM values are inaccurate

[ISS Support Case] Discrete tags go to NULL after a reboot and stay NULL until data changes

Is there a way to force it to use a default value to tags that have had no data update?

[ISS Support Case] With regard to the _TagExtendedProperties table what level security rights are needed in order to see the TagName column in views or tables?

With regard to the _TagExtendedProperties table what level security rights are needed in order to see the TagName column in views or tables? If the account uses aaAdministrator rights to the database, the TagName column is available. The account being used has db_datareader access which does not see the TagName column.

[ISS Support Case] Historian database not populating

not showing in trend no sys admin account designated tries to log on server-cannot open the table failed to update to server

[ISS Support Case] Getting errors after applying updates on Historian

Error: Data packet was rejected and lost (XXXX_sysdrv) Info: SQL Server returned the following message (Violation of PRIMARY KEY constraint 'PK__#BBA88A9__5BAAE5D46E72A78D'. Cannot insert duplicate key in object 'dbo.@AllCandidateAttributes'. The duplicate key value is (4353).) [P-HIST1; config.cpp; 2558

[ISS Support Case] ArechetrA Historian

8-5-2022: System management console, trying to add tags but, everything grayed out when operator signs in.

[ISS Support Case] InSight SetUp

Searh bar isn't working

[ISS Support Case] Updating IDAS Results In Missing Tags

Setting up a new replacement system running 2020 R2 SP1. Imported IDAS but when compared to the old system almost half the tags are missing.

[ISS Support Case] Historian Driver Connection Failed

8-9-2022: Driver-Test connection failed. Aveva Historian Access "Historical Value" 2020 R2 OI-Server, OI-ABCIP, Control Logix version L83, Version 34.

[ISS Support Case] Dream Reports, Alarm Graphic Crashing Web Report.

8-11-2022: Running new alarm and events, crashes dream reports. Web access giving errors, Generator is not running. When the graphic is deleted though, the web report will show all other graphics perfectly.

[ISS Support Case] HIstorian Error

Tag count violation after power outage. 2. Historian trends showing null and not matching with the PLC.

[ISS Support Case] Is there a 64-bit Add-In for Historian Client?

Is there a 64-bit Add-In for Historian Client?

[ISS Support Case] Unable to Start Historian

New Historian installation doesnt allow Historian to start. SMC States "Unable to Install Historian (Failed to open configuration to connection database

[ISS Support Case] Historian

Updating Historian Windows. Store forward not showing data after restart

[ISS Support Case] Unable to Connect to Logger

[ISS Support Case] Needs to Locate XML Licenses

Something I'd like to chase down is the XML file that is associated with a license server that isn't there any more. I'm sure it's on a disc somewhere but I haven't got a clue where it might be

[ISS Support Case] A2ALMDB Migration

I trying to copy an A2ALMDB database from an existing ASP2020 R2 SP1 system (upgraded from ASP2014 R2 SP1) to a newly installed ASP2020 R2 SP1 system. On the new system alarms are logged as expected to the A2ALMDB database created by the Configurator. However, when I backup the A2ALMDB database from the existing system and restore to the new system, alarms are no longer logged. I'm guessing this is a security/authentication issue. I see one warning in the Historian logger "Please update Historian Server properties with valid credentials (on client computer)". I'm not sure that's the underlying issue and how to do that.

[ISS Support Case] Database migration Upgrading Historian

Have upgraded a Wonderware Backup Local Historian server from Wonderware 2014 R2 SP1 to SystemPlatform 2020 R2 SP1. Would like to migrate the Runtime db on the Backup Local Historian from SQL Server 2012 to SQL Express 2017. Using the Database Migration steps as recommended on page 145 of the Install Guide. Made a backup of the SQL Server 2012 Runtime db and successfully restored the db into SQL Express 2017. Got to step 3, but then encountered the error message in the attached file. Logged on as a local admin on the server and can write to the destination data path folder. So, Im not exactly sure why Im getting the error message or the best option to proceed.

[ISS Support Case] HIstorian

Data Not showing correctly. not getting trend data since restart Art Called See Activities for Call Notes.

[ISS Support Case] Getting aahCfgSvc Remaining Disk Space messages sporadically in batches

having a lot of messages come through about a historian (info) 3-4 or 10 remaining disk space on circular drive messages in blocks 5:55 am - 10:55 am

[ISS Support Case] Historian Server log not logging

The Historian Server log is not getting any new entries (since 8/6). Yes, I've checked to see if I accidentally have a filter turned on, and I don't. This happened one previous time, and I can't remember the fix. I'm sure a reboot was involved somehow. I checked just now, and the ArchestrA Logger service IS running. Speaking of reboots, this log stopped updating just after the last reboot, just in case there is a tie-in there somewhere. You can reach me best via my work email. Thanks. (not sure I have the version of the Historian Server correct in the form above... where does one find this info?)

[ISS Support Case] Deleted MDAS tags still show up in HC Trend

Needed to delete several objects in IDE. History was enabled for these objects. Even after IDE deletion, these objects still showed in the Trend app; no new data, just the old history data that was collected. I deleted from the historian in the manual tags section, then deleted in the Trend app. I verified they were gone in all 3 places. However, when I deploy another object in the IDE, for some reason these objects show back up in the trend app - they do not reappear in the IDE or the Historian manual tags. Need to get this fixed and curious what other source the trend app might be pulling data from - or is there more than one location in the Historian that i need to delete objects from. Thank you,

[ISS Support Case] aahBackfill does not backfill replication data unsupported backfill SQL script

I have some historical data that I forgot to set to replicate to our tier 2 historian a few weeks ago but the data is still in the database on the tier 1 historian. In the past, I have used aahBackFill to perform this but for whatever reason it is not working with this data. Needing some assistance figuring it out.

[ISS Support Case] Connecting to Historian aahIoSvrSvc

I seem to recall Historian could act as a data source and serve out data from a tag, is this right? Do you know how to do that? There is at least one tag in historian, a SYS tag, which appears to trend the CPU performance. I was thinking perhaps I could create an object in app server which points to this tag. I could then set an alarm. If the value goes above, say, 50% for more than 30 seconds, I sound an alarm. I could even set Win911 to send me a text message if this alarm goes off

[ISS Support Case] Historian Client 32 Bit Insight Issue

Historian Workbook installed 32 bit version of EXCEL located the add in and selected tag selection would hang SWOD. office 365 apps for enterprise Excel 32 bit

[ISS Support Case] Not connecting to historian

Adding tag contrologix process oi server abcip, error disconnecting reconnecting. Watchdog question

[ISS Support Case] Not writing to historian

2 platforms not writing to historian. please update historian server properties with valid credentials

[ISS Support Case] Migrating Historian

[ISS Support Case] Alarm History "Not Connected"

Two location re not able to query historian, status shows as not connected.

[ISS Support Case] Alarm History "Not Connected"

Two location re not able to query historian, status shows as not connected.

[ISS Support Case] Change network account is missing from Historian Node

I have a couple of questions that I was hoping you could answerI was wondering whether the Change Network Account Utility is still used in System Platform. In the Historian Admin Guide it is mentioned, but I dont see it in the Aveva menu and dont find aaAdminUser.exe anywhere on the hard drive of the local backup Historian after install of SP 2020 R2 SP1. Is this replaced by the Configurator Security? With Wonderware 2014 the change network account needed to exist on all Wonderware workstations and servers and needed to be the same user ID and password. Is this still the case for SP 2020 R2 SP1? I was hoping to make some changes in what users are Historian Admins and Historian Power Users.

[ISS Support Case] No Historical Data

After upgrading to 2020. Historian is recording live data but none of the old data is available

[ISS Support Case] Historian CSV Manual Data Upload Question

Left VM: Has a question about the process

[ISS Support Case] Historian using too much memory

Historian event storage is using 60% of memory. 2020 r2 sp1

[ISS Support Case] Historian users

[ISS Support Case] Tags for a particular topic are not updating

Collecting data for a topic in historian. All of the tags for a specific topic are not updating.

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

[ISS Support Case] IDAS Historian

2014 R2 -Remote IDAS License. -IDAS Offline, status has stopped (data-acquisition) . -Historian has been running before, the IDAS is new. -Does say successfully connection to IDAS. -Is online and can do a teams.

[ISS Support Case] Historian - does not have rights to configure

Historian is disabled. Made sure his acct could access SQL and was in aadmin group.

[ISS Support Case] Purge wwAlmDB Fails with Purge Failed

Purge Archive utility on a tier 1 historian keep failing purge failed db was originally 200+ GB now 5.3

[ISS Support Case] No new data in Tier-2 Historian

Getting lots of the following warning message: Store/forward Storage(C:\ProgramData\ArchestrA\XXXX\XXXXX\Event) failed to load file C:\ProgramData\ArchestrA\XXXX\XXXXX\Event\A000000_001\taginfo.dat, error = 18 (Invalid file identifier) [XXXX; e:\build\11\s\src\storage\aahstorage\historyblockmetadataserver.cpp; 358]

[ISS Support Case] Could not allocate space for object 'dbo.events'.'P_Events' in database WWALMDB

While trouble shooting seeing messages about space issues when trying to log alarms. Would like to know why these are present environment has plenty of room SMC : Could not allocate space for object 'dbo.events'.'P_Events' in database WWALMDB because the primary file group is full Wil do that next Monday or Tuesday. On one station was set up as application vs service read that a reboot can 'break' that.

[ISS Support Case] High CPU Usage with Historian

After an update to SQL server a month ago, Historian has been clocking 99-100% usage

[ISS Support Case] Historian upgrade issue

Upgrading customer from 2014 r2 sp1 to 2020 r2 sp1. They moved the historian. It didnt use the Data folder, it setup a data folder inside of the normal data folder. Data is going into the right folder but is not showing the icon. ------------ Cannot start the aveva historian search service.

[ISS Support Case] Unable to see any data from aahIOSvrSvc Post Migration

Migrated a 2014 R2 SP1 Historian to 2020 R2 SP1. All modules are green in the SMC. In task manager ArchestrA Historian IO Server Service is running (validated in services)

[ISS Support Case] Replicating Alarms and Events

Can you replicate alarms and events to another Historian

[ISS Support Case] Unable to Import LGH Data Into Historian

Historian data import wizard not importing data

[ISS Support Case] Seeking Historian Configuration Documentation

Direct email: Could you point me in the right direction to find a guide/tutorial for setting up the historian?

[ISS Support Case] How to Install Historian

Looking for information on how to configure historian. We have some intouch tags we would like to now track.

[ISS Support Case] Migrated Historian Missing Days Of Data Randomly

We are upgrading a customer from WSP 2014R2Sp1 to 2020R2Sp1 and everything went fine except Historian. Everything came up ok but when I moved the old circular files over there is about 4 days that seem to be missing. Has blocks for the time period that is missing. On the old historian can see the data but on the new historian those 4 random days where data is missing. Can see older history blocks

[ISS Support Case] Set Up Historian Client Unable to reach INSQL Historian server, make sure that INSQL Historian server is running

Historian Client Installed on a laptop, Unable to connect to Historian. Historian client trend cannot connect with domain user and displays error "Unable to reach INSQL/Historian server, make sure that INSQL/Historian server is running"

[ISS Support Case] Historian Error

2014 R2 SP1 -RPC Server is unavailable and Historian is disabled. -Only change is installing service pack 1. -SP1 installed 10/15/2022. -Intouch Multiple machines. -Historians on it's own Node. -Sent Possible Resolves on how to fix RPC failures. -This seems to be a Window's Issue not a AVEVA Issue.

[ISS Support Case] Historian Errors Replication Job queue unable to send non streamed data

Historian Local Log See attached file Main Replication job queue unable to send non-streamed data transaction for server Insight_Historian16, error = 247 () [CCDWHIST 16; e:\build\4\s\src\acquisition\aahreplicationserver.ccp; 2172] Main Replication failed to send original non-streamed data, error = 247 () [Insight_Historian16; e:\build\4\s\src\acquisition\aahreplication\aahreplicationserver.cpp; 1986]

[ISS Support Case] Displaying Historical Values In An Object Attribute

I am looking for help to create a tag in the system platform that can display historical values from historians. For that, do I need to create a driver for historian database in the system platform?

[ISS Support Case] Historian 2012 R2 Stopped working

Historian Issue, When I launch Historian Client I cant view any data everything just says null. Seeing some weird messages in the SMC logger Main Storage Memory Exception caught, et={0135789} StartDataRetrievalQuery failed ... error 58 (not initialized) Domain Environment Was previously working, system started started doing this last week. A reboot worked for like an hour and the symptoms returned. Historian 2012 R2 Server 2008 R2

[ISS Support Case] Random IDAS Disconnects

IDAS disconnecting randomly for multiple seconds to minutes

[ISS Support Case] Null Values in Tags Post Power Outage

After a power outage, random tags have null values. Never understood why but servers are on UPS, Switches are on UPS... everything should stay running through an outage and it does but after a blip random tags (reels, bool etc) across servers (abcip, gateway) show up as null. Can typically do a delta or full reimport of tags to resolve, but not today though. Has 7 workstations 6 intouch applications in Historian (IDAS) CORE v6.0 ABTCP v4.0 ABCIP v7.0 Gateway 6.0

[ISS Support Case] IDAS Unable to Connect Modules Not Starting Post 2023 Upgrade

After upgrading, IDAS sources no longer connect. When attempting to reinitialize the connections the SMC crashes Ran executable, everything looked good, seems to be locking up Status under management console OMC is locking up now unable to validate. SMC is slow to navigate OLEDB provider says is stopped, Went with legacy SQL connection in the installation upgraded from 2020R2 SP1 8Gig at 99% memory usage.

[ISS Support Case] New historian tags not able to read.

[ISS Support Case] Adding Tags to Historian

Guidance on adding a tag to Historian IDAS course

[ISS Support Case] License Count Violation

Historian is showing a license count violation in the Management Console

[ISS Support Case] Replication to PI Server

Customer is using the PI replication feature in Historian 2023. He has other plants where this is setup and working. At this particular plant the Historian keeps going into Store & Forward. As you can see at the end of the attached log file, the system gets disconnected from the PI system and enters S&F (7:19:49 AM). Also attached is a screen shot showing the system in S&F. 11/11/2022: -Teams Meeting, Checked TCP Port, Checked File path, Changed File path, The D: Drive is very full, Customer is going to clean up the D: Drive. -Some Analog tags are set as "Delta" tags, going to change them to a non priority type tag so that the data is not pulling in, in such a vast data pool.

[ISS Support Case] Data missing?

Getting suitelink resume messages.

[ISS Support Case] Upgrade Question

Can you Upgrade from 2017 to 2023

[ISS Support Case] Historian Question Regarding Time Stamps

Does the Historian get its time for data points from the Server or the PLC

[ISS Support Case] Randomly one or more topics will stop

Same machine with CIP issue (83020) experiencing a condition where they are seeing live values updating in SMC diagnostics. Error log is clean, data quality is good. At random points in time one or more topics will randomly stop writing to the SQL server.

[ISS Support Case] Historian Client showing flat lines

IDAS errors

[ISS Support Case] Unable to Replicate to T2

Unable to replicate from T1 Historian to T2

[ISS Support Case] Historian Not Capturing Data

Historian no longer logs data from data sources as of 11/19. Logger floods with the message ***Buffer discarded occurred xxxx times.

[ISS Support Case] Wonderware Historian IDAS Configuration Assistance

In the past I have used Historian to TOP server to communicate to CTI 2500 series PLCs. We are slowly migrating to Allen-Bradley Compact Logix controllers. The Automation Engineer has the AB PLC to Wonderware communications working but I cannot pull the data into Historian.

[ISS Support Case] Is It Possible To Track Historian Changes Before ModLogTrackingStatus Is Enabled

I just learned about setting of the ModLogTrackingStatus parameter in https://knowledge.insourcess.com/?title=Operational_Efficiency%2FHistorian%2FMaximize_%26_Optimize%2FTN_Hist246_Enable_tracking_and_reporting_on_modifications_made_in_Wonderware_Historian. Are Historian tag changes recorded to a SQL Runtime database? I was hoping to have a way to discover recent tag changes that may have been made prior to turning on the ModLogTrackingStatus parameter.

[ISS Support Case] SQL server restarts after handling queries with large numbers of parameters

Historian version: 2017 U3 SP1 P01 The image is a VMWare ESXi image hosted on a Nutanix host SQL Server 2016 SP2 13.0.5108

[ISS Support Case] 2020 R2 SP1 P01 Historian Lic

[ISS Support Case] Historian - mdas tags are not communicating

Historian - he restarted it and had issues with MDAS. Still does not have communication. MDAS tags are not communicating. --------------------- Doing a reindex now after shutting down historian

[ISS Support Case] No Data Being Captured After Restart

Restarted Historian after adding more RAM and now the Historian no longer stores values.

[ISS Support Case] Data Backfilling with No Store Forward Folder Specified

No Store forward directory chosen but after a disconnect and reconnect of Historian from App server, data back fills. Client has 2 existing galaxies, pursuing migration inhouse by mimicking what they had seen. None of the galaxies have SF directory defined but SF is somehow working. Looking for an explanation as to how.

[ISS Support Case] License Agreement is Blank on a Fresh Installation

Trying to install Historian describing issue outlined in TA000034767

[ISS Support Case] Cant Log back into Historian

over the weekend his IT dept disabled his admin login on all servers and assigned him a new one