We're currently experiencing an issue where aupair.exe would consume 100% at random times and it doesn't happen everyday, more like once every other week. We are running 4.1(3) and it has happened at least once on each subscriber/publisher. Most of our callmanagers, with the exception of toronto are located at the same site. Any ideas on what maybe causing these spikes? I have looked at the tac collection tool and the stated solution is to restart the db layer monitoring service. However, this is a reoccuring issue. Does anyone have any idea of the root cause and what maybe the solution?
Yes we got the chance to reboot the cluster during dst patching. We have a case opened with tac and they want us to hard code the duplex settings on the nic and switch. Thanks
Btw, I could only lookup the last bug in your list. The first two were not found in the bug toolkit.
