[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now


Single Exchange 2010 Mailbox cannot be accessed

Posted on 2014-04-24
Medium Priority
Last Modified: 2014-04-28
I have one exchange mailbox that cannot be accessed this morning.  If I try to logon to it from OWA I get the error, A Problem occurred while you were trying to use your mailbox.  The mailbox opens in Exchange but will not send any emails nor will it receive any new ones.  I checked the logs on Exchange server I do not see anything referencing this.

I just tried moving the mailbox to see if that would fix the issue.  I get the below error trying move.

Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:01

Test User

MapiExceptionMailboxQuarantined: Unable to open message store. (hr=0x80004005, ec=2611)
Diagnostic context:
    Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=179]
    Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0xA33][length=258][latency=15]
    Lid: 32881   StoreEc: 0xA33    
    Lid: 50035  
    Lid: 64625   StoreEc: 0xA33    
    Lid: 50128  
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 26426   ROP: ropLogon [254]
    Lid: 22787   Error: 0x0
    Lid: 13032   StoreEc: 0x8004010F
    Lid: 25848  
    Lid: 7588    StoreEc: 0x8004010F
    Lid: 25840  
    Lid: 6564    StoreEc: 0x8004010F
    Lid: 61867  
    Lid: 37291   StoreEc: 0xA33    
    Lid: 53675  
    Lid: 12716   StoreEc: 0xA33    
    Lid: 20794  
    Lid: 28474   StoreEc: 0xA33    
    Lid: 22330   dwParam: 0x0        Msg: 14.03.0123.002:MAIL
    Lid: 1750    ---- Remote Context End ----
    Lid: 50288  
    Lid: 23354   StoreEc: 0xA33    
    Lid: 25913  
    Lid: 21817   ROP Failure: 0xA33    
    Lid: 26297  
    Lid: 16585   StoreEc: 0xA33    
    Lid: 32441  
    Lid: 1706    StoreEc: 0xA33    
    Lid: 24761  
    Lid: 20665   StoreEc: 0xA33    
    Lid: 25785  
    Lid: 29881   StoreEc: 0xA33    

When an item can't be read from the source database or it can't be written to the destination database, it will be considered corrupted. By specifying a non-zero BadItemLimit, you are requesting that Exchange not copy such items to the destination mailbox. At move completion, these corrupted items won't be available in the destination mailbox.

Exchange Management Shell command attempted:
'Consoto.com/PD Users/IS/Test User' | New-MoveRequest -TargetDatabase 'Mailbox Database 0482295700' -BadItemLimit '20'

Elapsed Time: 00:00:01
Question by:PDIS
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions

Expert Comment

ID: 40020435

If it is not related to the authentication (username and password seem to be ok, and account is not locked), then:
* Maybe the database is corrupt. Do you have several databases? Could you move that mailbox to another database, just to check?
* This issue can occur because the Exchange 2010 Store limits the number of non-MAPI sessions that other services generate, such as IMAP, POP, Outlook Web Access, Microsoft Exchange ActiveSync (EAS), or Exchange Web Services (EWS). By default, sessions per user are limited to 32, and service sessions per user are limited to 16. Such values are quite high bit, can you think it could be the reason?
* To get diagnostic information, you can run the Exchange connectivity test using that mailbox credentials: https://testconnectivity.microsoft.com/ -> you can perform several tests; at least run EWS and Outlook test.

Is that mailbox migrated from another mail server?
Are you using the credentials of the user who own the mailbox? Or administrative or delegated credentials?

Expert Comment

by:Mohammed Tahir
ID: 40020500
Below link may help you.



Author Comment

ID: 40020606
Thanks Tahir - I'm not moving the mailbox from 2007 to 2010.  It's been functioning on 2010 for several years now.  I tried to move it to a different database today  and that's when I got that error.  

Carlos - I tried increasing the store limits and it did not help.  I tried the connectivity tests but they did not find any issues with the mailbox.  

I am using the credentials of the user of the mailbox.  I verified the credentials are still valid.

Expert Comment

ID: 40020882
Have you tried restoring the mailbox from a backup prior to the day you had the problem with it?
LVL 63

Accepted Solution

Simon Butler (Sembee) earned 2000 total points
ID: 40023292
Before going to a restore, try a Mailbox Repair.
That uses the command new-mailboxrepairrequest



Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

How to deal with a specific error when using the Enable-RemoteMailbox cmdlet to create a mailbox in the cloud-based service, for an existing user in an on-premises Active Directory.
One-stop solution for Exchange Administrators to address all MS Exchange Server issues, which is known by the name of Stellar Exchange Toolkit.
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…
This video discusses moving either the default database or any database to a new volume.

656 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question