Showing results for 
Search instead for 
Did you mean: 

HTTP Status 404 - /InfoViewApp/logon.jsp

Former Member
0 Kudos


I am getting the following error 'HTTP Status 404 - /InfoViewApp/logon.jsp' when I try to log into Business Objects InfoView on our current production servers.  We have been using AD/SSO for four years now without issue.  Last night we rebooted the web server and this morning now one could log in using SSO. There have not been any changes on this server that we are aware of.  We are currently on Tomcat 5.5, BOXI 3.1 SP2 FP 2.3.

In the log files I am getting this error '

[DEBUG] Wed Nov 12 11:08:31 MST 2014 jcsi.kerberos: Message sent sucessfully to KDC:

12-11-14 11:08:31:698 - {ERROR} [localhost].[/InfoViewApp] Thread [Thread-1];  Exception starting filter authFilter

com.wedgetail.idm.sso.ConfigException: Configured service principal name `HTTP/vmedwboeweb1.PHS.ORG' could not be found [caused by: Client not found in Kerberos database].


Does anyone have any ideas why all of a sudden this would happen.


R Perez

Accepted Solutions (1)

Accepted Solutions (1)

Active Contributor
0 Kudos


It seems that the Domain Controller with IP can't find the Service Principal Name `HTTP/vmedwboeweb1.PHS.ORG' that I understand it is the name of your Web Application Server.

This may be due because:

- Somebody has created a duplicated SPN with the same name and different account

- Somebody has deleted the service account or the SPN

- Name resolution problems for the DC

This seems to be a problem related to your domain resolution.

I will recommend you to use AD Explorer to find for duplicates or missing SPN.


Former Member
0 Kudos

Hi Julian,

Thanks for the response.  I don't see any duplicates and when I do a SETSPN -L, I do see the SETSPN.

I am not sure how to find out if it is a resolution problem with a DC. Is there a tool or test I can do?



Active Participant
0 Kudos

Hi Rufina,

You can run setspn -x from server command prompt and verify the result. You can also check SAP Note: 1387370 to find the duplicate SPN's using AD explorer.


Answers (0)