Page 1 of 1
Posted: Wed Jan 28, 2004 3:02 pm
I am trying the evaluation version of Webinator so I can decide whether it's a suitable search engine for a web application I am developing for my agency.
When I run the Admin module, the browser interface brings up what looks like a malformed URL:
, which cannot run.
I would expect to see something more like:
In the Home Directory tab of the default web site properties, I have given execute permissions of Scripts and Executables, and have given both read and write access (which IIS 5 cautions against).
Posted: Wed Jan 28, 2004 4:21 pm
You need a CGI directory in your webserver, one that is configured for execution. Once you have that do the webinator install. Specify that directory as your CGI directory when asked. IIS often has a "scripts" directory already setup that way. So you would say c:\inetpub\scripts for the CGI directory. Then the proper url would be http://YOURHOST/scripts/texis.exe/Webinator/dowalk
Then, if you have URLSCAN installed you need to configure it to allow .exe and possibly . .
Posted: Thu Jan 29, 2004 9:41 am
I set up a virtual web server and gave it full script read/write rights. I have a cgi folder in c:\perl\bin. I'm logged in as administrator. When I went to reinstall Webinator, when copying the files I got a Webinator setup error message:
"An error occurred in the move data process -132.
Posted: Thu Jan 29, 2004 10:42 am
Posted: Thu Jan 29, 2004 3:29 pm
Uninstalling and reinstalling got me into the admin page, but when I Update or Go or Update and Go, I get the page not found message: http://zntiis2/CGI-BIN/texis.exe/Webina ... wwFqnBn5B/
Posted: Thu Jan 29, 2004 5:06 pm
Maybe urlscan kicking in again. We've found that it's slightly broken. The rule for "." seems to kick in when there's a trailing "/" on a url. We're working on a workaround, but for now you need to allow ".".
Posted: Fri Jan 30, 2004 10:05 am
I modified the ini in urlscan so that "." would be allowed. Is there anything else I should do? I still get page not found:
is the command line generated.
Posted: Fri Jan 30, 2004 10:26 am
That appears to be a problem with urlscan. There is an updated version of the scripts available at http://www.thunderstone.com/texis/site/ ... ample.html
that will work around that.