How do I "un-fail" messages in the UnityMTA\Failed folder?

[michael.armstrong]

Following the loss of Unity-Exchange communication after installing Server 2003 SP1 on the Exchange server, we have a bunch of .wav/.txt message pairs in the CommServer\UnityMTA\Failed folder. We've applied a temporary fix to restore Unity-Exchange communications OK, and new messages are delivered properly. How do I ask Unity to please try the "failed" messages again? It turns out we've got "failed" messages going back for a year and a half. Restarting Unity and resynching with Exchange don't have any effect.

[michael.armstrong]

I've tried moving the .txt/.wav pairs to the UnityMTA folder, but they fail again, with an Event Log entry like:

A message with the subject:

Message from an unidentified caller (1316)

to recipient hnn could not be delivered and was moved to the failed directory. This can occur for several reasons: the recipient mailbox may be disabled or inaccessible, Cisco Unity may be having trouble connecting with the partner server, or the Cisco Unity messaging component may not be properly configured. If this condition persists, contact Cisco TAC. 0x00000514

New messages to the same recipient are processed normally. I can build e-mails to the affected recipients and send them all manually, but there must be a better way.

[Hin Lee]

Please see Keith's post regarding Windows 2003 sp1.

http://forum.cisco.com/eforum/servlet/NetProf;jsessionid=9llip3o9t1.SJ1A?page=netprof&forum=IP%20Communications%20and%20Video&topic=Unified%20Communications&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1dd7cfdd

CSCsa80702 AvWM OpenSCManager gets access denied when connecting to W2K3 SP1

Symptom:

After installing Windows 2003 SP1 on an Exchange 2003 server Unity is communicating with, Unity can't communicate with it anymore.

Conditions:

This occurs after installing Windows 2003 SP1.

Workaround:

At this time the workarounds are:

1. Uninstall Windows 2003 SP1 from the Exchange 2003 server. Once this is complete the Unity server must be fully (Windows) rebooted.

or

2. Place the UnityMsgStoreSvc account (the account the AvMsgStoreMonitor service logs on as) in the local Administrators group on the Windows 2003 SP1/Exchange 2003 server. Once this is complete the Unity server must be fully (Windows) rebooted.

If the Windows 2003 SP1/Exchange 2003 server is a clustered Exchange server place the UnityMsgStoreSvc account in the local Administrators group for all nodes in the cluster. Once this is complete the Unity server must be fully (Windows) rebooted.

If the Windows 2003 SP1/Exchange 2003 server is a domain controller it is not recommend to place the UnityMsgStoreSvc account in the Domain Admins group because this group has explicit denies be default on all Exchange Message Stores. Placing the account in that group will allow Unity access to the Services Control Manager so Unity will be able to 'see' the Exchange server again but all mailbox logins will fail. Instead do option number 1 -- uninstall Windows 2003 SP1.

Further Problem Description:

For more information on diagnosing Exchange server offline issues please see:

http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_tech_note09186a008011934a.shtml

Are all the messages left from outside callers, and from other subscribers making it into the subscribers' mailboxes?

I presume that you have already looked at

Field Notice: Unity 4.0(4) Does Not Support Microsoft Exchange 2003 SP 1

http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_field_notice09186a008024d72f.shtml

[michael.armstrong]

I did see Keith's post (too late to avoid the original issue, of course). I hadn't looked at the Field Notice (is there some way of getting notified of applicable Field Notices, or do you just have to look at them periodically?), but even if I had, it wouldn't have mattered. I did upgrade and re-run the Permissions Wizard, which ran just fine. Apparently there's something it doesn't test for which fails in this situation.

All messages, from whatever source, failed. They wound up in the UnityMTA\Failed folder. I sent them to their recipients manually.

At this point I've opted for workaround (2) which seems to be working OK.

This bug in SP1 apparently affects SQL also, so it may be fixed sooner rather than later. Finally, I've been told that SP1 can't always be uninstalled, so be extra careful.