IE9 & Infoview (XI3.1 SP5)

[Former Member]

Hi all,

I have a client who has upgraded to IE9 and is having issues when trying to open Infoview. The same issues are described is this archived thread: http://scn.sap.com/thread/1972219.

The solution then was that IE9 was not supported for that particular environment and would be supported in SP5.... Well, my client has SP5 and it's not working, so I'm stumped. IE9 has been used in both Compatibility Mode and in 'non Compatibility Mode, this generates the same error (attached).

We'd raised an SAP case previously, the resolution was to uninstall and reinstall IE9, which worked for a short while, but now the issue seems to have returned. (I can't ask them to uninstall and reinstall IE9 again, that's beyond a joke).

Environment details:

Product version: SAP BusinessObjects Enterprise XI3.1 SP5

Server OS: Windows Server 2008 R2

Client OS: Windows 7

IE Version: IE9

I could suggest rolling back to IE8, however, the poition we're in is that there is a desktop standardisation projocet going on and IE9 is being rolled out on new Windows 7 laptops as standard, so, rolling back to a nearly unsupported browser doesn't seem like the way 'forward'

Anyone else having these  issues, if so, how did you resolve them?

[Former Member · Accepted solution]

Hello Ian,

Request you to check the following KBA, if it has some relevance to your issue. There is a workaround given as well:

1407984 - Error: HTTP Status 400 - Invalid path /AnalyticalReporting/WebiView when clicking a WebI r...

Thanks,

Madhumitha

[Former Member · Accepted solution]

Madhumitha,

These settings have already been applied unfortunately, I've just checked this with my client. Also the ADAPT number quoted in that SNote (ADAPT01328338) isn't mentioned anywhere on the Service Marketplace, except referenced in that SNote.

The problem still remains

[former_member188911 · Accepted solution]

Hi Ian,

It would be a quick test if you can redeploy the war files and check if there are changes in behavior.

I believe that a proper investigation should be able to identify the root cause whether you solve the problem with the re-deploy of war files or in case it still persists.

If you already have an open incident with support please let me know

Thanks

Simone

[Former Member · Accepted solution]

Hi Simone,

The WAR files were re-deployed on the 10th of January, but I've asked for them to be redeolyed again, I'm waiting for their server admin to come back to me on when this can be done. In the meantime, I'm going to create an SAP case anyway as this is causing hold-ups with a major project.

Once I've raised the case, shall I send you the number as well?

[former_member188911 · Accepted solution]

Yes please, that would allow me to follow how the investigation is going

thanks!

Best regards,

Simone

[Former Member · Accepted solution]

Hi Simone,

No problem, I'll either send a private message, or post the message number here once it's raised.

Further to the above, I've just checked with my client and as mentioned, the WAR files were redeployed on Jan 10th, but this has been done again more recently, both times, this has had no effect.

I've just got details for their SUID, so I'll create a message now.

Ian

[Former Member · Accepted solution]

Hi Simone,

I've just raised SAP Case: 334989 as a High priority case as it's actually affecting a project.

If necessary I can escalate this with the Customer Interaction Centre?

Ian

[former_member188911 · Accepted solution]

Hi Ian,

I hope it won't be necessary to escalate through CIC however if you have to do so please use this opportunity.

In the meantime my suggestion is to gather some http traces using the F12 function within IE9, you should have additional details that the engineer should use in the investigation.

Thanks

Simone

[Former Member · Accepted solution]

Simone.. I'd completely forgotten to come back to you regarding this. The issues my client was having have been resolved now. 

We made some changes in DEV initially, but these changes were also made in LIVE after a successfuly test in DEV.

Logging in as an enterprise user worked in IE9 but not for AD authenticated users. The reason for this was that the client has two separate logon.jsp and web intelligence apps on tomcat, one is configured to use enterprise authentication and the other to use windows AD. The one locked down to windows authentication is the one that services the user from the client domain and is located: Tomcat55\webapps\ROOT

However, the the enterprise logon is located in Tomcat55\webapps\InfoViewApp\ - This is not configured as it should have been configured.

We modified the web.xml file in the InfoViewApp\WEB_INF directory to set the 'authentication.visible’ property to ‘true’ rather than false giving users the ability to logon with whichever security we see fit.

So at this point we knew that logons serviced from the logon.jsp in the ROOT folder was failing in
IE9. So we tested we replaced both the logon.jsp and web.xml in the hope that this would resolve the issue but unfortunately it didn’t. 

So... We noticed that the application folders for InfoView in the ROOT folder where out
of date. So we backed these up offline and copied the contents of Tomcat55\webapps\InfoViewApp\ into the ROOT folder.

This resolved the issues after restarting Tomcat (although I'm not sure if this was necessary to be honest.

Going forwards for my client and for any future updates / fix packs they need to ensure that they are using the latest version of the InfoView app in the root folder as this seems to be the root
cause (pun intended) of the issue.

The issue was closed with SAP and this information was also provided to the engineer.

[DayaJha]

Hi Ian,

Please refer the below SNotes From SAP Market Place.

1626796 - HTTP status 500 error is raised when viewing a webi report in Infoview

Links:

https://service.sap.com/sap/support/notes/1626796

1544021 - HTTP 404 Error when creating new Web Intelligence document through Infoview

Links:

https://service.sap.com/sap/support/notes/1544021

1521215 - Does BusinessObjects Enterprise XI 3.1- BI4.0 support Internet Explorer 9.0?

Links:

https://service.sap.com/sap/support/notes/1521215

IE 9 will to be supported in BI 4.0 as of Feature Pack 3.

The following link will bring you to the PAM document for FP3:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/80ba792f-5e2a-2f10-0594-89315609e...?

For your reference please see the below PAM Matrix of SAP BOBI 4.0 Browser Supported by Operating System.

Or refer below URL

Links:

http://www.forumtopics.com/busobj/viewtopic.php?t=170250

Hope this will help you as well.

Thanks,

Daya

[Former Member]

Daya,

Thank you for the information above, in response to you:

SNote: 1626796 mentions SP3 and SP4, my client is on SP5, I am also unable to find any references to ADAPT01577881 on the SAP Marketplace except that one SAP note... but I have a feeling that this would advise the isues are resolved in SP5 for XI3.1.

SNote: 1544021 seems very helpful indeed, I will ask the client to go through these steps, however if a restart of Tomcat is needed (not mentioned but probably advised) then this will need to wait until later on as this is their production system.

SNote: 1521215 tells me what I already knew and had seen in the PAM Documentation

The BoB forum link mentions redeploying War Files, that's about the only thing we've not tried, but with that thread being over two years old now and the client being on SP5 (support for IE9 included), I'm skeptical as to whether this needs doing or not.

[Former Member]

I've just checked out the Tomcat settings (mentioned in SNote: 1544021 and they are exactly as described in the note... - although that's a good thing, it doesn't help in finding the cause of the issues.