Troubleshooting Issues with the Add-In

• Review the HistorianSDKErrors.log file. This file is usually located in the LogFiles folder in your Historian program folder. Historian records additional information for some errors in this file. Sometimes, by reviewing this file, you can determine the cause of the error.
• If using Historian security, verify that the user has the appropriate security rights. If the rights are incorrect, log in as a user with the correct privileges or change the rights for the current user.
• Verify that there are no empty rows between valid rows in your spreadsheet. These empty rows can cause issues.
• Note if any errors occur. If an error occurs with any line of the import, Historian aborts the whole import.

• If you remove or add Historian servers, and then if you attempt to search for tags, the add-in may not recognize the default server, and may display a message, stating that the default server has not been set. To avoid this issue, close and reopen the Search Tags window.
• Make sure that you are not trying to import the Calculation Execution Time, Last Modified, or Last Modified User fields for each tag. These fields are read-only. As such, you can export them but cannot import them.
• Verify that your collector does not contain any duplicate tagnames.
• Verify that the number of tags that you want to import does not exceed the maximum licensed tag count. If it does, you will not be able to import the tags.

• Ensure that the time stamps of any online archives are not prior to the start time of the oldest online archive.
• Ensure that the time stamps are within the active hours setting in the Data Store Maintenance page of Historian Administrator.
• Ensure that the time stamps are not for a time greater than 15 minutes ahead of the system time on the Historian server.
• Ensure that the tags are valid Historian tags. To do this, import your tags before importing their associated data.

You can export a 64-bit tag, include it in a report and perform calculations on it. However, there will be a minor precision loss while retrieving the data due to a Visual Basic limitation.

Description: If you export all the fields and attempt to import the read-only fields LastModified and LastModifiedUser, you may receive an error message.

Error Message: Import failed, Error with Import Header.

Workaround: Export the tags without selecting the read-only fields, and then import the tags.

Description: If you follow the recommended installation procedures, you should not have any difficulty in running the sample reports. If you do encounter any problems, they are likely to relate to the locations of files and the links to those files.

Workaround: When opening a sample Excel report, you may receive a message prompting you to update all linked information in the workbook or keep the existing information. We recommend that you select No (that is, keep the existing information). The links will be automatically updated for your worksheet. Save your worksheet after the links have been updated.

For problems in the worksheets themselves, refer to Excel online Help for assistance.