Hello, I've been experiencing a problem which I am not able to figure out how to solve it.Situation:A user corrupted his mailbox few months ago and received a new mailbox so the person could mail again to resolve the incident.The problem still remains, the corrupted mailbox.- First thing I tried was trying to delete... no go.- Second using ExMerge to export the mailbox from the store and delete the original location...no go, It reduced the size of the mailbox though because all "healthy" items were exported succesfully, but the faulthy still remains.- Third: moving to new store and delete it... no go.- Fourth: Using isinteg.exe and eseutil.exe multiple times... fixed some errors and reduced the size of the store, but on the end...no go.- Fifth: trying to delete the most likely cause "the result an iterative process of creating a folder in a folder". This is what I was able to delete using a utility called "mdbvu32"... but this didn't get me any further in the process. So: no go.- Retried step 1, 2 and 3 again... no go.All these tasks take place in a testing environment ofcourse!From the start I was thinking of moving all mailboxes to a new store and delete the original store containing only the corrupted mailbox. Due the lack of available storage space... this is actually the last option, but I realise it may be the only solution to get rid of the corrupted mailbox using Microsoft tools.The environment in which this take place has got Exchange 2003 Server on Win2003 servers.Does someone have an other idea what I can try besides the new store solution?Regards, Cyp.

Hi there,Reading through the steps you've taken and then following your next logical step - moving all mailboxes bar the corrupt one and then deleting the store appears to be the most sensible option.Depending on the size of the store, you could perform this work out of hours onto temporary storage, delete the original store and re-create it, and then move mailboxes back to your production storage.If the mailbox is not large, you could simply create a new mailbox for this user on another store and forget about it. I provide this information based on the fact, 1) you are not having any issues backing up this database and this mailbox is not causing any other problems other than this user accessing it, and 2) you have tested the restore function of a database with this corrupt mailbox within and it posed no problems for production disaster recovery.In lew of that information, you may find your employers are more supporting of temporary storage to fully resolve the problem. OliverOliver Moazzezi | Exchange MVP, MCSA:M, MCTS:Exchange 2010, BA (Hons) Anim | http://www.exchange2007.com | http://www.exchange2010.com | http://www.cobweb.com |