Hi Jacob:
As you are likely aware, this doesn't sound like a Witango 5 problem but
rather, a permissions issue.
It depends entirely on how you copied your directory. If, for instance, you
copied it onto your desktop, then moved it into position and pointed your
IIS website at it, you likely have not got the correct file and / or
directory permissions set up to allow the web server to allow the TAF to be
executed.
To test this, create and save a simple TAF directly into the executable
directory, and prove that you can get the desired results by hitting the
site. Next, create and save a similar file to the desktop, then move it
into the same directory as the first file. It likely will not work for you.
If the permissions thing proves to be the problem, then copy your previous
files into the new website directory, overwriting the files that will not
execute. Or, if as you indicated, you have made changes to the files,
change the permissions on the new files to include execute.
HTH,
Ian
-----Original Message-----
Anyone have any ideas? This is a critical set back for me and my
livelihood.
Please help!
Did I sound too desperate there? ;)
-----------------------------------------------------------------------
Hello Everyone,
Recently I've upgraded to Witango 5 Server and had absolutely no
problems. However to use the license I received I had to install a newer
version of the software. This also worked just fine. I am running the
latest build.
However, I made a duplicate of a site that needed several variable scope
changes to run properly. After making these changes I now cannot follow
links from within the site without getting a Witango error. If I load
the root of the site (index.taf by the IIS default document setting)
everything works great. Then the next couple links also work great.
However after only a couple links I begin to receive a file not found
error by Witango Server. I had been running the site fine prior to the
latest build.
One thing I perhaps shouldn't have done was to first rename the old copy
of the site directory, and to give the new copy the same name...
As I am supposed to get this site live on the new server software this
afternoon, can anybody give me any ideas of what might be wrong? I'm
hoping its some obvious oversight, but I can't figure this one out.
Thanks in advance for any advice. If you'd like or need to see the
problem in action I could send you a link to the development site.
- Jacob Stevens
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
