Deploying a FoxISAPI Application

[ontsjc]

Hello,

I wrote a small web app using FoxISAPI with VFP 9 SP1. On my XP development Machine it works great. When I try to deploy it to the windows 2003 server, I can't get it to run.

I've set my directory and virtual directory structure the same on both machines. Just as a starting point, I set the security to full rights for everyone (I don't intend to keep it this way, it is on a corporate intranet and I intend to back this down as soon as I get the site working). I've put all the runtimes (even the one's I don't need) in the execution path and registered those that need registering). I've registerd the COM server I created. I set the permissions on the two databases I have.

The one thing that doesn't seem to be the way Microsoft says it should is the DCOMCNFG. When I run it, it brings up the Componet Services window and I can't find my COM object listed to do anything with it. All the windows are not as described either.

The error I'm getting when I try to call the site from IE just from a localhost call is the standard 404 explorer error.

All the site does is display some pictures, allow the users to vote for the pictures they like best and logs those votes. I've compliled it as a multi threaded dll. There are no independent html pages, I've just had the com object return some very basic html code to build the pages on the fly. I realize this is kind of a non-descrip question, but is there anything obvious that I may have overlooked? Thanks for any help you maybe able to provide.

 

[Mike Gagnon]

The one thing that doesn't seem to be the way Microsoft says it should is the DCOMCNFG. When I run it, it brings up the Componet Services window and I can't find my COM object listed to do anything with it. All the windows are not as described either.

Does this mean that you were not able to add your COM to the component Services? If so that would be a place to start.
I wrote something on the subject a while back (Sorry, its in French), but perhaps the screen shots are the same are yours.

http://www.atoutfox.com/modules/articles/mht/0000000079.mht

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.
ReFox XI (www.mcrgsoftware.com)

 

[ontsjc]

Hi Mike,

Its been a long time since I've had the opprotunity to read French. I'm rusty, but it's fun. So if I'm getting this correct. XP/Server 2003 has changed the way DCOMCNFG operates. The main articles out there that I've found on MSDN and the like are NT 4 through 2000, but not updated for the newer operating systems.

So you add an empty application first, then associate your COM object that has already been registered and then you can set your user permissions. I'm assuming that your empty application should be named the same as the Componet.

I'll give it a try and let you know how it goes, thanks for the response.

 

[ontsjc]

Hi Mike It worked! There was one other issue as well. I had tested the site with IIS 5.1, I was trying to deploy it on a machine using IIS 6. When you add in foxisapi, it automatically filters it in the ISAPI filters area and I had to configure it to "Allow all unknown ISAPI extensions". Once I did that, it worked great. Not a very big program but it is super fast. Thanks for your help again, and the opprotunity to brush off my French.

 

[Mike Gagnon]

I am glad it worked out for you (Reading French that is );-)

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.
ReFox XI (www.mcrgsoftware.com)