Don't know how to solve this problem and need more brain power. .....
pausing for sarcastic remarks ....

I have a client who is getting an error 139 across all of their
clients at random times throughout the day. I learned of this problem
and asked how long this had been happening. The answer was "about a
year now". (insert Jaw droppage here) I don't know why they didn't
bring it up when it started but it doesn't matter.

Since the problem affects all pervasive clients at once and the server
has to be rebooted to correct the problem ... I don't know how to
narrow down the culprit.

The client is running Macola 7.6.100 and our custom VB5/Smithware OCX
warehousing app with Pervasive 7.5 SP3 installed. The server is
running Pervasive 7.5 SP4. It has been running since 1997 when
Smithware still existed. Obviously they don't anymore.

I need a Magnum P.I. tool kit. Anyone have suggestions on how to go
about figuring out what the problem or culprit is?

I had never seen a status 139 before so I had to research it (read the
manual from http://www.pervasive.com/library .

"139 - Unacceptable value in key number

Certain operations either use, or reserve the use of, the key number
parameter as a subfunction number, rather than as a means to specify a
file index to be used with the operation. (Note: This is also done in
the GetEqual operation). This status code is returned if an
application does not specify a valid subfunction number (via the key
number parameter) to one of these operations:

* You issued a Begin Transaction operation with an invalid key number.
* You issued an End Transaction operation with an invalid key number.
* You issued an Abort Transaction operation with an invalid key
number.
* You issued a Start Extended operation with an invalid key number. "

This sounds like the application does not properly initialize /set the
key parameter before every call to the database engine. I have seen
uninitialized key numbers cause issues on opens.

A MKDE trace would show the key number for those operations in
question.

This sounds a little bit different than a status "6 - Key number
parameter is invalid. The value stored in the key number parameter is
not valid for the file being accessed. The key number must correspond
to one of the keys defined for the file. Valid key numbers are 0
through 118" (and 125 for the system key if present).

Leonard

On 10 Aug 2004 05:45:46 -0700, dwilliamson (AT) ivsi (DOT) com (Dave Williamson)
wrote:

Nice to hear from you again Leonard.

I too had never seen a 139 before. I actually had to tell the client
I can't do anything for you right now because I have to do some
research. Naturally they thought "yea right".

Would a client passing an unacceptable value in key number cause all
clients to get the 139 at the same time and bring the entire plant to
a stop until the server was rebooted? I wouldn't think so either. It
would only affect that client's connection at most. So it seems like
a server side problem.

When I get remote connectivity I'll run a MKDE trace and see if I can
catch it when it happens.

Until then any thoughts on why all clients suddenly get a 139 and the
server has to be rebooted to correct the problem?