>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.

Thanks, Randy, I'll check these out one by one. Sooner or later this will work :).