I had something similar recently and it turned out to be .NET permissions on the client Pc, I don't know if MS have changed there policy but installing version 2.0 of the framework didn't install the Code Access Security Policy applet so you need to use the CLI ( good luck there ! ) HTH