Hi a very odd behaviour especially that you set up a new pool including fresh servers. You might want to open a support case at Microsoft Support for more in-depth support. Please note, the above are just some ideas and thoughts and might be incomplete.
Test if the errors still occurs or is vanished. Re-Run SFB 2019 setup/bootstrapper (all steps, so that it installs IIS vDirs and stuff as needed). Re-Install IIS (SFB 2019 prerequisites as described on I'd just run the powershell prereq script/cmdlet). Manually checking the IIS directories (file directories in C:\.) are removed (if not I'd remove these). Uninstall the complete IIS role on the Windows Server. you try to get the existing Windows Servers in good shape. Either a new pool on new/fresh Windows Servers or. Did you consider to start from scratch? Would that be an option?. Are there any workloads / migrated users already on the server? I'd guess no, right?. In case there is did you configure exclusions or try to turn it off in order to check if than works? Is there any antivirus scanner on the servers?. However, I don't think that the event ID 9009 is the actual root cause. Or delete the folder manually or just renamed it. You could try to set the permissions for the 'C:\inetpub\history' or the 'C:\inetpub\history\CFGHISTORY_0000000064' manually?. Hi me this seems like the IIS configuration was messed up anyhow. Especially the URL rewriting rules and bindings? (actually that's nothing you should have to deal with because the bootstrapper configures it the right way). Did you check the IIS virtual directory settings? yes, all settings are correct. Did you try to re-run the configuration wizard installation process?YES, I reinstall the IIS and WEB Components (also I try to reinstall the pool and install again and it's shown again 503 services. Is there any load balancer involved in front of the pool which might not allow the traffic? No, only I have 3 A record of the pool that points to Each FE server separately. I don't know if it's related to the issue because I get this Event In general. 
The data field contains the error number. Note that the directory may still get deleted in the future if the service restarts.
The directory will be skipped and ignored. If that's not working, too, did you check event logs on the frontend servers? I get this event ID 9009 - The Application Host Helper Service encountered an error trying to delete the history directory 'C:\inetpub\history\CFGHISTORY_0000000064'.However, did you also try to go onto one frontend server and try to open it via macp or /cscp, too? I try its get the same error 503.
0 kommentar(er)
