| Event Id | 101 |
| Source | AvUMR_MC |
| Description | IAvDohMessage::Submit() returned [0x80070057] on line 349 of file h:\commsvr\Sources\UnityUMR\AvUMRSyncSvr\UMRThread.cpp |
| Event Information | According to Cisco: Cause: Upgrade the Cisco Unity Server to a 3.1(4) release or later to resolve the problem. A new folder and registry key are created for handling failed message submissions. It is the same folder and registry key that is described here. You can manually add a registry key to Cisco Unity 3.0(4) or Unity 3.1(3) to enable the automatic moving of blocking messages to a specified directory for undeliverable messages. Complete these steps to enable this (assumes Cisco Unity is installed on C:, modify the drive letter as needed). Stop the AvUmrSyncSvr service. Create a directory called Failed in c:\Commserver\unityMTA. Run regedit and add the registry key HKLM/Software/ActiveVoice/UnityUMR/1.0/MtaFailedPath = c:\Commserver\unityMTA\Failed. Start the AvUmrSyncSvr service. With this key in place, whenever a message is moved to the failed directory, an information message appears in the application event viewer. This information should be used to repair or recreate the accounts of the recipients of the failed messages. If this fix is not available in your version of Cisco Unity, complete these steps to prevent the problem from happening again after it is discovered on your Cisco Unity system. Go to the MTA directory (located in \Commserver\unityMTA.). Move all of the messages (including each message associated text file) in this directory to another directory. Move each message and associated text file back to the Unity MTA directory one at a time. Stop and start the AvUMRSyncSvr service each time. You will see which messages are delivered and which are causing the problem. Remove these undeliverable message(s) from the MTA directory. Determine the affected subscriber(s) from Step 1, and repair or recreate the account(s) on Cisco Unity. Possible causes include no Exchange mail box, or a failed import during a 2.4.6 upgrade. |
| Reference Links | High CPU Utilization, AvUMR_MC Errors: No Message Delivery |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.