'Local Failure Notice' messages

A.Schmidt · Post by **A.Schmidt** » Fri Jun 26, 2009 4:31 am

Hi,
one of our customers is receiving 'Local Failure Notice' messages several times a day. He has two notebooks, each of them running Outlook 2007 with ZCO 5.0.2992.16, Server version 5.0.16_GA_2923.
These mails have several xml files attached which are totally useless for him (and even us) because they only contain technical details. Yes, they could be interesting for the developer team but sending them to an end user is quite useless. Sending these messages to the Sysadmin would maybe make more sense. Names of the attachments are "obj_request_xxxxxx.xml", obj_response_xxxxxx.xml" and "sync_response.xml", where xxxxxx stands for ascending 6 digit numbers.

It seems that synchronization works accurate, though. Even though there are no obvious faults we are not sure that synchronization really works properly.
We asked our customer to enable logging with ZCOLogCtl.exe. He sent us an 8MB log file which again is totally useless for us because there are too much information stored in it and so again it is interesting for developers only. Nevertheless I had a look at the log file but could not find something that could help us.
Reinstalling ZCO, restarting Outlook, restarting Windows and so on did not help. Our customer still receives the 'Local Failure Notice' messages. Of course he's not happy about this situation, neither are we...
I have read in the forum that the messages can be disabled, but that's of course no real solution:
"Set HKLMSoftwareimbra urnOffLocalFailures to 1"
Does anyone know what the reason for this strange behaviour of Outlook 2007 / ZCO is?
Especially if Zimbra developer read this, please help us to find out what we can do for our customer! If you are a developer and need the logfiles for analysis, please contact me. We cannot post them here because they contain private content.
Thanks!

fsiegel · Post by **fsiegel** » Fri Jun 26, 2009 2:02 pm

Generally, these local failures occur with recurring appointments that have data in them that Outlook cannot handle. Sometimes this can happen from bad migrations, messages from other clients that support features that Outlook does not, previous bugs, etc. An example would be something like this:
A recurring meeting that recurs every Thursday with an update to a recurrence. The update refers to a recurrence on a Wednesday.
Outlook cannot process this, so we give a local failure. We don't want to sync this to Outlook, because if you then modify things, you'll get even more out of sync. We used to sync it, and we found there were more problems.
These errors always go in the Sync Issues -> Local Failures folder (this is an Outlook thing). However, customers complained that they weren't seeing these errors, so we also put them in the Inbox. In 5.0.12, I added some UI so you don't need to use the registry key if you dont' want to see them in the Inbox. Just do View->Errors to Inbox, and uncheck it.
Note that local failures can happen for other reasons as well -- like being unable to download HTML, etc. There are also Server errors and Conflict errors.
As far as debugging the error, you can post that log file, or what's better would be just to post those xml files that came with the local failure, as well as the complete text of the local failure message. I can take a look and probably identify why you are getting the failure.

A.Schmidt · Post by **A.Schmidt** » Fri Jul 31, 2009 6:12 am

Hi, thanks for your reply.
I added all mentioned xml files to a password protected zip file.

As they may contain private information I don't want to make them available for everyone.

@fsiegel: I will send the password to you via private message.

Here is the complete text from a local failure message:

Local Failures were detected. No action is required.

This e-mail was generated for technical support purposes.
Sync Type: Delta Sync
Sync Token (before request): 1920660
Sync Token (most current): 1932866
Store: Zimbra -
Computer Name: CA-NB-BR2
Version: 5.0.2988.16
Error IDs:

id (715615) type(task)

id (715625) type(task)

id (715634) type(task)

id (715638) type(task)

id (715642) type(task)

id (715655) type(task)

id (715685) type(task)

id (715707) type(task)

id (715713) type(task)

id (715611) type(task)

id (715774) type(task)

id (715807) type(task)

id (715811) type(task)

id (715929) type(task)

id (715944) type(task)

id (715956) type(task)

id (705102) type(task)

id (716930) type(task)

id (716932) type(task)

id (716937) type(task)

id (707287) type(task)

id (705104) type(task)

id (685846) type(task)

id (717089) type(task)

id (717091) type(task)

id (717129) type(task)

id (717711) type(task)

id (717755) type(task)

id (711245) type(task)

id (712964) type(task)

id (717134) type(task)

id (717074) type(task)

And here the message text of another local failure notice mail:

Local Failures were detected. No action is required.

This e-mail was generated for technical support purposes.
Sync Type: Initial Sync
Sync Token (before request): no sync token
Sync Token (most current): 1933731
Store: Zimbra -
Computer Name: CA-NB-BR3
Version: 5.0.2988.16
Error IDs:

id (570506) type(message)

local_failure_notices.zip

HarlettODowd · Post by **HarlettODowd** » Fri Jul 31, 2009 6:09 pm

so long as someone's willing to look at these failure notices, here's two of mine:
1)
_____________________
Local Failures were detected. No action is required.

This e-mail was generated for technical support purposes.
Sync Type: Delta Sync
Store: Zimbra - (User name)
Computer Name:
Version: 5.0.2992.16
This object does not have an ID, it is a newly created item
Error Code: -2147467259

Error Message: Unspecified error
________________________________
2
________________________________
Local Failures were detected. No action is required.

This e-mail was generated for technical support purposes.
Sync Type: Initial Sync
Sync Token (before request): no sync token
Sync Token (most current): 50333
Store: Zimbra - (user name)
Computer Name:
Version: 5.0.2931.15
Error IDs:

id (10205) type(appointment) message([Subject: Vacation]

[Details: could not find occurrence for this date(20100320T120000Z Main

appt time zone: Eastern Standard Time)ERROR - Problem processing an

exception. Inconsistencies may result

])

id (9076) type(appointment) message([Subject: Vacation]

[Details: could not find occurrence for this date(20080209T130000Z Main

appt time zone: Eastern Standard Time)ERROR - Problem processing an

exception. Inconsistencies may result

])

id (7062) type(appointment) message([Subject: Vacation]

[Details: could not find occurrence for this date(20060603T180000Z Main

appt time zone: Eastern Standard Time)ERROR - Problem processing an

exception. Inconsistencies may result

])

id (6325) type(appointment) message([Subject: Vaction]

[Details: could not find occurrence for this date(20051029T120000Z Main

appt time zone: Eastern Standard Time)ERROR - Problem processing an

exception. Inconsistencies may result

])

id (5728) type(appointment) message([Subject: Vacation]

[Details: could not find occurrence for this date(20050514T120000Z Main

appt time zone: Eastern Standard Time)ERROR - Problem processing an

exception. Inconsistencies may result

])

_______________________

thanks!

fsiegel · Post by **fsiegel** » Wed Aug 05, 2009 11:26 am

I would think there would be mime txt (.txt) files that came along with the xml. Those are the most interesting -- to see if the data is bad. I can't really tell what the task issues are without these files also.
I either need a zco log, or these mime files to go along with it. The calendar local failures are undoubtedly caused by recurrence ids that don't exist. Maybe bad migration data, or something. But I need the mime files or the zco logs.

dsfeldmann · Post by **dsfeldmann** » Mon Sep 28, 2009 4:40 am

Hi,
I'm getting the the e-mail below every minute or so. I have attached the log files. Please advise how I might fix this. Thanks.
David
************
Local Failures were detected. No action is required.

This e-mail was generated for technical support purposes.
Sync Type: Initial Sync
Sync Token (before request): 22537
Sync Token (most current): 22537
Store: Zimbra - David S Feldmann
Computer Name: MAIN
Version: 5.0.3064.18
Error IDs:

id (4275) type(message)
zco-20090928T134205.064-OUTLOOK.EXE-656.log
zco-20090928T134211.428-SearchProtocolHost.exe-2988.log

fsiegel · Post by **fsiegel** » Tue Sep 29, 2009 8:55 am

Well, I can't tell what message 4275 is, since the zco log didn't have Http logging enabled, but you might try deleting the message whose id is 4275. To find out what it is, you can either enable http tracing and send another zco log, or you can go to a browser where you're logged into your server and do:
:/service/content/get?id=4275&fmt=sync">http://:/service/content/get?id=4275&fmt=sync

deltatango · Post by **deltatango** » Thu Oct 01, 2009 7:30 am

Seems the entire Outlook Connector thing is really bugged. I just at up a test system with:

- fresh vanilla XP SP3, patched up with all Microsoft updates

- Office2007 Trial

- ZCO connector for Outlook 6.0.1_GA_1816_6.0.5691.1
and started an initial Sync agains our Zimbra Network Edition 6.01 with an account normally only used with Thunderbird.
Yet I receive a "Local Failure Notice" about a "mime to mapi conversion returned partial completion".
And we are having a problem with randomly vanishing mails sent via Outlook connector (are stored in the sent folder of both Outlook and webmail, but never reached the postfix part of Zimbra), yet the support doesn't respond after 24 hours, not even with a message saying "we received your ticket and are looking into it". Nothing, nada, niente.
???

deltatango · Post by **deltatango** » Thu Oct 01, 2009 11:00 am

[quote user="deltatango"]Seems the entire Outlook Connector thing is really bugged.[/QUOTE]
OK, as I understand it, sync errors come normally from items that Outlook cannot fully digest, so one cannot do much about it and it's not really a bug.

And I don't have to be afraid that my message store is now corrupted.
Right?

krbaker · Post by **krbaker** » Tue Oct 27, 2009 3:37 pm

Hi,

I've had numerous local failures that seem like the timezone id is just an invalid character. I've downloaded the appointment via the /zimbra/user//calendar and found nothing that looked odd there. We've seen it on more than one account and more than one meeting. It seems to only be an issue with the Outlook Connector

Failure Notice (a few bits removed for obvious reasons):

Server Failures were detected. No action is required.

This e-mail was generated for technical support purposes.

Please see the attached files for more details about the problems

encountered.
Computer Name: MC-1493
Version: 5.0.2891.12
Parent Folder EID: 000000002df59728ea8f46489631f1919a479edf02820000
Parent Folder Name: Calendar
Parent Folder ID: 10
Target Object EID: 000000002df59728ea8f46489631f1919a479edfa4252b00
Store: Zimbra - Ken Tomaselli

Download error_report.xml [text/xml 3.1k]

http://www.w3.org/2003/05/soap-envelope"> xmlns="urn:zimbra">_REMOVED__REMOVED_Weekly Sales Call

Guest Instructions
1. Dial +1 (617) 555-1212

2. When prompted for the conference number enter 123#

3. When prompted for the conference PIN enter 1234#

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">

<HTML>

<HEAD>

<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=Windows-1252">

<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7036.0">

<TITLE>Weekly Sales Call</TITLE>

</HEAD>

<BODY>



 
Guest Instructions


 1. Dial +1 (617) 555-1212
 2. When prompted for the conference number enter 123#
 3. When prompted for the conference PIN enter 1234#


</BODY>

</HTML>soap:Senderparse">http://www.w3.org/2003/05/soap-envelope ... enderparse error: Error on line 1 of document : An invalid XML character (Unicode: 0x4) was found in the value of attribute "id" and element is "tz". Nested exception: An invalid XML character (Unicode: 0x4) was found in the value of attribute "id" and element is "tz".service.PARSE_ERRORbtpool0-5985:1256588655484:e174b3d8bd546d69