Results 1 to 8 of 8

Thread: Nokia Activesync not working.

  1. #1
    Splat is offline Senior Member
    Join Date
    Nov 2005
    Posts
    51
    Rep Power
    9

    Default Nokia Activesync not working.

    Im running 3.1.4 GA. Im using a nokia E70 w/ activesync. Getting the following in my sync.log

    2006-07-06 23:10:01,346 WARN [http-443-Processor98] [mid=4;name=user@mydomain.com;DeviceId=IMEI35234200 039743;DeviceType=NokiaE70;SyncCmd=FolderSync;] sync - Bad ZimbraSync Protocol
    com.zimbra.zimbrasync.BinaryCodecException: java.io.IOException: Unexpected EOF
    at com.zimbra.zimbrasync.wbxml.BinaryParser.startDocu ment(BinaryParser.java:169)
    at com.zimbra.zimbrasync.wbxml.BinaryParser.<init>(Bi naryParser.java:153)
    at com.zimbra.zimbrasync.ZimbraSyncServlet.processCom mand(ZimbraSyncServlet.java:262)
    at com.zimbra.zimbrasync.ZimbraSyncServlet.doPost(Zim braSyncServlet.java:212)
    at com.zimbra.zimbrasync.ZimbraSync$HttpHandler.doPos t(ZimbraSync.java:25)
    at com.zimbra.cs.extension.ExtensionDispatcherServlet .service(ExtensionDispatcherServlet.java:106)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:802)
    at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:252)
    at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173)
    at org.apache.catalina.core.ApplicationDispatcher.inv oke(ApplicationDispatcher.java:672)
    at org.apache.catalina.core.ApplicationDispatcher.pro cessRequest(ApplicationDispatcher.java:463)
    at org.apache.catalina.core.ApplicationDispatcher.doF orward(ApplicationDispatcher.java:398)
    at org.apache.catalina.core.ApplicationDispatcher.for ward(ApplicationDispatcher.java:301)
    at com.zimbra.webClient.filters.SetHeaderFilter.doFil ter(SetHeaderFilter.java:243)
    at org.apache.catalina.core.ApplicationFilterChain.in ternalDoFilter(ApplicationFilterChain.java:202)
    at org.apache.catalina.core.ApplicationFilterChain.do Filter(ApplicationFilterChain.java:173)
    at org.apache.catalina.core.StandardWrapperValve.invo ke(StandardWrapperValve.java:213)
    at org.apache.catalina.core.StandardContextValve.invo ke(StandardContextValve.java:178)
    at org.apache.catalina.core.StandardHostValve.invoke( StandardHostValve.java:126)
    at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105)
    at org.apache.catalina.core.StandardEngineValve.invok e(StandardEngineValve.java:107)
    at org.apache.catalina.valves.AccessLogValve.invoke(A ccessLogValve.java:541)
    at org.apache.catalina.connector.CoyoteAdapter.servic e(CoyoteAdapter.java:148)
    at org.apache.coyote.http11.Http11Processor.process(H ttp11Processor.java:869)
    at org.apache.coyote.http11.Http11BaseProtocol$Http11 ConnectionHandler.processConnection(Http11BaseProt ocol.java:667)
    at org.apache.tomcat.util.net.PoolTcpEndpoint.process Socket(PoolTcpEndpoint.java:527)
    at org.apache.tomcat.util.net.LeaderFollowerWorkerThr ead.runIt(LeaderFollowerWorkerThread.java:80)
    at org.apache.tomcat.util.threads.ThreadPool$ControlR unnable.run(ThreadPool.java:684)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: java.io.IOException: Unexpected EOF
    at com.zimbra.zimbrasync.wbxml.BinaryParser.readByte( BinaryParser.java:214)
    at com.zimbra.zimbrasync.wbxml.BinaryParser.startDocu ment(BinaryParser.java:164)
    ... 28 more

  2. #2
    jholder's Avatar
    jholder is offline Former Zimbran
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    20

    Default

    Code:
      Caused by: java.io.IOException: Unexpected EOF
    Looks like that's the problem.

    What version activesync?
    Did you try a reinstall of the active sync software?

  3. #3
    Splat is offline Senior Member
    Join Date
    Nov 2005
    Posts
    51
    Rep Power
    9

    Default

    Its the Latest version for the Nokia E series phones.

    Mail For Exchange 1.2.13 (.SIS, 1 MB)

  4. #4
    schemers is offline Zimbra Employee
    Join Date
    Aug 2005
    Posts
    228
    Rep Power
    10

    Default

    This has been fixed in ZCS 3.2. We have a few E61s in house that are working pretty good (calendar/contacts/email). I have mine set up to sync every 15 minutes and it has been working quite well.
    Bugzilla - Wiki - Downloads - Before posting... Search!

  5. #5
    Risotto is offline Intermediate Member
    Join Date
    Apr 2006
    Posts
    18
    Rep Power
    9

    Default More problems

    Hi everyone,

    I also get some errors when trying to sync with my E61. Is this also corrected in 3.2? Will the bugfix be released for the current 3.1.x versions? We currently can't switch to a beta server...

    Code:
    2006-07-27 00:05:54,406 WARN  [http-443-Processor97] [mid=2;name=an@onymous.net;DeviceId=IMEI356211000123243;DeviceType=NokiaE61;SyncCmd=Sync;] sync - 
    000000:  03 01 6A 00 45 5C 4F 50 03 43 6F 6E 74 61 63 74  73 00 01 4B 03 30 00 01 52 03 66 64 65 66 64 62 
    000020:  64 37 65 66 32 36 33 34 62 61 62 37 34 65 66 32  62 37 38 35 36 37 33 37 38 65 2D 37 00 01 60 00 
    000040:  01 1E*29 1F 27 20 13 0C 2B 12 32 1B 1C 1D 37 28  19 09 0D 0E 0F 10 11 26 21 22 23 24 25 2D 2E 2F 
    000060:  30 31 08 01 01 01 01 
    2006-07-27 00:05:54,406 WARN  [http-443-Processor97] [mid=2;name=an@onymous.net;DeviceId=IMEI356211000123243;DeviceType=NokiaE61;SyncCmd=Sync;] sync - Bad ZimbraSync Protocol
    com.zimbra.zimbrasync.BinaryCodecException: END_TAG expected
            at com.zimbra.zimbrasync.wbxml.BinaryParser.nextText(BinaryParser.java:93)
            at com.zimbra.zimbrasync.wbxml.BinaryParser.skipUnknownElement(BinaryParser.java:299)
            at com.zimbra.zimbrasync.commands.CollectionSync.parseRequest(CollectionSync.java:482)
            at com.zimbra.zimbrasync.commands.Sync.parseRequest(Sync.java:84)
            at com.zimbra.zimbrasync.ZimbraSyncServlet.processCommand(ZimbraSyncServlet.java:264)
            at com.zimbra.zimbrasync.ZimbraSyncServlet.doPost(ZimbraSyncServlet.java:212)
            at com.zimbra.zimbrasync.ZimbraSync$HttpHandler.doPost(ZimbraSync.java:25)
            at com.zimbra.cs.extension.ExtensionDispatcherServlet.service(ExtensionDispatcherServlet.java:106)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
            at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
            at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
            at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
            at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:463)
            at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398)
            at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
            at com.zimbra.webClient.filters.SetHeaderFilter.doFilter(SetHeaderFilter.java:243)
            at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
            at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
            at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
            at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
            at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
            at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
            at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
            at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:541)
            at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
            at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
            at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667)
            at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
            at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
            at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
            at java.lang.Thread.run(Thread.java:595)
    2006-07-27 00:08:40,765 DEBUG [http-443-Processor97] [mid=2;name=an@onymous.net;DeviceId=IMEI356211000123243;DeviceType=NokiaE61;SyncCmd=FolderSync;] sync -
    I also don't seem to be able to send mail:

    Code:
    2006-07-27 00:10:18,077 WARN  [http-443-Processor96] [mid=2;name=an@onymous.net;DeviceId=IMEI356211000123243;DeviceType=NokiaE61;SyncCmd=SendMail;] sync - SendMail not supported
    Last edited by Risotto; 07-26-2006 at 04:30 PM.

  6. #6
    KevinH's Avatar
    KevinH is offline Expert Member
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    19

    Default

    As Roland's post pointed out you must have 3.2 for the E61 support. You also should make sure your using the latest client from Nokia's website. We don't plan to fix this in a 3.1 build but the GA for 3.2 should be out soon.
    Looking for new beta users -> Co-Founder of Acompli. Previously worked at Zimbra (and Yahoo! & VMware) since 2005.

  7. #7
    Risotto is offline Intermediate Member
    Join Date
    Apr 2006
    Posts
    18
    Rep Power
    9

    Default

    It's a pitty you won't fix this in 3.1. What are you referring to by saing "should be out soon"? Weeks, months, when it's done?
    Last edited by Risotto; 07-27-2006 at 06:55 PM.

  8. #8
    KevinH's Avatar
    KevinH is offline Expert Member
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    19

    Default

    Quote Originally Posted by Risotto
    It's a pitty you won't fix this in 3.1. What are you referring to by saing "should be out soon"? Weeks, months, when it's done?
    It's not a trivial bug fix to work around this and it's not critical enough to warrant a specific patch release. The plan for 3.2 GA has been and remains end of summer. I don't think an exact date has been set but your sales rep would be able to alert you to when it's available.
    Looking for new beta users -> Co-Founder of Acompli. Previously worked at Zimbra (and Yahoo! & VMware) since 2005.

Thread Information

Users Browsing this Thread

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

Posting Permissions

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