Sluggish VM/MWI not working properly- Unity 7.0 and Exchange 2007

[Victoria99]

Greetings,

Last week we began to have issues with VM being sluggish and WMI not lighting up or lighting up very late.  After looking at the event log, on the Unity server, it was noted that there were a lot of MAPI threshold over the limit events.  We still couldn't quite understand the root cause of this as that the problem seems to have gotten out of hand more since last Tuesday, however we've been trying to troubleshoot this and are focusing on the Exchange server.

Recently the Exchange admin upadted the ExchangeMAPICDO across all of the exhange servers.  I am not clear on if we need to do some sort of update also on Unity?  This may not even be the issue as that I'm seeing a few things which don't make sense but since the bulk ofthe errors have to do with this threshold error, I am looking here first.

The update happend approx a week before the VM/MWI started to go on the fritz so I'm a little perplexed as to where I should also troubleshoot.

Any assistance would be apprecated.

Thank you!

[Ginger Dillon]

Hi Victoria,

You might take a look at this Microsoft update in case it is not on your Exchange server.  I found a couple of references to it fixing MWI with Unity and Exchange 2007.

http://support.microsoft.com/?kbid=952580

I know the version of exchangemapicdo with Unity and Exchange 2010 must be the same and is referenced in the documentation for partnering Unity with Exchange 2010 but I did not find a specific reference for 2007.

Regards, Ginger

[David Hailey]

If you are seeing a lot of MAPI time threshold warnings in the logs, then it's worthwhile to attempt to fix it via the following:

Customers with Cisco Unity subscribers homed on Microsoft Exchange 2007 servers where MWIs are not working shall need modify the registry key UseProfileServerNameForMDB here in the registry:

Registry Key Location: [HKEY_LOCAL_MACHINE\Software\Active Voice\ExchangeMonitor]

Registry Key Name: UseProfileServerNameForMDB

Registry Key Type: DWORD

Registry Key Values:

0 or missing, current default behavior.

1, enables the engineering solution introduced in CSCsu80743

Cisco Unity must be restarted for the key to take effect.

Hailey

Please rate helpful posts!