SRM catalog navigation fails after Microsoft patch KB2416400

[Former Member]

After applying Microsoft patch KB2416400, displaying catalogs is failing in IE7 and IE8. Getting the "Navigation to the webpage was canceled"... If you uninstall the patch, it will fix the issue in IE7. I have already reviewed the settings found in OSSN 1511147, which has not solved the issue when the patch is applied. Has anyone else applied this IE security patch and experienced similar results? We are on SRM7.0, SP05 - EP and catalogs both using https. Thanks.

[Former Member · Accepted solution]

FYI, the McAfee issue only pertains to clients who have HIPs implemented. We do not, so this problem is still outstanding...

[Former Member · Accepted solution]

Hi Kris,

we are experiencing the same issue when accessing an external catalog with https.

On PC without KB2416400 it works fine.

Any update from SAP so far?

[Former Member · Accepted solution]

Hi Jan -

No further response from SAP has been received. I will keep this thread updated with any pertinent information. I am "glad" to hear that other customers are experiencing the same issue.

Thanks,

Kris

[Former Member · Accepted solution]

Hi Kris,

we found a solution. Please look in SAP Note 1456162.

The note was written for IE 8, but it looks that the MS patch KB2416400 provides the same security measure also for IE 7.

IE7 does not allow the dynamic rendering of html by the outbound handler after the patch.

Cheers,

Jan

[Former Member · Accepted solution]

Hi Jan -

I will review this note.. I have read it before, but never looked at it further as in the note SAP indicates it is only an issues when EP is in https and the catalog is in http. I think you indicated before, but are both your EP and catalogs using https?

Thanks,

Kris

[Former Member · Accepted solution]

We are finishing up testing, but this note will fix the issue. Thanks Jan, points provided, question closed. Thanks.

[Former Member]

FYI, SAP responded through our OSS message and looks like it is a possible issue with the combination of the patch and our use of McAfee as our AV, please see McAfee KB:

https://kc.mcafee.com/corporate/index?page=content&id=KB70810