problem with purging mailboxes

[seth]

I have 1 exchange 2003 sp2 server running on windows 2003 sp2.

I inherited it with 1 storage group with everyone's mailbox in one database.
Last few months I started noticing that after I attempted to purge a
mailbox, it really didn't purge it and stayed in the list with a red x. I
then noticed that in the application log it was showing this:

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

Event Type: Error
Event Source: MSExchangeIS Mailbox Store
Event Category: General
Event ID: 10001
Date: 12/21/2008
Time: 12:09:16 PM
User: N/A
Computer: <server>
Description:
The folder with folder ID 2-710AB1B could not be deleted. Additional
information: 0x8004010f.

I found kb articles that talked about how this can be ignored if the mailbox
was never accessed or because of a guid issue; though that isn't the case
here, and applied only to exchange 5 or 2007.

I then thought it was some sort of database corruption. I could have taken
the database offline to run eseutil, but I don't know how long it would take
with nearly 100gb database. To avoid downtime for users, I decided to move
everyone to separate databases so I can take this one offline and work with
it (at the same time organize mailboxes a little better). I'm about 90%
complete in that and all users are working fine on the new mailbox
locations. The only issue that occured with moving the mailboxes is that
after it copied to the new database and updated AD, it didn't purge from the
old mailbox (still in original store, detached) and the above errors
appeared every time.

I just tried to purge a mailbox from one of the newly created databases and
it failed, with the same error. I know the error code means
mapi_e_not_found but I have no idea what else could be causing this. Anyone
have any ideas?

[Rich Matheisen [MVP]]

[ snip ]

>I just tried to purge a mailbox from one of the newly created databases and
>it failed, with the same error. I know the error code means
>mapi_e_not_found but I have no idea what else could be causing this. Anyone
>have any ideas?
>

Could this be your problem?
http://support.microsoft.com/KB/940012
---
Rich Matheisen
MCSE+I, Exchange MVP

[seth]

At first, I thought it was...until I looked at the files.
That hotfix is version 6.5.7653.18 (22 Oct 2007)
This server is currently at 6.5.7653.38 (10 June 2008)

"Rich Matheisen [MVP]" <rich...@rmcons.com.NOSPAM.COM> wrote in message
news:5gatk45uuq8kn7u1r...@4ax.com...

[seth]

In addition, if I try to purge the mailbox now, it says it can't because it
was already reconnected to an existing user, which isn't correct.

"seth" <m...@myhome.net> wrote in message
news:%23nm2O27...@TK2MSFTNGP02.phx.gbl...

[Jamestechman]

Are these mailbox moves within the same Exchange server? The only time
I encountered similar issue was due to someone having imaged an
Exchange server in one site I don't recall the exact issue or history
of it now; this was causing havoc with mailbox moves and not being
able to purge source mailbox as well due to AD issues\replication\SIDS
etc. Are you seeing any AD related issues on your Exchange box?

James Chong (MVP)
MCITP | EMA; MCSE | M+, S+,
Security+, Project+, ITIL
msexchangetips.blogspot.com

On Dec 22, 6:33 pm, "seth" <m...@myhome.net> wrote:
> In addition, if I try to purge the mailbox now, it says it can't because it
> was already reconnected to an existing user, which isn't correct.
>
> "seth" <m...@myhome.net> wrote in message
>
> news:%23nm2O27...@TK2MSFTNGP02.phx.gbl...
>
>
>
>
>
> > At first, I thought it was...until I looked at the files.
> > That hotfix is version 6.5.7653.18 (22 Oct 2007)
> > This server is currently at 6.5.7653.38 (10 June 2008)
>

> > "Rich Matheisen [MVP]" <richn...@rmcons.com.NOSPAM.COM> wrote in message

> >> MCSE+I, Exchange MVP- Hide quoted text -
>
> - Show quoted text -

[seth]

this is within the same server; there is only one exchange server in the
environment

I'm not seeing any AD issues on either the exchange box or any of the 4
domain controllers.
I did find one posting that said someone had the exact same issue and
resolved it by removing exchange attributes, then was able to purge the old
mailbox and attach the new one.

might try it on my mailbox first later today

http://social.msdn.microsoft.com/forums/en-US/windowsgeneraldevelopmentissues/thread/c732d0a3-4dec-40de-9d1d-72918f8cb8c4/

Not sure why that topic ended up in a vista msdn forum but it might be the
solution regardless

"Jamestechman" <jamest...@gmail.com> wrote in message
news:59775d98-5c48-48a7...@g1g2000pra.googlegroups.com...

[seth]

seems to be a matter of timing; i just ran cleanup on the old store (again)
and most of the first mailboxes that i moved are now purged

"seth" <m...@myhome.net> wrote in message

news:e0I8rsR...@TK2MSFTNGP04.phx.gbl...