I noticed that after updating Unity and message store with latest recommended Microsoft patches, we are expieriencing delays for message delivery and in turn MWI turn ON (up to 20 minutes). I'm running 4.0.3, I checked port availability and system is well proportion with both Voicemail and MWI/notification.
I've also noticed problems when Unity is started prior to Exchange or when Exchange is restarted, but Unity is not. Make sure that Exchange is running before Unity is started. If this is the problem, you can simply restart the Unity services.
Unity and Exchange box both have the same latest cisco recommended Microsoft Updates (downloaded from cisco software dowloads for unity).
I found that the problem is not with unity or MWI, the problem is in the exchange server "Categorizer". I turned on message tracking and captured some internal message from one mail box to another and notice that the delay occurs in the categorizer, I was wondering if I should re-apply the Exchange roll-up for EXCH SP3... any ideas!!
I don't think reinstalled SP3 rollup will fix the problem with Exchange. Do you have enough memory/cpu? Maybe a reboot will clear your problem. Don't worry about rebooting Unity. It'll reconnect back up to exchange w/o problems.
last night. I Stopped waited a couple of minutes and restarted Unity services on Unity box, and this morning Unity and Exchange are working o.k, I have no message delay, I don't know if this did it, I'll monitor and let you know what happends. Thanks for the help both you and bbuffin
Sometimes Unity and Exchange become out of sync for whatever reason. When Unity goes through the Exchange database to look for IPM's the subscribers mailbox, it makes a note it's own database.. (light on or off) I have had the same issue, where if I just restart the Unity services, it re-scrubs the Exchange database for voicemails and does a count, MWI on/off, etc. If you continually have problems, it could be a slow link, bad links, exchange or unity running slow, etc.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.