andrew_50
-
Posts
77 -
Joined
-
Last visited
Community Answers
-
andrew_50's post in Jaspersoft Studio CE (6.21.2) - stalls on startup was marked as the answer
Super tacky...
The solution appears to be this...
Delete the .snap file from the folder .metadata/.plugins/org.eclipse.core.resources/ Start JasperSoft Studio - the main screen is now ok, but projects are all "lost" Shut down JasperSoft Studio Restore the .snap file Restart JasperSoft Studio Happy days or whatever...
-
andrew_50's post in Jaspersoft Studio 6.16 does not complete startup was marked as the answer
NOTE: This solution requires re-importing of projects. Thankfully they are not zapped.
Step 1: Delete lock file(s) from C:Program FilesTIBCOJaspersoft Studio-6.16.0configurationorg.eclipse.osgi.manager folder (or wherever Studio is installed)
Step 2: Delete the *.snap files located in <WORKSPACE_PATH>/.metadata/.plugins/org.eclipse.core.resources/
Step 3: Open Project from FileSystem... Your reports should still be where they were, just need to be "brought back into" Studio.
I put it down to the unasked for Edge update (aka some folk at Microsoft probably need a good dose of "education" of the type grandparents usually dish out)
-
andrew_50's post in Community Jasperserver 7.8 fails to start was marked as the answer
The problem:
I was trying to install JasperServer with Tomcat and Postgresql aleady present/running. Installation worked but didn't JasperServer would not run. Jasperserver couldn't find files required for encryption. Note that these files had been successfully written/saved. The epiphany:
They could not be found!? Why? Because the installation was saving them in the home directory of the installing user. Not cool. Tomcat is generally set to run as a faux user (no home directory etc) The Solution:
Create a Tomcat user WITH a home directory Install JasperServer as that user (the required files are now where they "should" be) Ideal? No. Works? Yes. -
andrew_50's post in Error 500 on trying to publish a report update was marked as the answer
As per the comment, the answer was that the server (despite the fun error 500: internal server error) was actually complaining about this...
textAdjust="StretchHeight"
Deleting that solved the problem (it actually appeared in three locations).
Weird that that exact code existed in the pre-updated report and it worked fine.
Weird again that that the report update (to the query part only) somehow was the cause of this error.
Anyhow, mischielf managed. Note as to this fun behaviour noted.
Thanks to "heavensinformatica" for the assist.
-
andrew_50's post in Combining 5 separate reports in One Spreadsheet was marked as the answer
It turns out I what I want to do can be done (should be done?) with a "Report Book."
Desperate times, desperate measures etc.
