Outlook 2007 Initial Sync Results in Massive zdb

[jurness]

In order to disable the PDFM Add-in, you need to delete or unregesiter the DLL (or uninstall Acrobat)- you can't disable it from within Outlook.

Go here for all of the removal options

I deleted the DLL using following these steps:
To delete PDFMOutlook.dll, follow these steps:

1. Close Outlook and Adobe Acrobat
2. Open Windows Explorer, and navigate to
“C:\Program Files\Adobe\Acrobat 7.0\PDFMaker\Mail\Outlook”
If you own another version than Adobe Acrobat 7, your path will differ in this version number
3. Delete PDFMOutlook.dll if it exists

[jurness]

OK, I can't say for sure that the issue is resolved, but things are looking positive. The Outlook client is no longer hanging and my Sent folder appears to be full rather than having only the last few days.

[jurness]

Spoke too soon. The performance was pretty snappy there for a bit and appeared to be working as expected, but then it hung as I was clicking through email. It gave the message "not responding" and then restarted itself- again complaining about the zimbra add-in (see above image).

Obviously I can't disable that so what next?

Also, right after the crash I get this email, is it related?

*****************************

This e-mail was generated for technical support purposes.

Sync Type: Delta Sync

Sync Token (before request): 469862

Sync Token (most current): 469865

Store: Zimbra - John Urness

Computer Name: OAK-WS-WIN06

Version: 6.0.5736.2

Error IDs:
207065 : File download HTTP error. Error code: 500

202623 : File download HTTP error. Error code: 500

1209 : File download HTTP error. Error code: 500

1210 : File download HTTP error. Error code: 500

..[snip]...


12657 : File download HTTP error. Error code: 500

48945 : File download HTTP error. Error code: 500

60496 : File download HTTP error. Error code: 500

59287 : File download HTTP error. Error code: 500

[jurness]

OK, back to my original problem. Now that Outlook will actually run, it is filling up my hard drive which may explain why Outlook seems to be getting sluggish.

The zdb file is 17 GB and counting.

Additionally, the "local failure notice" emails that show up in Outlook are not showing up in my web client, so that means syncing may not be working correctly.

[fsiegel]

As far as the 500 errors, you might want to check mailbox.log to see why things aren't downloading. Maybe some bad server configuration? Maybe it's just in some loop and continually syncing.

So what I would suggest is to enable ZCO logging (just logging and http logging), and do a run. Your log file will get really huge, so you 'll want to put 0 for the size (in zcologctl.exe), or do the multiple .bak files stuff. In any case, I don't need to see all of the log, but if you could post the last few megs that could be enough for me to see what's going on.

But I think something is not configured correctly somewhere.

[jurness]

I uninstalled ZCO and the profile (since I assumed it was somehow corrupt) and reinstalled ZCO and restarted Outlook.
I enabled logging with "0" for size.
I am tailing the log on the client and the log is quickly growing while the ZDB file is now static at aroun 8.2MB

No email is syncing this time around at least not after 10-15 minutes. The log shows a lot of http errors, but is is still growing- 50MB and counting.

Here is a snipit:

06-11-2009 15:34:14.324 [4556]: *4510*
06-11-2009 15:34:14.324 [4556]: *4510* DEBUG: in Zimbra::Rpc::Connection::ReadResponseFully - Total bytes read from wire: 1438
06-11-2009 15:34:14.324 [4556]: *4510* <<<<-------- HTTP stream End (Response) ----------------------------------------------->>>>
06-11-2009 15:34:14.324 [4556]: *4510* Exit Zimbra::Rpc::Connection:oGet ...
06-11-2009 15:34:14.324 [4556]: Zimbra::Sync::SaxHandlers::SyncSAXHandler::WriteSo apToTempFile. No Req RPC -- local failure tempfile not written
06-11-2009 15:34:14.324 [4556]: Zimbra::Sync::SaxHandlers::SyncSAXHandler::WriteSo apToTempFile. No Rsp RPC -- local failure tempfile not written
06-11-2009 15:34:14.327 [4556]: Zimbra::Sync::SaxHandlers::SyncSAXHandler::WriteSo apToTempFile. trying write 1468 bytes into C:\Users\jurness\AppData\Local\Temp\Mim-20091106T153414.324-118302.txt
06-11-2009 15:34:14.342 [4556]: SyncSAXHandler:ownloadCreateMessage() - File download HTTP error 500 on id 118302
06-11-2009 15:34:14.342 [4556]: Zimbra::Sync::SaxHandlers::InitialSyncSAXHandler:: DownloadCreateMessage. the base function failed for mids
06-11-2009 15:34:14.342 [4556]: Zimbra::Sync::SaxHandlers::SyncSAXHandler::WriteSo apToTempFile. No Req RPC -- local failure tempfile not written
06-11-2009 15:34:14.343 [4556]: Zimbra::Sync::SaxHandlers::SyncSAXHandler::WriteSo apToTempFile. No Rsp RPC -- local failure tempfile not written
06-11-2009 15:34:14.345 [4556]: Zimbra::Sync::SaxHandlers::SyncSAXHandler::WriteSo apToTempFile. trying write 1468 bytes into C:\Users\jurness\AppData\Local\Temp\Mim-20091106T153414.343-118302.txt
06-11-2009 15:34:14.358 [4556]: ERROR: Zimbra::Sync::SaxHandlers::InitialSyncSAXHandler:: StartMessage - DownloadCreateMessage failed to init sync message id(118302)
06-11-2009 15:34:14.363 [4556]: *4511* Enter Zimbra::Rpc::Connection:oGet ...
06-11-2009 15:34:14.363 [4556]: *4511* <<<<-------- HTTP stream Start (Request) ----------------------------------------------->>>>
06-11-2009 15:34:14.370 [4556]: *4511* HTTP Headers:
06-11-2009 15:34:14.370 [4556]: GET /service/user/~/?fmt=sync&id=118301 HTTP/1.1
Cookie: ZM_AUTH_TOKEN=0_72b8f5d544fff8ae0fd6e3238b9ac81f7e 2ad644_69643d33363a34363764393830322d363435302d343 764382d616339362d3231343236393430636532623b6578703 d31333a313235373732323638383930363b747970653d363a7 a696d6272613b
User-Agent: Zimbra-ZCO/6.0.5736.2 (6.1.7600 ; en-US)
Cache-Control: no-cache
Pragma: no-cache
Connection: Keep-Alive
06-11-2009 15:34:14.370 [4556]: *4511* <<<<-------- HTTP stream End (Request) ----------------------------------------------->>>>
06-11-2009 15:34:14.370 [4556]: *4511* <<<<-------- HTTP stream Start (Response) ----------------------------------------------->>>>
06-11-2009 15:34:14.370 [4556]: *4511* DEBUG: in Zimbra::Rpc::Connection::ReadResponseFully - content-length in http response header: 1438
06-11-2009 15:34:14.370 [4556]: *4511* HTTP Headers:
06-11-2009 15:34:14.371 [4556]: HTTP/1.1 500 system failure: sync formatter failure
Cache-Control: must-revalidate,no-cache,no-store
Date: Fri, 06 Nov 2009 23:34:14 GMT
Content-Length: 1438
Content-Type: text/html; charset=iso-8859-1
06-11-2009 15:34:14.371 [4556]: *4511* HTTP body:
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
<title>Error 500 system failure: sync formatter failure</title>
</head>
<body><h2>HTTP ERROR 500</h2>
<p>Problem accessing /service/user/~/. Reason:
<pre> system failure: sync formatter failure</pre></p><hr /><i><small>Powered by Jetty://</small></i><br/>

I'll attach more, bit it looks like it is looping and won't finish until my hard drive fills up.

[jurness]

Well...

The zdb file is up to 140MB, so not much mail was downloaded, but I don't see any in Sent or Inbox and a spot check of other folders I didn't find more than a handful of mail.

The Outlook ZCO log file got to 125MB, but after an hour or so with no mail showing up, I got tired of waiting and tried to close Outlook, but it freaked out at that and crashed.

Attached is about 10MB of the end of the ZCO log.

[fsiegel]

Maybe a few things going on here. Based onthe error in the log, it seems like a server error, but it looks like the Outlook connector is not handling it very well, as it appears to be looping and filling up the disk.

Questions:

1) When you said it worked on 6.0.1, and not on 6.0.2, then when you back to 6.0.1, it still didn't work -- did you go back to 6.0.1 with both the Outlook connector and the server, or just the Outlook connector?

2) You have a bug filed (42393) where you say it never really worked, even on 5.0.18 and 6.0.1 (which is different from what you say here). Is that possibly because the Adobe addin was causing some of the problems?

3) Were you using some different formatters (i.e. you had set ziplevel registry key for zco)? Probably not -- just a shot in the dark.

The main error I keep seeing is

Problem accessing /service/user/~/.
system failure: sync formatter failure

I will look into this

[jurness]

Originally Posted by fsiegel

Maybe a few things going on here. Based onthe error in the log, it seems like a server error, but it looks like the Outlook connector is not handling it very well, as it appears to be looping and filling up the disk.

Questions:

1) When you said it worked on 6.0.1, and not on 6.0.2, then when you back to 6.0.1, it still didn't work -- did you go back to 6.0.1 with both the Outlook connector and the server, or just the Outlook connector?



2) You have a bug filed (42393) where you say it never really worked, even on 5.0.18 and 6.0.1 (which is different from what you say here). Is that possibly because the Adobe addin was causing some of the problems?



3) Were you using some different formatters (i.e. you had set ziplevel registry key for zco)? Probably not -- just a shot in the dark.

The main error I keep seeing is

Problem accessing /service/user/~/.
system failure: sync formatter failure

I will look into this

1)
Just the Outlook connector

2)
With 5.0.18 it seems like if it worked initially, then it worked from then on. So that has happened in a couple of cases where it just worked. If it never did the initial sync correctly, or if it appeared to have, but then on inspection directories were empty, at least with 5.0.18 I was able to recover after multiple uninstalls/reinstalls. This also happened with 6.01 where if it didn't sync correctly the first time, a couple of resintalls (deleting the profile) would fix it. No dice with 6.0.2. That may not have been clear in bug submission.

Again 5.0.18 did work for me and 2 other users, but sometimes it took multiple reinstalls to get it right. These same two users migrated with me to 6.0.1 without trouble. When I went from 6.0.1 to 6.0.2, I have not been able to get a working ZCO.

3)
I am not sure what a "formatter" is so presumably no to that question...

[fsiegel]

This seems like a server error to me. Undoubtedly a hassle to go back to a 6.0.1 server unless you've got an installation around somewhere, but the fact that it worked with 6.0.1, and then not with 6.0.2, and then when you went back with just 6.0.1 ZCO, it failed, sounds like a server issue.

It also sounds like ZCO needs to handle whatever this error is in a better way.

I need to come up with a way to repro this in-house.