Hmm, not a lot to go on, buutttt ...
What borked the install of Clam, at what point did it fail, lockup, reboot the server, or whatever?
Try running the Clam install script from Jesper Knudsen to 'repair' stuff.
Try issuing the command /sbin;e-smith/signal-event post-upgrade to force SME to reconfigure itself (followed by a reboot of course).
I can't think of anything offhand in the Clam install routine that would affect the server manager unless the panel installation was the componenet that failed thereby leaving the server manager somewhat screwy. A manual un-installation of the panel and clam may be an option.
Make sure that userpanel (if installed) is good - perhaps doing a --force of the rpm may help.
Thats all my 'stream of dribble' can come up with for now

Good luck