I just had a really interesting experience with Unity 4.0(4).
I was suppose to add 16 "new" ports to a system, added them correctly in both CCM and TIM, was going for a restart within TIM but got stuck on shutting down "remote access connection manager". I have seen this ras-issue a couple of times - never thought more about it, rebooted the server and lived happily ever after.
However, after _this_ reboot - no ports would register correctly. All ports showed up as registered in CCM, but when trying to place a call to the Unity the call just kept ringing. Watching current port status never showed the call at all ....
I spent some time troubleshooting this and could find out from the application eventlog that the registration process actually crashed with event 522 from CiscoUnity_Miu (CAvMiuLine lineinit, EVT_AVMIUMSG_CATASTROPHICFAILURE_SEQ_LINE). I got sick of having to reboot to attempt re-registration, so I disabled ras connmgr per instructions for dealing with another issue, after that last reboot - all ports registered and works fine .....
DrWtsn32 did not "see" these crashes.
Is there any practical purpose for "Remote access connection manager" on a Unity server? Can disabling this service cause any other issues?
Sure beats me. Any input?
/M
