Pervasive Btrieve errors

If you have PSQLv7.9, then I would recommend patching the engine to Service Pack 4, and then to the SP4 hotfixes.  You can find a link to them here: http://www.goldstarsoftware.com/psql2k.asp

Be sure to install these updates from the server console, and NOT from a Terminal Services/Remote Desktop session.  The new communications server in the HotFix update has been known to resolve some problems, especially if they pop up immediately after a Microsoft OS patch.  

Otherwise, Mirtheil is correct, as these errors indicate a network failure.  You can check switch logs, or perhaps UPS power logs to see if power spikes or sags have been impacting equipment.  (A momentary power drop could mess with an unprotected switch, and the subsequent "reboot" time could be long enough that the sessions are dropped.)

Then, verify that the network is clean.  There's a white paper towards the bottom of this page (http://www.goldstarsoftware.com/press.asp) that discusses testing your network with the Pervasive System Analyzer or SmartScout.  (Either will work with your version.)  Note the section on reading the results -- it's not enough to get a successful test, but rather you must watch the packet counter running.

If you are having intermittent failures and you just want to survive them, then you can enable Pervasive Auto ReConnect (PARC) on the server AND the clients.  PARC will retry a new connection when a previous one is lost, and can often allow an application to survive a momentary outage.  (Think of hitting "redial" after dropping a cell phone conversation.)  However, PARC is not a panacea -- while it may allow the app to work, you will actually be masking the problem.  Also, during the reconnect attempt (by default, 3 minutes), it may appear as if the application has hung (and will even show "Not Responding" in TaskManager).  This can cause some users to abnormally terminate their app before the timeout expires, so some user education may be needed.

BTW, to use the Monitor, just run it from a workstation and click Options/Connect to connect to the server and monitor it.  You'll need a network admin username, but this is a decent solution.  You can also do the same from an RDP session.  The registry change will work (especially if you are patched), and here's the details:

Pervasive.SQL 2000i has an additional registry entry
      HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Utilities Interface\Settings\
The value for Restricted Access On WTS client has a default value of 1 meaning access will be restricted.  If the administrator changes this to 0, everyone will be able to run utilities as if they are logged on to the machine physically.  This will allow them to remotely administer their PSQL 2000i server.

It should be noted that changing this value to 0 gives all users full control of the DTI functions on the server.

It looks like it turned out to be a screwed up antivirus.