Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Problems Expanding Backup Exec Reports In IE 11

Created: 26 Nov 2013 | 12 comments

Hi there

Anyone know how to enable the possibility to expand Backup Exec Reports in IE 11 ? Works fine in 10, but not in 11.

I've tried from backup Exec 11d to 2010 R3, same problem.

Ideas ?

Kind Regards

Kim

Operating Systems:

Comments 12 CommentsJump to latest comment

CraigV's picture

Hi,

Probably an incompatibility issue.

Have you tried to save the report and use the compatibility mode in IE to open it in a different version?

Otherwise use another browser, or downgrade your version of IE...

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Kim Mortensen - IT Forum's picture

Not workinging Chrome or Firefox.

How can i choose that IE 11 should open attached HTM file in compatibility mode ? Tried to add *.htm, but makes no diference.

Kind Regards

Kim

CraigV's picture

...save the file as *.htm and then open it. Once done, press F12 which brings up a dialogue box. Press the Browser Mode: and choose a lower version.

If this doesn't work, see if you can print to a PDF printer.

But you are most likely using an incompatible version...

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Steve Czatt's picture

Has there been a resolution to this problem?  Craig, an incompatible version of WHAT?

I'm running windows 8.1 and IE 11, but it doesn't work with Firefox either. So is this an OS problem? is Windows 8.1 not supported? That should be corrected SOON!!!  I'm not going back to Windows 7, that's not an option...

Thanks for any help.

Colin Weaver's picture

I have received internal confirmation that our Dev teams have checked reports with Backup Exec 2010 R3 and Backup Exec 2012 on Windows 2008 R2 SP1 with IE 11.0 installed and all is working as expected as such anyone having problems with IE 11 and reports (or job logs) should log formal support cases for us to look into it further.

Steve Czatt's picture

OK, so I opened a support case for this issue.  The FIRST thing the tech asked me to do was move the html file to another machine to see if it would open normally outside of ie 11 and windows 8.1.  Of course it opend fine and the buttons all worked.  I was then told that the html file is fine AND that Backkup Exec is working as expected.  I was also told that this would be MY problem to figure out since it is MY ie 11 that is having the issues.  The tech further told me that I would have to "play" with the ie 11 setting to see what is keeping it from displaying correctly.

So, to summarize, Symantec has stated that the issues is NOT with the code that is being generated from the product, but with MY ie 11 install and MY windows 8.1, and that it is MY problem to resolve.

So much for tech support being helpful.

Has anyone found the settings in ie 11 that are causing this issue since tech support doesn't want to do their job?

sandy_sym's picture

I had the same issue -

Windows 8.1 & IE 11

Open the Backup Report File in IE

Hit F12 key or Select Developer Mode from Setting Menu

Change the Document mode from Edge Default to 8 ( Refer attachment for Snapshot)

And Voila...it works..

IE11Settings.png
KREMREXS's picture

Same issue with BE2012 and Chrome any ideas??

Frank Larsen's picture

Have done some "research" on this regarding IE.

The attached html need only to have an extra line inserted at the top of the html.

Origial html code:

New html code:

This forces IE 11 to view the page in compatiblity mode.

If IE=5 in META content, then there is no prompt to "Allow Blocked Content" in IE 11

I do not know how to put Chrome or Firefox into similar mode.

Symantec should use some time to make a patch that changes the way how html-code is made.

SchiederLeonardo's picture

Any updates on this issue? I'm having the same issue with IE11 and BE2010R3 reports.

usafseic's picture

OK, being annoyed by this issue for a while, I went in and checked out the Javascript code that manages the report interactivity and figured out what needs to be changed to get it to work both in IE (8-11) and Chrome.  I don't use FF, but I'd imagine the changes will work for it as well, since they're standard DOM objects and methods.

There are two Javascript functions named Expand() and ExpandAll() that control this functionality.  In order to fix the Expand() function, only one line of code needs to be changed:

var child = srcElement.parentElement.parentElement.all[srcElement.getAttribute('child',false)];

needs to become

var child = srcElement.parentElement.parentElement.querySelector("#"+th[i].getAttribute('child',false));

The querySelector() method is supported back to IE 8 and in Chrome.  I remember from my days of DHTML coding that the use of the all property is "frowned upon in this establishment" because it doesn't translate well across browsers other than IE, and even IE balks at it nowadays in some places.

As for the ExpandAll() function, it needs a few more changes.  The same change as above needs to be made to querySelector(), as well as the following block

var th = document.all.tags('TH');
for (var i=0;i<th.length;i++) {
   for (var j=0;j<th[i].all.length;j++) {
      if (th[i].all[j].tagName == 'INPUT') {
         th[i].all[j].value = image; } } }

needs to become

var th = document.getElementsByTagName('TH');
for (var i=0;i<th.length;i++) {
   for (var j=0;j<th[i].childNodes.length;j++) {
      if (th[i].childNodes[j].tagName == 'INPUT') {
         th[i].childNodes[j].value = image; } } }

Again, the all property needs to be replaced by childNodes for it to work in IE 11, and getElementsByTagName will make it work in Chrome.

Now as for applying the fix, if there's some kind of HTML or XSLT template file that's used to build the report from the source XML file, then changing the function code there will fix the issue permanently.  But if the presentation logic is coded into the BE application itself, then only Symantec can patch that for us.  I tried looking (although not very hard) for a generic template in the program folder, but didn't see anything that might be it.  If anyone knows about that, please reply and I'll test it out.  The other option is to set up a script (Powershell) on the server to run at a set interval through Task Scheduler that parses all .htm files in the Data directory and makes these changes automatically.  However, that would be correcting it after the fact, as I'm guessing the original report file would have been e-mailed out to me immediately before being stored on the server for very long.

And I don't know whether this was corrected in BE 2014.  I don't have plans to upgrade from BE 2012 yet.

pkh's picture

For better visibility, post this as an Idea in the Ideas section