FairCom error codes 400 - 499

400

RCRE_ERR

Indicates the resource is already enabled.

401

RNON_ERR

Indicates the resources are not enabled.

402

RXCL_ERR

Indicates the file must be exclusive in order to enable the resource.

403

RZRO_ERR

Indicates an empty resource ID.

404

RBUF_ERR

Indicates the output buffer is too small.

405

RDUP_ERR

Indicates the resource ID was already added.

406

RCSE_ERR

Indicates the resource search mode is bad.

407

RRED_ERR

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.

408

RNOT_ERR

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.

409

RELN_ERR

Indicates the resource length is <= 0.

410

USTP_ERR

Indicates the user is not active.

411

BSUP_ERR

Indicates there is not a superfile.

412

SOPN_ERR

Indicates there was an attempt to create an open superfile member.

413

SDIR_ERR

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.

414

SNST_ERR

Indicates superfiles can not be nested.

415

SADD_ERR

Indicates AddKey() was illegally called on a superfile.

416

SDEL_ERR

Indicates DeleteKeyBlind() was illegally called on a superfile.

417

SPAG_ERR

Indicates the superfile was created with a different index node size.

418

SNAM_ERR

Indicates the superfile was created with a maximum name length that exceeds the current maximum.

419

SRCV_ERR

Indicates the host superfile does not support recovery.

420

TPND_ERR

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.

421

BTFL_ERR

Indicates the filter is not supported likely due to an invalid value in a mode parameter.

422

BTFN_ERR

Indicates the function is not supported likely due to an invalid value in a mode parameter.

423

BTIC_ERR

Indicates a batch is incomplete. This likely occurred because you specified BAT_COMPLETE in a DoBatch() call.

424

BTAD_ERR

Indicates an add list error or an internal processing problem, possibly due to a memory overwrite.

425

BTIP_ERR

Indicates a batch is already in progress. You likely made a call to DoBatch() to open a new batch before the previous batch had completed. Instead, try making a call with a mode of BAT_CAN first.

426

BTNO_ERR

Indicates there is no active batch. You are likely calling DoBatch() with a mode of BAT_CAN or BAT_NXT.

427

BTST_ERR

Indicates the status information was already returned. You are likely making two consecutive DoBatch() calls looking for status information.

428

BTMT_ERR

Indicates there is no more information, and that the batch was cancelled.

429

BTBZ_ERR

Indicates bufsiz is too small for a single record - you need a larger buffer for this file.

430

BTRQ_ERR

Indicates the request is a NULL pointer.

431

LAGR_ERR

Indicates the aggregate/serialization lock was denied.

432

FLEN_ERR

Indicates the fixed-length string requires len in DODA.

433

SSCH_ERR

Indicates the segment definition is inconsistent with the schema.

434

SSCH_ERR

Indicates a very long def block is not supported.

435

FMEM_ERR

Indicates there is a file def memory error.

436

DNUM_ERR

Indicates the def number is bad.

437

DADR_ERR

Indicates defptr was NULL during GETDEFBLK().

438

DZRO_ERR

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.

439

DCNV_ERR

Indicates the file definition conversion is missing. You should contact FairCom.

440

DDDM_ERR

Indicates there is a dynamic dump is in progress.

441

DMEM_ERR

Indicates there is no memory for a dynamic dump file bumper.

442

DAVL_ERR

Indicates one or more files are not available for dump.

443

DSIZ_ERR

Indicates there is a file length discrepancy.

444

DCRE_ERR

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.

445

SDAT_ERR

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.

446

BMOD_ERR

Indicates an invalid key mode.

447

BOWN_ERR

Indicates you must be the owner of this file.

448

DEFP_ERR

Indicates the file definition permission was denied.

449

DADM_ERR

Indicates an ADMIN has opened file, and it cannot be deleted.

450

LUID_ERR

Indicates an invalid user ID when logging on server.

451

LPWD_ERR

Indicates an invalid password when logging on server.

452

LSRV_ERR

Indicates the server could not process user/acct info.

453

NSRV_ERR

Indicates an invalid server name.

454

NSUP_ERR

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.

455

SGRP_ERR

Indicates user does not belong to group.

456

SACS_ERR

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.

457

SPWD_ERR

Indicates an invalid file password.

458

SWRT_ERR

Indicates write permission not granted.

459

SDLT_ERR

Indicates delete permission denied

460

SRES_ERR

Indicates resource not enabled.

461

SPER_ERR

Indicates a bad permission flag.

462

SHDR_ERR

Indicates no superfile directory found during CTSBLD() processing.

463

UQID_ERR

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.

464

IISM_ERR

Indicates ISAM level logon not performed.

465

IINI_ERR

Indicates an incremental index and dnumidx < 1.

466

IIDT_ERR

Indicates an incremental index and dfilno is not an ISAM file.

467

IINM_ERR

Indicates an incremental index and aidxnam is NULL for first.

468

IITR_ERR

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.

469

NGIO_ERR

Indicates a negative IO request.

470

LGST_ERR

Indicates that the guest logons were disabled. This error occurs when you are trying to log into a server via a guest and that option is turned off for that server.

471

JOBT_ERR

Indicates a job thread launch error - ctFeatJOBMGTSYS.

476

SORT_SWDEL_ERR

Indicates an error deleting sortwork file.

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

477

SORT_ALC_ERR

Indicates an error getting first data area.

478

SORT_INITS_ERR

Indicates sinit phase not previously performed-srelease.

479

SORT_RET_ERR

Indicates sreturn phase already started.

480

SORT_DATA_ERR

Indicates no records in data buffers.

481

SORT_INITR_ERR

Indicates sint phase not previously performed-sreturn.

482

SORT_NOMEM_ERR

Indicates not enough memory.

483

SORT_DATAP_ERR

Indicates no valid record pointers in merge buffers.

484

SORT_SWOPN_ERR

Indicates an error opening sortwork file.

485

SORT_SWCRE_ERR

Indicates an error creating sortwork.00x file.

486

SORT_SIZO_ERR

Indicates no records fit in output buffer.

487

SORT_READ_ERR

Indicates an error reading sortwork file.

488

SORT_SIZM_ERR

Indicates bytes in buf <> merge buf size.

489

SORT_PTR_ERR

Indicates an error adjusting file pointer.

490

SORT_SWECL_ERR

Indicates an error closing sortwork.00x.

491

SORT_SWCL_ERR

Indicates an error closing sortwork file.

492

SORT_SWDEL2_ERR

Indicates an error deleting softwork file.

493

SORT_REN_ERR

Indicates an error renaming sortwork.00x.

494

SORT_CLSO_ERR

Indicates an error closing output file.

495

SORT_CREO_ERR

Indicates an error creating output file.

496

SORT_SWAP_ERR

Indicates insufficient disk space or no more work file segments.

497

SORT_PATH_ERR

Indicates ct_tmppth is too long.

498

NLOG_ERR

Indicates old log file found during log create.

499

FIDD_ERR

Indicates mismatch between recovery log and file ID.