Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 

After an upgrade to Cisco Unity 4.0.5, messages cannot be delivered to a Microsoft Exchange mailbox. The server only runs in UMR mode. The CiscoUnity_AvWM: Error accessing server: "Name of Server". RpcMgmtIsServerListening:1715. Process: AvCsMgr ProcessID

Core Issue

This issue can occur if either a second Network Interface Card (NIC) with a bogus IP address is installed on the Microsoft Exchange server or if a modem has created a Point-to-Point Protocol (PPP) connection.

Issue the ipconfig /all command at a DOS prompt to verify the problem:

c:\> ipconfig /all

PPP adapter {23F75FF8-D979-4374-9AAD-60DC8A2DA95A}:

Connection-specific DNS Suffix  . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.234.235
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Resolution

This problem is tracked by Cisco bug ID CSCsb43902.

If there is a secondary NIC on the Microsoft Exchange server or a PPP connection is seen, disable the modem or NIC properly.

If there is no second NIC or PPP adapter present, perform these steps:

  1. Re-run the Message Store configuration wizard from the Add/Remove program.

  2. If that does not fix the issue, reboot the Cisco Unity server and possibly the Microsoft Exchange server.

Note: If the issue is still not fixed, a permanent fix to this bug has been integrated in Cisco Unity Engineering Specials (ES) versions 4.0(3)ES119, 4.0 ES97, 4.0(5)ES26, and 4.1(0.32).

After this, all messages temporarily stored in the Cisco Unity Message Transfer Agent (MTA) folder (:\Commserver\unityMta) flow straight to Microsoft Exchange, and all new voicemail messages are delivered successfully.

To obtain an appropriate ES version, open a service request with the Cisco Technical Assistance Center (TAC) through the Service Request Tool.

Version history
Revision #:
1 of 1
Last update:
‎06-22-2009 05:26 PM
Updated by: