Page 1 of 2

Sync not working

Posted: Thu Aug 02, 2007 3:28 pm
by Service
Anyone seen this error before, I just installed the .51 desktop client and setup. It gets error below when trying to sync for first time.
thanks
2007-08-02 15:24:21,581 ERROR [Timer-Offline-Main] [] offline - unexpected exception during sync for account user@mydomain.com

java.lang.StringIndexOutOfBoundsException: String index out of range: -1

at java.lang.String.substring(Unknown Source)

at com.zimbra.cs.account.offline.OfflineAccount$Version.(OfflineAccount.java:58)

at com.zimbra.cs.account.offline.OfflineAccount.getRemoteServerVersion(OfflineAccount.java:85)

at com.zimbra.cs.mailbox.OfflineMailbox.getRemoteServerVersion(OfflineMailbox.java:756)

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

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

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

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

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

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

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

at com.zimbra.cs.mailbox.OfflineMailboxManager$SyncTask.sync(OfflineMailboxManager.java:128)

at com.zimbra.cs.mailbox.OfflineMailboxManager$SyncTask.run(OfflineMailboxManager.java:98)

at java.util.TimerThread.mainLoop(Unknown Source)

at java.util.TimerThread.run(Unknown Source)

Sync not working

Posted: Thu Aug 02, 2007 3:29 pm
by Service
Also, found this error in the zdesktop.err file:
Zimbra server process is not running as root

Sync not working

Posted: Thu Aug 02, 2007 3:52 pm
by jjzhuang
The StringIndexOutOfBoundsException is very interesting. What version of ZCS server are you running? This failed in parsing version string.
The "not running as root" message is benign. We just need to avoid printing that. Thanks!

Sync not working

Posted: Thu Aug 02, 2007 3:58 pm
by Service
4.5.4 OS on Fedora Core 5

Sync not working

Posted: Thu Aug 02, 2007 3:59 pm
by jjzhuang
I actually need the exact output of "zmcontrol -v" if you have it. Thanks!

Sync not working

Posted: Thu Aug 02, 2007 4:00 pm
by jjzhuang
BTW the bug is filed:
Bug 19076 - Version parsing should be more robust

Sync not working

Posted: Thu Aug 02, 2007 4:01 pm
by Service
Release 4.5.4_GA_763.FC5_20070323134056 FC5 FOSS edition

Sync not working

Posted: Fri Aug 03, 2007 10:10 am
by maron
Hi.
Is there a workaround for this error, as I really miss the Zimbra Desktop functionality.

Sync not working

Posted: Tue Aug 07, 2007 3:56 am
by maron
Hi.
This is still an issue in 0.53 of the Desktop client:
java.lang.StringIndexOutOfBoundsException: String index out of range: -1

at java.lang.String.substring(String.java:1768)

at com.zimbra.cs.account.offline.OfflineAccount$Version.(OfflineAccount.java:58)

at com.zimbra.cs.account.offline.OfflineAccount.getRemoteServerVersion(OfflineAccount.java:85)

at com.zimbra.cs.mailbox.OfflineMailbox.getRemoteServerVersion(OfflineMailbox.java:756)

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

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

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

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

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

at com.zimbra.cs.mailbox.InitialSync.sync(InitialSync.java:155)

at com.zimbra.cs.mailbox.InitialSync.sync(InitialSync.java:142)

at com.zimbra.cs.mailbox.OfflineMailboxManager$SyncTask.sync(OfflineMailboxManager.java:126)

at com.zimbra.cs.mailbox.OfflineMailboxManager$SyncTask.run(OfflineMailboxManager.java:98)

at java.util.TimerThread.mainLoop(Timer.java:512)

at java.util.TimerThread.run(Timer.java:462)
Are there any known workarounds?

Sync not working

Posted: Tue Aug 07, 2007 6:13 am
by jjzhuang
Right, the fix missed the 0.53 cut so it will be in a future release. Unfortunately there's no workaround.