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