guys, I'm experiencing a major delay in unity. Have a user complained that he left at 4:30 and didn't see any msgs or mwi, the next day he got the msg and timestamped at 3:30pm. we are running 4.05 on box 2003 server. Pls help in narrowing the troubleshooting steps as the person experiencing the problem is the CFO.
We've seen this on a few occasions. We are running Unity 4.01 and Exchange 5.5. We've seen this delay in the Exchange server.
We've also seen a very slow reponse when users are retrieving messages via the TUI... again, we think this is due to a old, slow Exchange 5.5 implmentation (we're scheduled to upgrade to the latest version of Exchange on a new fast HP blade server Real Soon Now).
On the Unity/Exchange server, start Exchange System Manager. Drill down to the section Message tracking. Do a search for your CFO's Exchange alias and mail server name. You should be able to see the path of the message and the time it appeared in the user's inbox. Check the application and system event logs to see if there are any errors accessing the CFO's mailbox (any services such as AvNotifier or Exchange MTA). I don't think the message was stuck in the UMR, i.e. the repository for external caller messages when Exchange is down. Reason - if Exchange is down, the time stamp of the message is generated when it is submitted from UMR to the message store; and in your post you indicated the time stamp was prior to the CFO checking voicemail. Is your CFO the only one reporting this problem and is it still occurring? If the problem is isolated to one user's mailbox, I would check that area for additional clues - inbox space; was user's mailbox moved; permissions; inheritance 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.