Greetings!

Running DBISAM v4.23 build 2

We sometimes get this in our logs:

DBISAM Engine Error # 10050 Invalid filter handle specified for the table 'MY_COUNTER'


How best can we trace this down?

Thanks!

Sam,

<< We sometimes get this in our logs:

DBISAM Engine Error # 10050 Invalid filter handle specified for the table
'MY_COUNTER' >>

In what context are you seeing the error ?  Have you been able to connect it
back to a specific operation in the application ?

--
Tim Young
Elevate Software
www.elevatesoft.com

>> In what context are you seeing the error ?  

We don't know. DBISAM (or our higher level code) is throwing an exception, and the 10050
is coming from the DBISAM object. We cannot reproduce the issue in house.

>> Have you been able to connect it back to a specific operation in the application ?

No, as neither we nor our user can reproduce it at will. However, we would like to solve it.

Is there some low level logging that DBISAM can do to help us understand what is going on?

Thank you!

Sam,

<< Is there some low level logging that DBISAM can do to help us understand
what is going on? >>

Well, we have debug versions of our servers that we can send you, but they
run a bit slower due to the debug layer.  If you are interested in using one
of these, just send me a private email.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thanks.

Any chance that could be an option in the main dbisam distro?

(even if just in the server code)

We compile the dbisam server into our own process, it is not stand alone...

(e.g. if there were a compile time or run time option as part of the dbisam code, we could
take it from here. But there is no useful way for us to run the stand alone dbisam server,
because it would be a mess to set up in our production environments at client sites.)

Sam,

<< Any chance that could be an option in the main dbisam distro? >>

I'm looking into it.  The debug layer that we introduced was generic, but
I'm thinking of using the stack tracing in the FastMM4 debug DLL instead
because it is cleaner and doesn't involve as much work for the customer.

--
Tim Young
Elevate Software
www.elevatesoft.com