91: The application encountered a server error.
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 value for the Number of Sessions configuration option is too low. Use the Setup utility to specify a higher value for this option.
- An application specified a path for a file and did not include the volume name in the path.
- The Btrieve Message Router has not been loaded, and the following situation has occurred: an application that uses both the Btrieve Message 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 Btrieve
Message 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.
- 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.
+ 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”.
Paul Wesson
paul@wessoft.com
