PSQL 3112 or 3103 encountered while launching or working in AGRIS

PSQL 3112 recorded in AGRIS error log or user encounters this error when trying to use AGRIS first thing in the morning:

PSQL 3112 errors can be recorded if a client has a session of AGRIS open and the database server is restarted. This can be a common occurrence if a user forgets to close AGRIS at the end of the day and then the server is rebooted overnight. Sometimes the server reboot can be automated/unexpected and this can cause confusion about why this error is encountered. Best practice would be to use the idle timeout feature in AGRIS to ensure users are gracefully backed out of AGRIS prior to any kind of scheduled reboot or backup process. This feature can be set by going to Maintenance > Dataset Maintenance > (selecting the live dataset) and then adjusting the "Allow _____ idle minutes between ____ and ____" setting. This feature is useful in instances where your system backup skips files or shuts down because data files are open. In order to prevent a workstation from holding open data files that are not being used, you can set a time limit for keeping data files open.
To configure this feature:

Type the idle time in minutes. When an AGRIS session exceeds the idle time, all data files are closed and a message appears, stating that the workstation was logged off.
OPTIONAL - Enter the time frame in hours and minutes, using military time format, if you want the idle time to apply only to a specific time frame.

An example of the above being set to back users out of AGRIS after 30 minutes between 8PM and 5:45AM: Allow 30 idle minutes between 2000 and 0545
Contact the support team for additional help configuring this setting.

Btrieve 3103 and 3112 Errors Consistently Encountered on All Network Clients Trying to Launch AGRIS V9:

First, try restarting the Pervasive engines (KB article 2424). If that does not work, proceed with the following to enable multihoming on the database server:

Get everyone out of AGRIS V9
- On the database server, click Start - Programs - Pervasive.SQL - Control Center
- Click on the 'plus' next to Pervasive.SQL Engines
- Click on the 'plus' next to (Server_Name)
- Click on the 'plus' next to Configuration
- Click on the 'plus' next to Server
- Click on the folder called 'Communication protocols'
- Double-click the TCP/IP Multihomed setting on the right-hand window
- Change the setting to ON and click OK
- Click on the Edit - Apply
- Right-click on (Server_Name) on the left-hand side of the window and select Tasks - Restart Pervasive Services
- Close the Pervasive Control Center and try to get back into AGRIS V9

Even if the TCP/IP Multihomed option is already set above, try stopping/restarting the PSQL engines anyway. A 3103 error is commonly observed when the PSQL engines are not running or not running properly.