Exchange 2010 SP2 UR4 mailbox move to another DB on the same server with newly created databases gives warning/error:
The Microsoft Exchange Mailbox Replication service completed request <mailbox> with warnings.
Warning: Failed to clean up the source mailbox after the move.
Error details: MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634)
The mailbox has been moved and can be accessed. I think this is a bug which MS should solve.
See also http://social.technet.microsoft.com/Forums/da-DK/exchange2010/thread/6043b74f-a41e-4674-b2b1-08c3b1a3afbd
A technical blog about real life experiences with Exchange Server and Lync
Showing posts with label Exchange 2010 SP2. Show all posts
Showing posts with label Exchange 2010 SP2. Show all posts
Friday, August 31, 2012
Monday, January 30, 2012
Exchange 2010 SP2 and special characters in database name
Event ID 4999 is logged on an Exchange Server 2010 Client Access server (CAS) describes the following Exchange 2010 SP2 bug:
Consider the following scenario:
I was able to reproduce this in my Exchange 2010 SP2 test environment. After creating a test DB with name 'DB1 (Test)' and access a mailbox with Outlook 2007 I got the following Application Log error:
Result: Outlook 2007/2010 Out of Office (OOF) are not working anymore. This is because OOF is using Exchange Web Services on Exchange CAS.
An Interim Update (IU) is available from Microsoft.
Update 16-2-2012: this issue has been solved with Exchange 2010 SP2 Update Rollup 1
Consider the following scenario:
- You have a server that is running Microsoft Exchange Server 2010.
- The name of a mailbox database on the server contains one or more of the following special characters: ():
- You install Microsoft Exchange Server 2010 Service Pack 2 (SP2).
- The System Attendant homeMDB attribute for a user points to the mailbox database that has special characters in the name.
- The user tries to access the Exchange Server 2010 SP2 mailbox.
I was able to reproduce this in my Exchange 2010 SP2 test environment. After creating a test DB with name 'DB1 (Test)' and access a mailbox with Outlook 2007 I got the following Application Log error:
Result: Outlook 2007/2010 Out of Office (OOF) are not working anymore. This is because OOF is using Exchange Web Services on Exchange CAS.
An Interim Update (IU) is available from Microsoft.
Update 16-2-2012: this issue has been solved with Exchange 2010 SP2 Update Rollup 1
Subscribe to:
Posts (Atom)