Wrong webroot for a new Lucee website on Win/IIS

dev
1

Hi,

when you do something often over the years, but always with an interval of weeks or months, you are likely to overlook details… That happened to me regarding the creation of a new Lucee website on Windows/IIS. The last time 4 weeks ago everything worked fine, but today of many tries each failed… My steps are as follows:

  1. Creation of the webroot C:\inetpub\webroot\NameOfSite

  2. Creation of the website NameOfSite in IIS

  3. Creation of C:\lucee\tomcat\conf\Catalina\w3svc*[nn]*\ROOT.xml where nn is the number of the new site in IIS as follows:

<?xml version='1.0' encoding='utf-8'?> WEB-INF/web.xml
  1. Restart of the Apache/Tomcat service

Normally after the last step or browsing the new site for the first time the directory C:\inetpub\webroot\NameOfSite\WEB-INF is created and the website is ready to run. Not so today - Lucee is placing/searching the webroot of the new site under C:\lucee\tomcat\webapps\ROOT instead of C:\inetpub\webroot\NameOfSite and the configuration file under C:\lucee\tomcat\webapps\ROOT\WEB-INF\lucee.CFConfig.json instead of C:\inetpub\webroot\NameOfSite\WEB-INF\lucee.CFConfig.json. Consequently, www.NameOfSite.com is greeting me with “Welcome to your Lucee 6 Installation”…

I never had to re-run the Boncode Connector Configuration all the past years which is configured to work with all IIS sites.

I had this issue years ago, but can’t remember the solution… So any help is greatly appreciated!

Regards,
Rüdiger Graf

Lucee 6.2.1.122 in Multi Mode
Windows Server 2019
IIS 10 with Boncode Connector

2

Problem solved - turned out that (for whatever reason) the windows account used by Lucee didn’t have access rights for the new webroots… After changing this and restarting Apache/Tomcat, the WEB-INF subdirs have been created automatically and everything works like a charm.