Palm hotsync with outlook and zimbra

[Klug]

/me hides.
I did not see Sam's post.

Looks like it's opening case time.
8)

Merci !

[stwendl]

I don't blame zimbra that they can not verify all possible other outlook additions. Some of them may have been written against some older version, relying on some "intrinsicacies" of outlook, or, just depend on what updates you have loaded and in what sequence. Maybe some software additions to the OS alter the bahaviour. Without going into debugging hotsync or BB desktop it is hard to say. I have seen verious different behaviours and have little patience debugging it. I found one solution, for the palm notes/tasks, chapura pocket mirror, that solved this users situation. Any amount of time I spend to figure out what goes on, costs me more time/money than this little additional SW cost.

From what I read here (and the tests we made) it seems there are lots of issues with "any" device trying to sync through Outlook.

We have issues with Blackberry Desktop, with Nokia PC Suite (with a Communicator 9300 that syncs "sometimes", mostly crashes Outlook or PC Suite), with the Sony Ericson tool (with P990i, same story than PC Suite) but no issue (yet) with Windows 2003 PDA (with ActiveSync)...

Obviously the 9300 (with Dataviz' RoadSync) or the P990i syncs perfectly OTA.
But all customers do not want to buy additional software (Roadsync) or worse, change their PDA/Phone...

The answer from the support to Jason (in the linked thread) was "we do not test the ZCO with other connector".
Should we understand we won't get any support on all these setups ?

[sam]

stwendl nailed it. We cannot certify all 3rd party MAPI clients. We are collecting your input via Zimbra support and bugzilla and will test/certify 3rd party clients as you express interest for them.

[kdunphy]

I had a similar issue with HotSync crashing and I think the solution is to remove any function not used by Zimbra in the HotSync manager such as tasks and notes.

Keith

[susi2781]

I only skimmed through these responses since I am looking for a solution to a different problem, BUT... I had these errors mentioned earlier come up for one of my users on Friday. It turned out to be a bad entry in the calendar. I made a backup calendar and moved all of her entries to that - completely emptying the main cal. Then i moved entries back about 10 at a time - synching after each move. I knew all was well until i got the error again. So i found the last 10 that i moved and moved those one at a time - synching after each. then i just deleted the bad entry, entered it as a new entry, resynched and voila. it worked. no more errors.

[sam]

If you get us a copy of that bad data, we can implement a fix. Contact support@zimbra.com.