Results 1 to 10 of 10

Thread: Opening webmail in 6.06 script error message

  1. #1
    mrcoffee11 is offline Senior Member
    Join Date
    Oct 2007
    Posts
    57
    Rep Power
    7

    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.

  2. #2
    uxbod's Avatar
    uxbod is offline Moderator
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    24

    Default

    Is this happening across a WiFi connection ?

  3. #3
    mrcoffee11 is offline Senior Member
    Join Date
    Oct 2007
    Posts
    57
    Rep Power
    7

    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

  4. #4
    uxbod's Avatar
    uxbod is offline Moderator
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    24

    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.

  5. #5
    mrcoffee11 is offline Senior Member
    Join Date
    Oct 2007
    Posts
    57
    Rep Power
    7

    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

  6. #6
    uxbod's Avatar
    uxbod is offline Moderator
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    24

    Default

    Did it throw the timeout error again ? Have you tried clearing your browser cache ?

  7. #7
    mrcoffee11 is offline Senior Member
    Join Date
    Oct 2007
    Posts
    57
    Rep Power
    7

    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.

  8. #8
    toolhead is offline Starter Member
    Join Date
    Feb 2011
    Posts
    2
    Rep Power
    4

    Default

    I'm having the same problem, are this problem still unsolved?

  9. #9
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,566
    Rep Power
    57

    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


    Acompli: A new adventure for Co-Founder KevinH.

  10. #10
    toolhead is offline Starter Member
    Join Date
    Feb 2011
    Posts
    2
    Rep Power
    4

    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"

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Replies: 3
    Last Post: 08-26-2009, 11:11 AM
  2. [SOLVED] Zimbra logwatch.
    By nishith in forum Administrators
    Replies: 5
    Last Post: 06-10-2009, 04:42 PM
  3. zimbra opesource Backup Script Problem!
    By tashi in forum Administrators
    Replies: 4
    Last Post: 03-30-2009, 11:49 PM
  4. Zimbra Open Source Backup Help
    By ayush1440 in forum Administrators
    Replies: 8
    Last Post: 11-13-2008, 04:56 AM
  5. Zimbra 5.0.X Auto Install Script on openSUSE 10.3
    By vavai in forum Installation
    Replies: 0
    Last Post: 05-19-2008, 01:45 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •