Product
Support
Everything Else
Helix Utility: Error Code Reporting in Helix 7.0
Introduction

Helix Utility 7.0 improves the error reporting when a collection can’t be opened. This technote lists the error codes, along with a short description of what each one means.

Error Codes

These codes have long existed internally and historical documentation on them is sketchy at best. If you encounter one of these errors, please contact us so we can help you resolve the problem (and learn more about these errors).

IDErrorComments
100BadHepAlcThe collection scale is outside the legal limits.
101BadIdentEach Helix file starts with a header containing critical information about the collection. If the ‘identifier’ in the header does not match an expected value, this error is returned.
102BadClassEach Helix file starts with a header containing critical information about the collection. If the ‘class code’ in the header does not match an expected value, this error is returned.
103BadBktVerEach Helix file starts with a header containing critical information about the collection. If the ‘version’ in the header does not match an expected value, this error is returned.
104BadOpenHResThe resource fork of the collection was unable to be opened.
105BadPGToorThe Page Table (an internal table that tracks where every object in the collection is stored) resources can’t be loaded from the resource fork.
106BadPGTdupAn error was encountered while reading the Page Table. Perhaps an entry was corrupted.
Error Logs

When Helix Utility checks a collection, details shown in the Activity Log section of the window are also written to a permanent log file. See Helix Logs and How to Locate Them for information on retrieving these log files.