Associating ISAPI SOAP Handler with WSDL Files in IIS

The information in this article applies to product: e-Work 6.x

Issue

  • When trying to call a web service from a browser, 'Error 405 Method not allowed' is generated.

Resolution

  • SOAP Toolkit 3.0 does not automatically create the WSDL application mapping between the .wsdl file extension and the ISAPI handler (SOAPIS30.DLL). This mapping must be done manually or with the SOAPVDIR.CMD script provided in the toolkit.
  • The following procedure manually adds a .wsdl application mapping to the Default Web Site on IIS 5.0. This procedure assumes that this mapping does not previously exist. Furthermore, while this procedure adds an application mapping at the Default Web Site node, you can use these same basic steps to add an application mapping at a lower-level node, such as the Virtual Directory level.

    To manually create a .wsdl application mapping

    1. Open IIS, expand the server tree as needed, and then right-click the Default Web Site node.
    2. On the 'Home Directory' tab, click the 'Configuration' button.
    3. On the 'Mappings' tab, click 'Add' to add an application mapping for the .wsdl file extension.
    4. In the 'Executable' box, enter the path to the SOAPIS30.DLL file. If you enter this path manually, enter the short file pathname to the SOAPIS30.DLL (for example, C:\\PROGRA~1\\COMMON~1\\MSSOAP\\BINARIES\\SOAPIS30.DLL) because the user interface of the IIS MMC Admin tool does not accept a path that includes spaces.
    5. In the 'Extension' text box, enter '.wsdl' (without the quotes).
    6. In the Verbs section, select 'Limit to' and enter 'GET,POST,HEAD' (without the quotes).
    7. Select the 'Script Engine' option and clear the 'Check that files exist' option. Click 'OK' to enter the new entry.
Tagged: