Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Administrators

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 05-12-2010, 04:26 AM
Active Member
 
Posts: 41
Default Opening webmail in 6.06 script error message

Just upgraded from 6.01 to 6.06. Looked good.
Now when I log in via the webpage I get an error message (Firefox and IE):

A script on this page may be busy or it may have stopped responding.
You can stop the script now, or you can continue to see if the script will complete.
script: http://myhostname.mydomainname.com/zimbra/:2219


Any idea's how to solve this?

Thnx,
Roderick

(Fedora7, Zimbra 6.06 - migrating to Fedora11 x64 in the near future)

Last edited by mrcoffee11; 05-12-2010 at 04:33 AM..
Reply With Quote
  #2 (permalink)  
Old 05-12-2010, 07:09 AM
Moderator
 
Posts: 7,928
Default

Is this happening across a WiFi connection ?
__________________
Reply With Quote
  #3 (permalink)  
Old 05-12-2010, 07:44 AM
Active Member
 
Posts: 41
Default

Nope, it's directly on the LAN with a 100MB connection or faster. The error only occurs when I log in. And wifi never had an issue too with version 6.0.1
Reply With Quote
  #4 (permalink)  
Old 05-12-2010, 07:49 AM
Moderator
 
Posts: 7,928
Default

Okay; is it reproducible ? If it is would you please logout and log back in again but appending to the end of the URL ?dev=1 ie.
Code:
http://zcs_fqdn/zimbra/?dev=1
See if you get any JS errors.
__________________
Reply With Quote
  #5 (permalink)  
Old 05-12-2010, 08:17 AM
Active Member
 
Posts: 41
Default

Wow, there is a lot of info but I don't see any errors.

Logged in again and I could see the debug log grow, nice work there.

This is where the process started hanging:

Code:
GetMiniCalRequest (asynchronous) - 17:18:35.074

Body: {
  GetMiniCalRequest: {
    _jsns: "urn:zimbraMail",
    e: 1275861600000,
    folder: [
      0: {
        id: "10"
       },
      1: {
        id: "33270"
       },
      2: {
        id: "3854"
       },
      3: {
        id: "834"
       }
     ],
    s: 1272232800000,
    tz: [
      0: {
        id: "Europe/Brussels"
       }
     ]
   }
 },
Header: {
  context: {
    _jsns: "urn:zimbra",
    account: {
      _content: "myemailaddress_censored@r71.nl",
      by: "name"
     },
    authToken: "XXXXXXXXXXXXXXXXXXX",
    session: {
      _content: 167,
      id: 167
     },
    userAgent: {
      name: "ZimbraWebClient - FF3.0 (Win)",
      version: "6.0.6_GA_2330.F7"
     }
   }
 }
Then I got a popup:

Code:
A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.

Script: http://webmail.r71.nl/zimbra/js/zimbraMail/share/model/ZmZimletBase.js?v=100505192852:898


This is after the pop up appeared:

Code:
ROUND TRIP TIME: 183
RESPONSE (asynchronous) - 17:18:35.295

Body: {
  GetMiniCalResponse: {
    _jsns: "urn:zimbraMail",
    date: [
      0: {
        _content: "20100427"
       },
      1: {
        _content: "20100428"
       },
      2: {
        _content: "20100429"
       },
      3: {
        _content: "20100502"
       },
      4: {
        _content: "20100504"
       },
      5: {
        _content: "20100506"
       },
      6: {
        _content: "20100513"
       },
      7: {
        _content: "20100530"
       },
      8: {
        _content: "20100603"
       },
      9: {
        _content: "20100605"
       }
     ]
   }
 },
Header: {
  context: {
    _jsns: "urn:zimbra",
    change: {
      token: 260344
     },
    session: {
      _content: "167",
      id: "167"
     }
   }
 },
_jsns: "urn:zimbraSoap"

------------------------- Running response callback for GetMiniCalRequest
------------------------- Processing notifications for GetMiniCalRequest

Last edited by mrcoffee11; 05-12-2010 at 09:28 AM.. Reason: removed auth token
Reply With Quote
  #6 (permalink)  
Old 05-12-2010, 08:21 AM
Moderator
 
Posts: 7,928
Default

Did it throw the timeout error again ? Have you tried clearing your browser cache ?
__________________
Reply With Quote
  #7 (permalink)  
Old 05-12-2010, 08:24 AM
Active Member
 
Posts: 41
Default

Clearing the cache was one of the first things I did. Didn't work. Tried two browsers (FF and IE) on two computers.
I edited the post I made just a few minutes before and added info. Maybe this helps you.

Last edited by mrcoffee11; 05-12-2010 at 09:27 AM..
Reply With Quote
  #8 (permalink)  
Old 02-17-2011, 09:25 AM
Starter Member
 
Posts: 2
Default

I'm having the same problem, are this problem still unsolved?
Reply With Quote
  #9 (permalink)  
Old 02-17-2011, 10:54 AM
Zimbra Consultant & Moderator
 
Posts: 20,313
Default

Quote:
Originally Posted by toolhead View Post
I'm having the same problem, are this problem still unsolved?
You need to give a bit more detail than a 'me too' post. Which version of Zimbra, which browser, what error messages, what have you tried to resolve the problem, what exactly happens - that will be a good place to start.
__________________
Regards


Bill
Reply With Quote
  #10 (permalink)  
Old 02-18-2011, 04:52 PM
Starter Member
 
Posts: 2
Default

I have upgraded from 6.0.2 to 7.0.0, here are the logs loggin in w/?dev=1

This is the popup

Code:
A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.

http://xxx.xxx.xxx/zimbra/js/zimbraMail/share/model/ZmZimletBase.js?v=110127203235:931
before the popup

GetMiniCalRequest - 18:44:51.634
Code:
Body: {
  GetMiniCalRequest: {
    _jsns: "urn:zimbraMail",
    e: 1300082400000,
    folder: [
      0: {
        id: "10"
       }
     ],
    s: 1296453600000,
    tz: [
      0: {
        id: "America/Mexico_City"
       }
     ]
   }
 },
Header: {
  context: {
    _jsns: "urn:zimbra",
    account: {
      _content: "xxxxx@xxx.xxx",
      by: "name"
     },
    authToken: [authToken],
    session: {
      _content: 13503,
      id: 13503
     },
    userAgent: {
      name: "ZimbraWebClient - FF3.0 (Linux)",
      version: "7.0.0_GA_3077"
     }
   }
 }
GetMiniCalResponse - 18:44:52.449
Code:
Body: {
  GetMiniCalResponse: {
    _jsns: "urn:zimbraMail"
   }
 },
Header: {
  context: {
    _jsns: "urn:zimbra",
    change: {
      token: 322
     },
    session: {
      _content: "13503",
      id: "13503"
     }
   }
 },
_jsns: "urn:zimbraSoap"
and after the popup

SearchRequest - 18:45:06.335
Code:
Body: {
  SearchRequest: {
    _jsns: "urn:zimbraMail",
    calExpandInstEnd: 1298095199999,
    calExpandInstStart: 1297404000000,
    limit: "500",
    offset: 0,
    query: {
      _content: "inid:10"
     },
    sortBy: "none",
    types: "appointment"
   }
 },
Header: {
  context: {
    _jsns: "urn:zimbra",
    account: {
      _content: "xxxxx@xxx.xxx",
      by: "name"
     },
    authToken: [authToken],
    session: {
      _content: 13515,
      id: 13515
     },
    userAgent: {
      name: "ZimbraWebClient - FF3.0 (Linux)",
      version: "7.0.0_GA_3077"
     }
   }
 }
SearchRequest - 18:45:06.351
Code:
Body: {
  SearchRequest: {
    _jsns: "urn:zimbraMail",
    limit: "500",
    offset: 0,
    query: {
      _content: "inid:15"
     },
    sortBy: "none",
    types: "task"
   }
 },
Header: {
  context: {
    _jsns: "urn:zimbra",
    account: {
      _content: "xxxxx@xxx.xxx,
      by: "name"
     },
    authToken: [authToken],
    session: {
      _content: 13515,
      id: 13515
     },
    userAgent: {
      name: "ZimbraWebClient - FF3.0 (Linux)",
      version: "7.0.0_GA_3077"
     }
   }
 }
SearchResponse - 18:45:06.632
Code:
Body: {
  SearchResponse: {
    _jsns: "urn:zimbraMail",
    more: false,
    offset: 0,
    sortBy: "none"
   }
 },
Header: {
  context: {
    _jsns: "urn:zimbra",
    change: {
      token: 322
     },
    session: {
      _content: "13515",
      id: "13515"
     }
   }
 },
_jsns: "urn:zimbraSoap"
SearchResponse - 18:45:06.758
Code:
Body: {
  SearchResponse: {
    _jsns: "urn:zimbraMail",
    more: false,
    offset: 0,
    sortBy: "none"
   }
 },
Header: {
  context: {
    _jsns: "urn:zimbra",
    change: {
      token: 322
     },
    session: {
      _content: "13515",
      id: "13515"
     }
   }
 },
_jsns: "urn:zimbraSoap"
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.