Page 1 of 2 12 LastLast
Results 1 to 10 of 22

Thread: 'Local Failure Notice' messages

Hybrid View

  1. #1
    Join Date
    May 2008
    Posts
    3
    Rep Power
    7

    Default 'Local Failure Notice' messages

    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 \HKLM\Software\Zimbra\turnOffLocalFailures 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!

  2. #2
    Join Date
    Sep 2006
    Posts
    1,334
    Rep Power
    11

    Default

    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.

  3. #3
    Join Date
    Dec 2007
    Posts
    8
    Rep Power
    7

    Default

    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/<username>/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):
    Code:
    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]
    <SyncError><Request><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Header><context xmlns="urn:zimbra"><userAgent name="ZimbraConnectorForOutlook" version="5.0.2891.12"/><nonotify/><noqualify/><account by="id">_REMOVED_</account><authToken>_REMOVED_</authToken><nosession/></context></soap:Header><soap:Body><SetAppointmentRequest xmlns="urn:zimbraMail" l="10" nextAlarm="1257171900000"><default ptst="NE"><m><tz id="" stdoff="-300" dayoff="-240"><standard week="1" wkday="1" mon="11" hour="2" min="0" sec="0"/><daylight week="2" wkday="1" mon="3" hour="2" min="0" sec="0"/></tz><inv method="REQUEST" fb="B" transp="O" allDay="0" name="Weekly Sales Call" loc="" seq="0" class="PUB" uid="040000008200E00074C5B7101A82E00800000000209CF3418652CA010000000000000000100000001DE28C62F1FAEE4AA37D9F98C411C4D6"><s d="20090330T093000" tz=""/><e d="20090330T103000" tz=""/><or name="Ken Tomaselli" a="_REMOVED_@metacarta.com"/><recur><add><rule freq="WEE"><interval ival="1"/><byday><wkday day="MO"/></byday></rule></add></recur><alarm action="DISPLAY"><trigger><rel related="START" neg="1" m="5"/></trigger><desc/></alarm></inv><su>Weekly Sales Call</su><mp ct="multipart/alternative"><mp ct="text/plain"><content>
    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#
    </content></mp><mp ct="text/html"><content>&lt;!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"&gt;
    &lt;HTML&gt;
    &lt;HEAD&gt;
    &lt;META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=Windows-1252"&gt;
    &lt;META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7036.0"&gt;
    &lt;TITLE&gt;Weekly Sales Call&lt;/TITLE&gt;
    &lt;/HEAD&gt;
    &lt;BODY&gt;
    &lt;!-- Converted from text/plain format --&gt;
    &lt;BR&gt;
    
    &lt;P&gt;&lt;FONT SIZE=2&gt;Guest Instructions&lt;/FONT&gt;
    &lt;/P&gt;
    
    &lt;P&gt;&lt;FONT SIZE=2&gt;&amp;nbsp; 1. Dial +1 (617) 555-1212&lt;/FONT&gt;
    
    &lt;BR&gt;&lt;FONT SIZE=2&gt;&amp;nbsp; 2. When prompted for the conference number enter 123#&lt;/FONT&gt;
    
    &lt;BR&gt;&lt;FONT SIZE=2&gt;&amp;nbsp; 3. When prompted for the conference PIN enter 1234#&lt;/FONT&gt;
    &lt;/P&gt;
    
    &lt;/BODY&gt;
    &lt;/HTML&gt;</content></mp></mp></m></default></SetAppointmentRequest></soap:Body></soap:Envelope></Request><Response><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Body><soap:Fault><soap:Code><soap:Value>soap:Sender</soap:Value></soap:Code><soap:Reason><soap:Text>parse 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".</soap:Text></soap:Reason><soap:Detail><Error xmlns="urn:zimbra"><Code>service.PARSE_ERROR</Code><Trace>btpool0-5985:1256588655484:e174b3d8bd546d69</Trace></Error></soap:Detail></soap:Fault></soap:Body></soap:Envelope></Response></SyncError>
    Last edited by ArcaneMagus; 10-27-2009 at 03:32 PM. Reason: Wrapped in [code] tag

  4. #4
    Join Date
    Dec 2007
    Posts
    8
    Rep Power
    7

    Default

    Note that the tz id="" seems to have lost the invalid char in that post, but it was as the error message says 0x4

  5. #5
    Join Date
    Dec 2007
    Posts
    8
    Rep Power
    7

    Default Ugh, more parsing errors

    Seeing these more and more.

    Now I've seen one on a calendar update which just seemed to corrupt the content type field!?!

    XML Parsing Error: not well-formed

    Line Number 130, Column 55:</content></mp></mp><mp ct="image/gif"><content>GIF89a</content></mp><mp ct="image/gif"><content>GIF89aA</content></mp><mp ct="text/html"><content>&lt;html&gt;&lt;body&gt;&lt;/body&gt;&lt;/html&gt;</content></mp></mp><attach aid="aa3d13a5-f4e6-4a9e-8470-3030720711c8:c700549c-a2ea-4fb4-8ba4-20654f2002bf"/></m></default></SetAppointmentRequest></soap:Body></soap:Envelope></Request><Response><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Body><soap:Fault><soap:Code><soap: Value>soap:Sender</soap:Value></soap:Code><soap:Reason><soap:Text>parse error: Error on line 130 of document : An invalid XML character (Unicode: 0x10) was found in the element content of the document. Nested exception: An invalid XML character (Unicode: 0x10) was found in the element content of the document.</soap:Text></soap:Reason><soapetail><Error xmlns="urn:zimbra"><Code>service.PARSE_ERROR</Code><Trace>btpool0-6264:1257190678054:e174b3d8bd546d69</Trace></Error></soapetail></soap:Fault></soap:Body></soap:Envelope></Response></SyncError>
    ------------------------------------------------------^

  6. #6
    Join Date
    Sep 2006
    Posts
    1,334
    Rep Power
    11

    Default

    We hear of things like this extremely infrequently, and generally have a hard time reproducing. If you know where this meeting came from, or have any idea of anything special about, please let us know. That would help our repro cases.

    There is a bug on this (bug 32967) that is slated for 6.0.3, our next release. We will also put the fix in 5.0.21. We'll have to see if we can still repro, and the fix will probably just be to get rid of the bad character. But info on how to repro (even the MIME message) will help.

  7. #7
    Join Date
    Dec 2012
    Posts
    1
    Rep Power
    2

    Default

    Quote Originally Posted by fsiegel View Post
    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.
    I know I'm resurrecting a pretty old thread here, but I have a user who is experiencing the exact issue you've described. I turned off Errors to their Inbox, but this doesn't seem like the most elegant solution. The issue is exactly what you described- a recurring meeting with a single recurrence on a different day. Instead of syncing this meeting into Outlook, the user gets an error message, including XML of the meeting. However, they were receiving this error message every single time they synced- consistently every minute, sometimes multiple times per minute. Now that I've turned off Errors to Inbox, that doesn't actually make the error go away, it just means the user isn't seeing it. This isn't really what we want. Is there a way to simple tell Outlook to stop trying to sync this meeting? Is this going to cause issues down the road (because presumably this meeting, and its error, won't ever go away- it'll just languish on the calendar for a few years)?

  8. #8
    Join Date
    Jan 2012
    Posts
    7
    Rep Power
    3

    Default 'Local Failure Notice' Messages

    Just dropping a note here to report that we are also having this occur at our organization. We just upgraded from 7.2 to 8.0.2 and a few of our Outlook users have been getting this error.

  9. #9
    Join Date
    Jul 2012
    Posts
    8
    Rep Power
    3

    Default

    We are having several users with delta sync errors after the upgrade to 8.0.3.
    Turning off the message is not an option.
    Changing the sync token to an older version sometimes help.
    Someone any idea?

  10. #10
    Join Date
    Jan 2012
    Location
    Brisbane, Australia
    Posts
    58
    Rep Power
    3

    Default

    I'm in the same boat with many users reporting sync errors after upgrading to 8.0.3. Haven't done a thorough investigation yet. I have attempted deleting their outlook profile and resyncing their entire mailbox but this didn't fix the issue in that instance.

Similar Threads

  1. [SOLVED] Re-creating the spam training e-mail account
    By richard-hdd in forum Administrators
    Replies: 21
    Last Post: 03-20-2012, 08:34 AM
  2. Local Failure Notice Email
    By MP-NNCSB in forum Zimbra Connector for Outlook
    Replies: 19
    Last Post: 12-16-2009, 07:31 AM
  3. Local Failure Notice
    By cash@tcho.com in forum Zimbra Connector for BlackBerry
    Replies: 4
    Last Post: 05-22-2009, 08:58 AM
  4. Local Delivery Failure Messages
    By ewebzone in forum Zimbra Connector for Outlook
    Replies: 1
    Last Post: 02-10-2009, 12:01 PM
  5. Zimbra fails after working for 2 weeks
    By Linsys in forum Administrators
    Replies: 10
    Last Post: 10-07-2008, 01:42 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •