texte = --Apple-Mail-2--828833925Content-Transfer-Encoding: quoted-printableContent-Type: text/plain;charset=us-asciiVery strange that this problem is happening to another Windows Server =user. I reported the same problem last week on a system that has been =running for 5+ years and have NEVER seen the problem in 12+ years of =WebDNA experience.The problem tends to create a loop and brings the server to a grinding =halt by constantly using 100% of CPU.After reading the many rants in this thread I do suspect that it MAY be =a Windows problem brought about from a Windows update."Failed to aquire lock on database - Possible deadlock averted"The error that is being published in the errorlog.txt does not come from =the errormessages.db so must be coming from the WebDNA engine itself.Chris, maybe you could look into this please.RegardsStuart TremainIDFK Web DevelopmentsAUSTRALIAwebdna@idfk.com.auOn 07/07/2011, at 5:10 AM, Tommy Bell wrote:> Hello everyone, a few days ago a post was made about=20> "Failed to aquire lock on database">=20> I have been experiencing this for quite some time, and recently it has =gotten much worse, I was hoping someone could enlighten me to where to =go bug hunting, or just offer some tips with regards to what I could be =doing wrong.>=20> This is the error i get (One amongst many db's, not just online.db)> An unknown error occurred:> DBError> ../../database/online.db> Failed to aquire lock on database - Possible deadlock averted>=20> /Tommy>=20>=20> --------------------------------------------------------- This message =is sent to you because you are subscribed to the mailing list . To =unsubscribe, E-mail to: archives: =http://mail.webdna.us/list/talk@webdna.us Bug Reporting: =support@webdna.us--Apple-Mail-2--828833925Content-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=us-asciiVery =strange that this problem is happening to another Windows Server user. I =reported the same problem last week on a system that has been running =for 5+ years and have NEVER seen the problem in 12+ years of WebDNA =experience.
The problem tends to create a loop and =brings the server to a grinding halt by constantly using 100% of =CPU.
After reading the many rants in this thread =I do suspect that it MAY be a Windows problem brought about from a =Windows update.
"Failed to aquire lock on =database - Possible deadlock averted"
The error =that is being published in the errorlog.txt does not come from the =errormessages.db so must be coming from the WebDNA engine =itself.
Chris, maybe you could look into this =please.
Regards
Stuart =Tremain
IDFK Web Developments
AUSTRALIA
=div>
On 07/07/2011, at 5:10 AM, Tommy Bell wrote:
Hello =everyone, a few days ago a post was made about
"Failed to aquire lock on database"
I have been experiencing this for quite some time, and recently it has gotten much worse, I was hoping someone could enlighten me to where to go bug hunting, or just offer some tips with regards to what I could be doing wrong.
This is the error i get (One amongst many db's, not just online.db)
An unknown error occurred:
DBError
../../database/online.db
Failed to aquire lock on database - Possible deadlock averted
/Tommy
---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to: archives: http://mail.webdna.us/l=ist/talk@webdna.usBug Reporting: support@webdna.us
=--Apple-Mail-2--828833925--
Associated Messages, from the most recent to the oldest:
--Apple-Mail-2--828833925Content-Transfer-Encoding: quoted-printableContent-Type: text/plain;charset=us-asciiVery strange that this problem is happening to another Windows Server =user. I reported the same problem last week on a system that has been =running for 5+ years and have NEVER seen the problem in 12+ years of =WebDNA experience.The problem tends to create a loop and brings the server to a grinding =halt by constantly using 100% of CPU.After reading the many rants in this thread I do suspect that it MAY be =a Windows problem brought about from a Windows update."Failed to aquire lock on database - Possible deadlock averted"The error that is being published in the errorlog.txt does not come from =the errormessages.db so must be coming from the WebDNA engine itself.Chris, maybe you could look into this please.RegardsStuart TremainIDFK Web DevelopmentsAUSTRALIAwebdna@idfk.com.auOn 07/07/2011, at 5:10 AM, Tommy Bell wrote:> Hello everyone, a few days ago a post was made about=20> "Failed to aquire lock on database">=20> I have been experiencing this for quite some time, and recently it has =gotten much worse, I was hoping someone could enlighten me to where to =go bug hunting, or just offer some tips with regards to what I could be =doing wrong.>=20> This is the error i get (One amongst many db's, not just online.db)> An unknown error occurred:> DBError> ../../database/online.db> Failed to aquire lock on database - Possible deadlock averted>=20> /Tommy>=20>=20> --------------------------------------------------------- This message =is sent to you because you are subscribed to the mailing list . To =unsubscribe, E-mail to: archives: =http://mail.webdna.us/list/talk@webdna.us Bug Reporting: =support@webdna.us--Apple-Mail-2--828833925Content-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=us-asciiVery =strange that this problem is happening to another Windows Server user. I =reported the same problem last week on a system that has been running =for 5+ years and have NEVER seen the problem in 12+ years of WebDNA =experience.
The problem tends to create a loop and =brings the server to a grinding halt by constantly using 100% of =CPU.
After reading the many rants in this thread =I do suspect that it MAY be a Windows problem brought about from a =Windows update.
"Failed to aquire lock on =database - Possible deadlock averted"
The error =that is being published in the errorlog.txt does not come from the =errormessages.db so must be coming from the WebDNA engine =itself.
Chris, maybe you could look into this =please.
Regards
Stuart =Tremain
IDFK Web Developments
AUSTRALIA
=div>
On 07/07/2011, at 5:10 AM, Tommy Bell wrote:
Hello =everyone, a few days ago a post was made about
"Failed to aquire lock on database"
I have been experiencing this for quite some time, and recently it has gotten much worse, I was hoping someone could enlighten me to where to go bug hunting, or just offer some tips with regards to what I could be doing wrong.
This is the error i get (One amongst many db's, not just online.db)
An unknown error occurred:
DBError
../../database/online.db
Failed to aquire lock on database - Possible deadlock averted
/Tommy
---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to: archives: http://mail.webdna.us/l=ist/talk@webdna.usBug Reporting: support@webdna.us
=--Apple-Mail-2--828833925--
Stuart Tremain
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:
Encrypt question. (2000)
[WebDNA] Sorry WebDNA server not running /Template ERROR/ Slow speeds (2019)
Further on formula.db failure to calculate shipCost (1997)
transferring values (1998)
[sendmail] questions... (1997)
HELP - NONE STOP DIGESTS. Digest for 4/24/97) (1997)
Error Messages Returned to User (1997)
[WebDNA] Snow Leoopard and v7 (2011)
Merging databases (1997)
converchars in sendmail context.... (2004)
NEWBIE ? help with link (1998)
RE: error count with $purchase (1997)
authenticate (2002)
same bill to and ship to? (1998)
WebCat2b13MacPlugIn - [shownext method=post] ??? (1997)
Another question about credit cards (1997)
change the number format (1997)
Simple Page (2000)
Ampersand (1997)
Was 5.0 Pricing, now Sandbox versus Website and ruminating (2003)