Error codes 400 - 499

This could indicate there was an attempt to read an internal resource record but the data contained in the resource is not actually a resource. Check to verify that your data is not mimicking a resource record mark. Review Data Record Positions in the FairCom documentation for more information.

This could also indicate the file could be corrupted, you can copy the file and try to verify the file with ctvfyfil -chkdat, rebuilding the file with ctrbldif, or try compacting the file.

Indicates the resource was not found. A possible cause is that you are trying to rebuild a dat file with no IFIL resource.

You can also get this error if your file has no alternate collating sequence resource. Few files do have an alternate collating sequence resource, and it is not a concern if it is logged at file open by the server.

Indicates a superfile host was not opened.

If the file that you are receiving this error on is supposed to be part of a superfile, check that the superfile host file is open.

If the file that you are receiving this error on is not part of a superfile, something is communicating to FairCom that it is part of a superfile. Check for a "!" in the file path, this is what can trigger this error.

Indicates there is a key update with a pending transactions.

This could also indicate that your save failed (due to a duplicate key or something else), but you did not check the return type, and when you committed the transaction this error occurred.

Indicates the resource was found with zero length, meaning the requested def blk is empty.

This could also indicate that the file is being opening via OpenFileWithResource() and it has no DODA resource.

This error could also occur and be logged by the server if the file has no DODA and does not need one. In this case, this error is not concerning.

Indicates a file could not be created during a dump recovery.

ctrdmp will return this error if it can not write files in the destination directory. This is typically a problem with the path or the drive.

Indicates there is not enough data to assemble key value.

An index requires data outside of the defined record length. This can be caused by corrupted files, a bad table header, or a mistake in specifying an index.

Indicates the service is not supported. This occurs when you are attempting to use an option unavailable to this library.

This error could be returned if you are trying to create a segmented data or index file on FPUTFGET. Encryption on segmented files in FPUTFGET is not supported.

It could also be returned if you try to connect to an FQL (FairCom DB Standalone SQL Service) server with the ISAM Explorer, as FQL does not have a full ISAM implementation.

Indicates group access is denied.

If you get this error performing SQLize, a change was made in V11.2.3 that causes the server to ignore the password being sent in the clear and rely on the existing connection or the ctree.conf file (for c-treeRTG), and the permissions provided by that user.

To correct this, change the user to one that has the proper permissions or add COMPATIBILITY SQLIMPORT_ADMIN_PASSWORD to go back to sending the password in the clear, and having the server check it.

Indicates the file does not have a unique Server/File number.

A table being opened by the server matches an existing table already open. This is most often caused by duplicating tables and opening both copies. The FairCom DB header needs to be updated on the copy before you can open it.

Indicates an incremental index and that an active tran is not allowed.

This error can occur when you try to add a temporary index on a transactioned file if you are not handling the transaction correctly. For example, when you try to add the index outside of the transaction.

Indicates an error deleting sortwork file.

In versions before c-tree V11.7.x this was error 471.