Not sure if anyone else is running into trouble when using the _serverconfig application to configure IIS. When I execute this against IIS 7.5 or 8.5 it runs without error but, after checking in IIS Manager, I see that all existing websites and applications have been changed to the same app pool, WebConnection. I expected this to only happen to the one virtual app that was named in the config file. Obviously this creates a problem; the recommended config for this version of IIS is to use one AppPool per site/app. There is a unique AppPool account created for each new AppPool. Although the account will not appear in the OS user list, it can be identified for permissions by using the Check Name button against IIS AppPool\<AppPool_Name>. This account can be used to set all required permissions on your site, including the ability to Launch & Activate the COM Object. Maybe the *_serverconfig.prg was written for earlier versions. The code uses the WebServer library, wwiisadmin class. I'm looking into that now to see if there's anything obvious. Feedback is appreciated.

-Rob

If this is happening that's a bug - the configuration is only supposed to set for the selected site or virtual application. This is the first I've heard of this issues, so I'm not sure if this is a configuration issue or a real problem off the bat. There's been very little feedback around these relatively new server configuration features unfortunately so I have no idea how widely used - beyond what I use myself are.

Did you create the site first? I suspect the issue is that an invalid site id to configure was specified and that might be causing the issue. The site has to exist (without any further configuration) and then you can run the configuration tool against that site. I've set up a number of sites like this without ending up with a single AppPool to all sites - I run 20+ sites on my server and I would have noticed 😃

+++ Rick ---

Well, I have modified the <myapp>_serverconfig.prg to suite our needs, so it's possible the bug is there. I'll look into this more later.

We're going live with our app on Aug 1st at https:\\etrac.ticketcostars.com\portal\<portname> with fairplex, adventuredome, and frightdome as portals; more will be added in October. I do want to acknowledge how great your support has been Rick. You've been very responsive and that's given us all the confidence we needed to move forward. We're also extremely pleased with the performance of Web Connection and it will get a good load test once the LA County Fair starts in September. We're using it not only as a REST Server for online ticket sales, but also for moving transaction data from about 100 POS stations to a central database. The architecture is 100% Foxpro, no SQL Servers involved. We'll let you know how it goes.

Thanks Rob. I can look at other issues we discussed when I get back from my trip, but it'll be after the 1st.

As to support I am keeping this tool going because I know that there are lots of people still depending on it. It works well for what it is but overall FoxPro as a Web Server backend has its limits. Most applications can easily live within those limits however, and it'll be interesting to see how apps do on that monster of a machine you're running it on.

Aloha,

+++ Rick ---