• Randmark 40
  • Randmark 40
 
Kevod Insurance System
 
KS4 Data Platform

 

GILTS - BTRIEVE error codes. Print E-mail

RandMark40'(RM40) has prepared a GILTS support-pack, and include herewith the basic BTRIEVE uitility's common error code solutions.

Feel free to contact us for more information on GILTS data conversions into our KIS policy administration system.

 


Error#

Error name, description & suggested solution. 

46

ACCESS TO FILE DENIED: An attempt has been made to access a file that is read only, or that has been locked. Solution:  Ensure all users are logged out, and run the CLEAR utility.

55

AUTOINCREMENT ERROR: A key was incorrectly specified during creation.

17

CLOSE ERROR: The file could not be closed.

58

COMPRESSION BUFFER TOO SHORT: Only applies to compressed files.

80

CONFLICT: A record cannot be updated because another user has already updated it. Solution: Get all users to log out, and retry.

25

CREATE INPUT/OUTPUT ERROR: The file could not be created. Solution: Check for a) full disk, b) full directory, c) an open file (on networks), d) a read only file, or whether there are e) no rights on the directories.

22

DATA BUFFER LENGTH: The data buffer parameter on the BTRIEVE call is not long enough to accommodate the length of the data record. Usually as a result of data incompatibility between GILTS releases.

7

DIFFERENT KEY NUMBER: An attempt was made to access the file using a different key number from the previous page.

35

DIRECTORY ERROR: An error occurred while switching between directories.

18

DISK FULL: The disk is full and will not allow any records to be added. Solution: Make disk space available.

5

DUPLICATE KEY VALUE: An attempt was made to add a record which already exists.

9

END OF FILE: An attempt was made to read past the end of the file.

39

END/ABORT TRANSACTION ERROR: An attempt was made to end a transaction that has not been started.

52

ERROR WRITING CACHE: Only applies to files opened in accelerated mode.

57

EXPANDED MEMORY ERROR: Check on other TSR’s that could be running.

16

EXPANSION ERROR: The file could not be enlarged to accommodate more records. Solution: Do a recover on the faulty file.

32

EXTEND INPUT/OUTPUT ERRORS: Only applies to files that are split over different disks.

13

EXTENDE FILE ERROR: Only applies to files that are split over different disks.

59

FILE ALREADY EXISTS: An attempt was made to create a file that already exists, but that shouldn’t be re-created.

31

FILE ALREADY EXTENDED: Only applies to files that are split over different disks.

85

FILE IN USE: An attempt was made to lock a file or record that is already locked by another user. Solution: Get all users to log out, and retry.

12

FILE NOT FOUND: The file does not exist in the specified file directory. Solution: a) Check the data directory in the configuration field, b) exit the system and check the file exists in the data directory.

3

FILE NOT OPEN: The requested file is not open.

86

FILE TABLE FULL: BTRIEVE file table is full. Solution: a) In BROKER.BAT increase the number specified in the /F: parameter on the BTRIEVE call, b) change the CONFIG.SYS file in the ROOT directory so that the number on *FILEs=* line is increased, (reboot the PC!)

87

HANDLE TABLE FULL: The operating system’s table is full. Change the CONFIG.SYS file in the ROOT directory so that the number on *FILEs=* line is increased, (reboot the PC!)

93

INCOMPATABLE LOCK TYPE: An attempt was made to lock a file or record in an incompatible manner.

88

INCOMPATIBLE OPEN MODE: An attempt was made to open a file in an incompatible manner.

42

INCOMPLETE ACCELERATED ACCESS: Only applies to files opened in accelerated mode.

56

INCOMPLETE INDEX: A supplementary index has been corrupted. Solution:Do a recover on the faulty file.

45

INCONSISTENT KEY FLAGS: The key flags have been incorrectly specified during file creation.

2

INPUT /OUTPUT ERROR: An error occurred during disk read/write. The file may have been damaged and must be recreated, or the file was not created by BTRIEVE. Solution: Recover the faulty file (e.g. RECOVER GBS RISK) which will recover the risk file in the GBS subdirectory. Note: users cannot work until the error has been addressed.

48

INVALID ALTERNATIVE SEQUENCE: The key sequence of a file has been incorrectly specified.

34

INVALID EXTENSION NAME: Only applies to files that are split over different disks.

11

INVALID FILE NAME: The file name specified does not confirm to the file naming convention.

53

INVALID INTERFACE: Only applies to files created under older versions of BTRIEVE.

29

INVALID KEY LENGTH: The length of the key has been specified incorrectly.

6

INVALID KEY NUMBER: An attempt was made to access a file using a key number that does not exist.

27

INVALID KEY POSITION: The position of the key within the record has been specified incorrectly.

1

INVALID OPERATION:  The BTRIEVE operation number is invalid.

51

INVALID OWNER: An unsuccessful attempt to lock a file was made. Ensure all users are logged out, and run the CLEAR utility.

8

INVALID POSITIONING:  An attempt was made to update a record without having retrieved the record first.

43

INVALID RECORD ADDRESS: The record address specified whilst retrieving a record is invalid.

28

INVALID RECORD LENGTH: The length of the record has been specified incorrectly.

21

KEY BUFFER TOO SHORT: The key buffer parameter on the BTRIEVE call is not long enough to accommodate the key field.

49

KEY TYPE ERROR: The key type has been incorrectly specified.

4

KEY VALUE NOT FOUND: BTRIEVE could not fine the requested record in the file.

81

LOCK ERROR: An error has occurred whilst attempting to lock a record. Get all users to log out, and retry.

82

LOST POSITION: BTRIEVE has lost its key in the file. Solution: Exit and retry.

47

MAXIMUM OPEN FILES: Only applies to files opened in accelerated mode.

10

MODIFIABLE KEY VALUE ERROR: An attempt was made to modify a key field that may not be modified.

30

NOT A BTRIEVE FILE: Either the file that is being opened was not created with BTRIEVE, or the file has been corrupted. Solution: Restore from Backup. Refer to “Recovering error 30” instructions.  Note: users cannot work until the error has been addressed.

44

NULL KEY PATH: An attempt was made to access a record with a null key.

26

NUMBER OF KEYS: The number of keys on the file has been specified incorrectly. Solution: Do a BUTIL–STAT on the faulty file and check whether there is supplementary key/s. If so, a) do a clear, as well as b) a recover on the faulty file.

41

OPERATION NOT ALLOWED: Certain BTRIEVE operations are not allowed. Solution: Ensure all users are logged out and run CLEAR in the main directory. If under archives, check ARC.BAT - the /I: parameter should match the drive on which GILTS is being run (i.e.   /I:F   or   /I:C).

50

OWNER ALREADY SET: An attempt has been made to open a file that has been locked by another user. Solution: Ensure all users are logged out, and run the CLEAR utility.

24

PAGE SIZE ERROR: The file page size has been specified incorrectly. Do a BUTIL – STAT on the faulty file.

94

PERMISSION ERROR: BTRIEVE cannot perform the requested operation on a file due to an operating system restriction. Solution: Check a) the user has created/deleted/ updated rights to the main directory, and subdirectories, or b) the file is read only.

23

POSITION BLOCK LENGTH: The file position block has been incorrectly defined.

15

PRE-IMAGE INPUT/OUTPUT ERROR: The pre-image file could not be updated. Solution: a) Check whether there is disk space available; b) do a recover on the faulty file.

14

PRE-IMAGE OPEN ERROR: The pre-image file could neither be opened nor created. Solution: a) Check whether there is disk space available; b) do a recover on the faulty file.

83

READ OUTSIDE TRANSACTION: The application attempted to delete or update a record within a transaction, but the record was not retrieved with the transaction.

84

RECORD IN USE: An attempt was made to lock a record that is already locked by another user. Solution: Get all users to log out, and retry.

20

RECORD MANAGER INACTIVE: A BTRIEVE request has been made without BTRIEVE being loaded. Solution: Log out, log back in, and check whether BTRIEVE is being loaded before GILTS boots up.

38

TRANSACTION CONTROL FILE INPUT/OUTPUT ERROR: An error occurred when BTRIEVE tried to write to the .TRN file. Solution: Check for a) full disk, b) no rights to the directory, and c)  ensure all users are out of GILTS and in the main directory type DELETE*.TRN.

36

TRANSACTION ERROR: A transaction operation cannot be performed because the T: option has not been specified when starting up BTRIEVE. Solution: Log out and back in again. Ensure all users are logged out. In the main directory type DELETE*.TRN, and check BTRIEVE is being loaded correctly before GILTS boots up.

37

TRANSACTION IS ACTIVE: A transaction was started whilst another was already active.  Solution: Exit and retry.

40

TRANSACTION MAX FILES: An attempt was made to update more than the maximum number of files allowable within a transaction.

19

UNRECOVERABLE ERROR: An unrecoverable error has occurred. Solution: Do a recover on the faulty file. Replace the BTRIEVE file with its most recent back-up.  Note: users cannot work until the error has been addressed.

54

VARIABLE PAGE EDITOR: An unsuccessful attempt was made to access a variable length record, such as used in long descriptions. Solution: Use BUTIL-STAT to determine the faulty file, could be PDSC, RDSC, CLDC, CDSC, CRDC or MDSC.  Try to recover this file, or restore the file from a backup.

 

______________________________________

 

 

Old Telephone 

 

 

Kevod Insurance System

Our flagship solution for the intermediaries who manage their own schemes, collect premiums, issue policies and record claims.

Read More

Screen Shots

Screen ShotsTo take a closer look at how the system displays on your PC and the user interface.

Click Here

KIS Brochure

Brochure DownloadTo Download the latest KIS Brochure to read at your leisure.


Click Here

Copyright © Ks4 by Randmark 40 (Pty) Ltd

Aqua IT Consulting