v1.10 windows service: Error generating report when updating templates from file system
-
Hello!
We're running JSreports 1.10 as a windows service currently (jsreport win-install). What we're finding is that when we deploy new reports to QA, which we do by placing the template folders directly into the data/templates path, the PDF reports are not properly returned.
This issue was successfully replicated on a local enviornment, and we retrieved the following error message:
"Error when processing render request Error during rendering report: Unable to find specified template or user doesnt have permissions to read it: Report Error: Unable to find specified template or user doesnt have permissions to read it"
A work around is to run jsreport win-uninstall, and then jsreport win-install. After that, the issue is solved. We'd like to avoid that though, because it makes deployments more difficult, especially if done by someone not familiar with the technology.
Is there anything we can do to avoid this issue from occuring?
-
hi! if you are going to replace templates directory manually then a restart is needed, fs-store can not recognized files that are replaced in this way (specially, it can not recognize the new templates added by this method), it is not needed that you uninstall the windows service and install it again, you just need to restart it using windows services managment tool.
After that, the issue is solved. We'd like to avoid that though, because it makes deployments more difficult, especially if done by someone not familiar with the technology.
i understand, however a re-start is part of normal deploy process, so maybe you can automate this re-start by creating some kind of windows script that moves templates from dev to QA and that it restart windows service automatically, after that.. with that your other devs won't need to do this manually
-
It is very helpful to know you can restart the service through the service manager (or the studio). It's certainly much more straightforward and reliable for a deploy. Thank you much!
