Here's one you laugh at:<br><br>The scoop:<br><br>AD-120 Build 188.8.131.52<br><br>These guys used a script to stop all Exchanges the Exchange Services while the Voicemail was running ! I know. I know. Needless to to say the Voicemail would not start again after that. After looking at the following errors, I am pretty sure their machine is cooked and they need to flatten it, but I wanted to post just to be sure these poor fellas don't have any options:<br><br>The NT event viewer had this:<br><br>1) Unable to logon to the DOH<br>2) DOH logon failed due to Object caller error<br><br>I had 'em run SysCheck and it said this:<br><br>get the DOH.ccp line 42 <br><br>Are these guys hosed ? <br><br>Thanks for your help<br><br>
Have them try deleting the Unity Messaging System account out of Exchange and then remove the message profile off our local box for the Unity system as well... reboot and those should be recreated on the fly. That might clear the problem.
either way, they shouldn't be toast, just something a little unhappy.
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.