E
Eirik Brattbakk
Hi
I have some problems accessing a soap service made in c# using an
ATL/MFC client over SSL. I have tried both CSoapMSXMLInetClient and
CSoapWininetClient as template arguments with my stub class.
The service is returning with the error code: -2147467259. I have not
succeeded to find any additional information about the error. The
"SoapFault" method seems to return only a bunch of question marks.
There is no problem accessing the soap service from the ATL/MFC client
without SSL support. Also, accessing the c# soap service from a c#
client is not a problem (both with and without SSL support). The
sproxy.exe generates some warnings during the production of the proxy
class.
These warnings are:
warning SDL4001 : only one SOAP port will be processed.
warning SDL4004 : skipping currently unsupported element, with
[
namespace = "http://schemas.xmlsoap.org/wsdl/mime/"
name = "mimeXml"
]
Could these warnings cause any problems when using SSL? As mention
before, they do not cause any problems without SSL.
I have also tried to set up an ATL soap server. Using SSL with this
service is not a problem. The problem seems to be when mixing
technologies.
Both c# and Atl soap services are only simple hello world services
made by the Visual Net wizard.
I would appreciate some suggestions.
Best regards
Eirik
I have some problems accessing a soap service made in c# using an
ATL/MFC client over SSL. I have tried both CSoapMSXMLInetClient and
CSoapWininetClient as template arguments with my stub class.
The service is returning with the error code: -2147467259. I have not
succeeded to find any additional information about the error. The
"SoapFault" method seems to return only a bunch of question marks.
There is no problem accessing the soap service from the ATL/MFC client
without SSL support. Also, accessing the c# soap service from a c#
client is not a problem (both with and without SSL support). The
sproxy.exe generates some warnings during the production of the proxy
class.
These warnings are:
warning SDL4001 : only one SOAP port will be processed.
warning SDL4004 : skipping currently unsupported element, with
[
namespace = "http://schemas.xmlsoap.org/wsdl/mime/"
name = "mimeXml"
]
Could these warnings cause any problems when using SSL? As mention
before, they do not cause any problems without SSL.
I have also tried to set up an ATL soap server. Using SSL with this
service is not a problem. The problem seems to be when mixing
technologies.
Both c# and Atl soap services are only simple hello world services
made by the Visual Net wizard.
I would appreciate some suggestions.
Best regards
Eirik