• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 76
  • Last Modified:

Exchange 2013 mailbox keeps going under quaratnine.

Hello,

We have an exchange 2013 with around 40 mailboxes. Recently after a power failure the database got corrupted and we repaired it with eseutil. After the repair, a specific mailbox keeps crashing and after 3 crashes goes under quarantine. Is there a way to see why it crashes?
We use the Disable-MailboxQuarantine cmdlet and remove it from quarantine. The issue is that after removal from quarantine we have to restart the IS service and this causes disruptions. Also if there is way to disable quarantine in general and the mailbox keeps crashing, will this affect the database in the future ?

Thank you
0
Comp_support
Asked:
Comp_support
  • 3
  • 2
1 Solution
 
Mal OsborneAlpha GeekCommented:
Yeah, unfortunately, when a store if repaired with ESEUTIL, there is usually some missing data and corruption. Typically attachments go missing, they look to be there, but cannot be opened

Given your situation, I would export the entire mailbox out into a PST, delete it, then create a new one and import. That will probably filter out the corrupt objects, I would expect a heap to not export, however they will not actually be whole anyway.
1
 
Comp_supportAuthor Commented:
I thought about that, but i was trying to avoid it. Is ti possible to find out why the mailbox is crashing ?
0
 
Mal OsborneAlpha GeekCommented:
Well, I guess if you had access to Microsoft's documentation explaining how the store worked, you could try. Might take months.

If you try to export to a .PST, you may get some clues from what does not make it.
0
 
Comp_supportAuthor Commented:
OK, i will give it a shot later on and i will let you know how it went.
0
 
Comp_supportAuthor Commented:
Sorry for the late reply. Finally I exported the mailbox to PST. Created a new mailbox and started importing mails. Not all in once. A few every time. It turned out that there were a lot of corrupted messages in the exported PST that could not be imported. After deleting those emails and imported the rest, the problem is resolved.

Thank you for your support and sorry for the late reply once more.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now