New install on a Windows 2016 server. Works in File mode, getting this error when trying to load servers under COM.

Unable to load server - Access Denied. Active account: DefaultAppPool

It's clear that we don't want to be running against the Default App Pool. We did create a West Wind Pool per the documented instructions, though we initially forgot to set the flag to Enable 32-bit Applications. That's been corrected, but it's still pointing to the Default. I just need to associate the West Wind pool with my WConnect virtual directory. As I recall, changing that association was a trivial process under older versions of IIS, but I could not figure out how to do it under IIS 10.

Can someone point me in the right direction?

Thanks.

--stein

You need to change the identity of the Application Pool or if you have a custom pool make sure you actually assign it to the Web Site.

+++ Rick ---

if you have a custom pool make sure you actually assign it to the Web Site.

I understand that. I have a custom West Wind pool. I just don't know how to assign it. I want associate it with the virtual folder that hosts my application. That usually happens automatically but in this case it's pointing to the Default App Pool and I haven't been able to get it to use the custom pool.

--stein

It's in the Basic Settings for the site or virtual.

Make sure you are not using a Virtual but an Application in IIS. Virtuals are just folder mappings, Applications are virtuals with an Application Pool and full root configuration mapped to them. You probably have a virtual which is why you can't set the Application Pool.

+++ Rick ---

Thanks. I suspect application vs virtual is the issue as I'm pretty sure our legacy installer creates a virtual by default. Though I don't recall having app pool issues on other sites which would have been set up the same way.

--stein

If you're using the Web Connection IIS config classes it will always create Applications, never virtuals (even though it says create virtual) as Web Connection applications are considered to be 'Applications' in the IIS context.

+++ Rick ---

Our installer does use your config classes but the problem is that I haven't updated it in some time so not sure how current they are. Not to mention that it's been years since many of these sites were originally set up.

--stein

We use a custom installation program that sets up some stuff that's specific to our app, then launches the Web Connection server setup wizard. I tried to integrate your setup classes so that things would work the same as if it was run from the Console exe. It worked fine when I set it up a few years back, and I've been recompiling it periodically as WC updates are released.

However, digging into the source shows what appears to be deprecated code:

FUNCTION DoConfigureServer  && loWiz does the work based on the data typed into oWiz 
LPARAMETER loNP

loWiz = NEWOBJECT("wwAppWizard","wwAppWizard.prg") 

...given that wwAppWizard.prg hasn't been updated since 2014. It looks like that functionality now resides in the WebConnectionConfiguration class, so I modified my code accordingly

SET PROCEDURE TO WebConnectionConfiguration ADDITIVE 
loWiz = CREATE("WebConnectionConfiguration")

I ran the updated code on our test server (running Server 2012) and it did create an IIS Application. But what it did not do was generate the specified script maps, nor did it even generate a web.config file. There was no error or warning posted - it just didn't set up the mappings. Any idea what I might be missing?

We can of course create the handler mappings manually but I'd rather not put that responsibility on our techs.

--stein

Yes the class was renamed and there have been a few changes but this should have no effect on the old code or the underlying raw IIS integration features.

Realistically I would look into creating a simpler interface that just lets you pick the things you need and then run a simple scripts that's more akin to the new project features that let configure sites via code.

That'll be a lot easier to manage and keep up to date and modify than trying to deal with the complex logic inside of WebConnectionConfiguration.prg.

To get an idea what that looks like you can create a new project and look at the generated <yourApp>_ServerConfig.prg file.

More info in the docs:

• The generated Server Configuration Script

+++ Rick ---