03-31-2006 04:26 PM - edited 03-18-2019 05:44 PM
Unity 4.1.1, now integrating solely against Call Manager!
Last evening I removed the Dialogic cards from my Unity server, following the simple 33-step process outlined in the Unity Reconfiguration Guide (http://www.cisco.com/en/US/customer/products/sw/voicesw/ps2237/products_upgrade_guides_chapter09186a0080205a8d.html#wp1038715).
All went well, except that the Unity service refused to start. Event viewer indicated that the AvCsMgr service cannot start because it is dependent upon nonexistent service 'Dialogic'. I guess that'd be the 34th step!
My solution, short of reinstalling the software, was instead to remove the Dialogic dependency (in Hex, and I left TAPI in place) from the registry key for the AvCsMgr service and reboot the box. Once I did that everything started up just fine.
My questions: What have I done to myself? Will I regret, come upgrade time, having removed this dependency manually? Is it really that simple? Has anybody thought to adjust the reconfiguration guide referenced above with that 34th step?
Thank you,
- Tony -
Solved! Go to Solution.
03-31-2006 05:38 PM
I think you will be fine. On an upgrade Unity deletes all of its services and then reconfigures them again, so I have no reason to think there will be any lingering affects of this after you upgrade.
The Dialogic uninstall should have removed this dependency, so this extra step is not typically necessary.
03-31-2006 05:38 PM
I think you will be fine. On an upgrade Unity deletes all of its services and then reconfigures them again, so I have no reason to think there will be any lingering affects of this after you upgrade.
The Dialogic uninstall should have removed this dependency, so this extra step is not typically necessary.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide