BusinessObjects Board

http 403, INF 00105, JSP IIS/Tomcat

Crazy one here…

I’ve installed Webi 6.5.1. Configured Tomcat connector into IIS, configured JSP pages. Login page comes up ok, click on login and it reports through Tomcat - "HTTP Status 403 - The Business Objects server is not ready. (Error: INF 00105).

type Status report
message The Business Objects server is not ready. (Error: INF 00105)

description Access to the specified resource (The Business Objects server is not ready. (Error: INF 00105)) has been forbidden. "

IIS5 with Tomcat/4.1.30. Tomcat/JDK was installed off the 6.5.1 installation disk. :confused:

The connector works ok as it’s visible in IIS (green arrow) and the examples/jsp work fine on port 80 which is IIS->tomcat, plus going directly through on 8080. :shock:

The strange thing is, by going to http://server:8080/wijsp/scripts/login/login.jsp or LoginForm.jsp, the basic page comes up and allows you to login (minus the graphics and stuff because they’re not in the tomcat area).

(Also, I’ve setup some asp pages in the config tool and they work fine, and allow you to login and view docs etc). :o

Does anyone have any ideas? This brick wall is getting a lot of usage at the moment… :rotf:

Thanks…
Rich. :crazy:


::Rich:H :uk: (BOB member since 2002-09-11)

I have an open post here with an error that may share the root cause of the problem with a diff error msg for you since you are using iis and not apache.

https://bobj-board.org/t/34954

This post (https://bobj-board.org/t/34801) seemed to indicate using the configure tool to remove the app and virtual directory, update orb and then add back in the app and virtual directory, however that did not seem to fix my problem.

I will be watching here to see if a fix for your problem will help fix mine.

Davlun


davlun (BOB member since 2003-07-08)

Based on error code (Error: INF 00105). You might want to check config of WILoginServer.

Can you access http://server:8080/wiadmin/ ?

Check the authentication mode on repository. That might be the cause.

My response is based on 6.1b. Not sure abt 6.5


shamit (BOB member since 2004-07-01)

I’ve cracked the problem:

I edited the server.xml file under tomcat/conf and commented out the org.apache.coyote.tomcat4.CoyoteConnector entry on port 8080.

Rich. :+1:


::Rich:H :uk: (BOB member since 2002-09-11)

I had the same problem before and solved it by updating the ORB, deleting the web app and virtual directory and recreating them again (appears in a previous post).

I just installed BO on another server and I’m getting this error again, only while accessing InfoView(wijsp). I can access the admin console (wiadmin) just fine.

I followed the same procedure as I had in the past with no success. I also commented out the Coyote Connector on port 8080 as this post suggests…still no luck. Anyone have any ideas? Can any BO people out there offer any further suggestions?

Thanks,

Jason


codeman (BOB member since 2004-10-21)

click the link below, it might help

this


BO_Chief :us: (BOB member since 2004-06-06)

Not really related to the initial post…

But if you are getting this error (HTTP Status 403 - The Business Objects server is not ready. (Error: INF 00105)) and are using SiteMinder for authentication (or have a SiteMinder web agent installed on your web server)… you might like to check out Knowledge Base Resolution Entry 18115.

This resolution entry was for a supposedly unrelated issue, but there appears to be a problem with the logic in login.jsp that was causing me problems at a client site - the changes detailed in this resolution entry fixed things up!


GraemeSmith :switzerland: (BOB member since 2002-08-16)

After working with BO Tech support for two weeks, I am still having the same problem (HTTP Status 403, Server is not ready. INF 00105) when using Integrated windows authentication. The problem occurs when accessing http:///wijsp/ login. The http:///wiadmin/ is working fine. When I switch the authentication mode from Windows to Business Objects, everything works fine.

BO tech support told me today that they are getting a lot of phone calls for this same issue but they don’t have a solution yet. He is escalating this issue now.

Does anyone have a real working solution for BO E6.5.1 with Integrated windows authentication using IIS/Tomcat? If so, please share your insights. Thanks in advance.

My environment is
BO E6.5.1
Windows 2000 SP4
IIS 5, Tomcat 4.1.30, and JDK 1.4.2_03 (came with BO 6.5.1 software)


shuj (BOB member since 2004-04-30)

Hi shuj,

Please see my post here for some suggestions to a problem that sounds like yours.

It makes sense that wiadmin would still work, as it doesn’t attempt to use any kind of external authentication.

Joe


joepeters :us: (BOB member since 2002-08-29)

Joe
Thanks for pointing me to your posting.
I followed your suggestion and solved the NTLM/IIS/Tomcat problem that I had with wijsp in E6.5.1.

Jenny


shuj (BOB member since 2004-04-30)

This Entry (18115) is not found on the CSP site (maybe they pulled it) … Entry 16511 is related


Chris Pohl :us: (BOB member since 2002-06-18)