Historian Error Code Lookup Table (version 23)

Knowledge Base / Version 23 / System Admin Duties / Canary Historian

updated 8 mths ago

If a Canary Historian experiences an error it can be found in the 'Messages' log. Error codes may be diagnosed by using the chart below.

All Historian errors will start with the prefix of '0x8004' and are then followed by a unique 4 digit hex code.

Error Code	Description
0x800403E9	DataSet Name already exists.
0x800403EA	DataSet Name is NOT defined.
0x800403EB	DataSet cannot be deleted because it is currently being used.
0x800403EC	Cannot find valid DataSet Name in ItemID.
0x800403ED	Trend data is already present in DataSet Path. The path is probably the same as the path for another DataSet.
0x800403EE	Creating the directory for the specified DataSet path failed.
0x800403EF	Archive was closed with ItemHandles that were not released. This will occur if the network connection drops out.
0x800403F0	Memory Allocation Failure.
0x800403F1	The Item Handle is NOT a valid handle.
0x800403F2	The total number of tags which the Enterprise Historian can log has been exceeded.
0x800403F3	Class Creation Failure.
0x800403F4	ItemID type is not defined as a tag type.
0x800403F5	The free disk space has reached the minimum level for this DataSet.
0x800403F6	ItemID type is not defined as a table type.
0x800403F7	Invalid Timestamp (probably 0).
0x800403F8	TagKey contains no TrendVectors.
0x800403F9	Disconnect from CDataSet classed failed. CDataSet class not found.
0x800403FA	The timestamp is outside the current range of the specified tag.
0x800403FB	The new file cannot be created, because there are tags that are currently being logged into this DataSet.
0x800403FC	This DataSet does not contain any .HDB2 data files in either the primary path or the archive path.
0x800403FD	The ItemID specified is not found in this DataSet.
0x800403FE	FileIO Record Allocation failed because of an invalid disk address (-1).
0x800403FF	FileIO::ReadHeader caused an access violation when trying to read the header information for a record.
0x80040400	Record header type or location read from the disk is not what was expected. Probable file corruption!
0x80040401	The trailing marker for this record does not match the RecordLoc mark at the beginning of the record. Probable file corruption!
0x80040402	FileIO::IsTrailingMarkerValid caused an access violation when trying to read the trailing marker for a record.
0x80040403	Attempt was made to access data beyond the end of a read-only file.
0x80040404	This tag is currently being logged by an archive.
0x80040405	When trying to expand a record size, the trailing record should have been bump to the end of the file and then converted to a Dead Record. When trying to absorb the trailing record, it was found not be a Dead Record.
0x80040406	A trend vector present in the tag key was not found in the data file.
0x80040407	A String Record referenced in the String Vector was not found.
0x80040408	A TableVector referenced in the TableKey was not found.
0x80040409	An unknown record type was encountered when trying to bump a record to the end of the file.
0x8004040A	There are no TrendVectors in this TagKey.
0x8004040B	The Reader Interface was closed with ItemHandles that were not released. This will occur if the network connection drops out or the client crashes without releasing the Reader Interface.
0x8004040C	This DataSet does not contain any .HDB2 data files in the primary path.
0x8004040D	This item ID is already defined in this DataSet.
0x8004040E	There are no Table Vectors in the specified TableKey.
0x8004040F	An attempt was made to write into a .HDB2 file that is in the archive path. All .HDB2 files in the Archive path are read-only!
0x80040410	An attempt was made to write data, but no file covers the range of the specified timestamp. The timestamp was before the oldest time, later than the newest time, or within a time range in the middle of the DataSet where a data file does not exist. (This error will occur if the HDB2 files are not in the correct sequence which is controlled by the HDB2 file name. Possibly a renamed HDB2 file.)
0x80040411	The oldest-newest time range cannot be found for the specified tag.
0x80040412	The annotation at the specified time was not found.
0x80040413	The timestamp of the data moved in a backward direction. The data has been ignored.
0x80040414	This trend vector is full.
0x80040415	There is a hole in the data at the specified time!
0x80040416	Was not able to identify a valid DataSet Name from the itemID.
0x80040417	Invalid License Information
0x80040418	Historian cannot write information into the registry!
0x80040419	Table Key range is outside the requested time.
0x8004041A	The physical size of the file is smaller than it should be.
0x8004041B	File is questionable. Probably because the file was not closed through the normal sequence.
0x8004041C	File size is not correct. Probably because the file was not closed through the normal sequence.
0x8004041D	Timestamp is prior to the last timestamp logged. New data has not been logged.
0x8004041E	Tag Key Record is Bad.
0x8004041F	Requested Address is beyond file Size.
0x80040420	Invalid TVQ context in Trend Vector.
0x80040421	No archive path is defined for this DataSet.
0x80040422	The file in which you are trying to log data has already been rolled over.
0x80040423	The maximum HDB2 file size of 2 GB has been reached.
0x80040424	The variant type is unsupported.
0x80040425	There are inconsistent times between Trend Vector Records. Was not able to find the time in a vector, or determine the hole between trend vector records.
0x80040426	The DataSet Name cannot contain a period.
0x80040427	Invalid Path Specification.
0x80040428	The specified path is the same as either the primary, archive or hot-swap directory. The primary, archive and hot-swap directories must all point to different directories.
0x80040429	The total number of clients for the Enterprise Historian has been exceeded.
0x8004042A	File %1 does not exist.
0x8004042B	The Historian can NOT run under the Launching User account.
0x8004042C	The TagCount does not match after the Roll-Over.
0x8004042D	There were no Tags in the DataSet to Roll-Over.
0x8004042E	File does not exist.
0x8004042F	The specified directory does not exist, is invalid or can not be accessed.
0x80040430	The timestamp of the data is a duplicate. The data has been ignored.
0x80040431	The data value variant type sent to the historian is not supported.
0x80040432	The Global String Record is full.
0x80040433	Invalid Global String Handle.
0x80040434	Command Not Found.
0x80040435	Annotation timestamp is between .HDB2 files and can't be stored.
0x80040436	Extra Data in TrendVector has mismatching size parameters.
0x80040437	The specified tag has been deleted.
0x80040438	Cannot store the value in .HDB file. Requires an .HDB2 file format.
0x80040439	.HDB file case sensitivity is different than the DataSet's.
0x8004043A	The tag type is invalid.
0x8004043B	The file creation time is earlier than or the same as the creation time of the last .HDB file in the DataSet.
0x8004043C	The trend vector has reached capacity and needs split.
0x8004043D	Insert/delete of historical data has been disabled in the Historian.
0x8004043E	The tag is marked as obsolete.
0x8004043F	TagName contains invalid characters.
0x80040440	Historian is not licensed for high-speed tag data.
0x80040442	Error inserting the value.
0x80040443	Insert/Replace failed because the HDB file is off-line.

0x80040444	Bad file handle in Virtual IO
0x80040445	Insert failed because audit information is required when inserting directly after a tvq that contains audit information.
0x80040446	Replace/Delete failed because audit information is required when changing a tvq that contains audit information.
0x80040447	Delete range failed because audit information is required when deleting a range that contains audit information.
0x80040448	Nudging Timestamp forward failed - file will need to trimmed with the HDB File Recovery tool.
0x80040449	Tag Data is Flatlining in this file.
0x8004044A	Cannot determine if audit is required.