Error when running ESEUTIL /D

[Shock@discussions.microsoft.com Steven Shock]

I received this error when running eseutil /d against a private mailbox store:

Operation terminated with error -1605 (JET_errKeyDuplicate, Illegal
duplicate key) after 9035.219 seconds.

Exchange 2003 SP2.

Any help would be apreciated,

Steven

[Susan]

what's the exact command line you've entered?

--
Susan Conkey [MVP]

"Steven Shock" <Steven Sh...@discussions.microsoft.com> wrote in message
news:B34FC8FA-5562-46AC...@microsoft.com...

[Steven Shock]

eseutil /d "G:\Exchange Stores\Legal Mailbox Store\LP Mailbox Store 01
(CCEXCH2K01).edb" /tz:\tempdfrg01.edb /fz:\tempdfrg01.stm

[Susan]

leave off the /tz:\tempdfrg01.stm and try again...

--
Susan Conkey [MVP]

"Steven Shock" <Steve...@discussions.microsoft.com> wrote in message
news:021F74E9-09F0-40FB...@microsoft.com...

[Steven Shock]

Will do. Thanks for the suggestion. I will post a reply letting you know
what the result.

steven

[Steven Shock]

Susan,

I tried your suggestion and got the same result as before. Any other
suggestions?

[jamest...@gmail.com]

Try running it from an alternate server\workstation

http://support.microsoft.com/?id=244525

James Chong
MCSE |M+, S+, MCTS, Security+
msexchangetips.blogspot.com

[maki]

Hi Steve,

I'm having the same issue and am wondering what did you do to resolve the
issue?

I actually ran eseutil /p and it succeedeed and I managed to mount the store
but problem is now that i cannot send messages.

Since i am running exchange enterprise 2003 sp2, am thinking of creating a
new store and loading the database (mailboxes) into there to see if it works?

Just wanted to see what did u do to solve it.

Thanks.
Makit

[Leandro Amore]

do you get any error when trying to send emails?

"maki" <ma...@discussions.microsoft.com> wrote in message
news:A3789436-68F7-4376...@microsoft.com...

[maki]

Yeah I cant send or receive. What I've done, though, is moved the mailbox by
using exchange tasks however, some are moving but no items are moving with
them?! while others are not moving at all. With my account for instance, I
just ended up backing up the pst file on my PC then just delete mailbox in
old store and create in new one and now it is sending and receiving email but
it is a long process! i dont know what the exchange tasks just dont want to
move the mail box and the messages in them!

[Andy David {MVP}]

On Fri, 5 Jan 2007 01:08:00 -0800, maki
<ma...@discussions.microsoft.com> wrote:

>Hi Steve,
>
>I'm having the same issue and am wondering what did you do to resolve the
>issue?
>
>I actually ran eseutil /p and it succeedeed and I managed to mount the store
>but problem is now that i cannot send messages.

After running eseutil/p, you should always follow up and run isinteg
until there are no errors or the amount of errors does not go down
after two runs.

>
>Since i am running exchange enterprise 2003 sp2, am thinking of creating a
>new store and loading the database (mailboxes) into there to see if it works?

Yes, I would not trust any database that had a repair run against it,
Its a destructive process and I would recommend moving all the
mailboxes to a new, clean store.

[maki]

Thanks Andy.
Don't know why exmerge is not running though...i want to move all the
mailboxes into the new store, but not working. those that do work, move the
mailbox, but no items are moved with them?!?

can I assume that outlook 2003 keeps all the ost files onto the local
computer? if i cant move, i'd move all the mail by converting ost to pst
(have tool) and then just moving them into user computer...

[Dave Goldman [MSFT]]

I would check the application log on that server and look for events that would indicate that database pages have been removed during the /p operation. Running the /p switch on the database can remove database pages, and frequently does, this will have unpredictable results on the database operation. The problems that can happen after running the /p switch on the database, and then running that database later can be:

 

• The database stops accepting mail.
• The database stops accepting mail.
• E-mail messages remain in the Outbox.
• The Store.exe program runs with high CPU use with no load on the server.
• The Store.exe program generates an access violation if there is a heavy load.
• Users cannot open e-mail attachments or e-mail messages.
 
Running the hard repair on the database should be the last option. Preferably, you could restore from backup. However, if that is not an option, you should do the following after the database has been repaired:

 

• Run ISINTEG on the store to get the best result possible. After that, you should perform the following appropriate option:

• If ISINTEG results in all zeros on fixes, warnings, and errors:
• Perform an offline defragmentation of the repaired database, Eseutil /d, to create a new database.
• If ISINTEG did not clean up the database on the mailbox database, and all zeros was not achieved:
• Move all mailboxes to another server or store, remove the repaired database and create the new database on the original server, and then move mailboxes back if desired. or
 
• Run ExMerge to move all mailboxes out, remove the repaired database, create a new database, and then run ExMerge to move all data into this new database.
• If ISINTEG did not clean up the database on the public folder database, and all zeros was not achieved:
• Replicate all folders to another public folder server, remove the original database file, and then replicate folders back if desired.

 

or
 
• Export all public folders through Microsoft® Outlook®, remove the repaired database file, and then create a new database. Import public folders into this new database.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

 

Dgoldman
http://blogs.msdn.com/dgoldman

"Andy David {MVP}" <ada...@pleasekeepinngcheesebucket.com> wrote in message news:oaosp21rnpm43k8pu...@4ax.com...