This sounds like a DCOM permissions issue. One possibility is that the Access Permissions are not set the same as the Launch Permissions for your server application in DCOMCNFG.

Another possibility is the Default DCOMCNFG access and launch permissions are not set properly. For some reason, this is required even if your application has its own settings.

A third area to check is whether your VFP server (EXE) is compiled as "single use" (not multi-use).

Also confirm that your virtual directory setting for application protection is set to "Low (IIS Process)".

If these all come up empty, there have been situations in the past where the built-in IIS user accounts have become trashed (IUSR_machinename). One reason is machine name being changed after IIS is installed. The solution to this, I believe, is removing the accounts and getting IIS to recreate them.

-- Randy

>I'm not exactly a newbie in neither WWWC nor COM - but usually I've come to work on it when someone else did the groundwork (i.e. setup).
>
>Now I'm starting a new WC site, and I decided to go for COM for speed's sake. And it looked cleaner, anyway.
>
>I've got it to work, but -
>
>The first request goes wheezing by, it pulls few dozen records off the SQL server (on the same box, for now) and the page displays within twenty milliseconds. The next hit, then, goes
>
>Invoke failed with err code 80070005: Access is denied.
>
>First I thought it may be the two servers stepping on each other's toes, so I switched to one server - but the same happens. Second request actually kills the server (the status form goes away, which I can see via remote)... except that it's still stuck in memory. If I kill it (remotely via task manager), the next call gives
>
>Invoke failed with err code ffffffff:
>
>Then the next call launches yet another server, which then does fine once. Next call, it vanishes from the task manager's list (the old one is still there), and the result returned is
>
>Invoke failed with err code 800706bf: The remote procedure call failed and did not execute.
>
>The only way to get these unstuck is to call admin page (which shows no servers running), put them on hold, then switch again. Then it works once more.
>
>I figure I've done several things wrong... but some of this doesn't really make sense. Should I call .RevertToSelf() at some point? I see that, when I click "re-read configuration" on the ISAPI Settings page, it now shows SYSTEM for current user, where it first had shown IUSR_.
>
>And there should be a more detailed error log somewhere... I'll dig it out. The error log shows just
>
>07/03/2005 22:17:09:171 Forced Release of Server - 0
>07/03/2005 22:17:09:171 Web Connection Request timed out. - /stchain.wc?id=974 - 0