installation errors

Post Reply
tmarino
Posts: 94
Joined: Thu Apr 25, 2002 1:04 pm

installation errors

Post by tmarino »

Just got the following errors when installing Webinator 4.3.3-Unix-w/plugin. Should I try a reinstall?

******************

Creating tables in control database /usr/local/morph3/texis/testdb .

--------------------------------------------------------------------------------
175 [webinatoradmin](selectwalk) 2401: Table options not found in data dictionary in the function opendbtbl 115 [webinatoradmin](selectwalk) 2401: No such table: options in the database: /usr/local/morph3/texis/testdb/ 000 [webinatoradmin](selectwalk) 2401: SQLPrepare() failed with -1 in the function prepntexis
User avatar
mark
Site Admin
Posts: 5519
Joined: Tue Apr 25, 2000 6:56 pm

installation errors

Post by mark »

You could try a reinstall. Does the file options.tbl exist in /usr/local/morph3/texis/testdb ? If so, are it's perms the same as the other files there? If you don't have any existing profiles on this machine you might want to rm -r /usr/local/morph3 before reinstalling to make sure you're clean.
jintov
Posts: 29
Joined: Fri Feb 22, 2002 5:43 am

installation errors

Post by jintov »

I have downloaded a free copy of Webinator 4.3 for Solaris sparc and have been trying to install it,
with iplanet as the web server.

The installation is failing with the following error

------------error message-----------------------
Checking dir with a web fetch...failed, will try again
Trying again with file...*** Failed ***
.
.
could not be fetched.
Possibly the CGI URL prefix (http://Shost:9080/cgi-bin)
or the CGI extension (none) is wrong.
The web server response was: HTTP/1.1 404 Not found
---------------End of error message-------------------

The URL prefix and cgi extension seems to be correct....

What could be the problem?
User avatar
mark
Site Admin
Posts: 5519
Joined: Tue Apr 25, 2000 6:56 pm

installation errors

Post by mark »

The 404 would indicate that you've specified the wrong CGI directory during installation. See your webserver's error log to see if it give any more detail. Check your webserver's configuration for the proper CGI directory.
Post Reply