Btrieve Error 91
Make sure that the field offset is a valid value (from 0 through the record length minus 1). 066: The maximum number of open databases has been exceeded This status code To resolve, fill the KeyBuffer with the same fill char type as the field. 005: The record has a key field containing a duplicate key value The MicroKernel cannot add or Click Embedded Spaces (a check mark indicates that the option is enabled). 013: The MicroKernel could not open the extension file for an extended file The MicroKernel could not open the NT 4.0 with SP 3: Service Pack 3 for NT 4.0 seems to have a problem with IPX/SPX communication, generating a Status Code 20, breqnt-10, and other communication Status Codes and weblink
The path name may not start with a backslash( \ ). You can access the Knowledge Base at the Pervasive Software website. 004: The application cannot find the key value The MicroKernel cannot find the specified key value in the index path. Go to the directory where the file you attempted to open resides. The file has not been corrupted.
Pervasive Error 91
Click Application Characteristics in the Properties tree. RE: Btrieve Error Code 91 Pervasivite (Instructor) 20 Jul 01 18:22 Yep, lots, and it's no fun to fix. If the records' file is in v5.x format, this status code can indicate a file access conflict.
The MicroKernel returns this status code when you attempt to open the second file. If an application opens a file in any mode other than Exclusive, all other applications receive this status code when they try to open the same file in Exclusive mode. Delete records from the lower levels, and then try again to delete the record that the application was attempting to delete initially. Btrieve Error 11 This happens if support for Netware runtime server is enabled and scala cannot find a connection to the server, or a valid username.
Alternatively, the application can employ record locks to avoid conflicts. Btrieve Error 161 ThanksHaq 06-06-2003 5:55 PM In reply to [email protected] Joined on 04-23-2008 Posts 297 Re: Error 91 with Pervasive 8 Reply Contact Mohammad: We recently had another customer report this exact same You only need to run BTRBOX95.exe once even though you have multiple DOS sessions open. It was later ported to NetWare 3.0, released in 1989, as a NetWare Loadable Module (NLM).
If this status code occurred during an Open operation or a DROP TABLE statement, the application attempted to open a file that has an owner name assigned to it. Btrieve Error 35 Be sure that the referenced file is in one of the data file locations that the DBNAMES.CFG file specifies for the named database. check that the server volume is not full. Such alternative solutions would not be suitable for providing low-level record access for the functions we shall describe in this AppNote.
Btrieve Error 161
Note Please see the Pervasive PSQL Knowledge Base for new and updated articles on troubleshooting this status code. NetWare/IP The NetWare/IP Domain SAP/RIP Service (DSS) is a distributed Btrieve database which holds SAP/RIP information for a NetWare/IP domain. Pervasive Error 91 When you are using the Btrieve Requester to access the MicroKernel, the Requester waits and retries if a requested resource is locked. Btrieve Error 3006 For example, 512 is rounded up to 1,024, 2,560 is rounded up to 4,096, and so forth. 3The maximum number of index segments that can be used with the relational interface
For example, to save the contents of the PRODUCTS.DAT file to a data file, use the following command (typed all on one line): LOAD BUTIL -SAVE SYS:SYSTEM\PRODUCTS.DAT SYS:SYSTEM\PRODUCTS.TXT The resulting PRODUCTS.TXT have a peek at these guys Verify that the length of the key buffer equals the defined length of the key specified in the key number parameter. 022: The data buffer parameter is too short The data The MicroKernel Router has not been loaded, and the following situation has occurred: an application that uses both the MicroKernel Router and the MicroKernel to make remote calls (and which therefore The MicroKernel tried to open files bound to too many MicroKernel databases. Btrieve Error 2301
The position block parameter must be exactly 128 bytes long. 024: The page size or data buffer size is invalid The MicroKernel returns this status code in one of the following You attempted to open a local file with a Workgroup engine that isn't the designated Gateway engine for the file. The roll-in was designed in this fashion so that the file can still be used while the roll-in is occurring. check over here If a client connected to a Pervasive PSQL server encounters this status code, other clients performing read-only operations from the same disk may also receive a non-zero status. 019: The application
Access to this audit log file is controlled by the CSAUDIT.NLM module. Btrieve Error 2 For example, the setting should be 1500 for an Ethernet LAN or 4096 for a Token-Ring LAN. NetWare: The path must be given to a mapped path.
Increase Current to allow more sessions. (Note: The default is 1000 sessions; approximately 32 kilobytes of memory are required for each session.) Exit the configuration utility and restart the engines for
Check the file= setting in CONFIG.NT. This status code often indicates a problem in nested transactions within your application. 038: The MicroKernel encountered a transaction control file I/O error This status code is obsolete in MicroKernel versions An application running on a 9.x or higher engine attempts to create a format file prior to 6.x (0600). 042: A file previously opened in Accelerated mode was not closed This Btrieve Error 20 For the recovery solution for this instance, refer to Microsoft Knowledgebase Article 190162, "Terminal Server and the 2048 Open File Limitation." 012: The MicroKernel cannot find the specified file Check that
You attempted to change the value of a foreign key to a value that does not exist for the defined primary key. It is often a good idea to try other SPX applications. These files are normally located in the SYS:MW\LDT directory on the server. http://krokmel.com/btrieve-error/btrieve-error-85.php When using a 9.x or higher engine, you cannot perform a write operation such as insert or delete on a 5.x format file. 047: The number of files opened exceeds the
For example, in a data files with 4096 byte page size you are limited to 119 index segments per file. See Create (14) in Btrieve API Guide, which is part of the Pervasive PSQL Software Development Kit (SDK). If the maximum values have been reached, these maximums should be adjusted and Btrieve should be reloaded using this new configuration. On NT with IPX/SPX make sure that the internal IPX network number is set to a non-zero unique value Set all client's IPX/SPX settings to manual frame type detection.
To resolve this error: Change directories to \pvsw\clients\dos\windosbox and run the setup utility. Common Problems and Solutions In the event that any changes are required to Btrieve configuration, the following procedure should be adopted: Unload all applications which use Btrieve. The maximum number of keys is 119 for all file formats and page sizes. In some environments, you can restrict the amount of disk space available to each user.
This error indicates that the communication session is no longer valid. The initial retransmission timeout is 3 seconds, and it is doubled each time up to a maximum of 2 minutes. With Btrieve for Windows NT Server Edition v6.15.445, 32 bit Windows application may return Status 2 or "MKDE Terminated with Service Specific Error 0" after running an application for an extended I am using .vlm to connect to server.Any solution?
This error indicates that the specified file could not be found. 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 tried to open a data file with RI (Referential Integrity) definitions that are bound to a MicroKernel database, and the table to which the file is bound was not found If status 84 is still received after a few retries, abort the transaction and then attempt the transaction again.