This is 2.02 B11. In B12 release notes I don't see any related to this solved.

Every day I read the day's logged events. Every few days there is this error in function "Locate Row": Access violation at address 00545A21 in
module 'edbsrvr.exe'. Read of address 00000008

User simply logout/login again and nothing seems to happen. Any idea?

Tiago,

<< This is 2.02 B11. In B12 release notes I don't see any related to this
solved.

Every day I read the day's logged events. Every few days there is this
error in function "Locate Row": Access violation at address 00545A21 in
module 'edbsrvr.exe'. Read of address 00000008

User simply logout/login again and nothing seems to happen. Any idea? >>

Are you using the edbsrvr.exe that we provide ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

<<Are you using the edbsrvr.exe that we provide ?>>

Yes. And some functions in external modules. It's possible a.v. is raised on my dll, but log doesn't inform of it.
I asked users more information to reproduce it.
EDBsvr remains stable, it's running for some weeks.

Tiago,

<< Yes. And some functions in external modules. It's possible a.v. is raised
on my dll, but log doesn't inform of it. I asked users more information to
reproduce it. EDBsvr remains stable, it's running for some weeks. >>

It might be something in the DLL, but that would only be an issue if you
were trying to access a TEDB* component reference that wasn't actually
referencing a valid instance, i.e. a nil reference.  You shouldn't be able
to cause an AV simply by calling the Locate method on a valid TEDB*
component reference.

I'm looking at adding some stack tracing into the exception handling in the
server, and that should help in tracking down issues like this.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

After several weeks of continuous running, EDB server was suddenly stopped. In Windows event viewer I found this message (transtated from
Spanish):

Application, S:\ssc\EDBServer\edbsrvr.exe, produced application error on 05/15/2009 15:29:51.829. Exception was 80000007 at address
00000000 (ntdll!NtWaitForMultipleObjects)

This si 2.02 b11. Server logged events don't show anything significative before crash.

Any idea?

Tiago,

<< After several weeks of continuous running, EDB server was suddenly
stopped. In Windows event viewer I found this message (transtated from
Spanish):

Application, S:\ssc\EDBServer\edbsrvr.exe, produced application error on
05/15/2009 15:29:51.829. Exception was 80000007 at address 00000000
(ntdll!NtWaitForMultipleObjects)

This si 2.02 b11. Server logged events don't show anything significative
before crash. >>

Is the exception logged in the logged events ?  If not, then something
pretty serious happened.  The funny thing is that the edbsrvr.exe
application does not reference the WaitForMultipleObjects API call, but it
is possible that another API call resulted in it being called.

Are you still seeing the Locate error in the logged events on a regular
basis ?  If so, then I will send you a debug version of the EDB Server as
soon as I have something ready.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,


<Is the exception logged in the logged events ? >

No.

<then something pretty serious happened. >

This server is exposed with standard 12010 port to the Internet. But I'm inspecting logged events dayly and no unknonw IP address is found ever.
I'm using standard signature and no encryption, any advice of changing it?

<Are you still seeing the Locate error in the logged events on a regular
basis ? >

No. This didn't happen again, despite users and their job are the same.

I'll email you today's log in .csv format. Crash was on 15:29.

Tiago,

<< This server is exposed with standard 12010 port to the Internet. But I'm
inspecting logged events dayly and no unknonw IP address is found ever.  I'm
using standard signature and no encryption, any advice of changing it? >>

It shouldn't matter either way - an intruder should not be able to bring
down the EDB Server in any case, even if they can log in successfully.

<< No. This didn't happen again, despite users and their job are the same.
>>

Okay.  I think what I'll do is get you a debug version of the EDB Server
that you can run and get a dump when such unexpected errors occur.  That
should give us a better idea of what is going on.

It will be a few days, but I'll email you when it's ready.

--
Tim Young
Elevate Software
www.elevatesoft.com