Re: [WebDNA] An unknown error occured // Deadlock avoided
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106876
interpreted = N
texte = > Moving is simply not an option. Why not? If it's Windows or IIS that's causing the problem (wow, this would be a surprise, wouldn't it???) moving it to LInux would be the fastest, cheapest, and most effective solution. Why don't you try it? Is the reason because you don't know how to admin a Linux server? You said the problem occurs even when the site is not busy, so surely you could run a test on Linux to confirm or reject the theory that it's a Windows/IIS problem and not a WebDNA problem, right? > I guess ill have to resort to the ultimate solution and > attempt convince the man upstairs to implement a new > system, in something other than webdna. Are you suggesting that rebuilding the entire website in some other software is an option -- even though it would obviously cost thousands or tens of thousands of dollars -- yet moving the existing site to a different server (or properly reconfiguring the server you already have) which would cost 2-3 order of magnitude less is NOT an option? Sorry, but I fail to see any logic in this at all. > I realize it is not a very large DB; it only contains who > is online, and so on, but what I am still wondering is why > webdna is not able to write to it. The answer is more than likely bad WebDNA code by the person who wrote it (or modified it) or bad server configuration. Do you have enough experience with WebDNA to be able to diagnose a potential WebDNA problem? I'm willing to bet that WebDNA will work just fine on the current server -- once you fix the server or the WebDNA code that is causing this problem. > yes it is doing this, even when there is not heavy load After more than 16 years of programming WebDNA I have yet to see a problem like this that I cannot fix -- especially one where the problem is reportedly NOT due to extremely heavy traffic on the server! > our visitor > numbers have dropped significantly, we explain it by the > myriad of problems we've been having with webdna ... Maybe these "problems" are caused by a badly configured IIS server that is preventing WebDNA from functioning properly. Have you ever considered this possibility? Have you tried to reboot the server yet to see if that clears up the problems??? > I inherited this system, and I doubt it webdna, was ever > meant to run such a complex and large system. You seem to think that WebDNA cannot handle large and complex systems, which is wrong to begin with. But then you said the problem occurs even when there is a light load on the server -- which suggests a WebDNA coding error or a server misconfiguration to me. So how do you propose to track down the problem? What is your "plan of action"? > I have to explicitly tell it from the admin panel what to > do with it ... What are you telling this admin panel to do? And what "admin panel" are you talking about? The WebDNA admin panel that came with the WebDNA software, or a separate programmer's admin panel? Or some other admin panel? > ... and then delte the file and let webdna make a > new db whenever it decides to not be able to access it. How are you deleting this file? Via an admin panel button or link? Are you flushing the databases first BEFORE deleting the file? How is WebDNA "making a new db" if you are deleting the existing db? What is it using to populate this new db? Sincerely, Kenneth Grome
Associated Messages, from the most recent to the oldest:
> Moving is simply not an option. Why not? If it's Windows or IIS that's causing the problem (wow, this would be a surprise, wouldn't it???) moving it to LInux would be the fastest, cheapest, and most effective solution. Why don't you try it? Is the reason because you don't know how to admin a Linux server? You said the problem occurs even when the site is not busy, so surely you could run a test on Linux to confirm or reject the theory that it's a Windows/IIS problem and not a WebDNA problem, right? > I guess ill have to resort to the ultimate solution and > attempt convince the man upstairs to implement a new > system, in something other than webdna. Are you suggesting that rebuilding the entire website in some other software is an option -- even though it would obviously cost thousands or tens of thousands of dollars -- yet moving the existing site to a different server (or properly reconfiguring the server you already have) which would cost 2-3 order of magnitude less is NOT an option? Sorry, but I fail to see any logic in this at all. > I realize it is not a very large DB; it only contains who > is online, and so on, but what I am still wondering is why > webdna is not able to write to it. The answer is more than likely bad WebDNA code by the person who wrote it (or modified it) or bad server configuration. Do you have enough experience with WebDNA to be able to diagnose a potential WebDNA problem? I'm willing to bet that WebDNA will work just fine on the current server -- once you fix the server or the WebDNA code that is causing this problem. > yes it is doing this, even when there is not heavy load After more than 16 years of programming WebDNA I have yet to see a problem like this that I cannot fix -- especially one where the problem is reportedly NOT due to extremely heavy traffic on the server! > our visitor > numbers have dropped significantly, we explain it by the > myriad of problems we've been having with webdna ... Maybe these "problems" are caused by a badly configured IIS server that is preventing WebDNA from functioning properly. Have you ever considered this possibility? Have you tried to reboot the server yet to see if that clears up the problems??? > I inherited this system, and I doubt it webdna, was ever > meant to run such a complex and large system. You seem to think that WebDNA cannot handle large and complex systems, which is wrong to begin with. But then you said the problem occurs even when there is a light load on the server -- which suggests a WebDNA coding error or a server misconfiguration to me. So how do you propose to track down the problem? What is your "plan of action"? > I have to explicitly tell it from the admin panel what to > do with it ... What are you telling this admin panel to do? And what "admin panel" are you talking about? The WebDNA admin panel that came with the WebDNA software, or a separate programmer's admin panel? Or some other admin panel? > ... and then delte the file and let webdna make a > new db whenever it decides to not be able to access it. How are you deleting this file? Via an admin panel button or link? Are you flushing the databases first BEFORE deleting the file? How is WebDNA "making a new db" if you are deleting the existing db? What is it using to populate this new db? Sincerely, Kenneth Grome
Kenneth Grome
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:
carriage returns in data (1997)
[ListFiles] & [loop] (1998)
Reversing [ipaddress] normalization (1998)
[WebDNA] fastcgi 7+ & [cart]? (2010)
Web Catalog 2 demo (1997)
thankyou.tmpl (1997)
all records returned. (1997)
WC Database Format (1997)
WebCat2 Append problem (B14Macacgi) (1997)
Re:[off] Promotions Co? (1997)
Unix webcat perms & multiple versions of same db in cache issue (2000)
Multi-processor Mac info ... (1997)
webdelivery.html and webna (1997)
two unique banners on one page (1997)
replacing founditems ... (2002)
Mac 2.1b4 unknown error: BadSuffix (1997)
searching withe db up three directories not working (1999)
[math] with first letter in field? (1997)
BUG in [showif] using ^ (contains) (1997)
UPS (2003)