Hi George,
Any chance the crypto service is sending back illegal characters? Maybe the web service is doing its job, but the SOAP toolkit can't handle the result.
http://www.fawcette.com/vsm/2002_11/online/aspnet_jgoodyear_11_05_02/>Hi Troops,
>
>Got a problem here that has me shaking my head. Here's the deal...
>
>I've created, tested and debugged a C# Web Service in VS .NET 2003. In order to test from another application, I registered it in the VFP Intellisense manager without a problem. I created a program to access it from the code generated. However, when I try to call one of the methods, I get the following error.
>
>
Error: 1429 - OLE IDispatch exception code 0 from Server: Server:XML Parser failed at linenumber 1, lineposition 293, reason is: Illegal xml character.
> HRESULT=0x80004005: Unspecified error
> - Client:Loading the request into SoapReader failed. HRESULT=0x80070057: The parameter is incorrect.
> - Client:Unspecified client error. HRESULT=0x80070057: The parameter is incorrect.
>..
>Server:XML Parser failed at linenumber 1, lineposition 293, reason is: Illegal xml character.
> HRESULT=0x80004005: Unspecified error
> - Client:Loading the request into SoapReader failed. HRESULT=0x80070057: The parameter is incorrect.
> - Client:Unspecified client error. HRESULT=0x80070057: The parameter is incorrect.>
>All this seems to indicate that I'm sending a bad parameter. The only problem is that the method doesn't require a parameter and I'm sure not sending one.
>
>Any ideas?