Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Unity 4.05 MWI bug?

Unity 4.05 on CCM:

Had a complaint regarding intermittant MWI delays and looked at the system. Found the following in the event log:

Event Type: Warning

Event Source: CiscoUnity_Notifier

Event Category: Run

Event ID: 1008

Date: 1/19/2007

Time: 9:07:18 AM

User: N/A

Computer: WFUNITY


Received message event eNOTIFYQ_ACTION_MSG_NEW [2] on NotifyQ for user cn=WOZENILR,cn=Recipients,ou=First Administrative Group,o=WeirFoulds who is not monitored. No MWI or notifications will occur for this user. To correct, perform a resync of all mailusers with UTIM: go to the Properties tab of your integration and press the Resynchronize button.

This is an account with no Unity mailbox (probably deleted) - According to an earlier bugfix CSCeg82723 on 4.04 there was a problem with a MWI request stuck in the queue if it was outstanding at the time of the Unity mailbox deletion.

Is this not fixed in the 5.05 version?

I did a MWI resync and the error is still repeating.




Re: Unity 4.05 MWI bug?

Why don't you try adding the Subscriber again, make a MWI resync and then delete the subscriber again.

Re: Unity 4.05 MWI bug?

There are a couple Engineering fixs for 4.0.5 and also SP1 which fixes other problems in this version. MWI problems can also be related to TSP versions loaded on Unity. Make sure you have the latest and greatest TSP software loaded. If the TSP ports flake on you during MWI dial outs, Unity may get this error.

You could also have an orphaned subscriber account. In AD, if the account has been disabled, MWI's will fail. If the account has been deleted from AD, it usually will remain in Exchange until purged. Open up Exchange and check for their old mailbox. If it has an "x" on it, it just needs to be purged then Unity may ignore it then.

Possibly also, a quick Unity reboot is in order. Unity will then reconnect to AD, sync up it's SQL database with AD and possible purge this orphan out.

good luck!