Exchange 2010 SP1: Error when adding or removing a mailbox database copy
If an Exchange 2010 RTM server <or> an Exchange 2010 SP1 Beta has been upgraded to Exchange 2010 SP1 RTM administrators may experience an error when attempting to utilize the remove-mailboxdatabasecopy <or> add-mailboxdatabasecopy commandlets.
When running remove-mailboxdatabasecopy the following error is noted:
Remove-MailboxDatabaseCopy DAG-DB0\DAG-2 –Verbose
WARNING: An unexpected error has occurred and a Watson dump is being generated: Registry key has subkeys and recursive removes are not supported by this method.
Registry key has subkeys and recursive removes are not supported by this method.
+ CategoryInfo : NotSpecified: (:) [Remove-MailboxDatabaseCopy], InvalidOperationException
+ FullyQualifiedErrorId : System.InvalidOperationException,Microsoft.Exchange.Management.SystemConfigurationTasks.
RemoveMailboxDatabaseCopy
Although the error is reported, the remove was successful in updating the database object within the active directory to show the server no longer hosts a copy of the database. You can verify the copy was successfully removed by reviewing the Servers with the get-mailboxdatabase –identity <NAME> | fl name, servers commandlet.
Here is sample output (note DAG-2 is missing):
[PS] D:\>Get-MailboxDatabase DAG-DB0 | fl name,servers
Name : DAG-DB0
Servers : {DAG-1, DAG-3, DAG-4}
If an administrator attempts to add a database copy to a DAG member, the same error may also be returned.
Add-MailboxDatabaseCopy DAG-DB0 -MailboxServer DAG-2
WARNING: An unexpected error has occurred and a Watson dump is being generated: Registry key has subkeys and recursive
removes are not supported by this method.
Registry key has subkeys and recursive removes are not supported by this method.
+ CategoryInfo : NotSpecified: (:) [Add-MailboxDatabaseCopy], InvalidOperationException
+ FullyQualifiedErrorId : System.InvalidOperationException,Microsoft.Exchange.Management.SystemConfigurationTasks.
AddMailboxDatabaseCopy
Unlike the remove-mailboxdatabasecopy this command is not successful in adding the copy <or> updating the Active Directory to show the copy was added.
To work around this issue the administrator should:
1) Identify the GUID of the database that is being added.
2) On the server specified in the add command, using the database GUID identified, remove the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14\Replay\State\{DB-GUID}\DumpsterInfo
To identify the mailbox database GUID, use the following command:
[PS] D:\>Get-MailboxDatabase DAG-DB0 | fl name,GUID
Name : DAG-DB0
Guid : 8d3a9778-851c-40a4-91af-65a2c487b4cc
The GUID identified in this case is 8d3a9778-851c-40a4-91af-65a2c487b4cc. With this information we can no export and delete the DUMPSTERINFO key on the server where you are attempting to add the mailbox database copy.
Once the registry key is removed the add-mailboxdatabasecopy command will complete successfully and the database copy will be added.
Comments
Anonymous
January 01, 2003
@TheRictus Thanks for the feedback. I'm glad this was helpful. TIMMCMICAnonymous
January 01, 2003
@McCue: I have only removed them when I encounter the error. TIMMCMICAnonymous
January 01, 2003
@Victor: Yes - this blog post was written before the script was created. I appreciate the link... TIMMCMICAnonymous
January 01, 2003
@WorkingHardInIt This should not be related to any number of DAG members etc. Remember that upgrading a DAG does not simply expose this issue. You would have to upgrade the DAG and attempt to REMOVE a database copy.Anonymous
January 01, 2003
@Matt: Thanks for your comment. TIMMCMICAnonymous
January 01, 2003
@Verdure... Just so I understand you are adding a database copy and get the error the recursive removes are not allowed? If not then you are not having the same issue. TIMMCMICAnonymous
January 01, 2003
@JPTH It would appear this is tracking for Exchange 2010 SP1 RU3. TIMMCMICAnonymous
January 01, 2003
@Tim Thank you, this helped me migrate a database from one server to another - got the error both times. Should I just delete all the DUMPSTERINFO keys?Anonymous
September 13, 2010
Check this issue: social.technet.microsoft.com/.../37d96c3d-433e-4447-b696-c0c00e257765 I think this might be related. The servers not showing database copies have Dumpsterinfo with a value in there of the server name and an XML string. Perhaps I'm paranoid but the people in that forum post al have 3 Node DAG with one in seperate site/location. I did not see this issue with other DAG's I upgraded.Anonymous
September 30, 2010
had this exact problem. I only run one database store at present so I compared the guids on my second Exchange (one is the 'local' dismounted DB, the other the live) with the single guid on my first Exchange - this identified it for me. Deleted the dumpsterinfo subkey and added the database copy through EMC. all working fine and dandy :)Anonymous
October 23, 2010
@TIMMCMIC - I'm wondering if the RU1 SP1 fixed this issue? Does it mean it will not happen if we ever REMOVE the database copy? Thus, the problem/issue is there until we perform usual administration tasks such one simple "uhmmm I wanted to remove this database copy and re-create it ...." We're hosting 20,000 mailboxes in single Org and have many of DAGs and database copies so I hope the RU1 SP1 fix the issue.Anonymous
November 29, 2010
Worked for me. Thank you for the blog entryAnonymous
June 10, 2011
Just my 2 cents, Exchange Team made a script to remove this Key. gallery.technet.microsoft.com/.../ba70b2a1-dc7e-4c52-ada2-b20d7380efdb Att: Victor Welasco SantanaAnonymous
October 01, 2012
In my environment, i have Exchange 2010 SP2 RollUp4. I have the same problem when i try to add a maildatabaseCopy from the server hosting the active database. When editing the registry key, i didn't see any DumpsterInfo key under Replay | State | <db-guid> Any other idea? Thanks in advance, Verdure