I have just upgraded our Unity server from 4.04 to 4.05..
Everything seems to have installed correctly, so the pre-install check, Exchange 2000 updates, MSupdates, CD images have all loaded and installed ok..
However, upon reboot, I am now unable to reactive the Unity service.. I click on "start Unity " as normal and I can see it attempting to start the service but then it fails.. but it doesnt say why it cant start again..
As far I can see, all the other services have been reactivated again.. Have I missed something really obvious ?!!
Thanks for all your help with this guys.. I have had another go at upgrading again and still not getting any joy.. However, I have noticed a few things in Event viewer after the Unity services fails to restart...
1/ When I try to get the service AvCsMgr to start, it generate an error stating..
"An attempt to access the Primary Exchnage Mailbox Store by AvCsMgr via MAPI has failed , your profile has not been configured "..
2/ After investigating the Cisco error codes, I tried to recreate the MAPI profile by first deleting the existing entry in the registry..
3/ Upon restart, I still get the same error stating that the profile has not been configured..
The upgrade to 4.05 has not removed any of our existing user accounts, which worked fine under 4.04.. However, I have rechecked all the profile permissions and everything seems to be in the correct groups etc..
I don't run integrated Exchange so I can't offer more help than that. If anybody finds the equivalent of this document but it specifies Windows 2003 please post here as well. Some of the services are different in this document on Windows 2000 rather than Windows 2003 but it got me most of the way to where I wanted to be.
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.