Failure communicating with remote server. Please try again later.

If Zimbra Desktop had a sync failure, it may have told you to post your error in this section.
Post Reply
dmenden
Posts: 7
Joined: Sat Sep 13, 2014 12:27 am

Failure communicating with remote server. Please try again later.

Post by dmenden »

From an install of zdesktop_2_0_b10580_win32.msi, I was able to add a Zimbra account connecting to zcs-NETWORK-6.0.6_GA (patched) without any problem. When I added another Zimbra account connecting to zcs-6.0.7_GA_2470 (open source), it downloaded all of the mail and calendar events, but now it can't sync new messages. The error message follows:
Debug message: Java heap space
Exception:
java.lang.OutOfMemoryError: Java heap space

at java.util.Arrays.copyOfRange(Unknown Source)

at java.lang.String.(Unknown Source)

at java.lang.StringBuilder.toString(Unknown Source)

at net.fortuna.ical4j.data.CalendarParserImpl.parseProperty(CalendarParserImpl.java:263)

at net.fortuna.ical4j.data.CalendarParserImpl.parsePropertyList(CalendarParserImpl.java:196)

at net.fortuna.ical4j.data.CalendarParserImpl.parseComponent(CalendarParserImpl.java:355)

at net.fortuna.ical4j.data.CalendarParserImpl.parsePropertyList(CalendarParserImpl.java:193)

at net.fortuna.ical4j.data.CalendarParserImpl.parseCalendar(CalendarParserImpl.java:161)

at net.fortuna.ical4j.data.CalendarParserImpl.parseCalendarList(CalendarParserImpl.java:133)

at net.fortuna.ical4j.data.CalendarParserImpl.parse(CalendarParserImpl.java:94)

at com.zimbra.cs.mailbox.calendar.ZCalendar$ZCalendarBuilder.parse(ZCalendar.java:920)

at com.zimbra.cs.mailbox.calendar.ZCalendar$ZCalendarBuilder.buildMulti(ZCalendar.java:894)

at com.zimbra.cs.mailbox.calendar.ZCalendar$ZCalendarBuilder.build(ZCalendar.java:878)

at com.zimbra.cs.mime.handler.TextCalendarHandler.analyze(TextCalendarHandler.java:77)

at com.zimbra.cs.mime.handler.TextCalendarHandler.getICalendar(TextCalendarHandler.java:52)

at com.zimbra.cs.mime.ParsedMessage.analyzePart(ParsedMessage.java:1101)

at com.zimbra.cs.mime.ParsedMessage.analyzeNonBodyParts(ParsedMessage.java:433)

at com.zimbra.cs.mime.ParsedMessage.analyzeFully(ParsedMessage.java:467)

at com.zimbra.cs.mailbox.CalendarItem.getIndexDocuments(CalendarItem.java:342)

at com.zimbra.cs.mailbox.CalendarItem.generateIndexData(CalendarItem.java:218)

at com.zimbra.cs.mailbox.IndexHelper.indexItemList(IndexHelper.java:848)

at com.zimbra.cs.mailbox.IndexHelper.indexDeferredItemsInternal(IndexHelper.java:367)

at com.zimbra.cs.mailbox.IndexHelper.indexDeferredItems(IndexHelper.java:284)

at com.zimbra.cs.mailbox.IndexHelper.maybeIndexDeferredItems(IndexHelper.java:240)

at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.java:4341)

at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.java:4334)

at com.zimbra.cs.mailbox.InitialSync.saveMessage(InitialSync.java:1207)

at com.zimbra.cs.mailbox.InitialSync.syncMessagesAsTgz(InitialSync.java:1027)

at com.zimbra.cs.mailbox.InitialSync.syncMessages(InitialSync.java:960)

at com.zimbra.cs.mailbox.InitialSync.syncMessagelikeItems(InitialSync.java:433)

at com.zimbra.cs.mailbox.InitialSync.initialFolderSync(InitialSync.java:323)

at com.zimbra.cs.mailbox.InitialSync.prioritySync(InitialSync.java:397)

phoenix
Ambassador
Ambassador
Posts: 27272
Joined: Fri Sep 12, 2014 9:56 pm
Location: Liverpool, England

Failure communicating with remote server. Please try again later.

Post by phoenix »

WHat operating system is this installed on and how much RAM is on the machine?
Regards

Bill

Rspamd: A high performance spamassassin replacement

Per ardua ad astra
dmenden
Posts: 7
Joined: Sat Sep 13, 2014 12:27 am

Failure communicating with remote server. Please try again later.

Post by dmenden »

The client machine is Windows XP SP3 with 3G of RAM.
kirme3
Advanced member
Advanced member
Posts: 179
Joined: Fri Sep 12, 2014 10:09 pm

Failure communicating with remote server. Please try again later.

Post by kirme3 »

I'm getting the same error on Windows 7 64-bit.
17416jflanigan
Zimbra Alumni
Zimbra Alumni
Posts: 113
Joined: Sat Sep 13, 2014 1:20 am

Failure communicating with remote server. Please try again later.

Post by 17416jflanigan »

At first glance it looks like you have an appointment request in your mailbox which is rather large; too large for our default heap size settings so we are running out of heap when trying to parse it.
You can try increasing the maximum heap size in /conf/zdesktop.conf. You should find a line that looks like this:
java.arg.4=-Xmx120m
Change the value to -Xmx256m, save, and then restart ZD and try again. Since you are on Windows; when restarting be sure to select Quit from the system tray icon.
If that doesn't work, try 512 and so on. Please let us know what value works for you, or if this doesn't help.
can be found at:
Mac: ~/Library/Zimbra Desktop
Linux: ~/zdesktop
Windows XP: C:Documents and Settings\Local SettingsApplication Dataimbraimbra Desktop
Windows 7/Vista: C:Users\AppDataLocalimbraimbra Desktop
14241mphillips
Posts: 14
Joined: Sat Sep 13, 2014 12:40 am

Failure communicating with remote server. Please try again later.

Post by 14241mphillips »

I have the same issue as well. A e-mail with large attachments seems to be stuck. I get the following error:
Failure communicating with remote server. Please try again later.
Debug message: Java heap space
Exception:
java.lang.OutOfMemoryError: Java heap space

at java.util.Arrays.copyOf(Unknown Source)

at java.io.ByteArrayOutputStream.write(Unknown Source)

at com.sun.mail.util.ASCIIUtility.getBytes(ASCIIUtility.java:256)

at javax.mail.internet.MimeMessage.parse(MimeMessage.java:335)

at javax.mail.internet.MimeMessage.(MimeMessage.java:205)

at com.sun.mail.handlers.message_rfc822.getContent(message_rfc822.java:98)

at javax.activation.DataSourceDataContentHandler.getContent(Unknown Source)

at javax.activation.DataHandler.getContent(Unknown Source)

at javax.mail.internet.MimeBodyPart.getContent(MimeBodyPart.java:630)

at com.zimbra.cs.mime.Mime.getMessageContent(Mime.java:410)

at com.zimbra.cs.mime.MimeVisitor.accept(MimeVisitor.java:231)

at com.zimbra.cs.mime.MimeVisitor.accept(MimeVisitor.java:213)

at com.zimbra.cs.mime.MimeVisitor.accept(MimeVisitor.java:176)

at com.zimbra.cs.mime.ExpandMimeMessage.expand(ExpandMimeMessage.java:86)

at com.zimbra.cs.mime.ParsedMessage.init(ParsedMessage.java:286)

at com.zimbra.cs.mime.ParsedMessage.initialize(ParsedMessage.java:229)

at com.zimbra.cs.mime.ParsedMessage.initialize(ParsedMessage.java:193)

at com.zimbra.cs.mime.ParsedMessage.(ParsedMessage.java:140)

at com.zimbra.cs.mime.ParsedMessage.(ParsedMessage.java:135)

at com.zimbra.cs.mailbox.CalendarItem.storeUpdatedBlob(CalendarItem.java:2057)

at com.zimbra.cs.mailbox.CalendarItem.createBlob(CalendarItem.java:2122)

at com.zimbra.cs.mailbox.CalendarItem.create(CalendarItem.java:486)

at com.zimbra.cs.mailbox.Mailbox.createCalendarItem(Mailbox.java:5691)

at com.zimbra.cs.mailbox.Mailbox.setCalendarItem(Mailbox.java:3775)

at com.zimbra.cs.mailbox.InitialSync.setCalendarItem(InitialSync.java:846)

at com.zimbra.cs.mailbox.InitialSync.syncCalendarItem(InitialSync.java:652)

at com.zimbra.cs.mailbox.InitialSync.initialFolderSync(InitialSync.java:267)

at com.zimbra.cs.mailbox.InitialSync.prioritySync(InitialSync.java:397)

at com.zimbra.cs.mailbox.InitialSync.initialFolderSync(InitialSync.java:377)

at com.zimbra.cs.mailbox.InitialSync.initialFolderSync(InitialSync.java:387)

at com.zimbra.cs.mailbox.InitialSync.resume(InitialSync.java:198)

at com.zimbra.cs.mailbox.InitialSync.resume(InitialSync.java:182)
If issue persists please post description and debug information here.
I have changed the Xmx= 256, 512, 1024, 2048m and I still get the same message.
Zimbra Desktop 2, on Ubuntu 10.04 x64, 4gb ram

ZCS 6 on Centos.
Mark
17416jflanigan
Zimbra Alumni
Zimbra Alumni
Posts: 113
Joined: Sat Sep 13, 2014 1:20 am

Failure communicating with remote server. Please try again later.

Post by 17416jflanigan »

On Linux you'll need to change the Xmx in bin/zdesktop under your user data directory (typically /home//zdesktop).
You should find a MAILBOXD_JAVA_OPTIONS property around line 298.
To make sure you're actually affecting the runtime, you can do a ps -eaf | grep zimbra and note the XmX option displayed.
Post Reply