An infinite loop on a call handler can happen due to a configuration problem. A classic example would be you have a call handler's after greeting action set to go back to the same call handler. Even worse, if you have no greeting recorded and you hit this box, it'll "spin" like a top and cause all kinds of problems. The CDE (Conversation Development Environment) catches if you've entered the same handler object more than X times on a single call and will terminate the call with a message similiar to what you're seeing.
There are other possibilities, of course, but this is the most common.
If you pop open DOHPropTest under commserver\tech tools (don't enter a password, just "ignore" the error box and go into read only mode) and copy that string after the "Object=" in the error message into the dialog that comes up when you click "FindByOID", it'll take you to the object (call handler) in question. THen go check this guy's configuration out in the SA to make sure you don't have any looping conditions on that guy.
Jeff Lindborg
Unity Product Architect/Answer Monkey
Cisco Systems
lindborg@cisco.com
http://www.AnswerMonkey.net (new page for Unity support tools and scripts)