We are in the process of migrating from Exchange 2003 to 2010. I am having ongoing issues when using the management console and was wondering if they are just "nuisance" problems which we can safely ignore or if they may have an impact on the system when we migrate live users. e.g. WHen creating a new database, if I check the box to mount the database after creation, the mount operation fails. But if I wait a few minutes I can usually then go and mount the database. Similarly, if I add a copy of the database as part of a DAG, it creates the 2nd copy of the database but throws up an error when trying to initiate a data copy to it. Again, if I wait a few minutes I can usually manually initiate a copy and the database then goes to healthy. We're also not seeing some changes we make without actually closing the console down and re-opening it. As I said, we can probably live with these issues (if we need to) if they are only showing up during one-off management tasks. My concern is that there is something fundamentally wrong and I'd rather find out now before we have moved any live users over. Thanks

I blogged this a couple of days ago..... http://markarnold.blogspot.com/2010/05/create-mailbox-store-and-cant-mount-it.html might be what you're seeing. I'm terrible at re-finding stuff so I tend to blog it there, tag it and I can usually find what I'm looking for again. The refresh issues are most likely down to the same thing. "jarweb" wrote in message news:557b3579-fcec-4cad-bf19-ec96b67dd865... We are in the process of migrating from Exchange 2003 to 2010. I am having ongoing issues when using the management console and was wondering if they are just "nuisance" problems which we can safely ignore or if they may have an impact on the system when we migrate live users. e.g. WHen creating a new database, if I check the box to mount the database after creation, the mount operation fails. But if I wait a few minutes I can usually then go and mount the database. Similarly, if I add a copy of the database as part of a DAG, it creates the 2nd copy of the database but throws up an error when trying to initiate a data copy to it. Again, if I wait a few minutes I can usually manually initiate a copy and the database then goes to healthy. We're also not seeing some changes we make without actually closing the console down and re-opening it. As I said, we can probably live with these issues (if we need to) if they are only showing up during one-off management tasks. My concern is that there is something fundamentally wrong and I'd rather find out now before we have moved any live users over. Thanks Mark Arnold, Exchange MVP.

Thanks Mark (again - you've already responded to a query earlier) I'll try this tomorrow and create a few test DB's etc. Is this likely to be the cause of other issues we're having as well with the various management tasks outwith the database mounting problems ? Tasks failing with different errors but try again and it will possibly work etc. Cheers