Setup is always a bit more complicated in Windows.
In tomcat8-stdout*.log you’ll notice these lines. This tells you where the application expects to find the configuration files.
Using configuration locations [classpath:openboxes-config.properties,
classpath:openboxes-config.groovy, file:C:
\Windows\ServiceProfiles\LocalService/.grails/openboxesconfig.properties, file:C:
\Windows\ServiceProfiles\LocalService/.grails/openboxes-config.groovy]
[production]
In tomcat8-stderr*.log you’ll notice these four lines are stating that none of these files have been found on the file system.
Unable to load specified config location classpath:openboxesconfig.properties : class path resource [openboxes-config.properties]
cannot be opened because it does not exist
Unable to load specified config location classpath:openboxesconfig.groovy : class path resource [openboxes-config.groovy] cannot
be opened because it does not exist
Unable to load specified config location file:C:
\Windows\ServiceProfiles\LocalService/.grails/openboxesconfig.properties : C:
\Windows\ServiceProfiles\LocalService\.grails\openboxesconfig.properties (The system cannot find the path specified)
Unable to load specified config location file:C:
\Windows\ServiceProfiles\LocalService/.grails/openboxesconfig.groovy : C:
\Windows\ServiceProfiles\LocalService\.grails\openboxes-config.groovy
(The system cannot find the path specified)
My guess is that if you created a configuration file (openboxes-config.properties) then you likely created the file under %USER_HOME%/.grails because that’s what the installation instructions say to do. But with Windows, Tomcat is executed as a service with a configured run-as user account (“LocalService”). That means the configuration files should be under the home directory for that user, which seems to be …
C:\Windows\ServiceProfiles\LocalService
