We installed PVSW Ver 11 - Service Pack 1 a week ago.  We had no problems or issues at that time. But now we have had to reboot our server 4 times in 2 days. The app will freeze periodically. And of course then we get transactions out of balance. Our IT person can not find anything wrong. He did have to restart PVSW this morning, instead of a reboot. And it may not be due to PVSW. But if it is, does anyone else have/had this problem.
 
We do not het any message.  It just freezes.

OK, I work with Carol and I have some more information on the situation.  
 
It turns out that the Pervasive database is specifically locking up and causing disconnects when we run some reports through ODBC. They are Excel reports connecting to Pervasive through ODBC. Some of them work fine and do not cause lock-ups. However other larger reports (which might ordinarily time out if we weren't setting a larger timeout on the connection object) are causing these issues repeatedly.
 
It's possible that these reports were sporadically causing this issue before the upgrade, but now certain reports are causing these issues any and every time they are run.
 
Even when the user running the report is not in EVO, this issue happens and a reboot of Pervasive is needed before anyone can access EVO again.
 
The error received by the user running the reports is most often: "[Pervasive][ODBC Client Interface][Client LNA] You have been unexpectedly disconnected from the server. Re-start your application, then access the data source again. Contact your system administrator if you still need assistance."
 
Other EVO users have received the error Carol gave above.

I'm looking at this status code document - http://www.pervasivedb.com/psqlv11/Documents/Status_Codes_and_Messages_PSQLv11.p df - and it says this about the 3112 error:
 
Quote:

 
 
So it would appear that this issue may be a result of the network buffer which would explain why only larger reports triggered it.

Latest update from our IT company. Have you heard of this. Which set of files do we use and how to fix it?
 
 Also, I wanted to update you and Bill regarding what’s been going on with Pervasive.   I believe we’ve isolated the issue.  Each database has a set of DDF configuration files which tell Pervasive various parameters of the database.  We’ve reviewed two sets of DDF files; one set is in the \DMAMFG\ME folder.  This set is working fine and has no issues.  The other set is in the main \DBAMFG folder and has substantial issues.  Pervasive support says these files are causing the Pervasive engine to crash.  Now, the only problem is, we don’t know what database each set of files goes with.  My guess is that the “bad” files go with the database you are trying to write queries on.  Pervasive agrees since the “good” set of files don’t have the tables referenced in the query examples Amanda sent over to me.  As for Amanda’s queries, are those being done on the DBA database or the EVO ERP application database