Re: Unity 4.0(3) and E2K3 Cluster

buporter · ‎08-09-2004

Greetings all,

As stated, we're running Unity 4.0(3) partnered with an Exchange 2003 cluster (using the cluster IP address). We run along just fine and dandy until we move the Exchange resources from one cluster node to another. At that point, Unity will not re-establish communication with the E2K3 cluster until the Unity server itself is restarted.

Around the time the Exchange resources are moved, the following entries appear in the event log on the Unity server:

Event ID 30003: An attempt to access the Primary Exchange Mailbox Store by AvUMRSyncSvr via MAPI has failed. The MAPI subsystem return the following error: The attempt to log on to the Microsoft Exchange Server computer has failed..

For more information, click: http://www.CiscoUnitySupport.com/find.php

Event ID 30012: 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.

For more information, click: http://www.CiscoUnitySupport.com/find.php

Event ID 32013: Doh logon failed due to messaging component logon error: 8004052eH

For more information, click: http://www.CiscoUnitySupport.com/find.php

Event 144: Could not retrieve Outside Caller Object. The UMR will not function correctly until this is addressed. Please call technical support. 0x00000B88

About a minute so later, Unity will see the Exchange cluster come back online and the following appears in the event log:

Event ID 1005:Server CLUSTERNAME is back on-line. Resyncing mailboxes.

For more information, click: http://www.CiscoUnitySupport.com/find.php

In my mind, the above sequence of events is what I would expect to see when the Exchange resource is moved to another node, however from this point on no voicemails will appear in anyone's inbox until the Unity server is restarted (or until the correct service is restarted).

Any ideas?

Thanks in advance...

--

Bud Porter

kechambe · ‎08-09-2004

Was it just outside callers that had to problems or did inside callers with mailboxes on the Unity server have problems as well? Could people logon to their mailboxes ok? Were messages stacking up in the UnityMTA folder?

It would be interesting to see the MALEX 10,11,12 and ALCOMMON 10 traces for the AvCsMgr and AvUMRSyncSvr. Those can be turned on in the Unity Diagnostic Tool and you can attach them to this thread.

Thanks,

Keith

buporter · ‎08-12-2004

Hi Keith,

Based on tests thus far, it appears that only calls left from the outside are queueing up. And yes, I can see them stacking up in the UntyMTA folder. Inside calls are OK. This only occurs if the Exchange cluster is moved or fails over to the other node in the cluster.

I'd be glad to attach the logs you requested, but the logs contain userids that I'd rather not see in the forum. Please email me at bud.porter@ci.birmingham.al.us and I'll send you the logs I have.

Thanks...

--

Bud Porter

buporter · ‎08-12-2004

As a followup, whether it's an outside caller or not, if the call is from an "unidentified caller" it never makes it through and stacks up in the UnityMTA folder. I just tested internal extensions that don't have VM and they never made it.