[Webinar] Streamline your web hosting managementRegister Today

x
?
Solved

problem deleting mailboxes

Posted on 2008-10-22
4
Medium Priority
?
1,543 Views
Last Modified: 2010-04-21
I've been having some problems lately deleting mailboxes.  I've deleted several mailboxes over the last few months from people that have left the company and every time there is an error in the application log and the mailbox won't be purged until 3rd or 4th attempt.

Event Type:      Error
Event Source:      MSExchangeIS Mailbox Store
Event Category:      General
Event ID:      1203
Date:            10/22/2008
Time:            9:40:56 PM
User:            N/A
Computer:      <server>
Description:
Failed to delete the mailbox of /O=<company>/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=<user> with error 0x8004010f.


Now, I do know the error code means MAPI_E_NOT_FOUND so I'm trying to determine the cause.  I'm thinking there is some corruption.  I know I can run isinteg and/or eseutil, but that would take a while with a 100gb store and can't afford to have the store unavailable for that long.  Wondered if anyone had any ideas as to why this happens.  To avoid the downtime, I was considering creating a new store and moving user mailboxes there.  The mailbox won't be available during the move, but at least the downtime is only for x users at a time and less than that of running database tools on the entire store.
0
Comment
Question by:Seth Simmons
  • 2
  • 2
4 Comments
 
LVL 7

Expert Comment

by:icky2000
ID: 22783027
If you suspect the database is corrupt, and it sounds like you do, moving the users to a new database is a very good idea. You might also consider creating several databases to host those users instead of putting them all in one. A 100GB database isn't obscenely large but it is quite big. Most folks limit the size of their databases to a size they can restore within a reasonable period of time. Have you ever tried doing a restore of that 100GB database? I bet you'll be shocked at how long it takes...
0
 
LVL 36

Author Comment

by:Seth Simmons
ID: 22788164
I've worked with Exchange a lot and I wouldn't be surprised how long it would take to restore a database that large.  The problem is I need to implement mailbox quotas.  The last sysadmin didn't bother and some mailboxes are 2gb+  One user (who has since left) was nearly 8gb.  For now I'll try dividing into 2 or 3  different databases; some users need more space then others so I'll work on organizing that accordingly.
0
 
LVL 7

Accepted Solution

by:
icky2000 earned 375 total points
ID: 22789612
I've inherited systems like that too - big mailboxes and no quotas - so I feel your pain. I've had cases in the past where I was logging some scary stuff about an Exchange db and opened a case with microsoft and they wanted me to take down the server for x hours to try to repair it and all that - I've always tried to move the mailboxes first and then just delete the database because I couldn't tolerate the downtime. Moving mailboxes seems to be a "cleansing" process in that Exchange won't move something that is really corrupted so those new databases will be pretty clean.
0
 
LVL 36

Author Closing Comment

by:Seth Simmons
ID: 31509047
May not be a direct answer to the cause of the problem, though the mailbox moves are the best workaround for this database issue considering the circumstances.
0

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

Question has a verified solution.

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

Microsoft Jet database engine errors can crop up out of nowhere to disrupt the working of the Exchange server. Decoding why a particular error occurs goes a long way in determining the right solution for it.
Here is a method which can be used to help resolve a "Content Index Failed" error on a Microsoft Exchange Server.
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
Suggested Courses
Course of the Month8 days, 23 hours left to enroll

590 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