(I apologize if this is showing up multiple times... My posts don't seem to go in now that MS has updated their interface to thsi newsgroup. :(  
Please let me know if any deatils of this are not specific enough, and I can provdie the specifics..

I am having problems with applications that use remoting whenever I have interface functions at the service layer that are overloaded.  For instance,  GetInvoicesByCustomerId( int CustomerId) and GetInvoicesByCustomerName( string CustomerName), or other overloads with varying numbers of arguments.  The error that comes back says something about the service object not being found.  I think that, in particular, we ran into this problem when some overloads took more arguments than others

Our solution was a workaround, whereby we have instituted a poilcy that all interface functions will ahve unique names (no overloaded functions) but this SHOULDN'T be necessary.... Should it?  Is this a known issue in .NET, or could we be missing something?  I'm not real familiar with how all this remoting works too far under the hood.  I can tell you that we're using SOAP for the requests / responses.  We're using C#, if that is of any consequence.  I'd appreciate any feedback on this! :-

Jim