Error codes 800 - 999

800

TDEP_ERR

Indicates TRANDEP file operation pending.

801

FBLK_PND

Indicates an attempt to set file block; leave core.

802

FBLK_SUP

Indicates file block not supported for file type.

803

LNEW_ERR

Indicates existing lock not replaced: cts_lok81().

804

SETO_ERR

Indicates configuration option that was specified in settings file cannot be overidden.

805

MSTK_ERR

Indicates no memory for func stack alloc.

806

KCON_ERR

Indicates a failure to connect to kernel engine.

807

MSTK_COD

Indicates ctDBGstack limit exceeded: debugging only.

808

TRQS_ERR

Indicates request timed out.

809

TRSP_ERR

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.

810

SLOG_ERR

Indicates status log write failure.

811

IAPI_ERR

Indicates update only from internal API.

812

ZRCZ_ERR

Indicates unexpected zero node size in header.

813

UBLK_ERR

Indicates unexpected state for user block obj.

814

FBLK_ACT

Indicates thread did not have ctFBactive set.

815

FBLK_NTF

Indicates ctFILBLK already in progress for file.

816

QTUQ_ERR

Indicates only one ctQUIET process may be active at a time.

817

QTAB_ERR

Indicates transaction aborted by ctQUIET.

818

QTFB_ERR

Indicates ctQUIET/ctFILBLK conflict.

819

QTBB_ERR

Indicates unexpected failure to block thread

820

QTBK_PND

Indicates an attempt to get QUIET; leave core.

821

MLAB_ERR

Indicates transaction abandoned due to MAX_USER_LOGS.

822

MLHG_ERR

Indicates abort request would be suspended.

-823

TRAB_COD

Indicates QTAB_ERR or MLAB_ERR but operation performed.

824

MIMP_ERR

Indicates problem impersonating thread.

825

QTOP_ERR

Indicates ctQUIET called with files opened.

826

QBAD_ERR

Indicates Improper ctQT actions: see sysiocod:

827

UTIM_OUT

Indicates user block timed out.

-828

ICUV_COD

Indicates ICU version updated.

-829

ICUV_REB

Indicates ICU version updated & rebuild required.

830

TTAB_ERR

Indicates transaction abandoned due to TRAN_TIMEOUT.

831

TTHG_ERR

Indicates abort request would be suspended.

-832

ITMP_COD

Indicates sysiocod value when ITIM_ERR occurs on a temporary index and record is skipped.

833

XNOD_ERR

Indicates the connection attempt has been rejected because it would exceed the maximum number of concurrent client machines allowed.

834

XCON_ERR

Indicates the connection attempt has been rejected because it would exceed the maximum number of concurrent connections allowed from this client machine.

835

TRAB_ERR

Indicates transaction aborted (for example, MLAB_ERR or TTAB_ERR) before the requested operation was processed (compare with TRAB_COD).

836

LCON_ERR

Indicates the connection attempt has been rejected because only connections from the local system are allowed.

-837

IDUP_COD

Indicates sysiocod value when KDUP_ERR occurs on a temporary index and error is ignored.

838

CEXC_ERR

Indicates clnleaf(CLNIDXX) failed to clean node. This error is very unexpected, please contact FairCom.

839

CTRN_ERR

Indicates index file requires key level lock cleaning.

-840

CTRN_COD

Indicates sysiocod when read only, admin open request blocked by on the fly CLNIDXX.

841

SHMC_ERR

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 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.

842

FBLK_ABT

Indicates all threads could not be cleared from the core, abort ctFILBLK() attempt.

843

QTBK_ABT

Indicates all threads could not be cleared from the core, abort ctQUIET() attempt.

-844

BTNO_COD

Indicates batch has been closed.

845

DNCT_ERR

Indicates index does not have distinct attribute.

846

DNCT_XCL

Indicates DISTINCT set update in progress.

847

RPTD_ERR

Indicates auto recovery interrupted.

-848

RDND_COD

Indicates sysiocod: LOKDYN demotion denied

-849

SAVP_COD

Indicates sysiocod: LOKDYN free denied

850

TR_CLIL_ERR

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.

851

TR_RMAP_ERR

Transactional replication: Indicates a failure to open replication mapping file. See CTSTATUS.FCS for details.

852

TR_RATR_ERR

Transactional replication: Indicates a failure to open replica for writing because the file does not meet the requirements for replication. See CTSTATUS.FCS for details.

853

TR_FNOD_ERR

Transactional replication: Indicates a failure to set node name for connection to master server. See CTSTATUS.FCS for details.

854

TR_REDF_ERR

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.

855

TR_SAVP_ERR

Transactional replication: Indicates a failure to establish a savepoint because savepoint number is out of sync with master.

856

TR_RDIF_ERR

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.

857

XSUP_ERR

Multi-user standalone mode: Indicates the superfile host is open in exclusive mode. The superfile member must be opened in exclusive mode, not shared mode.

858

TR_NSUP_ERR

Transactional replication: Indicates this feature is not supported for replicas.

859

UVRC_ERR

Indicates the client's structure definition for the file FAIRCOM.FCS!USER.dat is out of date. Update client library.

860

UVRS_ERR

Indicates the server's structure definition for the file FAIRCOM.FCS!USER.dat is out of date. Update FairCom DB server.

861

KLLX_ERR

Indicates after recovery, a key-level lock for an undone transaction was discovered in optional diagnostic scan.

862

UNPG_ERR

Indicates system pagesize query failed in LOCK_CACHE.

863

IMPD_ERR

Indicates the request to impersonate the specified connection was denied because the target connection does not allow impersonation.

864

IMPU_ERR

Indicates the request to impersonate the specified connection was denied because the target connection does not allow impersonation by the specified connection.

865

IMPA_ERR

Indicates the request to impersonate the specified connection was denied because the target connection is already being impersonated.

866

IMPB_ERR

Indicates the request to impersonate the specified connection was denied because the target connection is executing a database operation or is blocked.

867

CBKD_ERR

Indicates a failure to load the filter callback library. See CTSTATUS.FCS for details.

868

CBKF_ERR

Indicates a failure to resolve the filter callback function in the filter callback DLL. See CTSTATUS.FCS for details.

869

RCBK_ERR

Indicates a user-defined callback function terminated the rebuild operation.

870

CBKV_ERR

Indicates the filter callback DLL version is not compatible with the FairCom DB server's filter callback version, see CTSTATUS.FCS for details.

871

XFR_SOPN_ERR

Indicates the file transfer operation failed because the source file could not be opened for reading. Check sysiocod for the system error code.

872

XFR_DOPN_ERR

Indicates the file transfer operation failed because the destination file could not be opened for writing. Check sysiocod for the system error code.

873

XFR_READ_ERR

Indicates the file transfer operation failed because the source file could not be read. Check sysiocod for the system error code.

874

XFR_WRITE_ERR

Indicates the file transfer operation failed because the destination file could not be written. Check sysiocod for the system error code.

875

XFR_BCON_ERR

Indicates a bound database connection called the file transfer function, but this function is supported for client connections only.

876

XFR_BSIZ_ERR

Indicates the file transfer operation failed because the caller specified an invalid file transfer block size.

877

XFR_SFNM_ERR

Indicates the file transfer operation failed because the caller specified a NULL or empty source file name.

878

XFR_DFNM_ERR

Indicates the file transfer operation failed because the caller specified a NULL or empty destination file name.

879

XFR_VER_ERR

Indicates the version of the file transfer structure supplied by the caller is not compatible with the FairCom DB library's structure definition. Check sysiocod for the required file transfer structure version.

880

XFR_DEXS_ERR

Indicates the file transfer operation failed because the destination file exists and the caller did not specify that the destination file is to be overwritten.

881

XFR_TREP_ERR

Indicates the file transfer operation between a local and master server failed because the server does not support the transactional replication feature.

882

XFR_TRLC_ERR

Indicates the file transfer operation between a local and master server failed because the server is not configured as a local server. Use the REPL_MAPPINGS option to configure the server as a local server.

883

MUOP_ERR

Indicates an attempt was made to open a file multiple times by the same user with different user file numbers; this support is disabled.

‑884

DUFL_COD

Indicates a sysiocod value that indicates a user file number mismatch during lock or unlock operations.

-885

OCHK_COD

Indicates a sysiocod value that indicates this API call to perform a checkpoint took no action because a checkpoint was already in progress.

886

UFLK_ERR

Indicates unexpected CHG_UFLOCK failure, contact FairCom (sysiocod specifies locale).

887

DUFL_ERR

Indicates promoting a secondary lock from read to write is not supported.

888

CONGRP_INVTASKID_ERR

Indicates the specified task ID does not correspond to an active client connection.

889

CONGRP_INUSE_ERR

Indicates the specified connection is a member of a connection group.

890

HSTNAM_ERR

Indicates an attempt to get the name of the host system failed. Check that the system's host name is properly configured.

891

HSTADR_ERR

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

892

MBUF_ERR

Indicates an 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).

893

DBUF_ERR

Indicates an 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).

894

NKEY_ERR

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

895

TSEG_ERR

Indicates partition index segment definition does not satisfy the following constraint: there must be at least one segment used to perform the key-to-partition map, and all the segments used must come at the beginning of the key.

896

VSEG_ERR

Indicates covering index segment definitions do not map to partition index, contact FairCom.

897

KINC_ERR

Indicates covering index segment map (ptmap) is empty.

898

QABN_ERR

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.

899

PMCN_ERR

Indicates ISAM Context operations cannot be performed on partition member unless it has been opened in stand-alone mode (i.e., independently of the host file).

900

SEQDUP_ERR

Indicates a sequence having the specified name already exists.

901

SEQNAM_ERR

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.

902

SEQHND_ERR

Indicates the specified sequence handle is invalid.

903

SEQTYP_ERR

Indicates the specified sequence type contains an invalid combination of sequence type options. The sequence type must be set to either ctSEQINC (incrementing sequence) or ctSEQDEC (decrementing sequence), and either ctSEQCYC (cycling sequence) or ctSEQTRM (terminating sequence), and optionally includes ctSEQLIM (enforce sequence limit).

904

SEQINI_ERR

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.

905

SEQCUR_ERR

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.

906

SEQLIM_ERR

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.

907

SEQINC_ERR

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.

908

DSTX_ERR

Indicates the file header shows the maximum number of partial key distinct counts supported by the file is greater than the system support limit: ctMAXSEGdistinct. The file cannot be opened.

909

VFYVER_ERR

Indicates the structure version specified for the input and output structures is not supported by this version of the code.

910

VFYTRM_ERR

Indicates a user-defined callback function terminated the index verify operation.

911

NSUP_DAR

Indicates file contains a Direct Access Resource (DAR) that is not supported. sysiocod contains the type of DAR, see ctopt2.h for dartyp assignments.

912

URES_ERR

Indicates special resource can only be added by system routine. sysiocod holds the special resource type.

913

DDAR_ERR

Indicates duplicate DAR not allowed. sysiocod holds the 'dartyp' value. See FC_DAR_TYPES in ctopt2.h for intrpetation.

914

XDAR_ERR

Indicates requested DAR does not exist.

915

LAUG_ERR

Indicates log file requires augmented log entries that are not supported.

916

NDAR_ERR

Indicates mismatch between header DAR count, and DARs found in resource chain.

917

ODAR_ERR

Indicates more instances of a particular DAR type for a single file could not be added - the limit has been reached.

918

RDAR_ERR

Indicates DAR attribute word is marked deleted (FC_DAR_delete bit). A nonTran file DAR delete forces DAR image to disk with FC_DAR_delete bit set in attribute word.

919

REPL_ERR

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.

920

FNAC_ERR

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, insufficient file handles cause this error. Increase the FILES keyword in this case.

921

IDFL_CHG

Indicates an attempt to change IDfield during an ISAM rewrite operation - the rewrite has failed.

922

IDFL_BUF

Indicates an attempted ISAM rewrite operation without current ISAM IDfield buffer contents and there is no way to determine if IDfield has been changed - the rewrite has failed.

923

IERR_COD

Indicates an internal error has occurred; similar to a catastrophic terr. Instead of terminating execution, IERR_COD is returned, sysiocod is set to a local code, and a message is written into CTSTATUS.FCS.

924

SADM_ERR

Indicates only the super administrator user account (named ADMIN) can perform this operation. For example, only ADMIN can change ADMIN group membership.

925

SCMP_ERR

Indicates the FairCom DB client is attempting to use features of the SECURITY API function that this FairCom DB Server does not support. Update your FairCom DB Server.

926

HLMT_ERR

Indicates the transaction history log scan terminated because the user-specified limit on the number of logs to scan was reached.

927

PNST_ERR

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.

928

PMRB_ERR

Indicates partitioned file rebuild did not successfully rebuild all partitions. See CTSTATUS.FCS for more details.

929

PRBL_ERR

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().

930

PNSX_ERR

Indicates partition member instance # exceeds maximum of 255 for a non-huge partitioned file. Use RBLIFILX8 to rebuild the entire set of partitioned files.

931

PALL_ERR

Indicates only bad partitioned file components could not be rebuilt, the entire partitioned file must be rebuilt instead. Additionally, badpartIFIL must be removed from tfilno member of IFIL used in RBLIFILX8.

932

BMPW_ERR

Indicates the specified encryption master password is incorrect.

933

ICOD_ERR

Indicates an encryption operation failed due to an unexpected internal error. See CTSTATUS.FCS for details.

934

IICT_ERR

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.

935

IICT_FIL

Indicates file has already been updated within a transaction. Open the file with a different user file number and set IICT state with the new file number, or, an add/rebuild index called for file previously placed in IICT state.

936

AREC_BUF

Indicates a buffer for an augmented variable length record operation — for example, ctCMPREC.

937

AREC_SUP

Indicates augmented record support not available (ctAUGREC / ctCMPREC / ctFeatFLEXREC).

938

AREC_DCM

Indicates data record could not be decompressed. sysiocod set to Z_xyz_ERROR.

939

AREC_ISM

Indicates compressed record length files require ISAM update, not low-level update.

940

AREC_NOP

Indicates requested operation not supported for augmented records.

941

LSEC_ERR

Indicates this FairCom DB server requires a secure logon that your FairCom DB client library does not support. Update your FairCom DB client library.

942

LSES_ERR

Indicates this FairCom DB client uses a secure logon that your FairCom DB server does not support. Update your FairCom DB server.

943

TFLN_ERR

Indicates FairCom DB does not support a rebuild or compact option that you specified in the IFIL's tfilno field.

944

AREC_MOD

Indicates bad augmented record file mode at create.

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

945

AREC_FXD

Indicates add/update varlen must match fixed length for file with ctAugmentedFxd specified at create.

946

CMPR_ERR

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

947

SMLO_ERR

Indicates an internal error code returned by the shared memory communication protocol receive function for 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.

948

PMXS_ERR

Indicates operation on partition host cannot be performed if partition members already exist. Operation must be performed after the host is created, but before any partition members are created.

949

IEXS_ERR

Indicates the request to start an IICT failed because an IICT is already active.

950

INON_ERR

Indicates the request to end an IICT failed because no IICT is active.

951

IACT_ERR

Indicates the request to commit the transaction failed because an IICTxtd is active. First commit or abort the IICTxtd. You may also abort the transaction, which first aborts the IICTxtd.

952

ENCK_ERR

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.

953

QTOC_ERR

Indicates a call to suspend a thread because of ctQUIET processing failed because the thread owned the file open/close semaphore.

954

NCMP_ERR

Indicates compacting a partitioned file is not supported.

955

DOTX_ERR

Indicates an attempt to acquire internal mutex, ctpdotsema, out of order. This error is unexpected, contact FairCom.

956

APND_ERR

Indicates partition member pending archive

957

DMAP_ERR

Indicates this index file is already mapped to a different data file.

958

IMIS_ERR

Indicates data record is missing identity field value.

959

LSEV_ERR

Indicates this FairCom DB client uses a different secure logon version than your FairCom DB server. Update your FairCom DB client.

960

LAUT_ERR

Indicates FairCom DB FairCom DB license authorization failed. Check CTSTATUS.FCS for error message.

961

PWDC_ERR

Indicates this FairCom DB server requires a secure password transmission method that your FairCom DB client library does not support. Update your FairCom DB client library.

962

PWDS_ERR

Indicates this FairCom DB client uses a secure password transmission method that your FairCom DB server does not support. Update your FairCom DB server.

963

LISM_ERR

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.

964

SCNT_ERR

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.

965

BCOD_ERR

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.

966

BORD_ERR

Indicates FairCom DB was compiled with the wrong byte order for this platform.

967

ULMT_ERR

Indicates logon is denied because this user account has reached its maximum number of concurrent logons. Use the FairCom DB monitor tool to see currently active connections.

968

GLMT_ERR

Indicates logon is denied because one of the groups for this user account has reached its maximum number of concurrent logons.

969

QTBK_THD

Indicates an attempt to suspend the thread that invoked ctQUIET. Such a suspension would hang the server. sysiocod is set to the type of suspension request such as ctQTtranbeg, or to a negative cterrc.h entry such as LWRT_COD.

970

ISAM_MUSR_ERR

Indicates the connection attempt has been rejected because it would exceed the maximum number of concurrent ISAM connections allowed.

971

SQL_MUSR_ERR

Indicates the connection attempt has been rejected because it would exceed the maximum number of concurrent SQL connections allowed.

-972

PRTL_COD

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.)

-973

PRTL_FF

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.)

-974

LWRT_COD

Indicates an attempt to write to log files when ctQTblockLogFiles is in force. (Prior to V10.3, the value of this error code was ‑972)

-975

FNOP_COD

Indicates sysiocod value to caller of file open that the file is not already open. (Prior to V10.3, the value of this error code was ‑10)

-976

FNOR_COD

Indicates sysiocod value to the caller of ctrcvopn81() that FNOP_ERR occurred because the file is not on the dump recovery list. (Prior to V10.3, the value of this error code was ‑11)

977

XATO_ERR

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.

978

SHMP_ERR

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.

979

FLIC_ERR

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.

980

KEYX_ERR

Indicates secure key exchange failed, see CTSTATUS.FCS for details.

981

CDLL_ERR

Indicates the specified DLL or shared library could not be loaded, see CTSTATUS.FCS for details.

982

CDLF_ERR

Indicates the specified function name in the specified DLL or shared library could not be resolved, see CTSTATUS.FCS for details.

983

IICT_A3T

Indicates client/server mismatch on IICTxtd communications.

984

ALMT_ERR

Indicates logon is denied because the number of distinct user accounts that are allowed to be connected at one time has been reached.

985

LDRQ_ERR

Indicates logon is denied because this user account requires LDAP authentication, but FairCom DB server has not enabled LDAP authentication.

986

UNKA_ERR

Indicates the specified user account authentication type is invalid or not supported.

987

LRUB_ERR

Indicates LRU scheme for index buffers did not find an available index buffer. This is most likely caused by a low IDX_MEMORY.

-988

CLSF_COD

Indicates internal routine try_FBclsfile successfully closed a low-level index file during an ISAM file block.

-989

OPNF_COD

Indicates internal routine try_FBopnfile successfully re-opened a low-level index file during an ISAM file block.

990

DPRT_NSUP_ERR

Indicates this operation is not supported for a dynamic partitioned file.

991

DPRT_NOMBR_ERR

Indicates no partition members have been associated with this dynamic partition host file.

992

ALGN_ERR

Indicates client cannot correct difference between client alignment and the alignment of the data file on disk.

993

DPRT_DDIF_ERR

Indicates the table, index, record, or field definitions of the partition member differ from those of the dynamic partition host file.

994

SCNV_ERR

Indicates server does not support server-side record image conversion.

995

VSSI_ERR

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.

996

MOFL_ERR

Indicates the MULTIOPN_DIFUSR/SAMUSR setting cannot be changed on this file because this connection has other open instances of this file that are using a different MULTIOPN_DIFUSR/SAMUSR setting than the one specified by the caller, or this file has pending locks.

997

RTGTRM_ERR

Indicates a user-defined callback function terminated the RTG operation.

998

MUOP_RCR

Indicates an attempt to perform multiple file open (co-file) with active recursive locks on the file.

999

MLOK_ERR

Indicates recursive data file lock not allowed if user has opened the file multiple times (co-files). An exclusive lock could not be obtained.