Unsupported Character errors?

[Vladimir]

One of my users is reporting syncing issues with his Treo. From his side he sees a 0x85010014 error and in my logs I see lots of :

2007-08-29 04:07:31,803 WARN  [http-443-Processor87] [name=*****;mid=21;item=12345;DeviceId=AEC0F8EB3E9B700725BB868BA3EBE0D6;DeviceTyp
e=PocketPC;class=Email;folder=2;SyncCmd=Sync;] sync - Unsupported character: 0x2019

Any ideas?

[jjzhuang]

Yup, there's already a bug filed for this. Thanks!

[Vladimir]

Could you please point me to it? A simple search didnt find anything

[Vladimir]

Further strangeness. The orginal user removed the last message his Treo received and syncing worked fine after that. As an experiment I asked him to forward that message to a different user (using a Blackjack this time). The message was forwarded as an attachemnt. Trying to open the attachement the message disapeared from his Blackjack and was placed in his trash folder. The logs show

2007-08-29 15:15:45,133 WARN  [http-80-Processor96] [name=*****@zt2.rutgers.edu;mid=10;DeviceId=0430ED32ABBA17C62751D09B1D8AE038;Devi
ceType=SmartPhone;class=Tasks;SyncCmd=Sync;] sync - 
000000:  03 01 6A 00 45 5C 4F 50 03 54 61 73 6B 73 00 01  4B 03 7B 37 33 31 39 35 46 31 35 2D 45 42 46 34 
000020:  2D 33 32 30 39 2D 42 44 33 43 2D 45 41 41 37 44  30 39 38 46 41 45 41 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 30 00 01 01 56 47 4C 03 33 
000060:  32 32 31 32 32 35 34 37 34 00 01 5D*00 09 05 4A  03 30 00 01 4E 03 31 00 01 5D 03 30 00 01 60 03 
000080:  50 69 74 20 32 20 64 65 73 69 67 6E 00 01 01 01  01 01 01 01 
2007-08-29 15:15:45,133 WARN  [http-80-Processor96] [name=******@zt2.rutgers.edu;mid=10;DeviceId=0430ED32ABBA17C62751D09B1D8AE038;Devi
ceType=SmartPhone;class=Tasks;SyncCmd=Sync;] sync - Bad ZimbraSync Protocol
com.zimbra.zimbrasync.BinaryCodecException: expected: END_TAG {AirSync}ApplicationData
        at com.zimbra.zimbrasync.wbxml.BinaryParser.require(BinaryParser.java:126)
        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:389)
        at com.zimbra.zimbrasync.ZimbraSyncServlet.processPostRequest(ZimbraSyncServlet.java:335)
        at com.zimbra.zimbrasync.ZimbraSyncServlet.doPost(ZimbraSyncServlet.java:229)
        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)

[phoenix]

Does this sound like it?

[Vladimir]

Unless my brain isn't reading that bug right, no. As far as I can tell that bug refers to calendar entries and this was with mail.

[Vladimir]

Also clearly the second error message was unrelated because he was attempting to sync tasks. I had him turn that off. The orginal problem however is still valid.

[jjzhuang]

The bug I was referring to is: Bug 15680 - mobile sync of international character sets

As to your second issue, what's the server version? I remember this was fixed at some point.

[Vladimir]

Server version 4.5.6, and as far as I can tell there where no foreign characters in the message in question.

[jjzhuang]

OK the second exception is simple. The user is trying to upload a "Task". Task sync is not yet supported, so please advise the user to disable Task sync in device settings.

As for the unsupported character, there is definitely something there. However this kind of warning doesn't really affect sync. The message will still be downloaded, but some characters may be replaced by a question mark.