General Information

Important: You do not have the latest version of Historian! You are missing out on the newest capabilities and enhanced security. For information on all the latest features, see the Historian product page. For more information on upgrades, contact your GE Digital sales agent or e-mail GE Digital Sales Support. For the most up-to-date documentation, go here.

Windows XP Login Notes

Windows XP handles blank passwords differently than other Windows operating systems. For this reason, it is recommended that you include passwords with all user accounts when you create them in Windows XP, whether or not you use Historian security. This is particularly important if you are running Historian in a 21 CFR Part 11-compliant environment.

In Windows XP, you can change the local policy to allow logins with blank passwords. However, domain policies can override local polices. Refer to your Windows XP Help for more information on changing security policies and the use of blank passwords.

Historian Errors and Message Codes

When you review errors and messages, for example, in an Historian archiver log file, full descriptions are usually included. If a number appears instead of a description, use the following table to determine the meaning of the error or message.
Table 1. Historian Error Codes and Messages
Number Description
-32 Operation not permitted
-31 The requested data store was not found
-30 The requested Enumerated Set was not found
-29 A supplied argument is outside the valid range
-28 A supplied argument is NULL
-27 A supplied argument is invalid
-26 Alarm and Event subsystem unreachable
-25 Attempted data delete outside allowed modification interval
-24 Data Retrieval Count Exceeded
-23 Invalid Server Version
-22 Backup Exceeded Space
-21 Calculation Circular Reference
-20 Not Licensed
-19 Duplicate Interface
-18 No Value
-17 License: Invalid License DLL
-16 License: Too Many Users
-15 License: Too Many Tags
-14 Invalid Tagname
-13 Write No Archive Available
-12 Write Outside Active
-11 Archive Read Only
-10 Write Archive Offline
-9 Write in Future
-8 Access Denied
-7 Not Valid User
-6 Duplicate Data
-5 Not Supported
-4 Interface Not Found
-3 Not Connected
-2 API Timeout
-1 FAILED
0 OK
0 Undefined
1 Connection Successful
2 Connection Unsuccessful
3 Audited Write
4 Audited Write Update
5 Audited Write Out Of Order
6 Audited Write Update Out Of Order
7 Message On Update
8 Message On Update Out Of Order
9 License Library Function Missing
10 License Library Missing
11 Failed Write
12 Tag Added
13 Tag Modified
14 Tag Deleted
15 Interface Added
16 Interface Modified
17 Interface Deleted
18 Archive Added
19 Archive Add Failure Time Overlap
20 Archive Deleted
21 Archive Overwritten
22 Archive Backup Began
23 Archive Backup Failed
24 Archive Backup Completed
25 Archive Five Days Till Closing
26 Archive Three Days Till Closing
27 Archive One Day Till Closing
28 License Key Removed
29 License Max Tags Exceeded
30 License Max Users Exceeded
31 License Max Tags Exceeded Shutdown
32 License Max Users Exceeded Shutdown
33 License Library Invalid
34 Buffer Normal
35 Buffer On Disk
36 Buffer Out Of Space
37 Incomplete Shutdown
38 Archive Modified
39 License Expired
40 Buffer Could Not Create
41 Archiver Startup
42 Archiver Shutdown
43 Audit Status Changed
44 Option Modified
45 Write Processing Stopped
46 Write Processing Resumed
47 Interface Status Unknown
48 Archive Closed
49 Interface Stopped
50 Interface Started

Determining the Version of the Historian Server

The version of the Historian Server that the Historian Administrator is connected to appears in the About dialog box. If the version number is "Unknown", you are connected to an Historian v1.0 Server.
  1. Open the Historian Administrator.
  2. Click the About link.
    The About Historian dialog appears.
  3. Note the version number that appear in Versions section of the About Historian dialog, as shown in the following figure.


Using VBA to Return a List of Valid Field Options

Use VBA to determine which fields are available for an SDK object.
  1. Open Microsoft Visual Basic for Applications (VBA).
  2. Ensure that you have selected the Historian Software Kit reference in the References dialog box.
  3. Select the Object Browser from the View menu.
  4. Select Historian_SDK from the Library drop-down list.
  5. Click an item in the Classes list to generate a list of valid fields for that item.
    when you click ihCollectionType, you see a list of fields that includes Polled and Unsolicited.

Scheduled Software Performance Impact

Running continuous backup or disk scan software applications such as anti-virus scans, automated backup software, or any other software that accesses disk drives to a high degree may affect the overall performance of your Historian System by competing with Historian for disk resources.

If your Historian System requires that you need an extremely high throughput (20k/sec or greater), consider disabling the scheduled software execution.

Intellution 7.x Drivers as OPC Servers

The ABR and the ABC drivers are OPC v2.0 compliant. All other Intellution 7.x drivers, including the MB1, support OPC v1.0 compliance.

Version 7.x drivers also comply with the OLE for Process Control (OPC) v1.0a standard. Any 1.0-compliant OPC client application can access process hardware data through the I/O Server.

The ABC I/O Server also supports the v2.0 standard and with the OPC Alarm and Events v1.0 specification. Refer to Using OLE for Process Control (OPC) Functionality to learn more about the advantages of OPC.