Bad ZimbraSync Protocol

Take your Zimbra with you!
Post Reply
Nutz
Advanced member
Advanced member
Posts: 135
Joined: Fri Sep 12, 2014 10:26 pm

Bad ZimbraSync Protocol

Post by Nutz »

So I don't know the model of the phone off the top of my head, but I know that it runs Windows mobile...
It seems to work ok, but I get a failed sync message on the phone/computer through active sync, and this shows up in the logs. We'd be ok except that it seems to want to sync everything every time... and sucks batteries dry pretty quickly...
2007-04-27 12:45:04,183 INFO [http-443-Processor90] [mid=19;name=user@domain;DeviceId=91F1690BB4252738EC6F10666BAD1A8B;DeviceType=SmartPhone;SyncCmd=Sync;class=Email;folder=2;] sync - HTTP/1.1 200 OK

2007-04-27 12:45:07,334 INFO [http-443-Processor90] [] sync - POST Microsoft-Server-ActiveSync?User=user@domain&DeviceId=91F1690BB4252738EC6F10666BAD1A8B&DeviceType=SmartPhone&Cmd=Sync

2007-04-27 12:45:07,465 WARN [http-443-Processor90] [mid=19;name=user@domain;DeviceId=91F1690BB4252738EC6F10666BAD1A8B;DeviceType=SmartPhone;SyncCmd=Sync;class=Tasks;] sync -

000000: 03 01 6A 00 45 5C 4F 50 03 54 61 73 6B 73 00 01 4B 03 7B 32 36 31 42 45 34 44 37 2D 32 43 46 46

000020: 2D 33 37 32 43 2D 38 35 46 44 2D 44 45 43 31 35 38 38 31 44 37 37 43 7D 31 00 01 52 03 31 35 00

000040: 01 1E 13 55 03 31 30 30 00 01 57 59 03 34 00 01 5A 03 34 00 01 5B 03 31 00 01 01 56 47 4C 03 33

000060: 32 32 31 32 32 35 34 38 31 00 01 5D*00 09 05 4A 03 30 00 01 4E 03 31 00 01 5D 03 30 00 01 60 03

000080: 31 20 73 65 72 76 69 6E 67 20 62 6F 77 6C 20 69 6E 20 42 6F 73 74 6F 6E 00 01 01 01 00 00 47 4C

0000a0: 03 33 32 32 31 32 32 35 34 37 37 00 01 5D 00 09 05 4A 03 30 00 01 4E 03 31 00 01 5D 03 30 00 01

0000c0: 60 03 31 20 73 65 72 76 69 6E 67 20 70 6C 61 74 74 65 72 20 69 6E 20 42 6F 73 74 6F 6E 00 01 01

0000e0: 01 00 00 47 4C 03 33 32 32 31 32 32 35 34 38 35 00 01 5D 00 09 05 4A 03 30 00 01 4E 03 31 00 01

000100: 5D 03 30 00 01 60 03 33 20 70 69 6E 65 20 62 6F 75 67 68 20 73 61 6C 61 64 20 70 6C 61 74 65 73

000120: 20 69 6E 20 54 65 6E 6E 65 73 73 65 65 20 00 01 01 01 00 00 47 4C 03 33 32 32 31 32 32 35 34 38

000140: 33 00 01 5D 00 09 05 4A 03 30 00 01 4E 03 31 00 01 5D 03 30 00 01 60 03 34 20 65 75 63 61 6C 79

000160: 70 74 75 73 20 70 6C 61 74 65 73 20 69 6E 20 54 65 6E 6E 65 73 73 65 65 20 00 01 01 01 00 00 47

000180: 4C 03 33 32 32 31 32 32 35 34 38 36 00 01 5D 00 09 05 4A 03 30 00 01 4E 03 31 00 01 5D 03 30 00

0001a0: 01 60 03 34 20 65 75 63 61 6C 79 70 74 75 73 20 73 61 6C 61 64 20 70 6C 61 74 65 73 20 69 6E 20

0001c0: 54 65 6E 6E 65 73 73 65 65 20 00 01 01 01 00 00 47 4C 03 33 32 32 31 32 32 35 34 38 34 00 01 5D

0001e0: 00 09 05 4A 03 30 00 01 4E 03 31 00 01 5D 03 30 00 01 60 03 34 20 70 69 6E 65 20 62 6F 75 67 68

000200: 20 70 6C 61 74 65 73 20 69 6E 20 54 65 6E 6E 65 73 73 65 65 20 00 01 01 01 00 00 47 4C 03 33 32

000220: 32 31 32 32 35 34 37 36 00 01 5D 00 09 05 4A 03 30 00 01 4E 03 31 00 01 5D 03 30 00 01 60 03 36

000240: 20 65 6E 67 6C 69 73 68 20 79 65 77 20 70 6C 61 74 65 73 20 69 6E 20 42 6F 73 74 6F 6E 00 01 01

000260: 01 00 00 47 4C 03 33 32 32 31 32 32 35 34 37 35 00 01 5D 00 09 05 4A 03 30 00 01 4E 03 31 00 01

000280: 5D 03 30 00 01 60 03 36 20 70 69 6E 65 20 62 6F 75 67 68 20 70 6C 61 74 65 73 20 69 6E 20 42 6F

0002a0: 73 74 6F 6E 00 01 01 01 00 00 47 4C 03 33 32 32 31 32 32 35 34 38 32 00 01 5D 00 09 05 4A 03 30

0002c0: 00 01 4E 03 31 00 01 5D 03 30 00 01 60 03 55 53 20 41 69 72 77 61 79 73 20 76 69 73 61 20 73 69

0002e0: 67 6E 61 74 75 72 65 20 63 61 72 64 20 3A 20 34 34 32 37 20 31 31 32 30 20 30 31 30 39 20 33 32

000300: 34 34 20 65 78 70 2E 20 35 2F 30 38 2C 20 73 65 63 20 63 6F 64 65 20 33 35 36 20 52 6F 62 69 6E

000320: 20 52 20 49 6E 67 6C 65 00 01 01 01 01 01 01 01

2007-04-27 12:45:07,466 WARN [http-443-Processor90] [mid=19;name=user@domain;DeviceId=91F1690BB4252738EC6F10666BAD1A8B;DeviceType=SmartPhone;SyncCmd=Sync;class=Tasks;] sync - Bad ZimbraSync Protocol

com.zimbra.zimbrasync.BinaryCodecException: expected: END_TAG {AirSync}ApplicationData

at com.zimbra.zimbrasync.wbxml.BinaryParser.require(BinaryParser.java:118)

at com.zimbra.zimbrasync.commands.CollectionSync.parseRequest(CollectionSync.java:663)

at com.zimbra.zimbrasync.commands.Sync.parseRequest(Sync.java:101)

at com.zimbra.zimbrasync.ZimbraSyncServlet.processCommand(ZimbraSyncServlet.java:387)

at com.zimbra.zimbrasync.ZimbraSyncServlet.processPostRequest(ZimbraSyncServlet.java:330)

at com.zimbra.zimbrasync.ZimbraSyncServlet.doPost(ZimbraSyncServlet.java:226)

at com.zimbra.zimbrasync.ZimbraSync$HttpHandler.doPost(ZimbraSync.java:35)

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:269)

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)

2007-04-27 12:45:07,466 INFO [http-443-Processor90] [mid=19;name=user@domain;DeviceId=91F1690BB4252738EC6F10666BAD1A8B;DeviceType=SmartPhone;SyncCmd=Sync;class=Tasks;] sync - HTTP/1.1 500 Bad ZimbraSync Protocol
jjzhuang
Elite member
Elite member
Posts: 1687
Joined: Fri Sep 12, 2014 10:24 pm

Bad ZimbraSync Protocol

Post by jjzhuang »

This is because you are trying to upload tasks which we don't yet support in 4.5 release. It will be in 5.0 release. For now please disable ActiveSync on Tasks.
Nutz
Advanced member
Advanced member
Posts: 135
Joined: Fri Sep 12, 2014 10:26 pm

Bad ZimbraSync Protocol

Post by Nutz »

Cheers!
As always, prompt, spot-on response from the Zimbra team.
I'll try it out, but thank you very much!
dlochart
Advanced member
Advanced member
Posts: 177
Joined: Fri Sep 12, 2014 10:20 pm

Bad ZimbraSync Protocol

Post by dlochart »

We are having issues with getting the global address list from the mobile. We see the following exception:
com.zimbra.zimbrasync.UnsupportedCommandException: Search
So I assume that this is another feature to be added in 5.0? Is there a list of the features that ARE supported at the 4.5 level?
thanks
Doug
jjzhuang
Elite member
Elite member
Posts: 1687
Joined: Fri Sep 12, 2014 10:24 pm

Bad ZimbraSync Protocol

Post by jjzhuang »

Which device and which software client are you using? There are few clients in the market that supports sever side search. If devices are adding search capabilities we'll prioritize that. Thanks!
dlochart
Advanced member
Advanced member
Posts: 177
Joined: Fri Sep 12, 2014 10:20 pm

Bad ZimbraSync Protocol

Post by dlochart »

[quote user="jjzhuang"]Which device and which software client are you using? There are few clients in the market that supports sever side search. If devices are adding search capabilities we'll prioritize that. Thanks![/QUOTE]
The phones are Treo700w. I did not set them up but I assume it is using the proper mobile connector. We did get mail to sync properly and we can see contacts but so search on the GAL. Since this company is split between 2 hemispheres access to the GAL is critical.
jjzhuang
Elite member
Elite member
Posts: 1687
Joined: Fri Sep 12, 2014 10:24 pm

Bad ZimbraSync Protocol

Post by jjzhuang »

It's not yet on our list but I just filed a ticket to track this feature:

Thanks">http://bugzilla.zimbra.com/show_bug.cgi?id=16532
Thanks!
dlochart
Advanced member
Advanced member
Posts: 177
Joined: Fri Sep 12, 2014 10:20 pm

Bad ZimbraSync Protocol

Post by dlochart »

Thank you!
Doug
pbradberry
Posts: 5
Joined: Fri Sep 12, 2014 10:22 pm

Bad ZimbraSync Protocol

Post by pbradberry »

In this thread you stated that the Treo700w

"It's not yet on our list but I just filed a ticket to track this feature"

Are you saying that there are phones and software that do support this feature? If so can you point me to the list.

Regards
jjzhuang
Elite member
Elite member
Posts: 1687
Joined: Fri Sep 12, 2014 10:24 pm

Bad ZimbraSync Protocol

Post by jjzhuang »

No. What I'm saying is most phones don't even have this feature in the client software. That's why I was asking which phone.
Post Reply