Btrieve Error 78
IPX/SPX, Timeout errors When running a Btrieve application on a Windows NT workstation using the Btrieve requester a Status Code 95, "The session is no longer valid," may be returned when These are listed in order of recommendation.#1) Copy your w*.dat files to a seperate directory and set nightmare up to edit those. If you have only a server engine installed and your Pervasive Event Log (PVSW.LOG) contains Status Code 3012 warning entries, perform the following steps: To Turn Off Local Engine support (for Use a backup copy of your data file. weblink
Specifics on auditing can be found on NT help or documentation. Login if prompted. Check the Pervasive Event Log (PVSW.LOG) for more information. 3030: Remote access not allowed This code is returned if the path is remote, the client configuration setting for Use Local MicroKernel you'll need to make sure your bbs has finished it's update process (see above) before you can overwrite that file.
Btrieve Error 161
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. For example, you segregate your defer list into two different queues by using batch code BATCH-1 and BATCH-2. Status Code PDF Download Status Code Information 46 Having problems with Status 46 (Unable to Write to File) messages coming back from your application, causing users to lose database changes? It is a good idea to just double, or at most triple them all.
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 If a new developer comes along and decides to do things a bit differently, i.e. The session could be dropped without Scala knowing it, you would then get this error. Btrieve Error 35 if you want your dat files to be updated you can either; a) wait for the next shutdown and startup for it to automatically run through, b) go to the sysop
Check the amount of free space on the scala volume. 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). The following are possible workarounds. For example, a given invoicing application may have two tables, for an invoice header and invoice detail records.
Back to index Copyright © Madis Kaal 2000- Sign in | Join | Help