Ranorex Report File (.rxlog) doesn't open using Chrome

[DMyers]

Hello!

We have a system in place where by we e-mail out links to Ranorex Report Files (.rxlog) which are hosted on a web server running IIS. Up until recently, everything has worked fine.

Now, Chrome has updated to version 34.0.1847.116 m and the report files no longer open. We can see the background image (dark grey on top, light grey on the bottom) but nothing else.

Using the Chrome debugger, we can see that the following error is occurring:

Uncaught ReferenceError: XMLHttpRequestException is not defined

This is occurring in the following function, in the catch block.

Code: Select all

	function checkForChromeWithoutDisabledWebSecurity()
	{
		if (document.browserInfo["BrowserName"].indexOf("Chrome") == -1)
			return;
		
		try
		{
			var doc = $.xsl.load(getDataFilePath());
			
			var a = 0;
		}
		catch(e)
		{
			if (e instanceof XMLHttpRequestException)
			{
				addErrorMessageBox("<b>Error:</b> Web security is enabled. Please start Chrome with <b>--disable-web-security</b> flag to allow access to local files.");
			}
		}	
	}

We have followed all of the instructions found here, http://www.ranorex.com/blog/share-your- ... ny-browser, and everything has been working well for several months now, until this latest update to Chrome.

We have also tested using Chrome with --disable-web-security and the issue still occurs.

Would anyone have any suggestions, or has anyone else even seen this? Or should I be raising this issue with Chrome directly?

Thank you!

[Support Team]

Hello DMyers,

Thank you for your request. Unfortunately you are right, Ranorex reports can no longer be opened since Chrome 34 and the current Ranorex Version 5.0.2. The reason for that is: In Chrome 34 the response to an 'XMLHttpRequest' (used to fetch the transformation and data file) is not placed in the 'xmlhttp.responseXML' property as Ranorex expects but in the 'xmlhttp.responseText'. Previous Chrome 33 as well as upcoming Chrome 35 place the result correctly again and as expected (we successfully tested that with Chrome 35 beta).

Since the official Chrome 35 version (non-beta) will take a while until it’s released, you can use the following workaround for Chrome 34 (next to opening the report in any other browser):

1. Open the Ranorex User Guide and proceed the steps creating a custom report template
2. Do not edit the CSS file or other files, but simply replace the 'View.rxlog' file by the attached 'View.rxlog' file below (extract the ZIP archive before)
3. With the next test run your reports can be opened again with Chrome 34 (also on your runtime machines once you re-build your test solution)

Note that the Chrome parameter '--disable-web-security' will always display the warning when opening Chrome:

sshot-372.jpg

When opening Chrome with parameter '-allow-file-access-from-files', you will not face a warning anymore but can still open the report.

Note also: The fix contained in the attached 'View.rxlog' file will be included in Ranorex 5.1 and also addresses the issue where reports could not be displayed if they are hosted by a webserver with no MIME-Type mapping for '.data' to 'xml/application'. So either mapping the mime type on your IIS web server or the workaround above should solve your problem.

Let me know if that helped.

Kind regards,
Stefan

[DMyers]

Thank you Stefan for the fast response!

Using the custom report template and attached View.rxlog file I am now able to open the reports using Chrome version 34.

Also I gave Chrome version 35 a try by switching to the beta channel in Chrome and confirmed that it works without any issues using the default report template.


Thank you again for all the help!

[Support Team]

Hi DMyers,

you are most welcome!
Meanwhile Chrome updated itself to another minor version (34.0.1847.131 m) where the problem is fixed. So no custom report template is necessary anymore with the current Chrome 34 version.

Still, we will ship a modified report template with Ranorex 5.1 that covers the MIME-Type problem mentioned above. That template will of course also work with Chrome 34 (in any case).

Kind regards,
Stefan

[mwillard]

Hi,

I'm having an issue where images are not being displayed because the URL contains '%5C' instead of '/'. My web server doesn't recognize these as \ and instead returns a 404 for the image links. Do you know if this will also be fixed in 5.1?

Thanks,
Mike