Solve Minor Operating Problems

The following is a table of troubleshooting tips for solving minor operating problems with Historian.

Issue	Suggested Action
After setting the system clock back, browsing the collector from Historian Administrator produces a Visual Basic script error.	Delete temporary Internet files and restart Internet Explorer.
With the Historian Non-Web Administrator, switching usernames causes the system to reject the login if the User must change password at next login option is selected at time of user creation.	New users with this setting must log in to the appropriate Windows operating system at least once. If the login is rejected, drag the Non-Web Administrator to your desktop, right-select the icon, select "Run as . . .", enter a new username and password, and select OK. The login of the new user is then accepted.
A long error message from the File collector does not fit within the message field in the Historian File collector console window, resulting a partial display of the message.	Open the File collector log file to see the complete text of the error message.
Excel Sample Reports do not display data.	When opening a Sample Excel report, you may receive a message prompting you to update all linked information in the workbook (Yes) or keep the existing information (No). It is recommended that you select No and keep the existing information. The links will be automatically updated for your worksheet. Save your worksheet after the links have been updated.
Need to connect an Historian Server to an Historian Client through a firewall.	Open port 14000 to enable client to server connection through a firewall.
Receiving archive offline failed writes messages.	These occur when the timestamps of data being sent to the archiver are not in the valid time range of any online archives. For example, failed writes occur when the timestamps appear before the oldest archive, the archive is offline, or timestamps are more than 15 minutes past the current time on another archiver.