Zimbra connector for Outlook 2007 Pro

[Caprazi]

Hi

I am having a problem with the ZimbraConnectorOLK_7.1.0.6315_x86, when i install it on a machine running Outlook 2007 Pro. It keeps throwing errors when i try to send or receive mail,and it crashes my Outlook session. Please advise

[fsiegel]

If it crashed, there should be a .dmp file in %TEMP%\zco-cores. Post that file, and we can take a look.

[Bkallen5]

Hi

I am having a problem with the ZimbraConnectorOLK_7.1.0.6315_x86, when i install it on a machine running Outlook 2007 Pro. It keeps throwing errors when i try to send or receive mail,and it crashes my Outlook session. Please advise

We have just converted from Lotus Notes to Zimbra (thank whoever!), I am also using the Outlook connector with OL 7 pro. I am getting multiple "Local Failure Notice's" Error IDS id 2683 type appointment.
Also the content of my folders are not being transferred from Zimbra, maybe connected? I can send email from Outlook. Our own support folks don't have any ideas & I have blown it away & reinstalled several times, same problem.
(Win XP Pro SP3)

[fsiegel]

Please post a copy of one of your local failure notices. They also usually come with the request and response XML that is causing the problem.

Also, is it always the same Zimbra ID? 2683? If so, you can go into the web browser and find out which appointment 2683 is, then save it off and delete it. That could allow you to sync. To find that appointment, type this url in your web browser (substitute your server and port name for <your-server> and <yourport> respectively):

http://<your-server>:<your-port>/service/content/get?id=2683&fmt=sync

[Bkallen5]

Thanks for the info, It is always the same id number (2683) I tried using the link to find it with our server name & port address with no luck I kept getting 404 page error. Full Msg:

This e-mail was generated for technical support purposes.

Sync Type: Initial Sync

Sync Token (before request): 30340

Sync Token (most current): 30340

Store: Zimbra - Bruce Allen

Computer Name: US02DDURNIL

ZCO Version: 7.1.0.6315

Server Version: 7.1.0_GA_3140

Error IDs:
id (2683) type(appointment)

[fsiegel]

Not sure why you can't find that appointment using that link I gave you, but 2683 looks like an appointment called Dave's Staff that occurs every Friday from 1:30 to 2:30 in the afternoon.

Maybe you can get rid of that one and see if that solves your problem.

[Bkallen5]

Many thanks for the help, I deleted the entry for Dave's Staff Meeting & that stopped the error on 2683 OK, but now I am getting failures on different appointment number! 3209. Should I delete ALL my appointments in Zimbra desktop? I know it is affecting updating my folders.
Also I notice on the Zimbra Send/Receive dialog it shows 'Network connection failure ' after each failed sync.

I have attached a Snagit screen grab which I hope may help. I can send the XML files if you like.

Any help gratefully accepted!

Regards

Bruce

[fsiegel]

It's probably just certain recurring appointments that are causing the problems. If you look at the obj_response.xml file, it will tell you which appointment is failing (it's in .ics format). I would think it would list more than 1 at a time.

I guess you could save off each offending appointment.

A ZCO log file might help. I wonder if there is some exception occurring. Enable ZCO logging -- just logging and http logging -- not verbose. Then send the log. Try to keep the run run small -- just a delta sync if possible.

[r.bozzetti]

Hi all, I have a similar problem during syncronization with outlook 2003 and 2007

ZCO Version is 7.1.1.6324
Server Version is 7.1.1_GA_3196

This happens when connector ver. 7.1.1 is installed as fresh install.
Everything is fine when a previous connector (ver. 6.0.9 for instance) is installed and 7.1.1 comes as an upgrade

Regards,
Rudy

[fsiegel]

Looks like it's crashing adding syncing a distribution list down, adding a certain email address to it. If you have a corresponding ZCO log file, it should have this entry in it right before the crash:

AddDLMembers: <email> <email>

What is that email address? And are there similar log file statements throughout the log where things work successfully?

Perhaps this will help us track it down.

Not sure if there is memory corruption before or what, since the statement itself looks farily innocuous.