Summary of the problem:
Unable to get the login screen on WebI 2.5 on Sun Solaris
Details:
We have installed WebI 2.5 on Sun Solaris.
First, I started the WebI Server using the wstart.sh shell script.
Then, I invoked WebI homepage using the URL:
http://IPAddress:Port/wi/HomePage.htm
The system gave me the InfoView Login Screen
When I clicked on the Login button, I get the error Message:
“The requested object does not exist on this server. The link you followed is either outdated, inaccurate, or the server has been instructed not to let you have it. Please inform the site administrator of the referring page”
The URL at this point shows:
http://IPAddress:Port/wi/bin/nph-cgiwi/WIGenerator/wigenerator/
generator/ExecuteWIS/sWIS=Logon
The OSAGENT_PORT that we used to install the WebI is 15069.
What I’m baffled about is, I don’t even get a login screen when I click on the Login Button in InfoView.
Any hints on getting this resolved will be greatly appreciated.
We were getting the same message initially after we installed WebI 2.5 under Solaris. We are a Sybase shop, so I’m not sure whether my information will be helpful, but I noticed that nobody else responded to your posting.
Which flavor of web server are you using? If Apache then the HomePage.htm is the correct URL. If it’s Netscape, you should go in under index.html.
We went with the default port of 14999. Don’t know if that could make a difference.
Do you have SSL installed on your Sun machine? You’ll need to enable each path in WebIntelligence under SSL. Check the security settings on your server and machine to make sure access is enabled.
Did you run the mainkey.sh program to create your bomain.key file and is the file stored in the proper directory?
Are all your paths set correctly?
Are you using port 8080 for something else? At our shop we were already using port 8080 for another product. WebI assumes 8080 is available for Java. If you are using 8080 for something else, you’ll have to change WebI to use a different port for Java.
If you are using Sybase, we got another document through tech support and Paris indicating some additional parameters to check. I can send it to you if it is relevant.
Check the log files. Turned out we had the wrong license key. The unix product is really new and shipping did not have their act together and kept giving us the wrong license keys. Double check with your sales rep that you have the correct keys. There are different keys if you are upgrading from a previous release as opposed to installing for the first time. The keys don’t get checked until you actually try to login, not when you install the product.
We worked with Tech Support to solve this and their suggestions did help. Ultimately we had the wrong keys. But we did manage to get past the initial URL Not Found problem with their help so that we could get to the login screen and discover that the keys were incorrect.
BTW, our installation is Solaris 2.7 and Apache 1.3.9 and it works even though B/O says they are only supporting Solaris 2.6 and Apache 1.3.3.
Debbie Kelly
Museum Informatics Project
University of California, Berkeley
dkelly@socrates.berkeley.edu