Try using the ASP server component first.

Also make sure that IIS is enabled and that the script ID that is called is allowed. I can't remember offhand but the ISAPI handler uses .wsdl I think as its script map to he Web Service handler and you need to make sure this script map is installed properly (and last I heard it wasn't even under XP) and the extension needs to be added to the allowed extensions.

For debugging in general it's usually better to use the ASP service and switch to ISAPI later on once everything is working.

The SOAP toolkit is such a piece of crap - bad installation, bad client error reporting and no decent docs for the server install.

+++ Rick ---

>I'm getting SOAP errors trying to connect to a WCF web service running on localhost. My first thought it that the SOAP Toolkit doesn't work properly on Vista. I can consume the WSDL and generate the Intellisense scripts and program stub. The error happens when I try to call the web service. Anyone know why I'm getting errors?