The system is temporarily unable to complete your call. Event Type: Error Event Source: CiscoUnity_ConvMsg Event Category: Network Event ID: 10045

Transcription

1 Products & Services Unity Server: Failure to Retrieve Voic Messages after Exchange Recovery Document ID: Contents Introduction Prerequisites Requirements Components Used Conventions Cause Solution 1 Solution 2 Solution 3 Solution 4 Solution 5 Solution Cisco Support Community - Featured Conversations Related Information Introduction This document describes reasons why subscribers are not able to retrieve the voic message on a Cisco Unity server due to the failure to verify the status of the mailbox. This document also provides solutions. This problem can occur after these tasks are performed in order to recover a Microsoft Exchange server due to a catastrophic failure: 1. Reinstall the Microsoft Exchange server. 2. Restore the user data from the backup media. Prerequisites Requirements Cisco recommends that you have knowledge of these topics: Cisco CallManager Cisco Unity Microsoft Exchange Components Used The information in this document is based on these software and hardware versions: Cisco Unity version 4.0(x) Off-Box Microsoft Exchange 2003 SP1 Partner Server Cisco CallManager The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command. Conventions Refer to Cisco Technical Tips Conventions for more information on document conventions. A Microsoft Exchange server becomes unusable due to catastrophic failures. The Exchange server is reinstalled and all data is recovered from the backup media. Both Permissions Wizard and Message Store Configuration Wizard run without incident. After these steps, voic still does not work. When subscribers login to voic , they receive this error: The system is temporarily unable to complete your call. The opening greeting and call transfer function properly. Both internal and external callers can leave voic messages. However, no subscriber can retrieve them. Correspondingly, these two errors are found in the event log on the Cisco Unity server. Event Type: Error Event Source: CiscoUnity_ConvMsg Event Category: Network Event ID: 10045

2 Date: 10/9/2002 Time: 17:42:19 PM User: N/A Computer: SYSTESTCLUST1 Description: Unity was unable to retrieve the mailbox for the subscriber to verify the status of the mailbox. Unity needs to know if the mailbox has the ability to send and receive mails. Possible reasons could be a missing mailbox, which can be determined through DBWalker or a corrupt memory. Technical information IAvDohMailUser::get_PrimaryMailbox returned [0x c] on line 199 of file e:viewscs_ue un_core2conversationengavstatesvravsgetmailboxstatus.cpp. Check the return code through DohErrorTest tool. Event Type: Error Event Source: CiscoUnity_ConvMsg Event Category: Network Event ID: Date: 10/9/2002 Time: 17:42:19 PM User: N/A Computer: SYSTESTCLUST1 Description: Unity was unable to determine the mailbox status for the subscriber. Unity needs to know if the mailbox has the ability to send and receive mails. Technical details - GetMailboxStatus returned [0x c] on line 98 of file e:viewscs_ue un_core2conversationengavstatesvravsgetmailboxstatus.cpp. Cause When data is restored to the Exchange server, all subscribers receive a new MailboxStorageObjectID value in the Active Directory (AD)/Exchange database. The SQL database on the Cisco Unity server still has the old MailboxStorageObjectID value which does not match the one on the Exchange server. Therefore, the mismatched MailboxStorageObjectID value between the Cisco Unity server and the Exchange server causes the failure of the mailbox status verification. The failure of the mailbox status verification prevents subscribers from retrieving voic messages successfully. The Cisco Unity server searches for the mailbox of a subscriber by the ObjectID in AD. This results in the occurrence of two event errors in the event log as shown in the section of this document. Solution 1 Complete these steps in order to solve the problem: 1. Query the SQL database in order to locate all MailboxStoreObjectID values in the MailboxStore table (see Figure 1). Complete these steps: a. Choose Start > Programs > Microsoft SQL Server > Query Analyzer. b. Choose UnityDb from the drop-down list (see arrow A in Figure 1). c. Run this query (see arrow B in Figure 1): select distinct MailboxStoreObjectId from MailboxStore d. Two MailboxStoreObjectId values are displayed. Between them, one value is for the old Exchange server that failed and the other is for the new one that was reinstalled and restored. Identify which one is the current MailboxStoreObjectId for the Exchange server that is now in production. In order to find the current MailboxStoreObjectId you can either find a user that is working and see what their MailboxStoreObjectID is, or you can create a new subscriber and then search for the MailboxStoreObjectId in the Subscriber table in the Cisco UnityDb. Figure 1 Query MailboxStoreObjectId - MailboxStore Table 2. Query the SQL database in order to locate all subscribers with the null MailboxStoreObjectID values in the Subscriber table (see Figure 2). Complete these steps:

3 a. Choose Start > Programs > Microsoft SQL Server > Query Analyzer. b. Choose UnityDb from the drop-down list (see arrow A in Figure 2). c. Run this query (see arrow B in Figure 2). select MailboxStoreObjectId from Subscriber d. Identify all subscribers with the NULL MailboxStoreObjectID value. Figure 2 Query MailboxStoreObjectId - Subscriber Table e. Test those subscribers with the correct MailboxStoreObjectId value. Check their voic messages and verify they can retrieve voic messages without error. 3. All subscribers with the NULL MailboxStoreObjectID in the subscriber experiences the problem of retrieving voic messages. Complete these steps in order to solve this issue: a. Choose Start > Programs > Microsoft SQL Server > Query Analyzer. b. Choose UnityDb from the drop-down list (see arrow A in Figure 3). c. Run this query in order to replace the NULL MailboxStoreObjectId value with the appropriate value (see arrow B in Figure 3): update Subscriber set MailboxStoreObjectId= {abcd-efgh} where MailboxStoreObjectId is NULL Figure 3 Replace the NULL MailboxStoreObjectId Value with the Appropriate Value in the Subscriber Table Note: The 5E0BB043-DF A5-63B28BC8BC82BD1 value represents the correct MailboxStoreObjectId value (see arrow B in Figure 3). Voic for all subscribers now functions with no issues. All subscribers that have NULL in their respective MailboxStoreObjectId column now have the correct Exchange server ID. Check voic for some of the previous NULL subscribers in order to verify this. Note: If the subscribers are not able to access the voic after you complete these steps, run setup.exe from C:commserverconfigurationsetupsetup.exe /sync in the Cisco Unity server and restart the Cisco Unity server. Refer to Scenarios and Solutions Cisco Unity for more information. Solution 2 This can also happen due to some Exchange server permission issues. Complete this procedure in order to resolve the issue: 1. Go to Start > Programs > Administrative Tools > Active Directory Users and Computers. 2. Go to the View menu in the management console, and make sure that the Advanced Features is selected. Note: If this option is not selected, the Security and the Exchange Advanced tabs will not be visible for the user account objects.

4 3. Double-click on the user to get the Properties window and verify the following: Solution 3 Go to the Security tab. In the Permissions box, make sure that the Send As permission is checked (greyed out checkmark) for the UnityMsgStoreSvc account. Go to Exchange Advanced tab and click on Mailbox Rights. In the Permissions box, make sure that the the Full Mailbox Access permission is checked (greyed out checkmark) for the UnityMsgStoreSvc account. This issue can occur due to the synchronization issue. Complete these steps in order to resolve the issue: 1. On the Cisco Unity server, browse to the location where Cisco Unity is installed (the default is C:CommServer). Then, browse to the TechTools folder. 2. Run DohPropTest.exe. 3. In the DohPropTest Logon dialog box, leave the Password box empty, and click OK. 4. On the warning dialog box, click Ignore to start the read-only mode of DohPropTest. 5. Click GC Monitor to display the Directory Monitor dialog box, then click TotalResync. 6. Close DohPropTest. Solution 4 Note: Lack of disk space on the Cisco Unity or Exchange server can cause problems such as this. Filling a disk beyond 80 percent capacity results in significant performance degradation. If the disk fills up completely, the database cannot grow, and Cisco Unity will stop. One main source of disk space problems on Cisco Unity is log files backed up in the Exchsrvr MDBDATA folder. In order to resolve this issue, free up some disk space and reboot Cisco Unity. This issue can occur due to Message store account (UnityMsgStoreSvc) is not a member of the Administrators group. Complete these steps in order to resolve the issue: 1. Go to Start > Programs > Microsoft Exchange > Active Directory users and computers. 2. Expand the Domain controller and navigate to Administrators group on the right pane under the Builtin folder. Right click and select Properties. Then, go to the Members tab. Click the Add button. 3. Select the messagestore account UnityMsgStoreSvc, click the Add button and click OK. This adds the UnityMsgStoreSvc account to the Administrators group. 4. Click OK in order to close the window. Solution 5 Sometimes a failsafe occurs when Cisco Unity is called in order to check voic and the voic is delivered to the Microsoft Outlook Inbox. In order to resolve this issue, complete these steps: 1. On the Cisco Unity server, run D:/commserver/configuration setup/setup.exe /sync. 2. Check the voic through the phone. The problem is the inability to take COBRAS Export of Unity 4.0(5) including voice messages. When you run the COBRAS Export on Cisco Unity server version 4.0(5) VM only to retrieve the messages so that you can COBRAS Import them to a new Unity Connection 7.1 server. This error is received: AvCsMgr service is not associated with UnityMsgStoreSvc account. Solution Perform these steps in order to resolve the issue: 1. Remove the UnityMsgStoreSvc account from the Exchange system manager if it is added as Exchange Full administrator. 2. Check in services.msc and reset the login for AvCsMgr service to the DomainUnityMsgStoreSvc account. Cisco Support Community - Featured Conversations Cisco Support Community is a forum for you to ask and answer questions, share suggestions, and collaborate with your peers. Below are just some of the most recent and relevant conversations happening right now.

5 Want to see more? Join us by clicking here Some users cannot leave voic mlong Replies 8 months, 4 days ago Unity failed to retrieve messages after... michael.armstrong 0 Replies 5 years, 10 months ago Unity failure after removing Exchange... bgrunewald 2 Replies 4 years, 1 month ago CUPC8 Voic connection to Exchange... jessehausner 0 Replies 2 months, 3 weeks ago cant retrieve voic from phone, but... jjoseph01 32 Replies 1 year, 6 months ago Unity: Voic for non-exchange... karlareyes 2 Replies 4 hours, 38 minutes ago Upgrade path from Unity / Exchange to... matthubach 2 Replies 6 months, 3 weeks ago User recieves voic 3X after... maratimer 0 Replies 4 years, 8 months ago Unity messages not delivered..added... bsugamele1 6 Replies 2 years, 8 months ago User unable to retrieve voic in... bigcappa1 5 Replies 2 years, 1 month ago Start A New Discussion Subscribe Related Information Voice Technology Support Voice and Unified Communications Product Support Troubleshooting Cisco IP Telephony Technical Support & Documentation - Cisco Systems Updated: Mar 13, 2009 Document ID: Contacts Feedback Help Site Map Cisco Systems, Inc. All rights reserved. Terms & Conditions Privacy Statement Cookie Policy Trademarks of Cisco Systems, Inc.