Trying to move away from Adobe and giving Lucee a shot.
Windows installer seemed to go fine and default Lucee page shows in IIS.
However when trying to load a .cfm page get the error:
Generic Connector Communication Error:
Please check and adjust your setup:
Ensure that Tomcat is running on given host and port.
If this is a timeout error consider adjusting IIS timeout by changing executionTimeout attribute in web.config (see manual).
The source was not found, but some or all event logs could not be searched. Inaccessible logs: Security. at System.Diagnostics.EventLog.FindSourceRegistration(String source, String machineName, Boolean readOnly, Boolean wantToCreate)
at System.Diagnostics.EventLog.SourceExists(String source, String machineName, Boolean wantToCreate)
at System.Diagnostics.EventLog.SourceExists(String source)
at BonCodeIIS.BonCodeCallHandler.RecordSysEvent(String message, EventLogEntryType eType)
at BonCodeIIS.BonCodeCallHandler.ProcessRequest(HttpContext context)
Been working on this for a while with no luck…
Hi @californiaimage and welcome to Lucee! The default Lucee page is a .cfm page so I’m not sure what you’re hitting. Have you created a new site in IIS or are you still using the default IIS site? Also, did you choose to tie Boncode to all IIS sites or a single site? There’s a lot of missing information here to know what you have going on.
To simplify your debugging, try hitting the HTTP port on Tomcat directly. You can find this in Tomcat’s server.xml file in the httplistener tag. While you’re in there, confirm the port of the AJP listener and also check to see if you have other servers installed on your machine that might be trying to use the same ports.
Lucee 5 doesn’t use that separate instrumentation jar. Can you track down where that’s coming from? Check the JVM args in catalina.bat? Just guessing at the file name. I haven’t used the standard installer in years now that I have CommandBox
Confirmed. The Windows service that is created by the Installer uses the service.bat file in the Tomcat/bin/ folder within the Lucee directory:
This batch file can also be used to remove and re-install the Windows service if necessary.
Last, the installer uses Tomcat 8.5, as Tomcat 9 (last I heard) isn’t fully supported by Lucee yet. The fact that this install is showing Tomcat 9 illustrates that this build did not come from the Installer.
@californiaimage Try running the latest Lucee Windows Installer on a clean system and see if you have better luck.
I should be more clear. Was the original error you posted the error you received just after you used the Installer, or after you modified it a bit?
If it was just after you used the Installer (without any other changes), then we can dig into that more. It looks like an issue with the BonCode Connector. So the Lucee install went fine, but connecting it to IIS did not. Can you tell us what version of Windows you’re using?
@californiaimage yes, please back up and show us the steps you’ve taken. Your original post said you simply used the Windows installer, but now you’re telling us that you’ve also been making manual changes to your server following some other set of instructions? These are very important things that you have left out as they completely change how we help you. For instance, I wouldn’t have pinged Jordan if you had told me you were making manual changes that weren’t from the installer.