Michael Bielkiewicz

There are several ways to attempt the upgrade. Our docs present one way. What I usually recommend is to install the new server (9.0) on it's own, then export ALL from the old server (either via command line or the UI), then import that export into your new 9.0 server. With no customizations, this should work ok. If your test worked and you've tested all your reports and resources, you should be fine to continue down that route as well. Good luck! -Mike

Can you let me know if you now see a "Create" option at the top of the screen when on our community website? There were some issues with it not displaying for everyone, but I do see it now myself (where I didn't before). -Mike

Unfortunately, this is likely due to our recent transition to this new website. Let me research this a little and get back to you. -Mike

I've never had this problem myself, so I'm not exactly sure what the issue could be, however you used to be able to report bugs via the ladybug icon from within the application (on the toolbar). I believe that essentially posted the bug to the old community site so now that we've just moved over, I'm not sure if that still works. Please give it a try and I will ping our Studio team internally to see if someone can chime in. In the meantime, I do see we have our Tracker feature here on the new site - I would post this issue there as a bug with Studio and perhaps the Studio team can get to it that way. -Mike

I've never had this problem myself, so I'm not exactly sure what the issue could be, however you used to be able to report bugs via the ladybug icon from within the application (on the toolbar). I believe that essentially posted the bug to the old community site so now that we've just moved over, I'm not sure if that still works. Please give it a try and I will ping our Studio team internally to see if someone can chime in. -Mike

This is a very vague issue, to be honest. There are many things that could possibly be wrong - if Tomcat is running (you can verify this by following above instructions), and you still can't reach Jaspersoft, that means the Jaspersoft application did not startup properly or you aren't hitting the correct URL. I don't want to repeat everything from earlier in this old thread, so can you post your specific issue and include anything you see in the catalina.out log that looks like an error on startup? That's really the only way to troubleshoot this issue.

Is the issue contained within Studio itself (during Preview maybe?) or are you talking about after publishing the report to the Server (or executing it via library or whatever) when you see the issue? Can you provide the jrxml (at least the snippit with the table of contents where you see the issue?

Are you talking about when you export a report to a certain format? If so, the only way to do this would be to customize the code behind the exporter. Can you provide more details about your process so I can let you know how you can accomplish what you need? -Mike

While I don't have much experience running JSS on Linux, I'm thinking you can try to increase the memory allocated to Studio on startup. It could be running out of space. This is done in the "Jaspersoft Studio Professional.ini" file in the installed location. You can also try to change out the Garbage collection method identified in that file to G1GC as that's generally a bit better at keeping memory consumption issues down. See https://community.jaspersoft.com/wiki/changing-garbage-collection-g1-tibco-jasperreports-server for more details on that (same settings should work for Studio in the ini file noted above). I don't believe the Java version would be an issue, however our JRS product only supports up to Java 11 at this time...you could try an older version than the one you are currently running, but I'd try the memory/GC settings first. I hope this helps. -Mike

We don't have a lot of Python experience, but I would suggest looking into our REST API. If you can make a call to JRS via REST, you can pass anything you want and run any report you have access to.

What do you mean "redeem Jasperreport" ??? Are you asking to download it? That version is probably 12 years old and hasn't been available for maybe 10 years.

You can also try adding the fully qualified classname before your Scriptlet references (i.e. "com.something.my.package.St3kDefaultScriptlet")

It seems to me that something is wrong with your compiled JAR. I do not sign any custom JARs that I create - I would try to recompile it with various options - should be pretty plain/vanilla. Also, ensure you are compiling to the same version of Java that you have deployed on your server (i.e. if you are running JRS with Java 8, make sure your IDE is using Java 8 to build the JAR file. I hope this helps.

I agree, we need more details - can you provide more info?

Hmmm. Have you played with the Compatibility settings in Jaspersoft studio? Check https://community.jaspersoft.com/documentation/jaspersoft-studio-user-guide-820/v820/setting-compatibility-earlier-versions -- if so, does the report work in JSS or is the problem only in JRS?