svelxgixoxdbbbqrjv

Hi there, Did you find a solution to this? I'm having the exact same problem with a jrdax file, Studio says it can't find it but it's there. I can get it to preview fine in Studio just once (export the global data adapter to the project, set the default data adapter to the exported jrdax, preview the report and set to the default data adapter) but if I publish to the server it breaks in both Studio and on the server (exactly the same error as you) and the server gives "There was an error on the server" when trying to run the report. Server logs give pretty much the same error as Studio (net.sf.jasperreports.data.DataFile{File: [not available]; line: 4; column: 37}). The only way I can then get Studio to preview again is to delete the data adapter from the project and re-export the global one, then set the default adapter on the report again. This will then work fine until I publish, at which point I get a report that doesn't work on the server or in Studio. Spent ages trying to get this to work without success, despite numerous guides showing this working (I think they may be something in it with your comment on it working on older versions). Thanks. EDIT: This is definitely a bug in the Studio software. Does anyone know where I can report this? I rolled back my copy of Studio (Windows) to 6.12 (using XML instead of jrdax) and it works perfectly. No errors in Studio and the report runs on the server.

I'm trying to follow this and have it working fine in Studio but I just get "There was an error on the server" when I publish. Totally stuck! Can you help? Thanks!

Hi, new to all this and completely lost. I've created a simple JSON data connector in Studio and created a single field, then published to the server. When I try to run in server I get "There was an error on the server. Try again or contact site administrators." and a UID. I'm just learning/testing at the moment so have apun up the Bitnami v8.0.0 release and have noticed that the "JSON File" data source isn't available for selection on the server. Is this the problem? Thanks!