Ok, I was not going to respond to this mess= age as I had nothing to really contribute, but the response that the develo= per should migrate to a different server environment to fix an issue he is = having with a programming language that was purchased (and does have a wind= ows version) is insane. What makes this worse is that Chris suggested it. I= am extremely shocked at this and a little concerned.
Ken you asked him why he could not migrate? Besides the "he should= n't have to," if he is at a company of any size, there is typicall= y many logistical issues that would have to be overcome. Server farms, IT d= epartment being MS certified (not *nix people), cost of a new Linux license= for a language that is already giving them troubles, to just name a few. <= br>
Now, I have run WebDNA on Linux, Mac, and Windows since I began using i= t (when I was hired at SmithMicro back in 99). All the servers have offered= hurdles that had to be overcome at one time or another. I was running WebD= NA on a windows server until just about a year ago and it had worked fine f= or years.
Threatening to move to another language to fix the issue is not obvious= ly the best way to get support for a product that you are having issues wit= h. Nor is telling the people who are using it that their language is not go= od enough or powerful enough to run enterprise level apps. I have built som= e extremely large and complex applications using WebDNA for many LARGE comp= anies (Boeing, Honeywell, Pillsbury, etc.). And for the record I am at this= very moment dealing with a massive PHP project that is having issues. And = in the past I have run into the=A0 same type of issues with ColdFusion, .Ne= t, and Perl. So none of the languages are perfect or error proof.
I think our time would be a little better spent looking at what could a= ctually cause these issues rather than bashing the language or server choic= es.
Tom, I know it can difficult to share code when it is technical= ly the IP of the company you work for, but there is not always a blanket re= ason for something to fail. There are too many variables that can come into= play (write permissions, drivers, registry constraints, etc.).
Some suggestions and questions to help you and possibly help us help yo= u:
1. Does this happen every time you attempt to write to that speci= fic database(s)?
2. Is it always the same database(s)?
3. Write a sim= ple script that is not accessed via the app to write test data to the datab= ase(s). Does this work or do you get the same error?
4. Give us more info about the environment:
=A0=A0=A0 - Windows version = (please include service pack too)
=A0=A0=A0 - IIS, Apache, something els= e? (give versions please)
5. Are other apps using the same files or dire= ctories?
6. Try stepping through the code and see if this is only happening after a = specific task is executed.
I am in agreement with Ken that this seem= s to be a configuration issue or an errant code. I am not going to blame th= is on the old developer, but perhaps something changed and the app is expec= ting A and getting B. We just cannot know at this time.
Best of luck!
RonOn Sun, Jul 10, 2011 at 5:13 AM, Kenneth Grome <ken= grome@gmail.com> wrote:
What is the URL to the website you're having all these
problems with?
What is the URL to the admin system you've been referring
to?
Yes I know we do not have a username/password to use it --
but I still want to see it so I know whether you're talking
about a system I'm familiar with, or one that someone built
as a custom admin system for your server.
You could redirect all http requests to the new Linux server
> No, the reason is that the entire architecture is
> designed around windows systems - there are tons of
> things running on the server that require windows, we
> are thoughouly tied into windows.
while keeping everything else running on your existing
Windows server. =A0Do you know how to do this? =A0If so, are you
willing to do this as your FIRST attempt to get the problem
resolved? =A0Or is this something you are willing to try after
you've tried other approaches to solve the problem? =A0Or are
you simply not willing to try this at all?
WebDNA does not refer to other servers, it only works with
> Now we could get another machine to run just the
> webserver on but the way the system is designed /
> implemented, that would mean I would have to
> change all places where webdna refers to the servers
the files on the server it is installed on.
Or are you talking about changing a bunch of http paths?
This sounds like a 5 minute change via UltraEdit "search and
replace in files" if you ask me. =A0Or maybe this would take an
hour or two -- which should still be no big deal in terms of
the value of actually getting the problem resolved, right?
Unfortunately you still haven't answered any of my other
questions so I get the feeling that you're not really
serious about getting WebDNA fixed anyways. =A0If this is true
then please tell us that you've given up on WebDNA so we
don't waste any more time trying to help you.
Otherwise will you please just give us the URLs I asked for
above? =A0Your answers to these questions would be a good way
to help us help you, too:
> > What is your "plan of action"?
> > Have you tried to reboot the server yet to see if that=
> > clears up the problems???
> > What are you telling this admin panel to do?
> > What "admin panel" are you talking about? = =A0The> > How are you deleting the probematic database file?
> > WebDNA admin panel that came with the WebDNA software,
> > or a separate programmer's admin panel? =A0Or some other
> > admin panel?
> > Via an admin panel button or link?> > BEFORE deleting the database file?
> > Are you flushing the databases first
> > 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
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <ta= lk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: suppo= rt@webdna.us
DOWNLOAD WEBDNA NOW!
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...