Btrieve Error: Btrieve error 3006 userinfo: btrieve_status(Thread3524) (Thread 0)

Btrieve Error: Btrieve error 3006 userinfo: btrieve_status(Thread3524) (Thread 0)



Error: Btrieve error 3006 userinfo: btrieve_status(Thread3524) (Thread 0) 


Solution: 

Btrieve error 3006 generally means the client machine and FOS server are not communicating. It is possible that there are hung sessions in Pervasive which may be generating these error messages at random times. 
NOTE -Performing the steps below (clearing hung sessions & applying the Local Engine settings) require Pervasive PSQL services to be restarted. For this reason you will likely want to perform these steps during off-hours where restarting the Pervasive services is less likely to affect your active FOS users. 

Clearing hung Pervasive sessions 
(ensure everyone will need to log out of FOS) 
1. On the FOS server, select the Start menu and select Pervasive-->Utility Monitor. 
2. Select Microkernel-->Active Users. Clear any remaining sessions 
3. Select Microkernel-->Active Files and clear any remaining files.
 
Configuring the Local Engine (to help prevent hung sessions in future) 
(ensure everyone is logged out of FOS) 
1. On the FOS server, open the Pervasive Control Center (PCC). (You will find the PCC in the Start menu under the Pervasive application group.) 
2. Select 'Configure MicroKernel Router' on the right. 
3. Select "Communication protocols and ensure 'Enable Auto Reconnect' is selected. Also, note that the only protocol that is required is TCP/IP. 
4. Back to the PCC menu and select 'Configure Local Engine.' 
5. Select "Communication protocols and ensure 'Enable Auto Reconnect' is selected. Also, note that the only protocol that is required is TCP/IP. 
6. Select 'Performance tuning' and ensure that "Limit Segment Size to 2GB" is NOT checked. 7. Restart the Pervasive PSQL services on the FOS server.