IMD SolutionComputing LibraryShop main store

Troubleshooting

Repoint InTouch trend files to a new Historian server

Edge computing and IIoT Published 6 min read

Short answer

The hang is a server-binding fault: each saved trend file carries the retired Historian's name and the client waits on it before the window opens. Map the old name to the new server with a DNS alias or a hosts entry, change the server reference inside each file, keep the tagnames, then remove the alias and confirm every file opens. Old history does not return with the tagnames; it exists on the new server only if the old database was restored or migrated into it.

On this page
  1. Why the file hangs on open
  2. Confirm the fault before changing anything
  3. Back up, then bridge the old name
  4. Repoint the server reference in each file
  5. Worked example: bridging HISTOLD to HISTNEW on one operator node
  6. Match the symptom to the layer
  7. Verify the repoint end to end
  8. Questions asked

Saved InTouch trend files hang on open because each one stores the name of the Historian server it was built against, and the client resolves and connects to that name while the file loads. The retired host never answers, so the client sits in a name-resolution or connection timeout while the window looks frozen and the HMI stops taking clicks. The pen tagnames are identical on the new system, so the pens are fine: this is a binding fault, not a tag fault. Bridge the old name to the new server with a DNS alias or a hosts entry, repoint the server reference inside each file, then delete the alias and verify. Old history does not come back with the tagnames; it exists on the new server only if the old database was restored or migrated into it.

Why the file hangs on open #

A saved trend file is more than a pen list: it carries the server reference it was configured with. Historian Client Trend is a stand-alone application whose properties are configurable at design time and at run time, and the server name is one of the properties that travels with the saved file. When the stored name points at a host that no longer exists, the client waits out resolution and connection timeouts before it gives up, and the screen appears hung for that whole period.

The reference lives in one of two places depending on how the trend was built:

  • In a saved Historian Client trend file (*.aaTrend), including the files behind the Historian Client Trend .NET control embedded in a modern InTouch application; tech note TN HistClient129 covers importing that control.
  • In InTouch's own trend configuration, where the historical data settings live under Configure -> Historical Data.

Either way the fix order is the same: bridge the name, repoint the reference, verify with the bridge removed.

Confirm the fault before changing anything #

Run these checks from the operator node that hangs:

  • Resolve the old server name with Resolve-DnsName. Expect a failure or a timeout, because the host is retired.
  • Resolve the new Historian's name the same way. Expect an answer. If it does not resolve from this node, fix name resolution first; no trend setting helps until the node can reach the new server.
  • Open one hanging trend's configuration and read the exact server string it stores. Use that exact string for the bridge, because a file can name the server differently, or by address, from what you assumed.

Back up, then bridge the old name #

A failed re-save can leave a trend file that no longer opens, so copy the application folder and every saved file to a dated backup first, and confirm the backup's file count matches the source. Record the old server string while you are there.

The rule in words: the file stops hanging once the name it stores resolves to a live Historian. Two ways to make that true:

  • A DNS alias (CNAME) or an A record for the old name, created on the site DNS server. Every client resolves it and no per-node edits are needed. If the record reaches some nodes but not others, the zone is not replicating between DNS servers, and repairing Active Directory DNS replication on Windows Server 2019 covers that layer.
  • A hosts file entry on one node, C:\Windows\System32\drivers\etc\hosts, edited as administrator. The line holds the new server's address followed by the old name, and it affects only that node, so treat it as a stopgap while you repoint files.

With the bridge active, open one saved trend file. It should open in normal time and populate its pens. If it opens and then reports a login or permission failure, the binding is fixed and the account is what remains: grant the client account read access on the new Historian, the layer covered by fixing the InTouch 2023 Test Connection failure to a Historian.

Repoint the server reference in each file #

The bridge gets the files open. The permanent fix removes the dependence on a name that points at a retired host:

  1. With the bridge active, open the trend file's configuration, in its pen or server settings.
  2. Change the server to the new Historian's name.
  3. Leave the pen tagnames unchanged; they already match.
  4. Save the file under its existing name, or under a new name if you want the original beside it.
  5. Delete the bridge, the hosts line or the DNS record, and reopen the file. It must open with the old name unresolvable. If it hangs again, that file, or one pen in it, still holds the old reference; repeat the edit for that string.

For many files, batch procedures exist: TN HistClient105 documents changing the embedded Historian server name across saved *.aaTrend files in one pass, and a 2014 tech note covers the same job on HistClient trend files. Editing file contents in a text editor is a last resort: only on a copy, only if the file opens as readable plain text, and a binary file is changed through the trend configuration, never through an editor.

Worked example: bridging HISTOLD to HISTNEW on one operator node #

HISTOLD and HISTNEW are illustrative names standing for your two servers; the checks and the decision are the deliverable.

Inputs:

  • Old server name, HISTOLD, read from the server string stored in a hanging file's configuration.
  • New server, HISTNEW, the site's current Historian holding the same tagnames.
  • One operator node whose saved *.aaTrend files hang on open.

Rule in words: a file opens without a hang when the name it stores resolves to a live Historian, and it is permanently repointed when the stored name is HISTNEW and the file still opens with every trace of HISTOLD removed.

Steps:

  1. Resolve-DnsName HISTOLD fails; Resolve-DnsName HISTNEW answers. Binding fault confirmed, pens untouched.
  2. Back up the application folder and the saved files; record the stored string HISTOLD.
  3. Add a hosts line holding HISTNEW's address followed by HISTOLD. A DNS CNAME from HISTOLD to HISTNEW does the same job for every client at once.
  4. Open a saved file: it opens in normal time and the pens populate from HISTNEW's recorded range.
  5. In the file's server configuration, replace HISTOLD with HISTNEW and save.
  6. Delete the hosts line, restart the node so no cached resolution survives, and reopen the file with HISTOLD unresolvable.

Result and decision: a file that opens after step 6 is repointed and done. A file that hangs after step 6 still stores the old string under a different spelling, so read that file's server configuration and bridge the exact string it names.

Match the symptom to the layer #

Operator sees Layer at fault Check
Window hangs on open Server binding Old name still stored; resolve the exact string in the file's configuration.
Opens, pens listed, no data at all Tags or storage on the new Historian Confirm each tag exists and is set to store values, the fault walked in historian trend empty: PLC tag collection troubleshooting.
Live data present, history before cutover missing Data, not configuration The new Historian holds only what it recorded or imported; backfilling trend history from a plant historian covers bringing the old data across.
Login or permission error on open Authentication Grant the client account read access on the new Historian.

Matching tagnames make the pens resolve; they do not create history.

Verify the repoint end to end #

  1. Remove the DNS alias and any hosts entry, and confirm the old name no longer resolves from the client node.
  2. Restart the client node so no cached connection or resolved name survives.
  3. Open every saved trend file from the operator screen. Each must open in normal time, with no hang.
  4. Confirm each pen shows live values and history across the new Historian's recorded range.
  5. Pick one pen and one timestamp, and compare the trend's value against a direct query of the same tag and time on the new Historian. They must match.

Questions asked

Can the DNS alias stay in place permanently instead of editing every trend file?

It can, and the files will open and bind through it indefinitely. The cost is that the retired name keeps living in the plant namespace: whoever reuses it for a different host points every saved trend at the wrong server at once. Use the alias as the bridge, repoint the files on a planned window, and keep the alias only as long as the backlog of unedited files lasts.

Do identical tagnames on the new Historian bring back the old history?

No. A matching name only lets the pen resolve and collect new values. Data recorded on the old server appears on the new one only if that database was restored or migrated into it, so a pen showing values from the cutover date forward but nothing earlier is behaving correctly.

Is there a batch way to change the server name in many saved trend files?

Yes, for both file generations: a documented batch procedure covers the embedded server name across saved aaTrend files, and an earlier 2014 tech note covers the same job on the older format. Run the batch against a copy of the folder, keep the originals until each edited file has opened with the alias removed, and treat any file that still hangs as holding a second, differently spelled reference.

The file now opens but shows a login or permission error. Did the repoint fail?

No. Once the error text names the new server, the binding is correct and the remaining fault is the account. Grant the client node's account read access on the new Historian and reopen the file; the server named in the error is the one the client actually reached.

Keep reading

  • Troubleshooting

    Redirect saved trend files to a new historian server

    A saved .aaTrend file keeps the server name it was created with, so it hangs when the old historian is gone. Open it in the current Trend client, let the connection attempt finish (observed one to two minutes), save a new copy, then search for the old server name in that copy and replace it with the new one; tag names stay unchanged.

    Edge computing and IIoT

  • Troubleshooting

    Fix InTouch 2023 Test Connection failure to Historian

    Test Connection from InTouch 2023 to a remote Historian fails for two reasons: the Historian node's firewall blocks the SQL Server listener even though ping works, and the Distributed Name Manager history provider does not support Windows credentials. Prove TCP reachability, then use a SQL Server login stored in Credentials Manager.

    Edge computing and IIoT

  • Troubleshooting

    Running redundant InTouch historians with parallel tag logging

    InTouch has no dual-Historian target, so a partner Historian configured for redundancy stays empty. Log process data in parallel: the same tag list imported into both Historians, an IDAS on each node reading the OI Server. Handle historical alarms separately with A2ALMDB, because IDAS failover does not carry alarm data.

    Edge computing and IIoT