When you say "adding the COM server into component services", do you mean COM+ ? I'm actually working with the same issue on 2003 Server with a VFP COM mtdll, so, maybe we can help each other out. Like you, it works beautifully from Win2k Server and XP Pro.
Getting the vfp mtdlls to work with IIS shouldn't be any problem at all, at least that's been my experience up until 2003 Server. The ActiveVFP tool I created usually installs and runs a sample demo web app in 1 step with no manual configuration...
>We have run into the rights issues you talked about before, so that was the first thing we checked. It seems that after adding the COM server into component services, the registry information just "goes away".
>
>To answer your question about why we are using a COM .exe server is that we haven't had any luck getting our compiled .dll's working on the web servers. They seem to compile in just fine, but just won't work when we call them from our ASP pages. It's something we are looking into though, because we have noticed requests starting to stack up sometimes.
>
>Any ideas on how to fix / improve our situation?