Thank you , but we already tried that.
Since there's no SOAP on Server 2003, we tried using the "Uses soap" option from the Component Services
At this time, a Virutal directory is automatically created in the IIS containing a Default.aspx
When browsing that Page, we can click a button to view the WSDL but this generates errors "System.BadImageFormatException: The format of the file 'remotequerySoapLib' is invalid."
and more...

Do we have to use the "Uses soap" option in the Component Service?
If not, do we have te manually create the Virutla Directory first? And then create the Component Service?

Thanks

Guillaume


>http://support.microsoft.com/?id=811215
>
>>Hi,
>>
>>We have made a foxpro dll webservice.
>>This runs fine when I deploy it on my local machine (XP) as a webservice with Com+
>>However, on our and most of our customers server, Windows Server 2003 is running.
>>
>>The Init goes fine, but when a method is called, we get a 0x800A13BE error
>>(Sending the soap message failed or no recognizable answer was received)
>>We've tried everything we could think of, including numerous threads from people experiencing the same problem (alas, no answers, only the same problems are stated)
>>
>>The WSDL file IS viewable when looked up thru Internet Explorer.
>>
>>Any suggestion would be helpfull.
>>
>>

>>   x = CREATEOBJECT("MSSOAP.SoapClient30")
>>
   x.ClientProperty("ServerHTTPRequest") = .t.
>>
>>   x.MSSoapInit("http://ipaddress/RemoteQuery/RemoteQuery.WSDL")
>>
>>   ? x.ShowVersion()     &&& This fails
>>
>>   x = null
>>

>>
>>Thanks
>>
>>Guillaume