We use the EDBSrvr and ODBC driver in our application.  We have the Server run as a service.   Everything seems to run fine except for a few different end users will repeatedly get a 300 error and I am not sure what causes them to get it repeatedly.  If I stop the service and then run the EDBSrvr as an application then everything runs fine.

I don't know what would be causing these end users to repeatedly get the 300 error when others do not, ideas?

On 1/28/2014 3:47 PM, jdm77 wrote:
> We use the EDBSrvr and ODBC driver in our application.  We have the Server run as a service.   Everything seems to run fine except for a few different end users will repeatedly get a 300 error and I am not sure what causes them to get it repeatedly.  If I stop the service and then run the EDBSrvr as an application then everything runs fine.
> I don't know what would be causing these end users to repeatedly get the 300 error when others do not, ideas?
>

What's the EDB version you're using and is there a more specific error
message ?

Error 300 is a locking error and message would identify what was locked.
Also is your code dropping/creating db objects (tables, views etc) or is
it just manipulating data in the tables.

If you can duplicate the error then quering the
"configuration.serversessionlocks" table when you see the message might
help to identify where the lock is coming from  ?

Raul