## installation/texis problem

bob.tumposky.bra
Posts: 4
Joined: Mon Jan 26, 2004 2:37 pm

### installation/texis problem

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:
http://zntiis2/perl/bin/texis.exe/Webinator/dowalk, which cannot run.

I would expect to see something more like:
http://zntiis2/perl/bin/texis.exe "Webinator dowalk"

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).

Any ideas?

bob.tumposky.BRA@ci.boston.ma.us
mark
Posts: 5505
Joined: Tue Apr 25, 2000 6:56 pm

### installation/texis problem

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 . .
bob.tumposky.bra
Posts: 4
Joined: Mon Jan 26, 2004 2:37 pm

### installation/texis problem

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.

Component:
File Group:
File:
mark
Posts: 5505
Joined: Tue Apr 25, 2000 6:56 pm

### installation/texis problem

bob.tumposky.bra
Posts: 4
Joined: Mon Jan 26, 2004 2:37 pm

### installation/texis problem

mark
Posts: 5505
Joined: Tue Apr 25, 2000 6:56 pm

### installation/texis problem

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 ".".
bob.tumposky.bra
Posts: 4
Joined: Mon Jan 26, 2004 2:37 pm

John