Hello, We recently migrated from exchange 2007 to Exchange 2010 SP1. After the movement was completed, I ran the command "Get-Mailbox –Database “Default DB” –arbitration | ft –wrap –auto". This command did not show any result, so assuming there is no mailbox attached to it I deleted the default database. Now when I create a new database I get a error "Couldn't set the System Attendant for new database". This database gets listed in exchange but no edb or log file is created for this database. Please let me know how to resolve this issue and move the System Attendant account to different database. Thanks

Restart the System Attendant service and try again.

I tried but no luck. Tried restarted AD Topology also.

how many stores on the server?

It is Exchange 2010 SP1 Standard edition. There are currently only 3 databases. The fourth was the default database which we have deleted.

It may require you to remount another store - however I am little puzzled by that error since the SA mailbox has been removed in Exchange 2010 per: http://blogs.msdn.com/b/dvespa/archive/2009/10/06/say-so-long-to-the-system-attendant-mailbox.aspx Anything in the event logs? Where are your arbitation mailboxes now? What store?

Hi Amit, Any updates? Frank Wang

I am still getting the same error when I create from EMC. But I was able to create and mount database using shell. Now able to figure out what can be the issue.

Are you doing exchange in a multi-domain forest, with the exchange servers not in the room domain? I had that error, and I fixed it when creating the databases in EMS by running this first to change the AD scope of the EMS: Set-AdServerSettings -ViewEntireForest $True Then I was able to create the databases without receiving the error

Are you doing exchange in a multi-domain forest, with the exchange servers not in the room domain? I had that error, and I fixed it when creating the databases in EMS by running this first to change the AD scope of the EMS: Set-AdServerSettings -ViewEntireForest $True Then I was able to create the databases without receiving the error

Are you doing exchange in a multi-domain forest, with the exchange servers not in the room domain? I had that error, and I fixed it when creating the databases in EMS by running this first to change the AD scope of the EMS: Set-AdServerSettings -ViewEntireForest $True Then I was able to create the databases without receiving the error This worked for me, thanks Peter.