TN - HC - 2503043 Active Factory (Historian Client) Menu Unavailable in Word

Last updated: May 18th, 2026

Description

Author: Brian Schneider
Published: May 18th, 2026

Details:

Problem Statement

User starts Word but does not see the menus to do ActiveFactory Queries.

Solution Details

The problem is because Word has lost its connection to the ActiveFactory (Historian Client) Addon. To fix this there are two solutions:

Solution #1:

Reinstall ActiveFactory on the problem computer. Once reinstalled the toolbar should be visible in Word.

Solution #2:

Open Word From the Tools menu choose Templates and Add-Ins.
On the Templates tab, if you see “HistClient.dot” select it and press OK.
If you do not see it press Add, and go to C:\Program Files\Common Files\Archestra and select the HistClient.dot file and press OK.
Ensure the “HistClient.dot” file is now selected and press OK.

Give feedback about this article

Recommended articles

[ISS Support Case] Historian Data Importer Failure

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

[ISS Support Case] Not writing to historian

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

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