1 Answer, 1 is accepted
0
Hi Leon,
We've tested this locally but could not reproduce the issue (see attached screenshot and files). Can you let us know how to proceed in order to replicate this on our side?
One thing that rings a bell is that you might get this error when you try to export to web archive. The html preview of our Reporting tool currently uses mhtml web archive. From what we've been able to research, it looks as if MS have locked down mhtml files due to an exploit found in Vista/IE7. According to MS, the vulnerability is in Windows Mail(Vista's OE) and there are 2 security patches that address the problem but still do not allow IE7 to open MHTML files.
Anyway we're aware of the issue and would address it for the Q2 release (or Q1 SP2 if we have SP2) by moving to standard html with some additional processing on our end to simulate the mhtml behavior.
If the above does not help, please provide more details on your scenario. Any additional information that you consider relevant would be appreciated.
Sincerely yours,
Steve
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
We've tested this locally but could not reproduce the issue (see attached screenshot and files). Can you let us know how to proceed in order to replicate this on our side?
One thing that rings a bell is that you might get this error when you try to export to web archive. The html preview of our Reporting tool currently uses mhtml web archive. From what we've been able to research, it looks as if MS have locked down mhtml files due to an exploit found in Vista/IE7. According to MS, the vulnerability is in Windows Mail(Vista's OE) and there are 2 security patches that address the problem but still do not allow IE7 to open MHTML files.
Anyway we're aware of the issue and would address it for the Q2 release (or Q1 SP2 if we have SP2) by moving to standard html with some additional processing on our end to simulate the mhtml behavior.
If the above does not help, please provide more details on your scenario. Any additional information that you consider relevant would be appreciated.
Sincerely yours,
Steve
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center