Does anyone have any suggestions on what could cause the following error message:

"ElevateDB Error #300 Cannot lock the catalog MyCatalog in the database MyDatabase for read access."

A customer is getting this error when connecting to the database (remote connection) but I am unable to reproduce it.  

I'm thinking maybe AV software or perhaps file permissions, which I've asked them to check.

Thought I'd ask here in case anyone else has experienced this error before.

= Steve

Steve


- dangling lock on the catalog file
- massive catalog taking a long time to read
- loads of people trying to access (log on) simultaneously
- corrupt catalog
- av holding onto things

Roy Lambert

Steve,

<< Does anyone have any suggestions on what could cause the following error message:

"ElevateDB Error #300 Cannot lock the catalog MyCatalog in the database MyDatabase for read access."

A customer is getting this error when connecting to the database (remote connection) but I am unable to reproduce it.  

I'm thinking maybe AV software or perhaps file permissions, which I've asked them to check. >>

Does it happen consistently, or is it reproducible ?

I've only seen this error here due to a bug in EDB:

https://www.elevatesoft.com/incident?action=viewrep&category=edb&release=2.22&incident=4367
https://www.elevatesoft.com/incident?action=viewrep&category=edb&release=2.04&incident=3306

It's also certainly possible that something external could cause such a lock error.  The key determining factor is whether the issue is reproducible.  If it is, then it's a bug.



Thought I'd ask here in case anyone else has experienced this error before.

= Steve

Tim Young
Elevate Software
www.elevatesoft.com

Sometimes it's the AV software they have installed as it starts working again if they disable the AV software and run the program again.  

It started doing it again the next day with the AV still disabled so it may also be because of a service I wrote that accesses the database once a day, but does it via a "local" connection rather than a "remote" one.  Perhaps the lock is not being released.

I asked the customer to uninstall the service so we'll see what happens over the next couple of days.

BTW, the catalog is 2MB approximately.  If he still has problems after this I may get him to install LockHunter to see what's locking the catalog.

= Steve

So this is weird.  Customer sets application to run as administrator on all workstations and no more error 300.

= Steve

Steve


If its W10 its not surprising - I think there are 372 different places to set security!

I say this cos I finally tracked down the last setting that was stopping a W7 notebook from doing things (file copy / delete etc) on a W10 notebook.

Roy Lambert

Steve,

<< So this is weird.  Customer sets application to run as administrator on all workstations and no more error 300. >>

That sounds like an issue with permissions on the hidden EDBDatabase.EBBLck file. I would check the permissions on that file and make sure that any processes that are *directly* accessing the database with local sessions are using a user account that can open and read/lock that file.

Also, make sure that both the ElevateDB Server and any local sessions that are directly accessing the database are using the same large file support settings.

Tim Young
Elevate Software
www.elevatesoft.com

<< That sounds like an issue with permissions on the hidden EDBDatabase.EBBLck file. I would check the permissions on that file and make sure that any processes that are *directly* accessing the database with local sessions are using a user account that can open and read/lock that file.

Also, make sure that both the ElevateDB Server and any local sessions that are directly accessing the database are using the same large file support settings.>>

That's the strange thing.  I only use EDB in client/server mode so there are is no direct access to the database for customers.  The only thing that did access the database directly was a Windows service that automatically updates the server when there are new releases, but this was changed to use remote mode.

It doesn't make sense to me but I will continue to monitor it.

= Steve

On 9/11/2017 6:17 PM, Steve Gill wrote:
> That's the strange thing.  I only use EDB in client/server mode so there are is no direct access to the database for customers.  The only thing that did access the database directly was a Windows service that automatically updates the server when there are new releases, but this was changed to use remote mode.
>
> It doesn't make sense to me but I will continue to monitor it.

Probably not related but 2 questions:

1. You said "Customer sets application to run as administrator" - that
should have no impact on the server if you're fully C/S so sounds like a
local file permissions issue for the system app is running on.

2. How does this service do the update ?
This is a total shot in dark but I have seen a scenario where if files
are temporarily stored in a different folder and then copied over they
would keep permissions from that temp folder sometimes.

Raul

Hi Raul,

<< 1. You said "Customer sets application to run as administrator" - that
should have no impact on the server if you're fully C/S so sounds like a
local file permissions issue for the system app is running on. >>

I agree, and it turned out to be a red herring.  The customer made a mistake as the error is back.  I am going to remote connect to the customer's server and reinstall everything.

<< 2. How does this service do the update ?
This is a total shot in dark but I have seen a scenario where if files
are temporarily stored in a different folder and then copied over they
would keep permissions from that temp folder sometimes. >>

Ahh, now that's interesting.  The service downloads a zip file, extracts it to a temporary folder it creates, copies the files to their correct locations, then deletes the temporary folder.  That's given me something to check.  

Thanks Raul.

= Steve