A virtual directory can be anywhere. That's why the browse button on the Virtual Directory wizard allows you to go anywhere.

Perry

>John,
>
>Can an IIS virtual directory be a network share (where the DLL and WSDL files are located) on a completely separate server box? Or does it all have to reside on the IIS box?
>
>>I had the same problem, I had to do a couple of things to fix. The first was to make sure the ISAPI listener was configured correctly. Here is a Google thread to help with that...
>>
>>http://groups.google.com/groups?selm=O%24VJEkhYBHA.1644%40tkmsftngp03&output=gplain
>>
>>I actually had to uninstall and re-install the latest version of the toolkit to get it configured properly, I couldn't get around the bug in the UI mentioned in the fix. The thread helped me realize what to look for.
>>
>>The second thing I had to do was compile the .dll into the same virtual directory for IIS as where the .wsdl file will reside. That took care of it.
>>
>>Hope this helps
>>
>>
>>
>>>I try to call a webservice to my machine with Vfp7 and MsSoap toolkit 2.0 and i always get a ole error code 0x800a13be Unknown COM status code.
>>>
>>>The Web service is build with vfp7 and it look like generate well and the Wsdl file look's good i think. the security for the directory of the Dll : Everyone Full Control.
>>>