Accedi
 
HomeLibraryRisorseFormazioneDownloadSupportoCommunityForumBlog
Risorse per professionisti IT >
> 
> 
Exchange 2010 Event 8010 Defer message

Risposta suggerita Exchange 2010 Event 8010 Defer message

  • martedì 8 maggio 2012 01:50
     
     
    Registrati per votare
    0

    Dear

    Recently, I got Event 8010 from Exchange 2010. I found the Journaling mailbox keep deferring the message with following error description:-

    400 4.4.7 The server responded with: 554 5.2.0 STOREDRV.Deliver.Exception:PropertyErrorException; Failed to process message due to a permanent exception with message Property: [0x67480014] FID, PropertyErrorCode: AccessDenied, PropertyErrorDescription: . PropertyErrorException: Property: [0x67480014] FID, PropertyErrorCode: AccessDenied, PropertyErrorDescription: .. The failure was replaced by a retry response because the message was marked for retry if rejected. [Stage: CreateMessage],400 4.4.7 The server responded with: 554 5.2.0 STOREDRV.Deliver.Exception:PropertyErrorException; Failed to process message due to a permanent exception with message Property: [0x67480014] FID, PropertyErrorCode: AccessDenied, PropertyErrorDescription: . PropertyErrorException: Property: [0x67480014] FID, PropertyErrorCode: AccessDenied, PropertyErrorDescription: .. The failure was replaced by a retry response because the message was marked for retry if rejected. [Stage: CreateMessage]

    How Should I stop the Exchange defer this message and either to stop generate this event log?

     

Tutte le risposte

  • mercoledì 9 maggio 2012 09:21
    Moderatore
     
     
    Registrati per votare
    0

    Hello,

    This is a known issue, and will be fixed in a futrue update.

    Thanks,

    Evan

    Evan Liu

    TechNet Community Support

     
  • venerdì 11 maggio 2012 14:50
     
     
    Registrati per votare
    0

    Hi Evan,

    Can you explain a bit more please?
    We also have this problem since a month.
    Is this due to an update? If so, which one?

    From where do you have this information?

    Is there a technical document or an explanation which I can send to our customer about this?

    Kind Regards,
    Andy

     
  • lunedì 14 maggio 2012 01:59
    Moderatore
     
     
    Registrati per votare
    0

    Sorry, based on our policy, I cannot post the detail information on the forum.

    Thanks for understanding.

    Evan

    Evan Liu

    TechNet Community Support

     
  • martedì 29 maggio 2012 16:00
     
     
    Registrati per votare
    0

    Evan,

    Have you heard anything about this bug?  We are having this issue with journaling and the same 8010 error message as the first post.  It seems like this is the most up-to-date answer I could find so I was just curious if there was any more available info.

    Thanks,

    Rob

     
  • giovedì 31 maggio 2012 07:52
     
     
    Registrati per votare
    0

    Same problem here...  It does not happen to all the emails only some handful will be stuck in the queue trying to be delivered to Journal mailbox.  Below is the exact error message:

    LastError: 400 4.4.7 The server responded with: 554 5.2.0 STOREDRV.Deliver.Exception:PropertyErrorException; F
                        ailed to process message due to a permanent exception with message Property: [0x67480014] FID, Prop
                        ertyErrorCode: AccessDenied, PropertyErrorDescription: . PropertyErrorException: Property: [0x67480
                        014] FID, PropertyErrorCode: AccessDenied, PropertyErrorDescription: .. The failure was replaced by
                         a retry response because the message was marked for retry if rejected.

     
  • martedì 12 giugno 2012 20:55
     
     Risposta suggerita
    Registrati per votare
    0
    It's definitely a bug, confirmed by Microsoft. Supposed to be fixed in SP2 RU4 but there's no ETA for that at this time
    • Proposto come risposta waddyjohn martedì 12 giugno 2012 20:59
    •  
     
  • giovedì 5 luglio 2012 20:32
     
     
    Registrati per votare
    0

    Yet another bug? That prevents Journaling from working properly? And no explanation, lest of all a solution. Just 'you got it, you eat it'. As a matter of official policy. 

    Nice. 

     
  • lunedì 13 agosto 2012 14:17
     
     
    Registrati per votare
    0
    Any updates on this yet from anyone ? We are having the same issue intermittently and it has brought down Exchange twice in 2 months.