When a server-based application is accessing the MicroKernel and the requested resource is locked, a wait is also required. These parameters are shown below with their default values: SPX VERIFY TIMEOUT=54 SPX LISTEN TIMEOUT=108 SPX ABORT TIMEOUT=540 These three parameters (in the order listed above) have values in a 1:2:10 You attempted to remove a file from continuous operation, but a different client placed the file into continuous operation. Drop the key, then add it again. weblink
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 Reinstall the client from a mapped drive. Otherwise, the application might enter a deadlock situation with another transaction. For key-only files, the maximum record length is 253 bytes (255 bytes if creating files in version 5 file format).
Btrieve Error 161
You will receive Status Code 0 if the work space is large enough to hold the filter/extraction expression and enough of the record to include all of the fields to be The MicroKernel tried to write to the transaction control file. Expand the Local Client node. This can be accomplished using the Btrieve Setup Utility (BSETUP.NLM), which adds a LOAD BDIRECT line to the BSTART.NCF.
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 Status 2 Status 11 Status 20 Status 35 Status 46 Status 80 Status 91 Status 3 Status 12 Status 85 Status 94 To avoid receiving this status code, you must set a higher value for the number of databases that the MicroKernel can open. Btrieve Error 35 If the file is extended, the MicroKernel requests an operating system handle for each of the extension files.
Make sure that each End or Abort Transaction operation in your program is executed only after a successful Begin Transaction operation. 040: The file access request exceeds the maximum number of Btrieve Error 3006 Refer to Advanced Operations Guide for more information about RI. 069: The Delete operation specified a file that is damaged The application encountered an error while the MicroKernel was attempting to On Vista/Windows7 machines, install your NEO product by right-clicking the installation file (NEOProSetup.exe or NEOFindSetup.exe) and selecting 'Run as administrator'. For more information about calculating the physical record length, see Pervasive PSQL Programmer's Guide. 029: The key length is invalid The MicroKernel returns this status code for the following situations pertaining
The MicroKernel cannot establish positioning based on a null key value. 045: The specified key flags are invalid The key flags specification on a Create operation is inconsistent. Btrieve Error 2 Below are listed some of the common error codes that Scala may return. If you have a dial up adapter installed, try to uninstall it and see if it solves your problem. If using a server engine, the key number parameter of a continuous operation MicroKernel call is not valid.
Btrieve Error 3006
The network administrator will have to check routing configurations for the particular network. Click Accessories then System then System Restore. Btrieve Error 161 UNC conventions do not work. Btrieve Error 2301 Consequently, the workstation requesters get the wrong server address out of the bindery and are unable to communicate - resulting in a Status Code 20 (or Status Code 91).
Pervasive database engine access issue Start Windows Explorer and navigate to the NEO install directory, which by default is: 'C:\Program Files\NEO Pro' or 'C:\Program Files\NEO Find'In this directory, you will find have a peek at these guys On this screen there is a field called internal network number. This paper can help! (Updated January 2007) 94 Many sites fight the dreaded Status 94 (Permission Denied) and cannot figure out how to get around it. You attempted to create a file with the Replace option, and a bound MicroKernel data file with the same name and location already exists. Btrieve Error 11
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. If the application that uses the file repeatedly opens and closes the file, you are advised to open the file with the function executor. When you are using the Btrieve Requester to access the MicroKernel, the Requester waits and retries if a requested resource is locked. check over here Conditions For Which Status Code 26 Is Returned The following conditions apply to the Btrieve Create API operation.
BSERVER was Database Error: 20 - the MKDE or Btrieve requestor is inactive Topic T1009 Applies to All NEO products Problem This error can occur for several reasons: a Pervasive Btrieve Error 20 If you are using the dynamic locator file with your Workgroup engine: Make sure the name of the second-level locator file specified in your first-level locator file does not have the Next, try to isolate the problem.
To check this setting go to control panel\network\protocols\NWlink IPX compatible transport.
View the active files with the Monitor utility to examine whether this may be happening. The roll-in was designed in this fashion so that the file can still be used while the roll-in is occurring. It is reset when responses resume. Btrieve Error 22 See Create Index (31) in Btrieve API Guide, which is part of the Pervasive PSQL Software Development Kit (SDK).
Return to top Status 3 This status code indicates that the operation cannot continue because the file is not open. The initial timeout value is three seconds. Before attempting any of the below solutions, please reboot your system to be sure the error was not caused by an incidental shutdown of the database engine. http://krokmel.com/btrieve-error/btrieve-error-85.php Refer to Advanced Operations Guide for information about recovering damaged files.
You could also compare the setup and version of Btrieve with workstations that are working. You set the maximum number of different files that you can access during a logical transaction when you configure the MicroKernel. 041: The MicroKernel does not allow the attempted operation The For example: The application attempts to perform a Step operation on a key-only file. If doubling these timeouts does not resolve or at least reduce the frequency of the problem, there is probably a communications problem on the network causing the SPX sessions to be
The first thing to check is, if you are running win95, that there is not a line with lastdrive=Z in your config.sys If this does not solve your problem, see the The application is currently processing a wait transaction and tried to access a file that another user has locked. See Create (14) in Btrieve API Guide, which is part of the Pervasive PSQL Software Development Kit (SDK). Btrieve for DOS returns this status code if it receives an error from the Expanded Memory Manager.
The Maximum Connection must be set to at least 2. In a Get Next Extended, Get Previous Extended, Step Next Extended, or Step Previous Extended operation, the number of records satisfying the filtering condition is less than the number of specified The application tried to unlock a single-record lock with a multiple-record lock or vice-versa. 082: The MicroKernel lost positioning When performing a Get Next or Get Previous operation on a key When you receive this status code on an Update or Delete operation, it usually means that the file is damaged, and you must recreate it.
Now, when you attempt to take the files out of continuous operation, a Status Code 88 is returned. A key segment data type is DATE, TIME, BFLOAT, or AUTOINCREMENT and the segment length is an odd number. If your environment includes both a server engine and Workgroup engines, you should have both settings enabled. If you are operating in a DOS server environment: Pervasive PSQL v10.10 installs BTRBOX95 by default.
Return to top Status 18 Disk is full This status code is pretty self explanitory Return to top Status 20 Status Code 20, 'The MicroKernel or Btrieve Requester is inactive/Btrieve Record Another version can cause Status Code 20. There is not enough space to append a new page to the data file. If for any reason the Winsock driver, Afd.sys, could not send the total amount on a nonblocking socket in a single data packet, Afd.sys would incorrectly report the total bytes sent
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 The following condition applies to the Btrieve Create Index API operation. Use the Clear Owner operation to remove the previous owner before specifying a new one. 051: The owner name is invalid The MicroKernel returns this status code for the following reasons: When reading a file in descending order according to an index path, the MicroKernel has already returned the first record in the index path.