Unity 5.01 ES55 - Unified with 2003 - DC/GC Crashed/Rebooted

Unanswered Question

Today, and a couple times in the past, this customers DC/GC(s) have either crashed or rebooted for emergency patching. The Event Viewer shows the DC/GC switchover as expects, then messages begin to randomly queue up in MTA folder, steadily getting worse and worse. The only solution provided by Cisco is to failover to secondary (all the UMR messages dump out at that time) then restart the entire primary server, then failback. Last ticket told me this was "expected" behavior.

There are also many times when the system recovers just fine from DC/GC reboots....

Does anyone else have this unreliable situation?

It is a large Exchange environment (10 DC/GCs and 20 Exchange Servers)

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Ginger Dillon Tue, 04/21/2009 - 10:26

Hi -

Just my opinion, but instead of failing over to your secondary Unity server, next time just try restarting the AvUMRSynchSvr service on the primary Unity server. If the Exchange servers are again online, the UnityMTA messages should be moved to the user mailboxes. Sometimes this occurs on Unity 4.2(1) as well when OS maintenance is performed on Exchange servers in our environment. The service occasionally needs a jump start. We routinely check the UnityMTA folder.

Ginger

Christopher McAlpin Tue, 04/21/2009 - 11:06

You may be running in to the following defect:

MAPI could return other than MAPI_E_END_OF_SESSION after GC reconnect

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsd17381

The following defect discusses the requirements for MAPI GC re-connects:

When GC is down, voicemail is not delivered

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCea26846

Actions

This Discussion