Hi Guys<br>A client has the following message<br>The specific extension is in use - please enter a unique extension.<br>Yes the customer deleted the user from exchange and not unity like they were advised.<br>We tried the good old trick of killing the call handler from the unity folder, but still same<br><br>What little tool (Jeff), could we use to fix this simply problem. Yes yes a non supported jeff fix-a-rupa.<br><br>Ta<br>C<br><br>
Head out to the answer monkey site below and snag the "dbWalker" utility... this will cruise through and remove any orphaned handlers that might be lingering around in the system (as well as make checks for a bunch of other common problems in the directory and kick out a report).
No, Unity should not have to be restarted... you do have to be logged in as the account that installed Unity, however, for security reasons (I don't want just anyone to be able to attach to our directory and go wild).
Any version of Unity 2.3.4 or later should be able to just install and run. I would have to guess it was a permissions error with the account the user was logged in as. If not, let me know and I can check it out.
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.