Hi Tim,

I haven't seen this error come up for quite a while:  "ElevateDB Error #300 Cannot lock the catalog xxxx in the database xxxx for read access".  The error is intermittent.  

Strange thing is, out of 5 computers on the network only 1 computer gets this error.

Remoted in to workstation today and it was working fine.  Ran the application several times without an issue.

When it's playing up, the application on this workstation often fails to connect to the server, and/or has trouble maintaining a connection.  The other 4 computers connect and maintain a connection without an issue.

* EDB 2.29 Build 1.
* Client/Server (remote) only.  No local connections to database.
* Computer *is* the furthermost away from the server but, like the other computers, uses an Ethernet connection not wireless.

= Steve

Steve


From what you've posted I'd suspect hardware - either PC, router or wiring. Quick test would be to swap ports on the router and see if the error moves to another PC. You could also try swapping PCs around.

Roy Lambert

On 12/26/2018 5:06 PM, Steve Gill wrote:
> * Computer *is* the furthermost away from the server but, like the other computers, uses an Ethernet connection not wireless.

How furthermost ?

Are we talking "last desk in the office" kind of thing or something
where they might be outside max cable length (100m/328feet) ?

As Roy pointed out checking connections/NIC card would be my first step.
I'd also see if there is anything in the windows event logs as windows
might log network related events (connects/disconnect/etc)

Raul

Hi Roy,

<< From what you've posted I'd suspect hardware - either PC, router or wiring. Quick test would be to swap ports on the router and see if the error moves to another PC. You could also try swapping PCs around. >>

Yeah, good idea.  Thanks.  I'll get him to do that.

= Steve

Hi Raul

<< How furthermost ?

Are we talking "last desk in the office" kind of thing or something
where they might be outside max cable length (100m/328feet) ?  >>

No idea yet - waiting for the client to respond.

<< As Roy pointed out checking connections/NIC card would be my first step.
I'd also see if there is anything in the windows event logs as windows
might log network related events (connects/disconnect/etc)  >>

Yep thanks.  I've asked him to try that.

= Steve

Steve,

<< I haven't seen this error come up for quite a while:  "ElevateDB Error #300 Cannot lock the catalog xxxx in the database xxxx for read access".  The error is intermittent.

Strange thing is, out of 5 computers on the network only 1 computer gets this error. >>

That's a server-side error and shouldn't have anything to do with the client computer.  Also, this is a *rare* error and should only occur when there's an issue with another session modifying the database catalog and taking too long (which should never occur - all writes to the catalog are optimistic in nature and very short-lived).

Are you using the global file I/O buffering with this EDB Server ?

Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

<< Are you using the global file I/O buffering with this EDB Server ?  >>

No, it's off by default and the customer hasn't turned it on.

= Steve

Steve,

<< No, it's off by default and the customer hasn't turned it on. >>

You might want to try to turn it on in this case and see if the error goes away.  However, you'll want to use the 2.30 EDB Server for this because of that last global file I/O buffering bug that was fixed in the latest.

If the error *does* go away with the global file I/O buffering turned on, then it's another issue with Windows (what, however, I don't know).

Tim Young
Elevate Software
www.elevatesoft.com