Endpoint Protection

 View Only
  • 1.  Indefinite loop in secondary.js

    Posted Mar 17, 2009 06:27 AM

    the reporting element from the management console is broken for instance if I click the more details from the security status it will launch internet explorer as its meant to but then ie will crash and not generate the report. I spoke to one of our guys from our internal development team and we attached a debugger to to the window to see what was happening and found that it just kept looping around the code shown below.

    while(1)
      {
       if(win.document.body !=null)
       {
        win.document.body.appendChild(f);
        break;
       }
       else
       {
        setTimeout("this.isIe7()",3000);
       

     

    this is extremely annoying we can't use any of the reports from the managhement console as they just crash. A temporary workaround we have used at the moment is to change the code to

     

    var retryCount = 0;
      while(retryCount < 100)
      {
       if(win.document.body !=null)
       {
        win.document.body.appendChild(f);
                 f.action=reloaction(url);
                 win.document.ska.submit();
        break;
       }
       else
       {
        setTimeout("this.isIe7()",3000);
                }
                retryCount++;

     

    while this works slightly better it doesn't work all the time and still only allow us to view the reports from http://server_address:8014/reporting it still will not work from inside the management console. Has anybody else come accross this issue? Does anybody from Symantec have a fix?



  • 2.  RE: Indefinite loop in secondary.js

    Posted Jun 22, 2009 02:07 PM
    HI,

    We appreciate your curiocity on this topic. Could you please let us know if the same is happening with the latest version of SEP MR4MP2 as well?

    Best Regards,
    Aniket Amdekar


  • 3.  RE: Indefinite loop in secondary.js
    Best Answer

    Posted Jun 23, 2009 04:18 AM
    Hi this was solved when we upgraded to IE8 so im not sure what was causing it I am yet to upgrade to mr4 mp2 I may look at this later today!