Failure communicating with remote server. Please try again later.

[mikeijze]

my Zimbra email-account (@mavenwire.com) ends up in a failure very frequently - the only solution then seems to be to do a complete reset of my email which is incredibly annoying.

Error message:

Failure communicating with remote server. Please try again later. (debug info)

Debug message: system failure: Unable to get calendar item notes MIME part

Exception:

com.zimbra.common.service.ServiceException: system failure: InitialSync.syncCalendarItem
ExceptionId:mid=9:1234173956287:570b81c55d29131f
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:253)
at com.zimbra.cs.mailbox.SyncExceptionHandler.checkRe coverableException(SyncExceptionHandler.java:40)
at com.zimbra.cs.mailbox.InitialSync.syncCalendarItem (InitialSync.java:681)
at com.zimbra.cs.mailbox.DeltaSync.deltaSync(DeltaSyn c.java:237)
at com.zimbra.cs.mailbox.DeltaSync.sync(DeltaSync.jav a:92)
at com.zimbra.cs.mailbox.DeltaSync.sync(DeltaSync.jav a:76)
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.mailbox.OfflineMailbox.syncOnTimer(O fflineMailbox.java:121)
at com.zimbra.cs.mailbox.DesktopMailbox$1.run(Desktop Mailbox.java:436)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
Caused by: com.zimbra.common.soap.SoapFaultException: system failure: Unable to get calendar item notes MIME part
ExceptionId:btpool0-0:1234173956265:82a51fe4fb376fa4
Code:service.FAILURE
at com.zimbra.common.soap.Soap12Protocol.soapFault(So ap12Protocol.java:88)
at com.zimbra.common.soap.SoapTransport.extractBodyEl ement(SoapTransport.java:263)
at com.zimbra.common.soap.SoapTransport.parseSoapResp onse(SoapTransport.java:224)
at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:262)
at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:217)
at com.zimbra.common.soap.SoapTransport.invoke(SoapTr ansport.java:315)
at com.zimbra.common.soap.SoapTransport.invokeWithout Session(SoapTransport.java:302)
at com.zimbra.cs.mailbox.OfflineMailbox.sendRequest(O fflineMailbox.java:776)
at com.zimbra.cs.mailbox.OfflineMailbox.sendRequest(O fflineMailbox.java:740)
at com.zimbra.cs.mailbox.OfflineMailbox.sendRequest(O fflineMailbox.java:736)
at com.zimbra.cs.mailbox.OfflineMailbox.sendRequest(O fflineMailbox.java:732)
at com.zimbra.cs.mailbox.OfflineMailbox.sendRequest(O fflineMailbox.java:728)
at com.zimbra.cs.mailbox.InitialSync.syncCalendarItem (InitialSync.java:655)
... 9 more

[jjzhuang]

could you please enable trace and try again? follow these steps: Yahoo! Zimbra Desktop FAQ - Zimbra :: Wiki

[mikeijze]

log attached

[jjzhuang]

the log is cut off at the beginning. please include from the start of the sync trace, which is indicated by this line:

============================== SYNC DEBUG TRACE START ==============================

[mikeijze]

the logfile

[jjzhuang]

OK, looks like a bug. Could you please file a bug and attach the log you just attached here?

This seems to be a ZCS server side issue. Do you have access to the server log somehow? Ideally we'd like to see the exception in the server log, which will have more information.

In any case, please open a bug first. Thanks!

[fc1]

I added a Yahoo account and started synchronising.

It synchronised the folder list first, then part of the inbox and stopped, indicating "failure communicating with remote server. please try later". Running the mouse cursor over the Inbox, it showed 75 items, but only 63 came over to desktop. All other folders were empty.

I have also tried resetting the account, deleting and re-adding the account, but the results are always the same. Looking at the Yahoo settings, I see that I do not have Mail-Plus and POP/IMAP/forwarding are not allowed. Is this the cause?

I have attached a trace (cut and paste of the syn log).

Would be grateful for any help and suggestion. Thanks.

[jjzhuang]

fc1, could you please file a bug with the trace you provided here. thanks!