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.
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).
| ID | Error | Comments |
|---|---|---|
| 100 | BadHepAlc | The collection scale is outside the legal limits. |
| 101 | BadIdent | Each 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. |
| 102 | BadClass | Each 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. |
| 103 | BadBktVer | Each 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. |
| 104 | BadOpenHRes | The resource fork of the collection was unable to be opened. |
| 105 | BadPGToor | The Page Table (an internal table that tracks where every object in the collection is stored) resources can’t be loaded from the resource fork. |
| 106 | BadPGTdup | An error was encountered while reading the Page Table. Perhaps an entry was corrupted. |
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.