We started having a problem yesterday where Unity appears to be acting normally, but isn't saving messages. I rebooted the machine this morning, and while everything appears normal on the surface, it still isn't saving the messages. I'm getting two errors in the application event log that appear related, but neither is informative as to what is the real problem. The errors I get are:<br><br>Event Type: Error<br>Event Source: AvUMR_MC<br>Event Category: UMR Thread Error <br>Event ID: 101<br>Date: 1/9/2002<br>Time: 10:24:50 AM<br>User: N/A<br>Computer: UNITY-UM<br>Description:<br>IAvDohMessage::Submit() returned [0x80070057] on line 350 of file h:\CommSvr\Sources\UnityUMR\AvUMRSyncSvr\UMRThread.cpp <br><br><br>and<br><br>Event Type: Error<br>Event Source: AvUMR_MC<br>Event Category: UMR Thread Error <br>Event ID: 101<br>Date: 1/9/2002<br>Time: 10:24:50 AM<br>User: N/A<br>Computer: UNITY-UM<br>Description:<br>SendUMRMessages() returned [0x80070057] on line 60 of file h:\CommSvr\Sources\UnityUMR\AvUMRSyncSvr\UMRThread.cpp <br><br>I'm also seeing this one, but I'm not sure if it is related, or simply a downstream effect:<br><br>Event Type: Error<br>Event Source: AvNotifier_MC<br>Event Category: Run <br>Event ID: 1048<br>Date: 1/9/2002<br>Time: 10:26:01 AM<br>User: N/A<br>Computer: UNITY-UM<br>Description:<br>Mailbox logon failed for user cn=ROBINH,cn=RECIPIENTS,cn=CVESLC,o=CACHE VALLEY ELECTRIC. <br><br>We are baffled. This was working correctly and then just started having problems. <br><br>
First, I'm assuming you've got a TAC case for this. Ideally we'd need to get remote access to your box and see what's going on.
next, be aware these messages are NOT lost! You'll find them under commserver\UnityMTA directory. They will be in there as pairs of .WAV and .TXT files. It appears to be a log jam getting the messages into Exchange for some reason.
Those errors essentially are the DOH saying they're getting an invalid value on a message submit event. What happens is for outside callers leaving messages, it's handed to the UMR which then talks to the DOH to deliver the message to the "Bridgehead" Exchange server (i.e. the guy you picked in step 2 setup). It could be that one of the messages in the UMR's queue is causing a problem and it's jamming up the whole process. If we can't get direct access to your system, I'd like you to do this:
1. Go to your Commserver\UnityMTA directory and get the oldest 6 or 8 files in there, zip them up and send them to me.
2. Turn on traces for alCommon and Malex (for both turn on #10). This is done in the SA under the tools link at the bottom. Repro the problem and then get us the logs from the commserver\logs directory. Basically snag the most recent several DIAGxxx.log files
3. email it to me at email@example.com
4. if you have a TAC case open, let me know who you're working with so I can keep them in the loop.
just to follow up on this for folks following along at home this turned out to be a rather odd piece of corruption in ActiveDirectory. One particular account was giving us trouble sending voice mail messages to and the UMR was basically stuck here and all other message were piling up behind it. The Exchange interface was basically returning account doesnt exist when we attempted to send a mail to this person even though you could see them in the directory OK. All the stuff in the DOH/SQL looked fine.
As it turns out the site was having other trouble with this particular account with outlook login issues and the like. After poking around in there we discovered the account actually had a bad directory string. A proper directory string looks like this:
small but subtle difference theres no ou reference in the bad one, instead it to seattle as a subcontainer to the Recipients container. As such it was causing lots of bad mojo. Theres no easy/safe way to change this in the directory so the site ended up blowing the account away and recreating it in AD again.
I have no idea how that AD reference would have been created that way or how it would have been changed (tough to do even if you were trying). Very odd but at least we figured it out.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...