We have Pervasive.SQL v8.60.192.030 running on five WinXP SP2 boxes. This version was installed when we upgraded to Maximizer 8 CRM software in October, 2004. We have had a persistent problem for a number of weeks now.

After routinely backing-up and restoring our db, everything opens and works fine for a day. The second day after the restore, we get the attached error message on all the machines that had previous versions of Btrieve/Pervasive installed, but not on the newest machine, which was a clean install. After clicking OK a few times, the db usually opens, but sometimes freezes.

Everything now on our servers has been created by the same version of Pervasive.SQL. I can only imagine that there is some registry entry or something lurking around from a previous version of Btrieve/Pervasive. Any suggestions would be welcome.

James from New York

Actually, 8.60 is the latest released version (V9 is in beta right now but isn't generally available) so you are either corrupting files or are somehow pointing to non-Btrieve files. You need to ask Maximizer which file they are trying to access when that status 30 occurs. THe fact that this occurrs after a restore has me questioning the integrity of the backup itself. What are you using to backup the Btrieve files?

Thank you for your quick reply. We use the Maximizer Administrator software for the back-up and restore.

James from New York

Do you know if that tool will properly handle open Btrieve files? I've seen backing up open files that aren't in COntinuous Operations Mode fail with strange errors.

@mirtheil,

Thanks again. We make sure the file is closed and no one is accessing it before we start the back-up. As mentioned, the problem only begins about a day after the back-up and restore routine.

James from New York

Post your PVSW.LOG from the server (the machine that has the engine that is actively accessing the data). It'll be in the WINDOWS directory.

@mirtheil,

Thanks again. Please find the log attached from my local machine, which is normally the gateway machine. (The software is set-up to assign the gateway to the first machine to access Maximizer, which is normally mine. Someone else was actually in ahead of me yesterday, so when he shut down his machine without warning me at 17:34 yesterday, it caused the error you see.) The db is stored on a network server. The last back-up and restore was Fri 04 Mar.

Regards,
James from New York

I see the following in the log:
02-28-2005 18:47:40 W3UPI234 00000A04 MaData6.dat EMT1281 I Btrieve server not found. PNSL open session by name returned status = 3103.
03-01-2005 09:30:13 W3MKDE 000006F8 w3dbsmgr.exe EMT1281 E System Error: 620.2.64 File: \\II-FSCL01VS3\SYS$\PROGRAMS\MAXWIN\FINANCIAL\MXZL.MAX
03-01-2005 09:30:42 W3MKDE 000006F8 w3dbsmgr.exe EMT1281 E System Error: 605.0.51 File: \\II-FSCL01VS3\SYS$\PROGRAMS\MAXWIN\FINANCIAL\MXZCFG.MA X
03-01-2005 09:33:31 W3MKDE 000006F8 w3dbsmgr.exe EMT1281 E System Error: 620.9.64 File: \\II-FSCL01VS3\SYS$\PROGRAMS\MAXWIN\FINANCIAL\MXZD.MAX
03-01-2005 09:34:33 W3MKDE 000006F8 w3dbsmgr.exe EMT1281 E System Error: 620.23.64 File: \\II-FSCL01VS3\SYS$\PROGRAMS\MAXWIN\FINANCIAL\MXZD.MAX
03-01-2005 09:36:55 W3MKDE 000006F8 w3dbsmgr.exe EMT1281 E System Error: 620.23.64 File: \\II-FSCL01VS3\SYS$\PROGRAMS\MAXWIN\FINANCIAL\MXZD.MAX
03-01-2005 09:38:27 W3MKDE 000006F8 w3dbsmgr.exe EMT1281 E System Error: 620.23.64 File: \\II-FSCL01VS3\SYS$\PROGRAMS\MAXWIN\FINANCIAL\MXZD.MAX
03-01-2005 09:38:30 W3MKDE 000006F8 w3dbsmgr.exe EMT1281 E System Error: 620.5.64 File: \\II-FSCL01VS3\SYS$\PROGRAMS\MAXWIN\FINANCIAL\FILE.DDF
03-01-2005 09:38:34 W3MKDE 000006F8 w3dbsmgr.exe EMT1281 E System Error: 620.9.64 File: \\II-FSCL01VS3\SYS$\PROGRAMS\MAXWIN\FINANCIAL\FIELD.DDF
03-01-2005 09:38:36 W3MKDE 000006F8 w3dbsmgr.exe EMT1281 E System Error: 620.5.64 File: \\II-FSCL01VS3\SYS$\PROGRAMS\MAXWIN\FINANCIAL\FILE.DDF
03-01-2005 09:38:38 W3MKDE 000006F8 w3dbsmgr.exe EMT1281 E System Error: 620.9.64 File: \\II-FSCL01VS3\SYS$\PROGRAMS\MAXWIN\FINANCIAL\FIELD.DDF
03-01-2005 09:38:42 W3MKDE 000006F8 w3dbsmgr.exe EMT1281 E System Error: 620.5.64 File: \\II-FSCL01VS3\SYS$\PROGRAMS\MAXWIN\FINANCIAL\FILE.DDF
03-01-2005 09:38:44 W3MKDE 000006F8 w3dbsmgr.exe EMT1281 E System Error: 620.9.64 File: \\II-FSCL01VS3\SYS$\PROGRAMS\MAXWIN\FINANCIAL\FIELD.DDF
03-01-2005 17:32:57 W3NSL244 000007C8 MaData6.dat EMT1281 E 3112: Status 10054 returned while receiving a maximum of 40960 bytes.

This is indicative of corruption of some sort. The fact that you're not seeing it after a restore is strange. You'll probably want to rebuild the file and the replace the backup with the one that's been rebuilt.