We have unity 2.4 on Windows 2000 with SP1. After rebooting the system avcsmgr would not start. Reinstalling unity made no difference. Service pack 3 on exchange 5.5 Neither did rebooting help.<br><br>How do you get the thing started again.<br><br>
Well thats kind of a tough one to answer without looking at your system. The first thing to check is the Application Event log. When you start Unity up youll see a series of events logged for Create then for Init then for Run. These are all the many parts of Unity coming up one after another They need to be created first, then they all initialize then they all run. Only when all of them finish this process will the AVCsMgr service start. Somewhere along this chain of events youll see an error and then youll see the a series of events where were shutting down the components and stopping.
You need to find the error (or errors) that are causing the startup sequence to flame out on you and look at the description. It should give you (and me) a clue where to look next.
Things like the TAPI driver not being loaded properly, the key not being programmed right, the account associated with the service not having appropriate rights (i.e. someone removed some rights after install), etc etc lots of things it could be. Take a look at the log and go from there.
Is the box installed as a domain controller? If so, you most likely have an LDAP problem which will stop the avcsmgr from coming up (You will also have a DOH error in the event log). Solutions to the LDAP problem have been posted in this message base, although will most likely require another clean re-installation of Unity.
Just for the record... this particular problem turned out to be that the Unity Messaging System account was hidden in the Exchange directory... this causes us all kinds of problems because in Exchange 5.5 when the object is hidden you can't find it in the directory via LDAP, even if you know the full name. Very annoying.
This happens from time to time because folks don't want that accoutn showing up in the address book. That's understandable, but we don't really have much of a choice in the matter.
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.