This problem-tackling blog incorporates a complete solution for Exchange error ‘Cannot Access Mailbox in Exchange 2010 / 2013 / 2016 / 2019’. This error interrupts the users from accessing their Microsoft Exchange mailboxes either via OWA and ActiveSync. The Exchange database can be totally disconnected, or the database can be separated from the Exchange server. Well, this is a common error message appears in Exchange user account. And there may several causes for this ‘The user cannot access mailbox in Exchange 2010′ issue such as Exchange database corruption, Exchange database is disconnected and so forth.
Sometimes, when the Directory Service Access (DSAccess) tries to find the disconnected mailbox in the Active Directory, it returns the same error. The GUID of Exchange mailbox contains the client-side cache and after that user tries to connect with Exchange Server database, the server DB GUID cache will be updated. It disconnects the Exchange Database and results DatabaseGUIDNotFound Error. Also, this error can occur in many forms and here, we are going to discuss some most common cases along with their resolution.
Instant Solution: When it becomes difficult to access mailbox in Exchange 2010 / 2013 / 2016, the best option to have a reliable and advanced application. There are efficient software available to repair corrupted Exchange EDB file and to access mailbox data easily. PCVITA Exchange EDB Recovery tool can fix MS Exchange database file and retrieve its data without any damage easily.
Sometimes while the users try to rename the Exchange account due to some reasons like changed surname or username, the users disable the Exchange mailbox to clean the databases. It makes mailboxes visible in Detached Mailboxes folder. Following Exchange Management Shell command can be utilized for cleaning mailbox database:
get-mailboxdatabase | clean-mailboxdatabase
After this, if a user deletes the AD user account and creates a new AD user account then, connect the Detached mailbox to new AD user account, the user gets new login credentials. It is the point where problem occurs. Because then, users could not log in to their account and OWA also says that the account was disabled and displays following error message:
To rectify this issue first, check the AD account and make sure it is not disabled. Then, force an AD Replication and disable the Exchange account, then replicate the AD. Still, if you cannot log in to OWA, run the below given command:
get-mailboxdatabase | clean-mailboxdatabase
After this, one can easily login to OWA and Outlook.
Users face problem in accessing their Exchange mailbox after exporting mailbox into a managed environment from Microsoft Exchange Server source. If there is an issue with the configuration of user mailbox, local profile or Autodiscover service it restricts users from accessing their mailbox after migration.
If you are running Microsoft Outlook 2010 or Microsoft Office Outlook 2007, you can check the main cause of error either it is configuration of the mailbox or Autodiscover service. Determine that the source object is configured properly or not.
Check Primary Simple Mail Transfer Protocol (SMTP) Address: Primary SMTP address should match with the primary SMTP address in managed environment. The managed primary SMTP address is recorded in the address book and in Active Directory schema of the managed environment. Now, review the source primary SMTP address in the source Active Directory schema.
Check the Target Address: Make sure that, the source object has a target address with a suffix of mgd.com. Also, make sure that, there is a matching secondary SMTP address in the managed domain. There should not be any target address on the managed object. Managed secondary SMTP address can be recorded in the address book and also in the Active Directory schema of the managed environment in user system. Eventually, review the source target address in source Active Directory schema.
Considering users query i.e., ‘Cannot Access Mailbox in Exchange 2019, 2016, 2013, 2010’ we have discussed some solutions to resolve this issue easily. Users can opt the solution according to their situation for manual solutions or automated solution. Repairing a damaged Exchange EDB file and accessing mailbox data is an easy and simple process now.