Not sure, but you should check the web.config file in the folder of your app and make sure that the script map is actually there. Also make sure that the folder supports script execution and that you allow the Web Connection ISAPI extension in that folder (ISAPI restrictions if the DLL folder is different than the other app).
I've seen some situations where the registration in the IIS management console doesn't put things into the config file which means it's getting created at the wrong level somewhere.
If the app is tied to a single virtual you can also use the managed module which is easier to configure:
<system.webServer> <handlers> <validation validateIntegratedModeConfiguration="false" /> <add name="wc_wconnect" path="*.wc" verb="*" type="Westwind.WebConnection.WebConnectionHandler,WebConnectionModule" preCondition="integratedMode" /> </handlers> <system.webServer>
The nice thing about the handler is that it doesn't have a path requirement - it picks up the module in the bin folder automatically. This means multiple scriptmaps can just be copied and added, then changing the path and name.
+++ Rick ---
from Maui, Hawaii