Hi, the messages posted are not errors. Are there actual error messages in the logs? If it worked before installation of the windows service, I would suggest you verify the datasource settings, because the windows service would be running under a different user thus the configuration files could be in a different location.

Anders,

Thanks for replying.  The error is the same error posted on the thread How to overcome Security Violation (Code 403), as far as errors in the logs go there wasn't anything quite so obvious as the entry I posted which has the same 403 error listed in it.

This doesn't have anything to do with datasource settings, directory locations or user credentials as I was able to work around the problem by commenting out the CSRFGuard entries  in the web.xml.  Everything is working correctly now but I assume those entries exist for a reason and was hoping that someone could explain how to resolve the problem properly or look at why it is failing under this scenario.  I certainly would be reluctant to run it this way if this were a public facing or publicly hosted site.

Originally I was using jdk 13 so I tried downgrading to v8 but that also did not resolve the issue.  It's possible that the version of Tomcat is also a factor (v8.5.50) but that seems unlikely - I believe the issue to be in the joget code itself.

If there is anything else that I can provide to assist in debugging this problem, please let me know.

Regards,

ps

Are you running the service behind a web server or reverse proxy? If so, then you need to configure it correctly like in the question IIS Reverse Proxy For Joget (Tomcat)

Neither, it is being used internally and directly connected.