Btrieve Error Code 91

[ITMaster]

Anyone,
I need some help finding out exactly what is causing this this error code 91 to occur in my application at startup. Sometimes, not all the time, when I have a 98 or 95 workstation plugged into a 10/100 Bay Networks switch I receive this error, but when I switch it to a 10 Bay Networks switch the error goes away. I am running 6.15 on a NT 4.0 server. The error also goes away if I remove the IP address and let the server assign the address. Anyone ever seen anything like this.

Thanks..

 

[Pervasivite]

Yep, lots, and it's no fun to fix. It depends on which SP version of NT and which version of Btrieve. Here is an extract from the latest Pervasive.SQL 2000i docs, which by the way should make the 91 go away if you upgraded - or at least you could get help in fixing it in the off chance you had other issues. In any case you may have to patch Btrieve and then mess with editing the registry to make this go away using old Btrieve 6.15. There is lots of info on the Pervasive site in Refshelf and in the docs and Toolbox areas.

91: The application encountered a server error


------------------------------------------------------------
Note
Please see our Pervasive.SQL Knowledge Base for new and updated articles on troubleshooting this status code. You can access the Knowledge Base at:

http://support.pervasive.com/kb/.

------------------------------------------------------------The MicroKernel returns this status code in one of the following situations:

The Requester cannot establish a session with the server. Either the client/server MicroKernel is not loaded or the server is not active.
The SPX drivers are not installed or are outdated.
The MicroKernel has reached the maximum limit for the number of sessions it can open at one time. To avoid receiving this status code, increase the value for the Number of Sessions configuration option.
To increase the Number of Sessions:

Click Start | Programs | Pervasive | Pervasive Control Center.
Expand Pervasive.SQL 2000i Engines and expand the desired database.
Expand Configuration, then expand Server, and click on Access.
In the right hand frame, double-click on Number of Sessions.
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 the new settings to take effect.
An application specified a path for a file and did not include the volume name in the path.
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 includes the server and volume name when performing an Open operation) has attempted to open a remote file. Because the MicroKernel Router does not interpret the server name, the MicroKernel attempts to do so but cannot.
A communication or network addressing problem exists in your network environment, so the MicroKernel requests never reach their destination server address. Ensure that your client and server network components are up to date and certified for your network environment.
There is a conflict using the DOS BREQNT requester with the SPX protocol. To resolve this error:
Change directories to \pvsw\clients\dos\windosbox and run the setup utility. This loads the appropriate file for clients running Windows 9x or Windows NT. The setup program creates and places a README.TXT file in the \pvsw\W32DOXBOX directory.
After installation, reboot the client.
For Windows NT users: open a command prompt and run a DOS Btrieve application.
For Windows 9x users:
Run the BTRBOX95.exe. A minimized dialog box appears, indicating that BTRBOX95 support is active. If you close this dialog box, it will unload BTRBOX95. You only need to run BTRBOX95.exe once even though you have multiple DOS sessions open.
Open a command prompt and run your DOS Btrieve application.
For NetWare servers only:
The Maximum Packet Receive Size configuration option is inappropriate for your environment. For example, the setting should be 1500 for an Ethernet LAN or 4096 for a Token-Ring LAN.
To adjust the Maximum Packet Receive Size:

Open the sys:system/BTI.CFG file.
Locate the Btreive Communications Manager option.
Ensure that the Maximum Packet Receive Size value is appropriate for your environment.
NetWare users may also receive this status code in the following situations:

The user count limit has been exceeded. Either close a session or upgrade your user count. For more information about purchasing and installing additive user counts, refer to the Pervasive.SQL User's Guide.
Ensure that the NDS network number is the same as the Internal Network Number viewed by BINDER.EXE output.
You ran BUTIL.NLM to roll forward a file using a log filename other than the default, and your BLOG.CFG file did not contain a correct entry such as "\dir\file.ext=vol:\dir\log.ext".

---------------------

Hope this helps,

Regards,
Pervasivite