Re: What is this error message?
This WebDNA talk-list message is from 2006
It keeps the original formatting.
numero = 66520
interpreted = N
texte = Hi Sal, Well, Googling for the exact phrase "failed to acquire lock on database" only brings up 2 hits, and those are to the change history log for WebDNA. Interestingly, this error message is listed: 1/13/2003 4.5.1 General release of WebDNA 4.5.1 for all supported platforms Changes / Additions All Platforms Database error messages have been improved to report more detail on why a database failed to load (or be accessed). These include: Not Enough memory to load database. Failed to acquire lock on database <-- Database file not found or opened Bad database format (with 'Merge' style databases) So I'm guessing that it means that it couldn't get read access to the database, though we don't know why. At any rate, an ExclusiveLock cleared up that error message from appearing and removing an old search and then replace within a founditems for the newer replacefounditems fixed the problem of the page loading slowly. How or why this suddenly broke is beyond me, but $hit happens. :) Thanks, Gary At 10:53 PM 3/27/2006, you wrote: >The error seems to show up on numerous sites. The common thread seems >to have something to do with website stats. > >Copy this into Google and take a look. >Failed to aquire lock on database - Possible deadlock averted > >Sal D'Anna ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Hi Sal, Well, Googling for the exact phrase "failed to acquire lock on database" only brings up 2 hits, and those are to the change history log for WebDNA. Interestingly, this error message is listed: 1/13/2003 4.5.1 General release of WebDNA 4.5.1 for all supported platforms Changes / Additions All Platforms Database error messages have been improved to report more detail on why a database failed to load (or be accessed). These include: Not Enough memory to load database. Failed to acquire lock on database <-- Database file not found or opened Bad Database format (with 'Merge' style databases) So I'm guessing that it means that it couldn't get read access to the database, though we don't know why. At any rate, an ExclusiveLock cleared up that error message from appearing and removing an old search and then replace within a founditems for the newer replacefounditems fixed the problem of the page loading slowly. How or why this suddenly broke is beyond me, but $hit happens. :) Thanks, Gary At 10:53 PM 3/27/2006, you wrote: >The error seems to show up on numerous sites. The common thread seems >to have something to do with website stats. > >Copy this into Google and take a look. >Failed to aquire lock on database - Possible deadlock averted > >Sal D'Anna ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Gary Krockover
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Upgrading old WebCat Database Files (1997)
International Orders (1998)
emailer error 103 part ii (1997)
Great product and great job ! (1997)
Protecting webdelivery (1997)
Image Upload and Auto Resize? (2003)
RAM variables (1997)
WebCat2 - Getting to the browser's username/password data (1997)
suggestions for a good text editor on windows? (2005)
Major Security Hole (1998)
Big Databases (1997)
$Quit, $CloseDatabase corrections (1997)
Filemaker Pro and [convertchars] (2000)
Upgrade Pricing? (2003)
text size limitation (1997)
[showif] or-ing (1999)
Help formatting search results w/ table (1997)
webcat- multiple selection in input field (1997)
Strange conversions (2001)
Weeks starting on Mondays (1998)