?
Solved

Unable to purge or reconnect mailbox. Phantom/Ghost Mailbox

Posted on 2006-11-09
6
Medium Priority
?
876 Views
Last Modified: 2008-01-09
We had a problem during a mailbox move process (from Exchange 5.5 to 2003) as one mailbox seems to have been created on the destination server but still exists on the source
server.  
The destination server indicates that the mailbox has all it's items in (as it's 250mb in sioze), whereas the source server states that it's mailbox is 1K in size and has 2 items in it.

This is a phantom/ghost mailbox that I cannot get removed from exchange 5.5 as attempts to delete the mailbox using Exchange Admin on the source server fail.

If I stop the information store on the exchange 5.5 server, the user cannot access her mailbox.

I get the following error when trying to access the source mailbox from Exchange 5.5 admin:  
The object cannot be found in the directory.  This may be because replication has not completed.

Microsoft Exchange Directory
ID No: c1010aae


Nothing is logged on the Exchange Server event logs.  
Any idea how I can remove the mailbox from the source (exchange 5.5 server).  I've already tried the DS/IS consistency adjuster, and I don't know if removing and rectreating the user's account in active directory would get rid of this mailbox as it's exchange 5.5.


cheers,
Mike

0
Comment
Question by:gei0089l
  • 2
  • 2
5 Comments
 
LVL 16

Expert Comment

by:The_Kirschi
ID: 17909772
I think I had this problem once before but unfortunately I can't remember how it was solved.

Two suggestions:

- Have you tried to move the mailbox back to 5.5 again and then back to the new server?
- Have you tried to change the server name in the users Outlook profile to the new server? Normally this happens when a mailbox is moved successfully. But in this case it might not have worked. If the user can access his mail then it should be ok as only those 2 items are still on the 5.5

HTH. Good luck.
0
 

Author Comment

by:gei0089l
ID: 17931315
Hi there,
I've moved the mailbox back to the original server, but the ghost mailbox still exists on the original server alongside the mailbox I've moved.
The server name in the User's outlook did get changed to the new server's name.
0
 

Author Comment

by:gei0089l
ID: 17946865
Hi All,

I'm going to have to close this question down.  I basically gave up and did the following:

1. Made a PST backup of the user's mailbox.
2. Deleted the User's Mailbox in Exchange 2003
3. Ran the DS/IS Consistency adjuster on the private information store in Exchange 5.5
4. Renamed the mailbox in Exhange 5.5
5. Moved the mailbox from Exchange 5.5 to Exchange 2003 using Exchange system manager
6. Deleted the Mailbox in Exchange system manager
7. Created a new mailbox in Exchange 2003
8 Reimported the PST

This ensured that there was no phantom mailbox left in the Exchange 5.5 server.

all the best,
Mike
0
 
LVL 16

Expert Comment

by:The_Kirschi
ID: 17947076
Nice workaround!
0
 
LVL 1

Accepted Solution

by:
Computer101 earned 0 total points
ID: 18176977
PAQed with points refunded (500)

Computer101
EE Admin
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

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

Exchange database can often fail to mount thereby halting the work of all users connected to it. Finding out why database isn’t mounting is crucial and getting the server back online. Stellar Phoenix Mailbox Exchange Recovery is a champion product t…
The Exchange database may sometimes fail to mount owing to various technical reasons. A dismounted EDB file can be the source of many Exchange errors including mailbox inaccessibility for users. Resolving the root cause of mounting problems becomes …
how to add IIS SMTP to handle application/Scanner relays into office 365.
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…

601 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