Connector - Bad request to the server

[dleman]

Hi!,

Having problems runnning the DocSample from the SOAP beta 2.0 help sample.
Can anyone help with the following error.

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
- <SOAP-ENV:Envelope
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
- <SOAP-ENV:Body>
- <SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server</faultcode>
<faultstring>Connector - Bad request to the server.</faultstring>
- <detail>
- <mserror:errorInfo
xmlns:mserror="http://schemas.microsoft.com/soap-toolkit/faultdetail/error/"
>
<mserror:returnCode>-2146823238</mserror:returnCode>
- <mserror:callStack>
- <mserror:callElement>
<mserror:description><HRESULT>800a13ba</HRESULT></mserror:description>
</mserror:callElement>
</mserror:callStack>
</mserror:errorInfo>
</detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

[Roger Wolter]

One possible cause for this is that the ISAPI didn't get registered properly
on the server. Try the following from the FAQ:

1.14 Why doesn't the ISAPI work on my virtual root?
When the ISAPI is installed, it registers itself to handle ".WSDL" files.
SoapToolkit 2.0 installation does this by creating an "App Mapping" to
associate the ".WSDL" extension with soapisap.dll at the machine (server)
level. If the "App Mappings" have changed at a lower node than the machine
level (such as at the "Web Site" or "Virtual Directory" level) prior to
SoapToolkit 2.0 installation, then the newly added ".WSDL" mapping will not
be inherited from the machine level settings. In this case you can manually
enter the "App Mappings" at the lower level node using the IIS MMC Admin
tool.

For example here are the steps to manually add the "App Mappings" for the
"Default Web Site" on IIS 5.0 using the IIS MMC Admin tool:

1.) Select the "Home Directory" tab under the properties for the "Default
Web Site".

2.) On the "Home Directory" tab click the "Configuration" button and select
the "App Mappings" tab.

3.) If the .wsdl extension does not exist, then add a new extension entry
for .wsdl by clicking the "Add" button.

4.) Enter the path to soapisap.dll. Note: Because of a bug in the UI of the
IIS Admin tool a pathname with spaces cannot be added. To workaround this
problem enter the short-file pathname to the soapisap.dll (Example:
C:\PROGRA~\COMMON~1\MSSOAP\BINARIES\SOAPISAP.DLL). Enter .wsdl in the
"Extension" text box. For "Verbs" select "Limit to" and add: GET,POST,HEAD.
Finally, "Script Engine" should be checked and "Check that files exist"
should be unchecked. Now click "OK" to enter the new entry.

Note: Although, the above steps will add the "App Mappings" at the "Default
Web Site" level, the same procedure can be followed at a lower level such as
the "Virtual Directory" level.

"dleman" <danny...@hotmail.com> wrote in message
news:eL#8Su#sAHA.1960@tkmsftngp03...