Does it work in other IE versions? The current product versions weren't tested with IE9, and there may be some issues with it.
Sorry I don't have other version of IE, it's ok work on other brower?
I can duplicate the problem.
On a W7 64bit PC I can use the MVM console in IE9, but a downloaded HTML report gives the error @tony.lin descibed above.
On another W7 64bit PC I can't even use IE9 to navigate the console correctly.
IE8, IE7 and IE6 work just fine. (tested on virtual XP)
You can try Firefox. we don't certify that it will work 100%, but it might help in this situation.
I have this problem, loading saved reports, regardless of which browser I use (as I recall, it worked in some of them previously).
Unfortunately, I do not have access to our MVM server at this time (but I do have a lot of saved reports I need to work with)
Browsers I have tested:
- Internet Explorer version 11.0.9600.16428IS
- Google Chrome Version 31.0.1650.63 m
- Firefox version 26.0
Messages vary according to browser; First message of each is shown:
- Internet Explorer
- /paging::ReferenceError: 'XPathEvaluator' is undefined
- Google Chrome
- reportconfiguration.xml::TypeError: Object # has no method 'load'
- ../I18N/en/customreportstrings.xml::[Exception... "Access to restricted URI denied" code: "1012" nsresult: "0x805303f4 (NS_ERROR_DOM_BAD_URI)" location: ""]
I am running Windows 7, 64 bit, SP1.
I have MVM version 7.5.
Also fails in Opera Version 12.16
reportconfiguration.xml::ReferenceError: Security violation
This question may have been "Answered", but not resolved.
Still, as at this date, the problem still exists. Report loads when launched from the MVM "application" (in a browser), but not from the downloaded HTML file set.
FWIW, I am running Windows 7 Enterprise SP1 x64. I have re-tested on each of the browsers I've already listed in this thread, current versions.
Any chance of this getting fixed anytime soon?...
I realize this post is almost a year old but it seems people are still finding this thread with this issue. IE11 can be run 'as' IE10 using the Developer Tools and this is the solution. Please see the Supported Browsers section of KB52115 for instructions.