Troubleshooting a status 3111

From the Pervasive Web Site - also check out the URL at the bottom

Problem Description:
Status 3111 followed by status 3006 when trying to run application..

Status 3111 being returned intermittently from application.

Status 3111 and 3014 on workstations and Bspxcom-13 reported on server.

Status 3111 when a 3rd or 4th workstation tries to open a file on server.

Status 3111 after 15 users login.

Status 3111 on one workstation , if another workstation logs out, then it connects.

Status 3111, 3112, 8505 and 8517 reported in client's pvsw.log and system errors reported in server's pvsw.log.

Status 3111: "Failure during send to the target server."

Troubleshooting a status 3111

Problem Environment:
Pervasive.SQL2000

Cause of this problem:
The Pervasive Network Services Layer attempted to send an application request to the target server and encountered a network specific error from the target. Check the Pervasive Event Log (PVSW.LOG) for more information. You can receive this error when the server's Btrieve Communication Manager or the MKDE Communication Manager's Number of Sessions setting is too low. To resolve this, increase the Number of Sessions setting for these two components using the setup utility. Refer to the Pervasive.SQL User's Guide for more information on the Number of Sessions setting and the Configuration Utility.

Solution:
Some of the strategies implemented to solve a status 3111 are:

1. Look in the monitor under 'Microkernel', 'Communications', and view the statistics for 'Total Remote Sessions'. If the value for 'Peak' exceeds the value for 'Maximum', then you have exceeded the session limit and will need to increase the amount of sessions in the Pervasive Control Center. This setting can be found in the Pervasive Control Center under the 'Access' folder under configuration for the server. (It can also be edited in the Bti.cfg file where it is called 'Max Clients'.) We recommend setting the sessions minimally to twice the number of users (licenses) that you have.

2. If the monitor does not show that the peak has exceeded the max for 'Total Remote Sessions', then you have dropped a session for some other reason. This is almost always network-related and you'll need to trouble-shoot to find the network problem and correct it. A sniffer may be very helpful in helping you to identify and isolate the network problem.

3. If using Pervasive.SQL2000i, SP3 or later, there is a new feature called PARC (Pervasive Auto-Reconnect) which can be turned on for both server and client in the Pervasive Control Center. When enabled, PARC will pick up the dropped network session and you will see verification in both the pvsw.log and the monitor that a network session was dropped and picked up again by PARC. This is only a band-aid for the real network problem though, and you will pay a price in terms of performance. (You will likely see at least a 10% performance hit for using PARC, however this % performance hit can increase greatly according to the amount of users you have and as PARC devotes time and resources to picking up the dropped network connections).

4. Look in the pvsw.log for both the client and the server. If you have simply reached the session limit, the server's pvsw.log will tell you that. If it is a different problem, either log may give you an error message which might help to explain why the session is being dropped.

5. Try running either the Smart Scout or PSA (Pervasive System Analyzer) utility to see if the machine can connect to the server. This may at least help you to determine if the connection problem is persistent or intermittent--(i.e., whether or not you can connect at all from this machine).

6. Many other errors may result when a network problem causes a session to be dropped, such as: system errors in the server's pvsw.log, status 8505's or 8517's in the client's log, status 2's or 3's being returned from the application, Bspxcom-13 being reported on server, status 3006 or 3014's being returned from the application, etc. A sniffer may be very helpful in helping you to identify and isolate the network problem. You may find helpful information at this link: http://www.goldstar-sw.com/papers/status95.htm.

NOTE: These suggestions were gathered from the customer interactions, and may not apply to your particular situation.