Home > Btrieve Error > Btrieve Error 9

Btrieve Error 9


If you are running an application in a client/server environment and also need to access files located on a local drive: Make sure the Btrieve Requester is loaded. You attempted to open a local file with a Workgroup engine that isn't the designated Gateway engine for the file. Returned as COBOL status: 9/077 This error should not be encountered if using XFH2BTR. The differences between the two modes of operation are explained in the section File Operations without ANSI COBOL Conformance later in this chapter. this content

You can access the Knowledge Base at the Pervasive Software website. 010: The key field is not modifiable During an Update operation, the application attempted to modify a key field that For pre-v6.0 data files, there is a large pre-image file inside a transaction, and there is not enough disk space for a write to the pre-image file. Start by asking a few simple questions like: *"Does it occur for every user?," *"Does it occur on every workstation?," and *"Does it occur for every user on every workstation?" Because Possible causes for receiving this status code include the following: the directory is full, the disk is full, or the MicroKernel has not been granted sufficient rights by the operating system.

Pervasive Error 9

All of the keys must be in the first 1014 bytes of the record. This information can be directed to a file using the TRACE-FILE attribute described above. Returned as COBOL status: 23 The record address specified in a READ DIRECT (Get Direct) operation is invalid. The Xfh2btr module does not verify the number of key components in the file; if your version of Btrieve does not support the required number of key components then any error

You set the Create File Version option to v5.x, and you attempted to create a file that contains a key with a locale-specific ACS. If your files are in pre-v6.0 format and you are in a transaction, the pre-image file size increases for the duration of the transaction. For an Insert operation, the MicroKernel does not insert the record if the data buffer is shorter than the fixed-length portion of the record. Btrieve Error 2301 Returned as COBOL status: ansi 85 status: 48 ansi 74 status: 9/148 The application opened a file in read-only mode and tried to perform an Insert, Update or

It is caused by a mismatch of two fields at the char level. When installing NT, you have the option to give the 'System' user rights automatically to all files or have the administrator specify them. The file cannot be extended. Re-positioning the Btrieve file position indicator after a WRITE operation can only fail if WRITELOCK directives are used and the file is shareable.

Page size is not returned on a Btrieve Stat operation. Record Size The maximum record size with Extfh is 62 Kbytes. Stat Operation The bits set in the file Btrieve Error 11 Pre-v6.0 workstation MicroKernels return this status code when the number of files opened in Accelerated mode exceeded the number of buffers available in the MicroKernel cache. However, if 'System' does not have permissions under NT, the server returns a Status Code 94. This status can also indicated a file corruption, especially in files with variable length records.

Btrieve Error 14

Note: The non-ANSI conforming mode of operation makes no attempt to re-position the CRP and can, therefore, be significantly faster. Attempting to direct file I/O to the converter in these situations causes an error to be returned. Pervasive Error 9 View the active files with the Monitor utility to examine whether this may be happening. Btrieve Error 161 On opening a file, Extfh automatically searches the run-time environment space to see if an environment variable of the same name as the file exists.

Click Here to join Tek-Tips and talk with other members! news Returned as COBOL status: 9/009 This status should not be encountered by XFH2BTR as directory operations are not used. The initial timeout value is three seconds. By default, these services use the 'System' user. Btrieve Error 3006

For more papers, see the Google+ link. It is often difficult to diagnose exactly what is causing the problem, but there are some actions that can be taken to help prevent it. However, the MicroKernel detected that the existing bound file was out of sync (that is, an attempt to open the existing file would have returned this same status code). have a peek at these guys The total length of any key in a Btrieve file cannot be greater than 255 bytes.

Extended file error. Btrieve Error 35 Retry the operation. You have either attempted to open more handles than the MicroKernel is configured to support, or the MicroKernel attempted to open more files than the operating system allows.

On a Stat Extended operation, the signature field in the data buffer is not set to 0x74537845, the subfunction field is not set to 0x00000001, or the Pervasive PSQL Explorer field

Therefore, it is not possible for the reading position to be affected by normal WRITE operations. Returned as COBOL status: 9/025 The chunk offset is too big. Make sure to include this file (MSDADC.DLL) in your installation script. Btrieve Error 2 Generally, the minimum record length defined in the COBOL program determines the length of the fixed part of the record.

When using the Get operation using ActiveX Data Control, this error will occur only after the application is compiled and deployed. Refer to Advanced Operations Guide for information about recovering damaged files. 044: The specified key path is invalid The application tried to use the Get Direct/Record operation to establish positioning on Contact the third party vendor for additional information on configuring the Antivirus software to eliminate scanning specific data files. 026: The number of keys specified is invalid The number of keys http://hammerofcode.com/btrieve-error/btrieve-error-73.php Record number 4 is now defined by the Current Record Pointer (CRP).

Consult your Anti-Virus software manual for instructions on how to exclude files. If a Btrieve error is not shown on the trace but a COBOL error is returned, this error is generated within the Xfh2btr module. This is the equivalent of the Btrieve format string and on a Btrieve Stat operation , all of the keys are returned as having string format. The handle table is managed dynamically by the engine.

Returned as COBOL status: 9/065 Redirected device table full. Copyright © 1999 MERANT International Limited. The application cannot open the referenced file for RI checking because it is already open in Exclusive mode. A key segment data type is NUMERICSTS and the segment length is less than 2.

The filter limit has been reached. Returned as COBOL status: 9/033 The application specified an invalid attribute for an auto-increment key. BTRMAXREC:nnnn This specifies the maximum record length that should be returned on an opcode 06 call to this file. Return to top Status 3 This status code indicates that the operation cannot continue because the file is not open.

Returned as COBOL status: 9/125 Btrieve requester unable to access NetWare Runtime server. Keys are stored in ascending order and are always modifiable. Check to see if the ~pvsw~.loc in that directory is flagged read only. On a Get Direct/Chunk or Update Chunk operation, the descriptor structure in the data buffer is incorrect, or is inconsistent either internally or with respect to the data buffer length.

This provides more flexibility in defining page sizes and record lengths. The user performing the OPEN OUTPUT receives a "file locked" error because the exclusive OPEN call fails. Record Lengths Variable length record Btrieve files consist of two parts - a Returned as COBOL status: 9/077 This status should not be encountered by XFH2BTR as files are never extended. Perform the same with NET2 while NET1 disconnected.

Handling C-ISAM Files Byte-stream File Handling Btrieve Error Codes 001 - 199 ← Pervasive PSQL MicroKernel (Btrieve) Database Engine Status Codes This section describes status codes that the MicroKernel returns. Nota: Verificar sólo es aplicable a los encabezados de las transacciones y a los archivos de facturas abiertas. 2. When the converter needs to call the Btrieve run-time to perform I/O, it calls the module _BTRV. This status is also returned if you do Get By Percentage with percentage value over 10,000 or file has no records.