It happens very frequently that IIS will not get provisioned for a site if fcgiext.ini is presumably locked. (The skeleton is created, but the virtual IIS server is NOT created.)
If you then change the physical hosting details, and save the hosting info, the fcgiext.ini is correctly written, but IIS won't get reprovisioned, rendering the site useless. (Since the virtual IIS server still isn't there.)
The only 'workaround' I have found is to backup the site, delete it, recreate it without any hosting and restore the backup.
This is a pain.
What's locking the fcgiext.ini file? If I manually check it, it's not locked or in use by any other process.
Tino
If you then change the physical hosting details, and save the hosting info, the fcgiext.ini is correctly written, but IIS won't get reprovisioned, rendering the site useless. (Since the virtual IIS server still isn't there.)
The only 'workaround' I have found is to backup the site, delete it, recreate it without any hosting and restore the backup.
This is a pain.
What's locking the fcgiext.ini file? If I manually check it, it's not locked or in use by any other process.
Tino