Cisco Unity server Error event, CiscoUnity_UMR[137]

[sbeukenkamp]

Below the eventlog output of an intermitent problem I have. Using 4.04sr1 with win2003 and exchange 2003 of box. Anyone seen this ? Network, Unity and Exchange load does not seem to be the problem. It is possible to tune the timeout parameters ? THX

Event Type: Error

Event Source: CiscoUnity_UMR

Event Category: UMR Thread Error

Event ID: 137

Date: 2005/04/02

Time: 17:14:30

User: N/A

Computer: x

Description:

Attempts to deliver Unity Message Repository messages have failed due to Unity configuration or connectivity issues with the Partner Mail Server.

AvUMRSyncSvr will suspend message delivery for 300 seconds, after which message delivery will be attempted again.

During this outage, messages may accumulate in the temporary store.

0x00000F00

[kechambe]

Take a look at this doc:

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

It gives you pretty much everything you need to know to troubleshoot these types of issues.

Also, if you install Windows 2003 SP1 on the Exchange 2003 server Unity won't be able to check the status of the Information Store process due to security changes Microsoft made in the Service Control Manager. Now only Administrators of the machine can poll services for status remotely, which the UnityMsgStore service isn't by default. Of course with wouldn't be intermittent so I doubt SP1 is your problem.

Thanks,

Keith

[rhindle2k2]

Keith,

I recently encountered this error in 4.0.4SR1 and was due to Exchange (2000 off-box) being taken offline to install some anti-spam software. The problem was after Exchange was back up the errors continued. Unity would still answer and take messages, but were not delivered to the mailstore until Unity was restarted. Then the messages were delivered and the errors stopped.

This brought up an important discussion between myself and the sysadmins as now we need to ensure each time Exchange is brought down that Unity is actually delivering messages to the mailstores and is not receiving the error above in the event log. This is now an extra step that we must take to ensure Unity is functioning properly and I can pretty much guess that someone is going to forget to check when Exchange is brought down and will only be noticed when I get see the event error in my email.

Shouldn't Unity be able to determine that Exchange is back up automatically? I had to restart 5 Unity servers in production in the middle of the day last week after determining vm's were not being delivered and of course seeing all those errors in the log.

Thanks!

Keith

[sbeukenkamp]

Thanks in advance for all your thoughts.

It is not windows 2003 SP1 and not offline Exchange 2003 servers as allmost all messages are delivered after the 300 sec hold time (sometimes it takes 600 secs).

And to make it even more confusing. Not all messages have these problems. I am know trying to figure out if it somehow subscriber related, but I did not manage to figure out which subscribe the delayed message should be send to.

[kechambe]

No this is not what should happen.

The problem you describe can happen if the GC Unity is using for MAPI name resolution goes offline. Is that Exchange server maybe the GC as well or is there a chance the GC went offline during that time?

If you install Exchange 2000 SP3 and the latest rev of the post-SP3 rollup _on_ the Unity server the GC issue won't happen anymore. The service packs update the Exchange System Manager client side MAPI code that Unity uses to communicate with Exchange and the GC. In 4.0(5) we are going to force the installation of these of the Unity server to protect against this issue and several other MAPI issues Microsoft fixed us. It's a good idea to install them.

Thanks,

Keith

[rhindle2k2]

Gotcha. Exchange is not the GC nor did the GC go down, but Exchange SP3 is the lastest update installed on Unity. The post-SP3 rollup is not installed on Unity. That sounds like what needs to happen.

Thanks!

Keith

[sbeukenkamp]

Not sure if this is the problem I got. My unity server is running on windows 2003 in an of box exchange 2003 environment.

If I focus for now on the nameresolution issue. Is there a way to manually set this (besides the hosts file) ? Or is it a bug in the Exchange 2003 mapi. On CCO there are no supported patches voor E2003 yet.