Hello,
We have a web farm of 4 servers running Windows Server 2012 R2 64-bit (IIS 8.5) using shared config and have performed the following:
- Installed Application Initialization feature on all 4 web servers.
- Set preloadEnabled=true on all websites (reflected on all 4 web servers due to shared config)
- Verified that each websites app pool is set to Start Mode= AlwaysRunning
- Performed a combination of recycling all app pools, IISReset, and even rebooted all 4 web servers after performing the above.
From my reading, this is the minimum requirement to have the first initial request hit the site and precompile.
Our website is a .NET web application and the initial page is a login page for users to sign in (i.e https://demo2.tdfanywhere.com )
However, even after verify and validating all of our settings, we noticed that none of our sites are being initialized like we would have thought.
Does anybody have any more insights on to why Application Initialization is not performing as expected? I've used Process Explorer to watch the w3wp.exe process for one particular site and recycled the application pool several times, but the .NET assemblies are not loading, verifying that the site is not initialization at all. Is there some sort of limitation when your web servers are in shared config mode or something?