Update on this IE issue in case anyone was curious...
Incident raised 22/04/14 after extensive testing. Acknowledgement that this is a bug finally received 18/08/14 after almost 4 months duration; only real progress made in August once Esri accepted our offer of utilising the client's development environment:
I have had a reply from our account manager at Esri Inc regarding this issue. He has spoken to the Tech Lead who is assisting with this call, who believes the issue to be a bug. The behaviour is inconsistent and specific to web-browsers. He sees different behaviours in IE9, IE10, and IE11, as you know and have reported. They believe they may have identified a workaround in IE10, but are currently testing this to ensure it works correctly. They have also contacted the primary product engineer for Esri Maps for Cognos, to see if this affects later versions of the product.
Will issue a final update once fix implemented.
Further update received from Esri 26/08:
I have received a response from Esri Inc regarding this issue at the end of last week. They have now confirmed the behaviour you have been experiencing and have therefore gone ahead and logged it as a bug:
NIM104434 - For a Specific report that has a drill through action, it will not display the map in Internet Explorer
They have been unable to identify the exact cause of the bug, but have found that in IE 9/10, if the report is run from the IBM Cognos Viewer (the Run Report button), the map will show up successfully. They have advised in the meantime that either Google Chrome or Mozilla Firefox browsers be used instead (as you reported back in March).
They have also asked me to advise you that Esri Maps for Cognos 4.3.2 will be retired on 1st January 2015 (as it is in the Mature Phase of Support). Unfortunately, because the product is in Mature Support, no further Service Packs, Patches or Hotfixes will be released for the product: http://downloads2.esri.com/support/TechArticles/ProductLifeCycle.pdf.
Esri Maps for Cognos 6.0 will be available for evaluation next month (30th September) should you wish to test against the newer version.
I am currently still working with Esri Inc to see if this issue has been fixed in later supported versions, or if the issue is still prevalent.
Latest response 12/09:
Apologies for the delay in getting back to you. Esri Inc do not believe they will be able to test the issue against the v6 release as they still have no way of consistently replicating the issue.
I think the quickest way to proceed would be to test this yourself with the v6 release when available to see if it has been resolved (which Esri Inc believe it will due to changes in the way the software behaves).
I appreciate that this is not an ideal suggestion, but I hope that it will allow us to keep progressing the call to a resolution. I am still trying to confirm the exact release date for the v6 software as well as the procedure to get hold of it.