Btrieve Error Codes

Btrieve(tm) Error codes

TAS Professional powered by CAS no longer ships with the Btrieve 6.15 workgroup engine

The Btrieve(tm) Record Manager returns a status code after each operation that an application performs. If the operation is successful, Btrieve returns Status Code 0. If the operation is not successful, Btrieve returns one of the nonzero status codes described in this section.

Summary of Btrieve error codes

1: The operation parameter is invalid.

2: The application encountered an I/O error.

3: The file is not open.

4: The application cannot find the key value.

5: The record has a key field containing a duplicate key value.

6: The key number parameter is invalid.

7: The key number has changed.

8: The current positioning is invalid.

9: The operation encountered an end-of-file mark.

10: The key field is not modifiable.

11: The specified filename is invalid.

12: Btrieve cannot find the specified file.

14: Btrieve cannot create or open the pre-image file.

15: The application encountered an I/O error during pre-imaging.

16: The application encountered an expansion error.

17: The application encountered a close error.

18: The disk is full.

19: The application encountered an unrecoverable error.

20: The Record Manager or Requester is inactive.

21: The key buffer parameter is too short.

22: The data buffer parameter is too short.

23: The position block parameter is not 128 bytes long.

24: The page size or data buffer size is invalid.

25: The application cannot create the specified file.

26: The number of keys specified is invalid.

27: The key position is invalid.

28: The record length is invalid.

29: The key length is invalid.

30: The file specified is not a MicroKernel file (The file specified is not a Btreive file.)

This status code is returned in one of the following situations:

•	The MicroKernel did not create the file, or a pre-v3.x MicroKernel created it.

•	While using an earlier version of Btrieve, you opened a file created by a later version that has a format incompatible with the earlier version.

•	The first page of the file may be damaged. Use a backup copy of your data file. If you receive this status code and you suspect that the header page of the source file is damaged, recover the file as described in Pervasive Advanced Operations Guide.

•

You have attempted to access a valid Btrieve file. This status code is returned when old engines access newer file formats. A likely scenario is that data created by a new server engine is later used by an earlier Workgroup engine. Status 30 can be reported if the file format is newer than the MicroKernel engine attempting to open it. Particularly, accessing a 7.x file with a 6.x engine causes this error.

NOTE: Previously, accessing a 6.x file with a 5.x engine returned Status 2: "the application encountered an I/O error". TAS7 Uses the World Famous Btreive 6.15 if for some reason you upgrade to the pervasive Database Engine you may get this error if you do make a backup of your data and run the pervasive Re build program.

31: The file is already extended.

32: The file cannot be extended.

34: The specified extension name is invalid.

35: The application encountered a directory error.

36: The application encountered a transaction error.

37: Another transaction is active.

38: Btrieve encountered a transaction control file I/O error.

39: A Begin Transaction operation must precede an End/Abort Transaction operation.

40: The file access request exceeds the maximum number of files allowed.

41: Btrieve does not allow the attempted operation.

42: A file previously opened in Accelerated mode was not closed.

43: The specified record address is invalid.

44: The specified key path is invalid.

45: The specified key flags are invalid.

46: Access to the requested file is denied.

47: The number of files opened exceeds the maximum allowed.

48: The alternate collating sequence definition is invalid.

49: The extended key type is invalid.

53: The language interface version is invalid.

54: The variable-length portion of the record is corrupt.

55: The application specified an invalid attribute for an autoincrement key.

56: An index is incomplete.

58: The compression buffer length is too short.

59: The specified file already exists.

60: The specified reject count has been reached.

61: The work space is too small.

62: The descriptor is incorrect.

63: The data buffer parameter specified on an Insert Extended operation is invalid.

64: The filter limit has been reached.

65: The field offset is incorrect.

66: The maximum number of open databases has been exceeded.

67: Btrieve cannot open the SQL data dictionaries.

68: Btrieve cannot perform the RI Delete Cascade operation.

69: The Delete operation specified a file that is damaged.

71: There is a violation of the RI definitions.

72: Btrieve cannot open the RI-referenced file.

73: The RI definition is out of sync.

74: Btrieve aborted the transaction.

76: There is a conflict on the referenced file.

77: The application encountered a wait error.

78: Btrieve detected a deadlock condition.

79: A programming error occurred.

80: Btrieve encountered a record-level conflict.

81: Btrieve encountered a lock error.

82: Btrieve lost positioning.

83: Btrieve attempted to read a record outside the transaction.

84: The record or page is locked.

85: The file is locked.

86: The file table is full.

87: The handle table is full.

88: The application encountered an incompatible mode error.

91: The application encountered a server error.

92: The transaction table is full.

93: The record lock types are incompatible.

94: The application encountered a permission error.

95: The session is no longer valid.

96: A communications environment error occurred.

97: The data buffer is too small.

98: Btrieve detected an internal transaction error.

99: Btrieve requester unable to access NetWare Runtime server.

100: No cache buffers are available.

101: Insufficient operating system memory is available.

102: Insufficient stack space is available.

103: The chunk offset is too big.

104: Btrieve does not recognize the locale.

105: The file cannot be created with Variable-tail Allocation Tables -(VATs).

106: The chunk cannot perform a Get Next operation.

107: The application attempted to perform a chunk operation on a pre-v6.0 file.

109: The application's transaction has become too complex.

130: Btrieve ran out of system locks.

133: More than 5 concurrent users attempted to access the same Btrieve file.

Page url: http://www.cassoftware.com/tas/manual/btrieveerrorcodes.htm