Re: [WebDNA] An unknown error occured // Deadlock avoided
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106884
interpreted = N
texte = --bcaec52e661777be1304a7be4ad0 Content-Type: text/plain; charset=ISO-8859-1 The issue I took with this thread (not sure if this is a new thread, moved from another thread, or what) was Chris, being part of the WebDNA company, telling a user that he does not like Windows and they should move to another platform. This might not be so bad if the company who sells (this is not open-source) only had a Linux version of the software. But they actually sell Windows versions. I am not saying that Tom went about this right at all. I do not think bashing WebDNA (or any language/platform/whatever) is the correct tactic to take when you go to its forum to seek assistance. I also agree that you asked him so pertinent questions that he did not respond to. He most certainly would need to give us A LOT more information before we can attempt to decipher the issue. I was not in disagreement with you Ken, except perhaps testing it on a Linux server would be prudent. You are right that it might help to find out if it is a Server issue or a WebDNA issue. But it failing on Linux does not in and of itself prove that it a WebDNA issue. He could set up the Linux server incorrectly, or the code could need something from a service call that the Linux server is not set up to do (and may not be able to do due to internal company constraints). Even it is work like a dream it does not get him really any closer to fixing the issue on the Windows platform that he has to use. I too agree with Chris in thinking this is a Server configuration issue. At this point we do not know (again unless this is a continuation from another thread that I missed) what version of WebCat, Windows, IIS/Apache/whatever, he is even having these issues on. Then when we know this we still do not know what configuration he is using. Does he have the UAC on or off? Are other applications or programs modifying the database file he is attempting to work with (btw, this has caused me a lot of grief in the past)? Is he running some Norton-esque anti-virus program that is being heavy handed and not allowing WebDNA to do its job? And it goes on and on. What has he tried to do and what happened, if anything, would be good information to have as well. I am not in total disagreement with what has been said here, ust felt that Chris could have perhaps worded his email a little different. If I were a consumer, especially one that inherited a project in a language I did not know and I was told that I need to get a new server, I would be thinking along similar lines as Tom in that I need to get this coded in something else. Sincerely, Ron 2011/7/10 Kenneth Grome
> 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 > --bcaec52e661777be1304a7be4ad0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable The issue I took with this thread (not sure if this is a new thread, moved = from another thread, or what) was Chris, being part of the WebDNA company, = telling a user that he does not like Windows and they should move to anothe= r platform. This might not be so bad if the company who sells (this is not = open-source) only had a Linux version of the software. But they actually se= ll Windows versions.
I am not saying that Tom went about this right at all. I do not think b= ashing WebDNA (or any language/platform/whatever) is the correct tactic to = take when you go to its forum to seek assistance. I also agree that you ask= ed him so pertinent questions that he did not respond to. He most certainly= would need to give us A LOT more information before we can attempt to deci= pher the issue. I was not in disagreement with you Ken, except perhaps test= ing it on a Linux server would be prudent. You are right that it might help= to find out if it is a Server issue or a WebDNA issue. But it failing on L= inux does not in and of itself prove that it a WebDNA issue. He could set u= p the Linux server incorrectly, or the code could need something from a ser= vice call that the Linux server is not set up to do (and may not be able to= do due to internal company constraints). Even it is work like a dream it d= oes not get him really any closer to fixing the issue on the Windows platfo= rm that he has to use.
I too agree with Chris in thinking this is a Server configuration issue= . At this point we do not know (again unless this is a continuation from an= other thread that I missed) what version of WebCat, Windows, IIS/Apache/wha= tever, he is even having these issues on. Then when we know this we still d= o not know what configuration he is using. Does he have the UAC on or off? = Are other applications or programs modifying the database file he is attemp= ting to work with (btw, this has caused me a lot of grief in the past)? Is = he running some Norton-esque anti-virus program that is being heavy handed = and not allowing WebDNA to do its job? And it goes on and on.
What has he tried to do and what happened, if anything, would be good i= nformation to have as well.
I am not in total disagreement with what= has been said here, ust felt that Chris could have perhaps worded his emai= l a little different. If I were a consumer, especially one that inherited a= project in a language I did not know and I was told that I need to get a n= ew server, I would be thinking along similar lines as Tom in that I need to= get this coded in something else.
Sincerely,
Ron
2011/7/10 Kenneth G= rome
<kengrome@g= mail.com> I have little patience with people who come here and
complain, then refuse to cooperate when we try to help. =A0I
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. =A0This 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. =A0If 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? =A0It would
be for me, especially if the server's traffic were important
to me.
--bcaec52e661777be1304a7be4ad0--
Associated Messages, from the most recent to the oldest:
--bcaec52e661777be1304a7be4ad0 Content-Type: text/plain; charset=ISO-8859-1 The issue I took with this thread (not sure if this is a new thread, moved from another thread, or what) was Chris, being part of the WebDNA company, telling a user that he does not like Windows and they should move to another platform. This might not be so bad if the company who sells (this is not open-source) only had a Linux version of the software. But they actually sell Windows versions. I am not saying that Tom went about this right at all. I do not think bashing WebDNA (or any language/platform/whatever) is the correct tactic to take when you go to its forum to seek assistance. I also agree that you asked him so pertinent questions that he did not respond to. He most certainly would need to give us A LOT more information before we can attempt to decipher the issue. I was not in disagreement with you Ken, except perhaps testing it on a Linux server would be prudent. You are right that it might help to find out if it is a Server issue or a WebDNA issue. But it failing on Linux does not in and of itself prove that it a WebDNA issue. He could set up the Linux server incorrectly, or the code could need something from a service call that the Linux server is not set up to do (and may not be able to do due to internal company constraints). Even it is work like a dream it does not get him really any closer to fixing the issue on the Windows platform that he has to use. I too agree with Chris in thinking this is a Server configuration issue. At this point we do not know (again unless this is a continuation from another thread that I missed) what version of WebCat, Windows, IIS/Apache/whatever, he is even having these issues on. Then when we know this we still do not know what configuration he is using. Does he have the UAC on or off? Are other applications or programs modifying the database file he is attempting to work with (btw, this has caused me a lot of grief in the past)? Is he running some Norton-esque anti-virus program that is being heavy handed and not allowing WebDNA to do its job? And it goes on and on. What has he tried to do and what happened, if anything, would be good information to have as well. I am not in total disagreement with what has been said here, ust felt that Chris could have perhaps worded his email a little different. If I were a consumer, especially one that inherited a project in a language I did not know and I was told that I need to get a new server, I would be thinking along similar lines as Tom in that I need to get this coded in something else. Sincerely, Ron 2011/7/10 Kenneth Grome > 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 > --bcaec52e661777be1304a7be4ad0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable The issue I took with this thread (not sure if this is a new thread, moved = from another thread, or what) was Chris, being part of the WebDNA company, = telling a user that he does not like Windows and they should move to anothe= r platform. This might not be so bad if the company who sells (this is not = open-source) only had a Linux version of the software. But they actually se= ll Windows versions.
I am not saying that Tom went about this right at all. I do not think b= ashing WebDNA (or any language/platform/whatever) is the correct tactic to = take when you go to its forum to seek assistance. I also agree that you ask= ed him so pertinent questions that he did not respond to. He most certainly= would need to give us A LOT more information before we can attempt to deci= pher the issue. I was not in disagreement with you Ken, except perhaps test= ing it on a Linux server would be prudent. You are right that it might help= to find out if it is a Server issue or a WebDNA issue. But it failing on L= inux does not in and of itself prove that it a WebDNA issue. He could set u= p the Linux server incorrectly, or the code could need something from a ser= vice call that the Linux server is not set up to do (and may not be able to= do due to internal company constraints). Even it is work like a dream it d= oes not get him really any closer to fixing the issue on the Windows platfo= rm that he has to use.
I too agree with Chris in thinking this is a Server configuration issue= . At this point we do not know (again unless this is a continuation from an= other thread that I missed) what version of WebCat, Windows, IIS/Apache/wha= tever, he is even having these issues on. Then when we know this we still d= o not know what configuration he is using. Does he have the UAC on or off? = Are other applications or programs modifying the database file he is attemp= ting to work with (btw, this has caused me a lot of grief in the past)? Is = he running some Norton-esque anti-virus program that is being heavy handed = and not allowing WebDNA to do its job? And it goes on and on.
What has he tried to do and what happened, if anything, would be good i= nformation to have as well.
I am not in total disagreement with what= has been said here, ust felt that Chris could have perhaps worded his emai= l a little different. If I were a consumer, especially one that inherited a= project in a language I did not know and I was told that I need to get a n= ew server, I would be thinking along similar lines as Tom in that I need to= get this coded in something else.
Sincerely,
Ron
2011/7/10 Kenneth G= rome
<kengrome@g= mail.com> I have little patience with people who come here and
complain, then refuse to cooperate when we try to help. =A0I
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. =A0This 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. =A0If 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? =A0It would
be for me, especially if the server's traffic were important
to me.
--bcaec52e661777be1304a7be4ad0--
Ronald Kirkland
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:
Re:no [search] with NT (1997)
WCS Newbie question (1997)
WAP and IIS server (2002)
Sku numbers (1997)
Rhapsody? (1997)
Configuring E-mail (1997)
'does not contain' operator needed ... (1997)
Error Lob.db records error message not name (1997)
all records returned. (1997)
Single Link browsing (1997)
WC Database Format (1997)
Great product and great job ! (1997)
MS Commerce Comparison (long) (1998)
Emailer tracking (1997)
Selecting sort fields (2000)
& in Lookups (1997)
Why is this not false? (2001)
[BULK] [WebDNA] Anyone using WebDNA7 and Lion Server? (2011)
Getting total number of items ordered (1997)
[movefile] (1999)