Error codes 800 - 999

Indicates response timed out.

A client request using a socket timeout failed because the configured timeout elapsed before receiving a response from the server. For replication environments, see Troubleshooting replication.

Indicates Improper ctQT actions: see sysiocod:

Indicates a connection attempt using the Shared Memory protocol failed due to an incompatibility between client and server.

As of 11.5, we use a newer (faster) Shared Memory system on Linux (Unix) systems. Both the server and the client have to be compiled to support it. Check for ctFeatSHMEMspin2 to be defined in ctopt2.h. If it is not defined, this error is returned.

Transactional replication: Indicates a failure to start FairCom DB remote client subsystem, see CTSTATUS.FCS for details.

This can happen if a distributed transaction replication target server (DRC model) can't load the mtclient.dll or libmtclient.so that it needs to communicate with the master server.

Transactional replication: Indicates an attempt to update replica without enabling transactional replication for the connection.

This means your server is a replication target using distributed commits (DRC model) and you are trying to write a record normally.

Transactional replication: Indicates a failure to read record for update. Local record differs from master record.

DRC 2 phase replication model: This error is returned if you try to lock a record for editing on a target server that needs to be updated from the master server by the replication engine but hasn't yet. Check replication logs to see if the agent quit or replication has failed.

Indicates an attempt to get the IP addresses associated with the host system failed. Check that TCP/IP name resolution is properly configured on the host system.

The machine name cannot be resolved. This can be because is cannot be resolved to an IP address or, on OS X, it can be caused by the hostname not matching the sharing name.

Check the CTSTATUS.FCS file for "Failed to get IP address for host." If you see this, the network is not resolving the machine name to an IP number. On Linux-based machines you can work around this by editing the server's hosts file and adding a line with the server's IP address and machine name. This should cause the machine name to resolve to the IP you entered.

On OS X, the network hostname has to match the sharing name in the Sharing control panel. Type hostname in the terminal to see the hostname and compare it to the sharing name. If they are different, type the following command in the terminal to set the hostname to match the Sharing control panel: scutil --set HostName myhostname

Indicates n attempt to perform a sequential, index-based retrieval when the index does not have a current key value. This may occur because ctISAMKBUFhdr has turned off key buffer updates (MBUF_ERR); or a partial record read or changing current ISAM record location does not permit the current key value to be assembled (DBUF_ERR); or a conditional index constraint or NUL key results in no key value (NKEY_ERR).

This error can be returned in V11, though it was fixed in V11.5

Indicates A logon fails with QABN_ERR when a ctQUIET() call has been abandoned, blocking attempts to validate user logons. This is typically because a connection called ctQUIET(), QuietCtree(), ctadmn (option 8), or the ctquiet utility and then was disconnected before it could unquiet.

When this happens, only the super user can logon and call ctQUIET() or QuietCtree() with a ctQTunblockALL argument. or call the ctquiet utility: "ctquiet -s FAIRCOMS -u -p ADMIN". or call ctadmn and use option 8 to wake up c-tree.

Create Sequence: Indicates an invalid sequence name was specified: the name is NULL, empty, or too long.

Open Sequence: Indicates no sequence exists that has the specified name.

Indicates the initial value specified for the sequence is out of range.

If the sequence enforces a limit, the initial sequence value must be less than the sequence limit for an incrementing sequence or must be greater than the sequence limit for a decrementing sequence.

Indicates the current value specified for the sequence is out of range.

For an incrementing sequence, the current sequence value must be greater than or equal to the initial sequence value, and if the sequence enforces a limit the current sequence value must be less than or equal to the limit value. For a decrementing sequence, the current sequence value must be less than or equal to the initial sequence value, and if the sequence enforces a limit the current sequence value must be greater than or equal to the sequence limit.

Indicates the limit value specified for the sequence is out of range.

The sequence limit must be greater than the initial sequence value for an incrementing sequence or must be less than the initial sequence value for a decrementing sequence. The sequence limit is only enforced if the sequence type specifies the ctSEQLIM bit.

Indicates the increment value specified for the sequence is out of range.

The sequence increment amount must be a positive value that is less than the difference between the initial sequence value and the sequence limit.

Indicates low-level operations are not allowed on replicated files.

This can happen in older versions (pre-V11) when performing operations like PutDODA() on a file that previously used replication.

Indicates the file exists but could not be accessed. Check the system error code stored in sysiocod for the reason.

Under Windows, it can't get an exclusive open on the file. This can be because you have a file open via the server and are trying to open it single-user as well.

The most frequent cause of this error is a failure to obtain an exclusive open on the file at the OS level. This can be because you have the file open via the server and are trying to open it single-user. It can also be caused by an unrelated process opening the file and blocking the exclusive open. Under Windows it can be caused by a permission-level issue. Check the sysiocod value for the OS error.

Under Linux (Unix), insufficient file handles cause this error. Increase the FILES keyword in this case.

Indicates the instance number of a partition does not match the instance number maintained for the partition by the host file.

Typically the instance number of a partition is increased only when it has been purged and then a new partition (with the same raw partition number) is created, or an individual partition member has been rebuilt through a call to PTADMIN.

Indicates partitioned file rebuild requires special support.

Rebuilding the entire partitioned file requires ctPARTITION to be defined at compile time. Rebuilding an individual partition member may require ctPARTITIONinstnc to be defined at compile time, and the member rebuild must be initiated through PTADMIN().

Indicates IICT operations without ctFeatIICT enabled were encountered.

IICT stands for Immediate Independent Commit Transaction: a single ISAM update operation treated as a separate transaction within an existing, pending transaction.

This can be returned in ctrdmp. It is a V11.5 bug that was fixed in V11.6.

Indicates bad augmented record file mode at create.

For example, specifying ctAugmentedFxd without ctVLENGTH. Two of the conditions that return this error are:

Indicates error setting up compressiion routines. Check sysiocod for details.

sysiocod Explanation:

1 Non-zlib compression requires DLL

2 Bad version number

3 Inconsistent attrstr/attrlen

4 DLL name Unicode conversion error

5 DLL load error

6->13 Function name Unicode conversion error

14->21 Failed to resolve function proc address

32 Type/version mismatch in FncInit()

33 Could not allocate attrval in FncInit()

34 attrlen disagreement in FncInit()

35 Could not initialize compress context in CmpInit()

36 Could not initialize decompress context in ExpInit()

37 Invalid attrstr contents found by FncInit()

38 Could not allocate dedicated attrstr in ctSETCOMPRESS

1000+err where err is a DLL-specific unexpected error code

2000+err where err is a DLL-specific code related to corrupted

Indicates an internal error code returned by the shared memory communication protocol receive function for Linux (Unix) systems when the receive for a logoff operation fails on the semaphore wait.

This is a normal occurrence if the FairCom DB server has removed the semaphore set before the client read the response. In this case the client side code returns success.

Indicates the current master encryption key's attributes are inconsistent with the master key used to encrypt the security resource of the specified file.

For example, you might be using a 128-bit master key and are trying to read a file whose security resource was encrypted with a 256-bit master key.

Indicates an attempt to close an ISAM data file with the low-level file close routine CLSFIL.

COMPATIBILITY CLSFIL_ISAM restores the old behavior when CLSFIL is called for an ISAM data file. For standalone applications, the CLSFIL behavior can be restored by compiling the code with NO_ctBEHAV_CLSFIL_ISAM.

Indicates pre-image space overflow of image update count.

Each update of a record location, within a single transaction, causes the pre-image update count to be incremented. Repeated update of the same record within the transaction eventually overflows the update count.

Indicates FairCom DB server was not able to decrypt the buffer sent to it by the client. This is an unexpected error, contact FairCom support.

This error can be caused by a missing user name being passed to a utility which prevents the utility from opening a file, then this generic error gets returned and it might even say the file needs to be rebuilt. If all you did is forget to send the user name, the file doesn't need to be rebuilt.

If the purgeIFIL option is used, a copy of the partial record is placed in a temporary file; the record is overwritten with 0xff bytes; and sysiocod is set to PRTL_FF.

If the record is successfully dumped to the temporary file, but there is a problem overwriting the partial record with 0xff bytes, sysiocod will be set to PRTL_COD not PRTL_FF.

Whether or not the purge option is used, CTSTATUS.FCS contains the byte offset and length of the partial record. (Prior to V10.3, the values of PRTL_COD and PRTL_FF were ‑970 and ‑971 respectively.)

If the purgeIFIL option is used, a copy of the partial record is placed in a temporary file; the record is overwritten with 0xff bytes; and sysiocod is set to PRTL_FF.

If the record is successfully dumped to the temporary file, but there is a problem overwriting the partial record with 0xff bytes, sysiocod will be set to PRTL_COD not PRTL_FF.

Whether or not the purge option is used, CTSTATUS.FCS contains the byte offset and length of the partial record. (Prior to V10.3, the values of PRTL_COD and PRTL_FF were ‑970 and ‑971 respectively.)

Indicates file create called with a segmax > 1 but without ctSEGAUTO bit set in x8mode. segmax and x8mode are members of XCREblk.

To create a new segmented file, you have to have called ctSETSEG or set the ctSEGAUTO bit so the segment number can be set.

Indicates a shared memory connection could not be established because the system denied access to the client process.

For example, if a client is run as a Windows service and FairCom DB server is not run as a Windows service (or vice-versa), Windows does not allow FairCom DB server access to the client process which is needed to establish the shared memory connection.

Most often this happens in V11.2 or later because of a difference in Windows permission level between the server and the client that used to fail over to TCP/IP, though this has since been corrected.

Indicates FairCom DB is not licensed to use this feature.

Your .lic file is not created to allow you to do what you are trying to do.

Indicates VSS writer support could not be initialized.

The 64-bit versions of Windows Vista and later only support native VSS writers (64-bit systems only support a 64-bit VSS writer). See CTSTATUS.FCS for details.