I am designing a system that uses an ASP.NET webservice to call methods on a
remoting singleton (I need the singleton to keep alive some specific COM
instances as the COM components exist and the budget to migrate them
doesn't).

I believe I either have an architecture problem or a configuration problem.
I can make one call with the webservice but any subsequent calls return a
remoting exception saying:

"Attempt to redirect activation of type 'A.S, A' which is already redirected"

I am using a configuration file and calling
RemotingConfiguration.Configure(web.config) either in the webservice
constructor or in the particular method being called prior to calling the
singleton method. I assume there is something wrong with this approach but
can find no reference on how to setup the remoting connection in this
situation. Is there another way I should be using to get the remoting system
up and running? I've been assuming that the webservice is starting fresh with
each call but apparently that is not the case.

Any help would be most appreciated.

Thanks,
Bill Strong