Re: [WebDNA] An unknown error occured // Deadlock avoided
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106899
interpreted = N
texte = Hi Tommy, No problem. We think your problem is a Windows issue anyways. It could be a combination of Windows and some "less than quality" WebDNA code, but I suspect that if your site was running fine for years and has only recently started to create problems then Windows is primarily (if not exclusively) to blame. My offer still stands for fixing the site and/or its WebDNA code on a consulting basis, but the first thing I would do along these lines is the same thing you can do yourself if you feel like it: Load a copy of the site onto a Linux box, try to reproduce the problem, and see what happens. If you learn that the problem will not occur on Linux, your options are simple: 1- Get someone to re-configure your Windows server so that it no longer interferes with the WebDNA database that it is improperly modifying or locking or blocking. OR ... 2- Get a new Linux HTTP server, get the site running properly there, then redirect all HTTP requests from the old Windows server to the new Linux/WebDNA server. If you decide to proceed with #2 you can eventually change your DNS to send visitors directly to the new Linux server instead of redirecting them from the old Windows server. But like you said, this may not be an option. Anyways I suggest using #1 if the last thing you want to do is migrate your website to Linux. It may cost you some money to hire a highly paid expert to fix the Windows server issue, but at least you'll have a site that's not rejecting visitors any more. Sincerely, Kenneth Grome > Ken, > I do apologise for not answering your questions, I must > have missed it when I replied to another email. > > And I shouldn't have bashed on webdna, that was an error > on my part. I was simply frustrated at the lack of > documentation and general knowlegde about the system > from my part and the company i work at. The previous > developer has left no documentation of anything so I > have to figure out everything from the ground up again. > > This unfortunately spilled into my email. > > /Tommy > > On 10-07-2011 23:17, Kenneth Grome wrote: > > I have little patience with people who come here and > > complain, then refuse to cooperate when we try to help. > > I had to ask him *twice* for answers to some > > important questions yet he still hasn't answered -- so > > does he want our help or not??? > > > > As Chris said, he hasn't provided a shred of evidence > > that this is a WebDNA problem. This could easily be a > > Windows issue which would be identified in a couple of > > hours if he just copies the site to a Linux server and > > learns that he cannot reproduce the problem there. > > > > This is why I agree with Chris that a couple hours to > > install and test the site on a Linux server is an > > excellent way to "cut through the crap" and possibly > > identify the source of the problem very quickly. If > > the issue goes away on Linux we have strong evidence > > that Windows is the culprit rather than WebDNA. > > > > And isn't the goal in a situation like this to identify > > the source of the problem in the least amount of time? > > It would be for me, especially if the server's > > traffic were important to me. > > > > Sincerely, > > Kenneth Grome > > ------------------------------------------------------- > > -- 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
Associated Messages, from the most recent to the oldest:
Hi Tommy, No problem. We think your problem is a Windows issue anyways. It could be a combination of Windows and some "less than quality" WebDNA code, but I suspect that if your site was running fine for years and has only recently started to create problems then Windows is primarily (if not exclusively) to blame. My offer still stands for fixing the site and/or its WebDNA code on a consulting basis, but the first thing I would do along these lines is the same thing you can do yourself if you feel like it: Load a copy of the site onto a Linux box, try to reproduce the problem, and see what happens. If you learn that the problem will not occur on Linux, your options are simple: 1- Get someone to re-configure your Windows server so that it no longer interferes with the WebDNA database that it is improperly modifying or locking or blocking. OR ... 2- Get a new Linux HTTP server, get the site running properly there, then redirect all HTTP requests from the old Windows server to the new Linux/WebDNA server. If you decide to proceed with #2 you can eventually change your DNS to send visitors directly to the new Linux server instead of redirecting them from the old Windows server. But like you said, this may not be an option. Anyways I suggest using #1 if the last thing you want to do is migrate your website to Linux. It may cost you some money to hire a highly paid expert to fix the Windows server issue, but at least you'll have a site that's not rejecting visitors any more. Sincerely, Kenneth Grome > Ken, > I do apologise for not answering your questions, I must > have missed it when I replied to another email. > > And I shouldn't have bashed on webdna, that was an error > on my part. I was simply frustrated at the lack of > documentation and general knowlegde about the system > from my part and the company i work at. The previous > developer has left no documentation of anything so I > have to figure out everything from the ground up again. > > This unfortunately spilled into my email. > > /Tommy > > On 10-07-2011 23:17, Kenneth Grome wrote: > > I have little patience with people who come here and > > complain, then refuse to cooperate when we try to help. > > I had to ask him *twice* for answers to some > > important questions yet he still hasn't answered -- so > > does he want our help or not??? > > > > As Chris said, he hasn't provided a shred of evidence > > that this is a WebDNA problem. This could easily be a > > Windows issue which would be identified in a couple of > > hours if he just copies the site to a Linux server and > > learns that he cannot reproduce the problem there. > > > > This is why I agree with Chris that a couple hours to > > install and test the site on a Linux server is an > > excellent way to "cut through the crap" and possibly > > identify the source of the problem very quickly. If > > the issue goes away on Linux we have strong evidence > > that Windows is the culprit rather than WebDNA. > > > > And isn't the goal in a situation like this to identify > > the source of the problem in the least amount of time? > > It would be for me, especially if the server's > > traffic were important to me. > > > > Sincerely, > > Kenneth Grome > > ------------------------------------------------------- > > -- 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
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:
FAX orders (1996)
Nesting format tags (1997)
serial number generation (1997)
flushdatabases (1997)
[convertchars] (2000)
Nav. 4 probs with cart - Serious problem (1997)
Showif for mulitple variations (1997)
sorting dates (1999)
[authenticate] (1999)
Major bug report on rootbeer (1997)
WebCat2 several catalogs? (1997)
WebCatalog NT beta 18 now available (1997)
Requiring that certain fields be completed (1997)
Separate SSL Server (1997)
restarting service remotely on NT (1997)
problems with 2 tags shakur (1997)
[TaxableTotal] - not working with AOL and IE (1997)
Hiding HTML and breaking the page (1997)
Faxing orders in place of email (1997)
RE: WebDNA-Talk searchable? (1997)