Hello, I got an error during Exchange database offline defragmentation: Operation terminated with error -1508 (JET_errColumnDuplicate, Field is already defined) after 5912.219 seconds. Command: eseutil /d "<edbFileName>" /t <tempDefragFolder> Environment: Exchange 2007 + SP3 + RU 5 Note: The DB is not corrupted (already tested with ESEUTIL) Have you ever gotten the error above ? Do you know how to resolve it (I already now the way to create a new DB and move all mailboxes to this new one). Thank you, Luca Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

Hi You must have 110 % free space for running Offline DB. Have you run the integrity scan ?Thanks Mhussain

Hello, yes of course, I have 130% free space !!! I don't have any problem with different DB of same size; just only one. As already written (see third point), I tested it isn't corrupted. Note: I opened a support case at Microsoft time ago about the problem, but they told me the only way is to create a new DB and move mailboxes; I hope some other got this error and could share some information about it. Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

On Sun, 12 Feb 2012 10:32:58 +0000, Luca_Fabbri wrote: > > >Hello, yes of course, I have 130% free space !!! I don't have any problem with different DB of same size; just only one. As already written (see third point), I tested it isn't corrupted. > >Note: I opened a support case at Microsoft time ago about the problem, but they told me the only way is to create a new DB and move mailboxes; I hope some other got this error and could share some information about it. So why not do that instead of trying to defrag the existing database? You obviously have enough disk space to do that. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hello Rich, answering to your question: because it is a FATA disk, used as temporary for defragmentation only; production Exchange DBs are on FC disks and I don't have so much free disk space there. And also because the defrag. process should be easier and faster then moving about 120 mailboxes to another DB, what about ? Bye, LucaDisclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

On Sun, 12 Feb 2012 18:34:23 +0000, Luca_Fabbri wrote: > > >Hello Rich, answering to your question: because it is a FATA disk, used as temporary for defragmentation only; production Exchange DBs are on FC disks and I don't have so much free disk space there. And also because the defrag. process should be easier and faster then moving about 120 mailboxes to another DB, what about ? I don't see you having any other choice than to create another database and move those mailboxes out of the damaged database. If you must, stand up another server with adequate storage (even if it's local to the machine), move the mailboxes to it and then use database mobility to move the entire database to the original storage location. Then you can remove the temporary machine. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hello Rich, yes, I now the only solution (better, workaround) is to create a new DB, move mailboxes, delete old DB, create a new DB and move mailboxes back. My post was only to share with the community the error, if someone already got it; but I'd like to understand why it happens !! ;-) Regards, LucaDisclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.