Sorry for the delay jan.
What if you just restart the jsreport. Do you also lose the content?
Yes. I tried stopping then starting the service, as well as restarting the service. Content loss both times in invoice-template.
What if you create just "hello" template in the root, do you also lose it after restart?
This is what happened when I created a "hello" template in the root with a simple text of 'hello' and clicked on SaveAll
But once I clicked off the message, the save seemed to have completed and I could render the report. I bounced the server and checked Studio. The "hello" content is still there.
Can you try it also in a fresh install outside the VM on your dev machine?
I'll check this one later, if I need to. This is just a test VM with nothing but jsreport on it so I can completely blow it away and start fresh 100% if I need to.
Are there some errors in the jsreport log (logs folder) or if you open F12 browser console?
Nothing in the console/dev tools for either IE nor Chrome.
This is the content of error.log:
2019-11-03T16:08:15.233Z - error: Error when processing OData PATCH: /odata/templates(Ohv7KTEF68ZB6e7a) Error: EBUSY: resource busy or locked, rmdir 'C:\jsreportapp\data\templates\invoice-template'
at Object.remove (C:\jsreportapp\node_modules\jsreport-fs-store\lib\fileSystem.js:93:11)
at persist (C:\jsreportapp\node_modules\jsreport-fs-store\lib\persistence.js:215:14)
at async lock (C:\jsreportapp\node_modules\jsreport-fs-store\lib\persistence.js:294:12)
at async Object.fn (C:\jsreportapp\node_modules\jsreport-fs-store\lib\provider.js:163:9)
And in reporter.log, there are a lot of info entries about Using extension, rs store, and being initialized. However, this error entry looks problematic and associated with the error.log entry:
2019-11-03T16:13:00.604Z - error: Error occured during reporter init Error: EBUSY: resource busy or locked, rmdir 'C:\jsreportapp\data\templates\invoice-template'
at Object.remove (C:\jsreportapp\node_modules\jsreport-fs-store\lib\fileSystem.js:93:11)
at load (C:\jsreportapp\node_modules\jsreport-fs-store\lib\persistence.js:144:14)
With all of the above findings, it looks like the issue is isolated to my specific invoice-template somehow. To test the theory out, I recreated the "Getting Started" example entirely. From root, I created a new "invoice" folder and created new template/sample data according to the guide. I made sure the report rendered and then bounced the server to see what happens on restart. As soon as the server came up, I checked Studio, and my new invoice report was all still there and functional.
I'm not sure what could have happened with my original invoice-template, but being that it was my first experience with jsreport I'm sure it's possible I did something along the way to impact it. Now that I have a much better understanding of the platform and what to look for, I'll keep an eye on it.
Thank you for taking the time to help out a free license evaluation jan; and quite rapidly at that! Much appreciated!