This is an existing Unity installation that has been working well for quite sometime, but suddenly started having issues with delivering messages to Exchange mailboxes after a restart of the Unity box. Now I get MALEx and Doh errors...
An occurred which prevents successful Exchange access by AvUMRSyncSvr via MAPI.
This is typically an indication of configuration issues with Unity, Exchange, or the MAPI subsystem.
Verify that the Unity services accounts are granted the correct permissions and that there are no issues with installation. The SysCheck utility may assist in diagnosing the problem.
Doh logon failed due to messaging component logon error: 8004052eH
An attempt to access the Primary Exchange Mailbox Store by AvUMRSyncSvr via MAPI has failed. The MAPI subsystem return the following error: The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance..
I've checked permissions on the Unity Installation, Directory Services and Message Store Services accounts with Permissions Wizard and the result was Success on items without any failures. I reran the wizard to set the permissions again but it didn't help. I also ran every test in Directory Access Diagnostics which also showed no problems. SysCheck also found no problems. Exchange seems to be running fine and restarting Unity didn't help.
No, didn't try that. I saw the same instructions but wasn't sure if it applied in this case since the Unity and Exchange versions were not the same, plus Unity is running on Server 2003. Also, the AvCsMgr service is running.
I deleted the MAPI profile and it was recreated, but that didn't help. I've verified that all the Unity service accounts all have the correct permissions and that the Unity_server name exixts in AD and have full permissions. Maybe it's time to recreate the account in Exchange and see what that does. Like I said, all has been working fine for a long time until a restart last Friday. None of the Unity accounts have been touched so I can 't figure why this started all of a sudden.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...