We are having weekly issues (kind of - it occurs on either Satuday or
Sunday) where our Btrieve 2000i server stops receiving incoming
connections. The error is:

[06/16/2007 18:30:28.961]: Exception of type
System.Data.Odbc.OdbcException

[06/16/2007 18:30:28.961]: Message: ERROR [HY000] [Pervasive][ODBC
Client Interface][LNA][Pervasive][ODBC Engine Interface]Unable to open
table: InChB.

ERROR [42S02] [Pervasive][ODBC Client Interface][LNA][Pervasive][ODBC
Engine Interface][Data Record Manager]No such table or object.

[06/16/2007 18:30:28.977]: At: W3ODBCCI.DLL.Void
HandleError(System.Data.Odbc.OdbcHandle, RetCode)


We have dug through NT App/System/Security logs, the PVSW.log, and
have looked at all scheduled jobs that hit the server and have not
found the root cause. Does anyone know what might cause this sort of
result? We feel like there's an interesting point that it only occurs
on weekends, but again, cannot find out why it has happened. The fix
(temporary) is to restart Windows, (Windows 2003 Server) and that
resolved it all three times (which has happened on 2 Sundays, and now
this last Saturday.

TIA!

This will probably be a tough one to pinpoint.

1) I would first verify that you have the latest & greatest code
running. For Pervasive.SQL 2000i, this assumes that you start with a
base of v7.90 (which is also Service Pack 3), then patch to Service
Pack 4 (v7.94), then patch to the SP4 HotFixes. The only way to verify
the exact version is to check with the files. In the C:\PVSW\BIN
directory, check the W3ODBCEI.DLL file. The SP4 release came out in
12/2001, and the HotFixes came out in 03/2003.

2) Second, we need to bettter troubleshoot the problem when it occurs.
"No such table" seems to indicate that the table is there, but may be
inaccessible for some reason. The next time it occurs, try a few
simple tests:
2A) Use the PCC on the server to try to open the same table.
2B) Use the PCC on a workstation to try to open the same table.
2C) Use the Function Executor from the server to try to open the same
table.
2D) Use the Function Executor from a workstation to try to open the
same table.
2E) Verify that the physical drive is still accessible from the
Server's OS. Do the same from the workstation.
2F) Try shutting down BOTH Pervasive services, then restart them -- see
if that helps.
With the results of these tests, along with any applicable error
messages, we'll be able to go a long way towards determining where in
the chain things are broken.

3) Check the Pervasive Event Log (C:\WINDOWS\PVSW.LOG) and see if any
events are being trapped there.

4) Enable DrWatson for visual notifications (I believe these are
DISABLED by default on Win2003) and see if anything pops there.

Beyond these, there are many other tests and items to try, including
the use of a network analyzer to try to capture the exact time of the
error, which may help as well.
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive Service & Support Class - 07/2007 ***


mzamborini (AT) gmail (DOT) com wrote:

Hallo Btrivieans!

we observed, that on a sertain installation of PSQL 8.1, while running the
backup-Agent, we get Btrieve-Error 46 on add-record-commands.

The situation is following:

the application is a btrieve-app.
While BA is on, there runs a backup of all files except *.^^^. The Backup is
performed by Backupexec.
(The procedure runs every day statring BA at 23:50, Backup at 0:05 an stopp BA
at 1:55 h)

Open file for (say) DVSALL.DAT returns status 0 - in the PBA-log appear the
statement: BA is now on for the file DVSALL.DAT.
An add record-command now returns error 46.

Unfortunately the error appear not allways, only once a month or so.

Any idea, what here happns?
Any hint will be welcome!

Thanks in advance

Mircea