Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Desktop > Error Reports

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-27-2010, 07:54 AM
Intermediate Member
 
Posts: 17
Default Zimbra Desktop 1.04 Tags are not synced

Hi,

i have the problem with several Accounts.
When i do the first time sync of an account to Zimbra Desktop then all objects with tags are not synced. (error reporting is below)
Then i switch to the webclient, remove the tag from the email and set it back again, then it will be synced. I can also set a new, 2nd tag, then the email and both tags are synced.
Only when i resync/sync the first time, they didnt get synced.
Looks like ZD hasn't the tags before it got an email with tags.

We use Zimbra Enterprise Edition 6.0.7, and ZD 1.04 on Windows and Mac. On both clients the same error, with different accounts.

Note: the tag is originally in the client called "Wichtig" and not like in the Error-Type ":Wichtig" (with : at the beginning), didnt know if this is normal.


Product name: Zimbra Desktop
Product version: 1.0.4
Build ID: 1833
Release type: R
OS Platform: Mac OS X x86_64 10.6.3
Time of event: 2010-05-27 16:20:24
Error type: For input string: ":Wichtig"
Item ID: 26594
Error summary: message sync failed

----------------------------------------------------------------------------
Affected data - PLEASE REMOVE ANY SENSITIVE INFORMATION (size=3332):
----------------------------------------------------------------------------


removed


----------------------------------------------------------------------------
Failure details - PLEASE REMOVE ANY SENSITIVE INFORMATION
----------------------------------------------------------------------------

java.lang.NumberFormatException: For input string: ":Wichtig"
at java.lang.NumberFormatException.forInputString(Num berFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:449)
at java.lang.Integer.parseInt(Integer.java:499)
at com.zimbra.cs.mailbox.Tag.tagsToBitmask(Tag.java:8 2)
at com.zimbra.cs.mailbox.Mailbox.addMessageInternal(M ailbox.java:4826)
at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.j ava:4728)
at com.zimbra.cs.mailbox.InitialSync.saveMessage(Init ialSync.java:1182)
at com.zimbra.cs.mailbox.InitialSync.syncMessagesAsTg z(InitialSync.java:992)
at com.zimbra.cs.mailbox.InitialSync.syncMessages(Ini tialSync.java:950)
at com.zimbra.cs.mailbox.InitialSync.syncMessagelikeI tems(InitialSync.java:431)
at com.zimbra.cs.mailbox.InitialSync.initialFolderSyn c(InitialSync.java:321)
at com.zimbra.cs.mailbox.InitialSync.initialFolderSyn c(InitialSync.java:385)
at com.zimbra.cs.mailbox.InitialSync.initialFolderSyn c(InitialSync.java:385)
at com.zimbra.cs.mailbox.InitialSync.sync(InitialSync .java:172)
at com.zimbra.cs.mailbox.InitialSync.sync(InitialSync .java:155)
at com.zimbra.cs.mailbox.MailboxSync.sync(MailboxSync .java:184)
at com.zimbra.cs.mailbox.OfflineMailbox.sync(OfflineM ailbox.java:140)
at com.zimbra.cs.service.offline.OfflineSync.handle(O fflineSync.java:47)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:429)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:286)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:160)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:275)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:187)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:362)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:716)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:406)
at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:211)
at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.handler.RewriteHandler.handle(Re writeHandler.java:176)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:313)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:506)
at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:844)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:644)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:211)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:381)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:396)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:442)

----------------------------------------------------------------------------

Can you help me?

Thanks in advance,

Martin
Reply With Quote
  #2 (permalink)  
Old 06-02-2010, 11:16 PM
Zimbra Employee
 
Posts: 70
Default

I guess you might be using ZCS 6.0.6 because 6.0.7 has not been released yet (it will soon be).

You have encountered bug 47162 which has been fixed for 6.0.7.
Reply With Quote
  #3 (permalink)  
Old 06-04-2010, 07:27 AM
Intermediate Member
 
Posts: 17
Default

Hi,


whoops sorry, we have 6.0.6...

Ok, thanks for the answer then we will wait for the 6.0.7 :-)

regards,

Martin
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.