Cisco Bug: CSCtf12187 - Ex2010 - Logon fails when partner mailbox is not on a CAS server
May 09, 2012
- Cisco Unity Servers
Known Affected Releases
Symptom: When using an Exchange 2010 server as the Cisco Unity partner server, Cisco Unity may stay in Unity Message Repository (UMR) mode despite the Exchange 2010 mailbox database being online. When calling in to retrieve messages, subscribers may hear, "The message server is offline..." or "Your messages are not available now." For this defect, the issue is caused by an incorrect value in the Exchange 2010 mailbox database RpcClientAccessServer property. This property is set when you create the Exchange 2010 mailbox database, however, it can become invalid with changes to the Exchange environment such as moving the Exchange 2010 mailbox database or when a Client Access Server (CAS) server is renamed or removed from the Exchange environment. Conditions: This issue will only occur if Exchange 2010 is the Cisco Unity partner server, i.e. the Cisco Unity system mailbox is in an Exchange 2010 mailbox database. If Cisco Unity is using Exchange 2000, 2003 or 2007 as the partner server, you are not seeing this issue. STOP HERE. This issue will affect every mailbox in the Exchange 2010 mailbox database and not just the Cisco Unity system mailbox (Unity_<server name> mailbox). If there are only problems with the Cisco Unity mailbox and other mailboxes in the mailbox database are not affected (e.g. users can access their Exchange 2010 mailboxes using Outlook), you are not seeing this issue. STOP HERE. This issue typically only occurs when the Exchange 2010 server that Cisco Unity is using as the partner server does not have the Client Access Server (CAS) role. If the partner server does have the CAS role, you are likely not seeing this issue but use the information below to confirm that the RpcClientAccessServer property for the Exchange 2010 mailbox database is set to a valid Exchange 2010 CAS server or Exchange 2010 CAS Array.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases