Welcome, Guest. Please Login.
06/18/25 at 04:30:59
News:
Home Help Search Login


Pages: 1
Send Topic Print
error message (Read 522 times)
cathyh
Active Member
*****


I used to be
indecisive; now I'm
not so sure......

Posts: 1210
Gender: female
error message
09/07/07 at 08:20:09
 
I have more than one user working in various programs (so far PO, GL) that are getting btreive errors sporadically, but this particular one seems to have increased since I loaded the latest patch (I am not sure that the file and line number is always the same):
WARN ERR- FILE ISTECH.LIB line:2217
Btreive error- M:\Default\ISLOG.B - 80
Click on OK and everything seems to go along as usual .
They are bugged by the bug though, so they are bugging me.  My turn.
Back to top
 
 

Cathy Hamilton
Wing Inflatables, Inc.
EVO-ERP2008.1(20 users) w/IS Tech update 5/25/09 (as of 08/21/09)
Windows 2008 Server/client
Pervasive V10.1
Email WWW   IP Logged
gtladmin
Active Member
*****


Diving is fun,
diving is fun!

Posts: 1306
Gender: female
Re: error message
Reply #1 - 09/10/07 at 07:35:54
 
Cathy,
 
An Error 80 is harmless, and things should continue normally.  The Pervasive help file says
80: The MicroKernel encountered a record-level conflict
The MicroKernel did not perform the Update or Delete operation because of a record-level conflict. For example, station A reads a record, station B reads the same record and updates it, and then station A attempts to update the record. The application should reread the record prior to resending an Update or Delete operation. Alternatively, the application can employ record locks to avoid conflicts.  In key-only files, you receive this status code if the record is moved in the file b-tree after being read and before being updated or deleted. A record can move as a result of other records being inserted, updated, or deleted.

 
With this specific error (most of the 80 series errors), I teach users to wait a few seconds and try their task again and there's usually no problem, and they only have to bug me on the more complicated errors (ones that usually involve path errors or corruption).  I would agree that the increase in frequency is a problem and hopefully it can be fixed!
 
Val
Back to top
 
 

Val Feehan
  IP Logged
Pages: 1
Send Topic Print