One customer is having problems when changing user passwords.  The application becomes non-responsive and after a few minutes produces an error: "Error #300: Cannot lock EDBConfig for Write Access."

The application calls a stored procedure which does an ALTER USER statement to change the password.

I can't reproduce the issue myself and I haven't had any other reports of it occurring.  The only security software they have installed is Windows Defender.

EDB 2.27 Build 1 (Remote connection), RAD Studio XE7 Professional.

Is there anything I can do to prevent this from happening?

= Steve

Steve

Have you looked in ElevateDB's system log to see if there's any help in there?

From your post, and the fact that you can't duplicate it, I'd guess something else that specific customer is doing is locking the config file. I'm not sure just what does lock it but I'd guess things like adding users, altering/creating tables including temporary ones.

Roy Lambert

Hi Roy,

<< Have you looked in ElevateDB's system log to see if there's any help in there?  >>

Good point, I'll check that out.

<< From your post, and the fact that you can't duplicate it, I'd guess something else that specific customer is doing is locking the config file. I'm not sure just what does lock it but I'd guess things like adding users, altering/creating tables including temporary ones. >>

Yeah beats me.  There shouldn't be anything like that happening.  Most things are done by stored procedures and there isn't any creating or altering of tables.

I'll keep digging (until I get to China).

= Steve

Steve,

Sorry, I missed this when you first posted it.

<< One customer is having problems when changing user passwords.  The application becomes non-responsive and after a few minutes produces an error: "Error #300: Cannot lock EDBConfig for Write Access."  >>

This means that EDB is having issues locking the edbconfig.edblck file (hidden), which is *not* a normal error and indicates that the OS lock calls are failing for some reason.  I would have them run Process Monitor:

https://docs.microsoft.com/en-us/sysinternals/downloads/procmon

and see if the OS lock calls indicate the reason for the failure.  I've seen this occasionally in the past where lock calls were failing due to a failure in an underlying SMB connection.

Tim Young
Elevate Software
www.elevatesoft.com

<< This means that EDB is having issues locking the edbconfig.edblck file (hidden), which is *not* a normal error and indicates that the OS lock calls are failing for some reason.  I would have them run Process Monitor:

https://docs.microsoft.com/en-us/sysinternals/downloads/procmon

and see if the OS lock calls indicate the reason for the failure.  I've seen this occasionally in the past where lock calls were failing due to a failure in an underlying SMB connection. >>

Will do.  Thanks Tim.

= Steve

Steve,

BTW, just so you know for when 2.28 is released: enabling the buffered file I/O also gets rid of OS locking so that all locking is performed within the engine, so this type of issue is no longer an issue.

More info:

https://www.elevatesoft.com/manual?action=viewtopic&id=edb2sql&topic=Locking_Concurrency

under "How ElevateDB Performs Locking when Global File I/O Buffering is Enabled":

Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

<< BTW, just so you know for when 2.28 is released: enabling the buffered file I/O also gets rid of OS locking so that all locking is performed within the engine, so this type of issue is no longer an issue.

More info:

https://www.elevatesoft.com/manual?action=viewtopic&id=edb2sql&topic=Locking_Concurrency

under "How ElevateDB Performs Locking when Global File I/O Buffering is Enabled": >>

That's awesome.  Looking forward to that.

= Steve