Title:
Silent installer - breaks ALL IIS connection pools - check params before doing anything
| View in TrackerStatus/Resolution/Reason: Open//
Reporter/Name(from Bugbase): Doug C. / ()
Created: 02/05/2020
Components: Installation/Config, Lockdown Installer
Versions: 2018
Failure Type:
Found In Build/Fixed In Build: /
Priority/Frequency: Normal /
Locale/System: / Win 2016
Vote Count: 0
I had run the lockdown tool in silent mode but a typo in the properties file for the “SILENT_WEBSITES_TO_LOCKDOWN” attribute (web site didn't actually exist) caused all connection pools to have the code management attribute set to null which stops them ALL!
I would expect the lockdown tool to fail if it can’t find the website entry which it did but it seems to have setall the application pools .NET CLR version: to null.
This caused them all to stop with not much idea of why. Eventually I figured it out and set them back to "No Managed Code" which fixed the issue.
Requested features:
1) The auto lockdown tool should sanity check these entries first before do anything and log the problem.
2) If it can’t find a site the lockdown tool should NOT affect any other sites
3) Failure logging can be much betterAttachments:
Comments: