This has to do with the funky way that FoxISAPI uses the extra path and IIS in its default configuration is not properly finding the DLL.

The other thing you want to do is set the FOXISAPI virtual directory to execute in Low Process Isolation. The error message seems to indicate that the COM+ application can't load properly. You might want to try an HTM or ASP page in that directory first to make sure it all works.

+++ Rick ---


>I installed the Foxisapi samples in a Windows NT 4.0 SP6 server and it works fine. I moved the same application to my personal PC running Windows 2000 profesional and IIS and it does not work anymore.
>When I issue: http://localhost/foxisapi/foxisapi.dll/reset I get 'The page cannot be displayed'. Also an entry on the NT event viewer shows up that says : Source: W3SVC Event Id: 36. The server failed to load application '/LM/W3SVC/1/Root/Foxisapi'. The error was 'No such interface supported'.
>I checked and re-cecked the security setting for the Foxisapi folder and the user IUSR_ and still does not work. I will apreciate any help.