Remote Serviced Component Auto-registers
-
This is driving me crazy, not because it doesn't work, but because sometimes it does! Maybe I just shouldn't be trying to work in this manner at all, however, here is a simplified version of the problem. I have a serviced component (Business Rules) written in .Net 2.0 installed on Server1. This calls other stuff including SQL 2005 I have a WebService written in .Net 2.0 installed on Server2. The Webservice code calls the serviced component. A .Net Windows Forms client calls this webservice. If Server1 and Server2 are infact the same server then there are never any problems, however, in the two server environment some methods cause the serviced component to auto register on Server2 (the web server). Consequently the method errors as the identity is not configured correctly. Of course it isn't it should never be configured at all on Server2! I have two methods as examples. 1. public System.Data.DataSet GetContactById(System.Guid id, string UserName) This works fine. 2. public System.Data.DataSet GetOtherContactById(System.Guid id) This auto registers the Serviced Component. Unfortunatly this is just a small part of a huge application and my attempts to replicate the error on a small scall have failed. Has anyone come accross this behavior?
If you have knowledge, let others light their candles at it. Margaret Fuller (1810 - 1850)