Jump to content
We've recently updated our Privacy Statement, available here ×

ybarkalov

Members
  • Posts

    4
  • Joined

  • Last visited

ybarkalov's Achievements

Newbie

Newbie (1/14)

  • Week One Done
  • One Month Later
  • One Year In
  • First Post Rare

Recent Badges

0

Reputation

  1. It seems that there is no reply or resolution to this. My company just got 5.5 Enterprise Edition and we run into the same exact problem. What's more I can't even save report copy into ANY folder other than the one it's deployed in. And I can't do it while logged in as Administrator, so it has nothing to do privilege level. And the error in catalina.out says " Error saving the report as a copy in another directory (uri: /jasperserver-pro/flow.html?null)". I hoped to find solution already logged, but will have to go through the support then.
  2. We are in process of upgrading (clean install + recreation of all objects) from 4.7 CE to 5.2 CE. And we are experiencing the same issue... What's more - running report in the background with attached PDF works fine, while scheduling it throws an error. I will keep debugging more and will post update...
  3. We have Jasper 4.0 CE version, but I'm pretty positive that it's the same in 4.5 as well. I created Master / Detail reports where from the list of sale records you can select one and open another report with more details about that sale. So the "Detail" report (Drilldown in your case) has the parameter that is NOT required. I say it capital letters because I created another copy of "Detail" report where user can just open it and enter sale id and that one has sale id as required. Another thing, which may be specific to 4.5 as oppose to 4.0 is that I speicified path to "Detail" report without "repo:" prefix. In my case it is "/Source_Code/Subreports/...". It's different when I reference company logo as resource - I put "repo:/Source_Code/Images/...", but NOT for opening another report.
  4. We are using 4.0 CE. The same behavior happened when the business user would modify and re-save the existing subscription. The only remedy we found was to delete and re-create a particular subscription. We further confirmed this issue when we had multiple subscriptions of the same report with different parameters and only the modified ones were triggered multiple times. Hope this helps, Yevgeniy
×
×
  • Create New...