Saturday, June 26, 2010

Remoting Exception "[...] is not registered for activation"

RemotingException "[...] is not registered for activation"

I had to write something about it, because I was stuck for a whole hour and couldn't google anything useful.

It happens when the Client is trying to create a new remoting class "X".
The Server, by mistake, registered a remoting class "Y".

The classes must have the same name. Fix the class name.
That's it.

1 comment:

  1. It could also simply mean that the remoting server is not running

    ReplyDelete