Environment: Exchange 2010 SP1
Volume containing mailbox databases ran out of disk space. Was able to clear up 1 GB of space and ran move-databasepath cmdlet. The process crashed with the following error message:
Error: Sending data to a remote command failed with the following error message: The WS-Management service cannot complete the operation within the time specified in OperationTimeout. For more information, see the about_Remote_Troubleshooting Help topic.
Even though the process crashed the .EDB file was moved to the new volume and the file size was an exact match to the original. However, upon attempt to mount the database I got the following error:
[PS] C:\Windows\system32>mount-database -identity 'DB1' Couldn't mount the database that you specified. Specified database: DB1; Error code: An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-1032). [Database: DB1, Server: exchsvr1.doamin.local]. + CategoryInfo : InvalidOperation: (DB1:ADObjectId) [Mount-Database], InvalidOperationException + FullyQualifiedErrorId : C7553590,Microsoft.Exchange.Management.SystemConfigurationTasks.MountDatabase
The mailbox database file was copied correctly however the cmdlet failed before the AD schema was updated. The resolution was to go edit the schema to point to the new EDB file.
- First thing was to check the health of the file. You can check the health of the Exchange DB file from the command line:
- eseutil /mh “[edb file path]” (If not healthy, stop and call Micrososft support for assistance)
- Open ADSIEdit
- Connect to the Configuration Container
- Navigate to:
- CN=Administrative Groups
- CN=[Administrative Group which database is a part of]
- On the container of your database, right click and select “Properties” and take note of the current value for attributes named MSEXCHEDBfile and MSESEParamlogfilepath
- Edit the attributes MSEXCHEDBfile and MSESEParamlogfilepath to the new location
An article describing this process in more depth for Exchange 2000 and 2003 can be found here: http://support.microsoft.com/kb/822676; even though the article isn’t updated for Exchange 2007/2010 the process is pretty similar.