well young Jedi, I suspect the primary call handler attached to the subscriber template object is missing or pointing back to the wrong template (a condition called "cross linked" handlers).
First, try running the latest dbWalker off AnswerMonkey and see if it's catches any cross linked conditions or stranded mailuser/templates/handlers.
Next, try creating a new subscriber template and then importing a subscriber (or creating a new subscriber) with that template to see if it barks about that.
In general it's a good idea to uninstall your previous version of Unity to get rid of the properties on the subscribers and toast the Unity folder entirely. You can always do this manually in raw mode for Ex55 prior to install but if you didn't uninstall properly (or couldn't) the subscribers will need to be cleaned manually unfortunately. There's no easy/safe way to automate this process for Ex55 (you can use BunnyKiller on AnswerMonkey for AD installs).
that said, all the template and handler information is stored locally on the SQL server. Did you uninstall the previous Unity install at all? It may have left the UnityDB hanging around and the install didn't handle this properly. If that's the case and I were you I'd take the opportunity to uninstall (use the latest Uninstall off AnswerMonkey, just made some fixes this last weekend), manually wax the Unity folder out of Exchange 5.5, clean your mail users (if they aren't already) and take another run at the setup.
If that's not the case, it's probably a fairly simple fixup of your templates.
Jeff Lindborg
Unity Technical Lead/Answer Monkey
Cisco Systems
lindborg@cisco.com
http://www.AnswerMonkey.net (new page for Unity support tools and scripts)
