on my testbed exchange 2010 box, i took a p2v of it and tried to upgrade to sp1 on the resulting VM.. This install only has 1 active mailbox so its not exactly used much. It failed at the Mailbox upgrade part, and completely stuffed the install..
I think its due to when I tried to move the mail database, and it corrupted, and I had to create a new database, and migrate the few test mailboxes to the new one, but the old one is still there.
Trying to delete the old database, I get the following:
Microsoft Exchange Error
The mailbox database 'Mailbox Database 1883401331' cannot be deleted.
Mailbox Database 1883401331
This mailbox database contains one or more mailboxes or arbitration mailboxes. To get a list of all mailboxes in this database, run the command Get-Mailbox -Database <Database ID>. To get a list of all arbitration mailboxes in this database, run the command Get-Mailbox -Database <Database ID> -Arbitration. Before you can remove this mailbox database, you must disable, move, or remove user mailboxes and move arbitration mailboxes.
Ive deleted all the old inactive test mailboxes in the exchange, and running the 2 commands above doesnt list any mailboxes any more.. But I still cannot delete the old database... Any suggestions? Cheers
Last edited by RabbieBurns; 24th February 2011 at 02:03 PM.
n my testbed exchange 2010 box, i took a p2v of it and tried to upgrade to sp1 on the resulting VM.. This install only has 1 active mailbox so its not exactly used much. It failed at the Mailbox upgrade part, and completely stuffed the install..
Just a FYI but...
Are you saying that u have both the physical and virtual online/active? Really, the only instance i can think of doing this is if you are retiring that physical machine [at least, retiring it in the sense of wiping it cleanly without ever booting it back up again ] or the changes ur making to the VM version will still be affecting the attributes and settings in AD, and should you turn off / bin the VM, and go back to the physical, you could be in for even more pain
I would say that best practice would be to just create a VM with Srv2008 R2, install Exchange 2010 RTM with the MBX role, move some mailboxes into it from the other server, and then try upgrading it.
Of course, none of this helps u really but thought i should mention it regardless.
Have you tried dismounting the database first? and if u've left the physical server on, then its probably not helping too
they both werent active at once no.. i shutdown the real one and switched to the virtual one for sp1 installation, it failed, so i shut it down and rebooted the other one, which just picked where it left of and is working fine. What modifications does sP1 make to AD out of interest, i hadnt thought of that..
Also, the old databse is offline/dismounted and inactive etc
I could just do a fresh sp1 integrated exchange install on another vm and move the mailbox accross, but Im interested in learning about what the error means..
As stated by Arthur it may be that you still have arbitration mailboxes in the mailbox DB. These are hidden so you won't be able to see them unless you run the PS command. Change the DB01 to your databse name and see the results of the PS command.
Get-Mailbox -Database DB01 -Arbitration | ft -wrap -auto
Then I assume you want to remove these mailboxes and NOT move them to another database, if so then perform the following from the EMS. Replace the SystemMailbox in quotes with your results from the command above.
hehe that was my initial thought until you said you had checked using both those commands the irony here is I've had the same message myself some while back but nothing to do with SP1 or anything.
Oh well, least you got there in the end.
What i meant is that Exchange itself has alot of aspects in AD, not SP1 specifically, so switching between two machines that have the same computername but different config's / SP's of exchange on them would be a very dangerous thing IMO. Yes, it may work, and in your case, its a test setup / domain / etc, but what if it did some horrific things "behind the scenes" that you ddint see / werent aware of, and you did the same on a production Exchange setup..... just advising caution here as you should never clone Exchange servers due to the way a exchange server is tied to AD is all I meant
I know you've sorted it but for anyone else, here's a little thing on this error message: