locked
User cannot set read or unread on messages RRS feed

  • Question

  • I have a user that is able to view his inbox and read messages.  However, he is unable to set items are read/unread.  I thought it was a client issue, but the issue occurs when accessing the mailbox via OWA.  This only happens in his inbox.  Any subfolders other folders work perfectly fine.  Suggestions?

    Thanks in advance.

    Exchange 2007

    Outlook 2013

    OWA error message:

    Exception
    Exception type: Microsoft.Exchange.Data.Storage.StoragePermanentException
    Exception message: Cannot set read flags.

    Call stack
    Microsoft.Exchange.Data.Storage.MessageItem.SetReadFlagsInternal(SetReadFlags flags)
    Microsoft.Exchange.Data.Storage.MessageItem.MarkAsRead(Boolean suppressReadReceipt, Boolean deferToSave)
    Microsoft.Exchange.Clients.Owa.Basic.ReadMessage.OnLoad(EventArgs e)
    System.Web.UI.Control.LoadRecursive()
    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

    Inner Exception
    Exception type: Microsoft.Mapi.MapiExceptionJetErrorReadVerifyFailure
    Exception message: MapiExceptionJetErrorReadVerifyFailure: Unable to set read flag. (hr=0x80004005, ec=-1018) Diagnostic context: Lid: 18969 EcDoRpcExt2 called [length=47] Lid: 27161 EcDoRpcExt2 returned [ec=0x0][length=572][latency=15] Lid: 23226 --- ROP Parse Start --- Lid: 27962 ROP: ropSetReadFlag [17] Lid: 17082 ROP Error: 0xFFFFFC06 Lid: 31841 Lid: 21921 StoreEc: 0xFFFFFC06 Lid: 27962 ROP: ropExtendedError [250] Lid: 1494 ---- Remote Context Beg ---- Lid: 1238 Remote Context Overflow Lid: 21970 StoreEc: 0x8004010F PropTag: 0x67870102 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x678A0102 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x678A0102 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x67870102 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x678A0102 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x67870102 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x678A0102 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x67870102 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x678A0102 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x67870102 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x678A0102 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x67870102 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x678A0102 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x668F0040 Lid: 13236 StoreEc: 0xFFFFFC06 Lid: 5227 StoreEc: 0xFFFFFC06 Lid: 5233 StoreEc: 0xFFFFFC06 Lid: 1750 ---- Remote Context End ---- Lid: 31418 --- ROP Parse Done --- Lid: 28622 Lid: 24526 StoreEc: 0xFFFFFC06

    Call stack
    Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, Object objLastErrorInfo)
    Microsoft.Mapi.MapiMessage.SetReadFlag(SetReadFlags readFlags)
    Microsoft.Exchange.Data.Storage.MessageItem.SetReadFlagsInternal(SetReadFlags flags)

    Tuesday, June 3, 2014 5:02 PM

Answers

  • In the mailbox, or the database? That -1018 usually indicates damage to the database itself. I'd check the application log for errors and warnings and prepare to move all mailboxes to another database and then destroy the current database.

    --- Rich Matheisen MCSE&I, Exchange MVP

    Monday, June 9, 2014 3:22 PM

All replies

  • ec=-1018 indicates some type of corruption in mailbox. Did you try moving the mailbox to another database?

    Blog | Get Your Exchange Powershell Tip of the Day from here

    Tuesday, June 3, 2014 5:28 PM
  • I was hoping that was not the case....  I will try that unless I can find an alternative.
    Tuesday, June 3, 2014 5:34 PM
  • Don't know if this helps, but this is the error the user gets from outlook:

    Cannot mark items read or unread.  The most likely reasons are:

    • you do not have permission to modify items
    • these folders do not support marking as read or unread
    • The server is unavailable
    • you did not select anything to mark.

    I have verified connectivity to the server and permissions.  Any other ideas besides corruption in the mailbox?

    Tuesday, June 3, 2014 6:32 PM
  • Hi,

    Does the issue only happen to one specific user?

    If it is, please follow Amit’s suggestion to move the mailbox to another database to check whether the issue persists. If it fails, we can rebuild the problematic user mailbox by exporting the mailbox, then creating a new mailbox and importing the mailbox to have a try.

    If it still doesn’t work, please collect some application logs in Event Viewer for further analysis.

    Thanks,


    Winnie Liang
    TechNet Community Support

    Wednesday, June 4, 2014 8:04 AM
    Moderator
  • Thank you for the reply and all the suggestions.  I will move the mailbox and update with my findings.

    Wednesday, June 4, 2014 4:16 PM
  • Hi,

    I am just following up to see if you have obtained the opportunity to test the solution. If anything is unclear with the previous information I've provided to you, please don't hesitate to let me know. I am glad to be of assistance.

    Regards,


    Winnie Liang
    TechNet Community Support

    Monday, June 9, 2014 1:34 AM
    Moderator
  • In the mailbox, or the database? That -1018 usually indicates damage to the database itself. I'd check the application log for errors and warnings and prepare to move all mailboxes to another database and then destroy the current database.

    --- Rich Matheisen MCSE&I, Exchange MVP

    Monday, June 9, 2014 3:22 PM
  • Hi,

    Have the issue been resolved?

    If there is any further updates about the issue, please feel free to let us know.

    Regards,


    Winnie Liang
    TechNet Community Support

    Friday, June 13, 2014 2:26 AM
    Moderator