active report not working in IE11 when opened from email attachment

[Niraj]

Hi,

I am using cognos 10.2.2
i've develped an active report which has no issues when i open it from cognos portal when i am online.
But when i send it in as email attachment and when i try to open it from email attachment, I get a popup message from IE11 browser "Internet Explorer has stopped working".
Any help is greatly appreciated

Regards,
Niraj

[stan.parker]

Hi,

I am using cognos 10.2.2
i've develped an active report which has no issues when i open it from cognos portal when i am online.
But when i send it in as email attachment and when i try to open it from email attachment, I get a popup message from IE11 browser "Internet Explorer has stopped working".
Any help is greatly appreciated

Regards,
Niraj

Try enabling compatibility mode in IE11.


Sent from my iPhone using Tapatalk

[Niraj]

thanks for the reply but the problem still persist.

as i mentioned earlier report runs fine when executed from cognos portal but i m trying to open active report from email attachment than Internet explorer pops up with a message"Internet Explorer has stopped working" and than the URL shows "res://ieframe.dll/acr_error.htm"

kindly suggest

Regards,
NY

[jhopper@nmu.edu]

I am having this same problem, however, it just started happening around October 20.  It seems like an issue between Outlook and IE that may have been caused by some kind of an update around Oct. 20.  I hope someone can HELP!

Judy H.

[MFGF]

I am having this same problem, however, it just started happening around October 20.  It seems like an issue between Outlook and IE that may have been caused by some kind of an update around Oct. 20.  I hope someone can HELP!

Judy H.

What happens if you save the attachment, then try to open it from the folder you saved it into? Do you see the same issue?

In Cognos 10.2.2, when you view an active report from within Cognos Connection, the Cognos server unpacks the rendered MHT file and presents it to the browser as a normal HTML page. When you view an active report from outside of Cognos Connection, you are relying on the browser's ability to open and present the MHT file. It sounds like your browser is having issues with the latter process. Knowing if it's consistent between opening the MHT as an email attachment vs opening the MHT from the filesystem might help steer you in the right direction to understand the cause. If you have issues opening the MHT in both cases, it's entirely due to your browser and nothing to do with Outlook. If you only have issues when opening the MHT as an attachment but not after saving to a folder, it's an IE/Outlook interop issue.

Cheers!

MF.

[jhopper@nmu.edu]

If I save the attachment on my desktop, it opens fine.  It only happens when trying to open from outlook.  Any suggestions?

Judy H

[MFGF]

If I save the attachment on my desktop, it opens fine.  It only happens when trying to open from outlook.  Any suggestions?

Judy H

Ok. It's not a Cognos issue or an issue with the MHT, then. If you only get this error when opening the MHT as an attachment in an email, it's probably something to do with the security settings in the browser, or possibly interference from your antivirus software? Just guesses, though.

This is something you should take to your IT department and ask them to investigate.

Cheers!

MF.

[jhopper@nmu.edu]

Thanks MF. 

[hespora]

http://answers.microsoft.com/en-us/ie/forum/ie11-windows_7/ie11-crashing-when-opening-mht-files-after/c750830d-94c4-4950-a26e-9798a7f0c08a?page=1

Apparently, this was introduced by a recent (mid-october) microsoft security update, and the bug occurs depending on the absolute length of path and file name. (i.e., if you save the file in the root of a drive and a copy in a sufficiently deep and long folder structure, it will only work from the root). As Outlook saves the attachment to a rather deep temp path, that's what causes the bug. I've found if I call my attachment "1234.mht", it will actually work even straight from outlook attachment.

[hespora]

Apparently, this was fixed by the MS updates released last week.