I think the trustworthy computing recommendation is to run on client. Did you put the CLR dll in the GAC on the server to allow it to run on the server? Try that. Otherwise, you can use group policy to deploy the dll to all clients and run on client only.
On Fri, Mar 6, 2009 at 8:18 AM, pkpeterson652 <[email protected]> wrote: > Forgot to put in error message being received: > > CLRInteropt is throwing the following error: > > Exception has been thrown by target of an invocation. > > I only get the above error when the class is being run on the server. > > Paul > > --- In [email protected], "pkpeterson652" <ppeter...@...> > wrote: >> >> I have a DLL supplied by a third party to handle WSDL communications with >> their website. >> >> This DLL functions with no problems when connecting to their test website >> which is unsecured reguardless if it is running on client or marked as run >> on server. >> >> However, when connecting to their production site which requires having >> some certificates installed we run into a problem that I'm not sure on how >> to debug. >> >> We have installed the required certificates on the terminal server and on >> the AOS machine. >> >> If the class that calls the DLL functions via CLRInterop is set to run on >> client we successfully connect. If it is set to run on server it fails. >> >> It doesn't matter that my client session is already on the AOS itself or >> on a terminal server it still fails when the class is set to run on server. >> >> Any suggestions on how to debug would be helpful. >> >> Thanks, Paul >> > >
