AnsweredAssumed Answered

All Scheduled Jaspersoft Reports are Blank

Question asked by Robert Ensinger on Jan 24, 2017
Latest reply on Jul 2, 2017 by NamitaMish

Like • Show 0 Likes0
Comment • 18

We're still in pilot mode, so I'm learning.

All Scheduled Reports, scheduled previous to our upgrade run and email successfully, only they're all blank with the message:

"No matching records were found"

Example attached.

- All reports run fine for all users

- Newly Scheduled Reports run & publish properly.

- There are no errors in the Jaspersoft logs.

- Although I am on the "Send Job Status Notification" for Send Failure Notifications, I have not received any notifications. I am assuming this is because they're not failing - they're just blank.

Off to re-read the documentation. Any ideas are greatly appreciated.

Suman Pramanik

Feb 7, 2017 2:12 PM

Correct Answer

Hi Rob,

I raised a defect and its DE32148 and its changed from CLRT series.

Regards

Suman Pramanik

See the reply in context

Attachments

PMO_Resource_Forecasted_Utilization_Detail-201701.pdf1.3 KB

No one else had this question

Outcomes

18 Replies

Nika_Hadzhikidi Jan 24, 2017 8:00 PM
Mark Correct
Correct Answer
Hi Robert

Can you run Load Data Warehouse - Access Rights job and see if that makes a difference?

Thanks -Nika
Like • Show 0 Likes0
Actions
- Robert Ensinger @ Nika_Hadzhikidi on Jan 24, 2017 8:54 PM
  Mark Correct
  Correct Answer
  All jobs have been running successfully and all reports run properly 'real time' for the users. All reports scheduled after the upgrade (evening of 1/12) publish & email properly.
  Since I was not upgrading PPM version or content, I skipped all "post installation" stuff content related. Re-reading the upgrade instructions - what about...
  -------------------------------------
  admin update jasperParameters
  This command updates the profile attributes so that the attributes can be re-encrypted.
  -------------------------------------
  I copied the keystore out of the old Jasper folder instead of generating a new one (the instructions read "you must generate the key store file before you upgrade the Advanced Reporting Content". We did not upgrade the advanced reporting content so I used my old keystore).
  
  Is my problem that there something in the plumbing of Scheduled reports that needs updated?
  Like • Show 0 Likes0
  Actions
  - Robert Ensinger @ Robert Ensinger on Jan 24, 2017 8:58 PM
    Mark Correct
    Correct Answer
    A custom Jasper Studio report is still publishing properly from a pre-upgrade Schedule. This appears isolated to CSK reports.
    Like • Show 0 Likes0
    Actions
  - Nika_Hadzhikidi @ Robert Ensinger on Jan 24, 2017 9:16 PM
    Mark Correct
    Correct Answer
    Hi Robert - I only asked because we have a known issue if the DWH Access job runs after the DWH job. If that's the case, please run the Access job again.
    
    If that doesn't help, ensure the CSK permissions are granted to the users, and run:
    admin jaspersoft syncPPMContext -userName superuser -password superuser
    
    Hope this helps -Nika
    2 people found this helpful
    Like • Show 2 Likes2
    Actions
    - Robert Ensinger @ Nika_Hadzhikidi on Jan 25, 2017 3:35 PM
      Mark Correct
      Correct Answer
      Hi Nika.
      I have run the admin update jasperParemeters and admin jaspersoft syncPPMContext command and re-run the Load DataWarehouse Access Rights job. This is my best guesses - we'll see what happens when scheduled reports run this weekend. Any additional ideas are appreciated.
      
      For the known issue you mention above - can you link us to a tech doc? Since there has been no change to PPM version and Datamart (this was a Jasper only upgrade), would this still apply?
      Like • Show 0 Likes0
      Actions
  - Suman Pramanik @ Robert Ensinger on Jan 25, 2017 9:37 AM
    Mark Correct
    Correct Answer
    If you schedule report go blank, then we need to check the timing of the schedule and the DWH job, if the DWH schema is blank at that time you will get blank report.
    Like • Show 0 Likes0
    Actions
    - Robert Ensinger @ Suman Pramanik on Jan 25, 2017 1:57 PM
      Mark Correct
      Correct Answer
      Educate me Suman! When is the DWH Schema blank?
      Like • Show 0 Likes0
      Actions
      - Suman Pramanik @ Robert Ensinger on Jan 25, 2017 2:59 PM
        Mark Correct
        Correct Answer
        Hi Rob,
        
        If you run the DWH in full sync then it truncates the table and starts to repopulate, this is the time you can get blank reports.
        
        Regards
        Suman Pramanik
        2 people found this helpful
        Like • Show 2 Likes2
        Actions
        Robert Ensinger @ Suman Pramanik on Jan 25, 2017 3:32 PM
        Mark Correct
        Correct Answer
        Awesome. Thanks Suman. These reports are not scheduled during the full sync but it's good to know this is something to be aware of.
        
        Just to be precise, Incremental updates do not truncate data and it is considered 'safe' for user to run reports during incremental updates?
        
        I feel an Idea coming on...
        Like • Show 0 Likes0
        Actions
        Suman Pramanik @ Robert Ensinger on Jan 25, 2017 3:53 PM
        Mark Correct
        Correct Answer
        Yes incremental updated do not truncate data. Another scenario to get blank report is if a new user is added Advance Reprorting right and Load DWH Right job is not run to populate his/her rights.
        
        When the report went blank, can you share the Jasperserver.logs
        
        Regards
        Suman Pramanik
        Like • Show 0 Likes0
        Actions
        Robert Ensinger @ Suman Pramanik on Jan 25, 2017 7:07 PM
        Mark Correct
        Correct Answer
        Hi Suman. Log is attached but I'm mindful to not turn a forum thread into a support ticket. I've run the update jasperParameters and synchPPMContext commands above - I'll know this Saturday & Sunday if this fixed my issue. If not, I'll open a real ticket and we'll run a proper support process.
        
        We have over 50 reports scheduled to run at random times on Saturdays, Sundays and Tuesdays. Our process is to email the reports (PDF & HTML) and embed the HTML in the email where possible. All of them are blank with the 'No Matching records where found' as shown below. All reports execute properly when run on demand and when a fresh schedule (email distro as above) is created. The reports scheduled prior to upgrading Jaspersoft to 6.2 fail as shown below.
        
        All noise in the logs from 1/12 is me wiring everything back together after the upgrade and troubleshooting this: No Report Scheduling Buttons after Jaspersoft 6.2.1 Upgrade.
        
        All noise since appears to be Ad-Hoc users breaking things. I'm not seeing anything that appears to correspond to these blank reports (14th, 15th, 17th, 21st, 22nd, 24th) but I'll gladly defer to your expert eyes.
        
        Again, if the reports are blank again this weekend I'll open a ticket on Monday.
        
        Thanks!
        Attachments
        jasperserver.log.zip11.8 KB
        Like • Show 0 Likes0
        Actions
        Suman Pramanik @ Robert Ensinger on Jan 25, 2017 7:41 PM
        Mark Correct
        Correct Answer
        Hi Rob,
        
        Two problems I see
        
        2017-01-12 22:57:12,302 ERROR ReportExecutionJob,quartzScheduler_Worker-2:349 [] - The report was not completed. An error occurred while executing it.
        com.jaspersoft.jasperserver.api.JSExceptionWrapper:
        java.lang.reflect.InvocationTargetException
        
        2017-01-12 22:57:33,017 ERROR CustomTenantBuiltInParameterProvider,http-apr-8080-exec-7:346 [root|superuser] - getProfileAttributes(User=superuser,tenant=null):Profile Level User(jasperadmin) specified could not be found in the tenant.
        2017-01-12 22:57:33,682 ERROR JaaSProxyJDBCPoolDataSourceFactory,http-apr-8080-exec-7:1234 [root|superuser] - ::org.apache.jasper.JasperException: JaaSProxyJDBCPoolDataSourceFactory.createService(){Tenant=null,User=superuser}-Dynamic Proxy Data Source Pool can only be used at a Tenant Level context.
        
        Also some dead lock
        
        at com.jaspersoft.jasperserver.api.engine.jasperreports.util.JRTimezoneJdbcQueryExecuter.createDatasource(JRTimezoneJdbcQueryExecuter.java:169)
        at com.jaspersoft.commons.util.JSControlledJdbcQueryExecuter.run(JSControlledJdbcQueryExecuter.java:157)
        ... 1 more
        Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Transaction (Process ID 55) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
        
        So there is some problem at the profile attribute where the update command should fix it.
        
        The schedule button is quite strange so a support ticket would be better
        
        Regards
        Suman Pramanik
        2 people found this helpful
        Like • Show 1 Like1
        Actions
Robert Ensinger Feb 6, 2017 4:31 PM
Mark Correct
Correct Answer
To close the loop on this - the work around was to open each scheduled report instance and click Save.
3 people found this helpful
Like • Show 1 Like1
Actions
- Suman Pramanik @ Robert Ensinger on Feb 7, 2017 6:06 AM
  Mark Correct
  Correct Answer
  Thanks Rob I had the same issue and this is something I will work on it and see what could be done.
  1 person found this helpful
  Like • Show 1 Like1
  Actions
  - Robert Ensinger @ Suman Pramanik on Feb 7, 2017 2:09 PM
    Mark Correct
    Correct Answer
    Hi Suman. Has an issue number been generated for this? This is something we'll want to track.
    Like • Show 0 Likes0
    Actions
    - Suman Pramanik @ Robert Ensinger on Feb 7, 2017 2:12 PM
      Unmark Correct
      Correct Answer
      Hi Rob,
      
      I raised a defect and its DE32148 and its changed from CLRT series.
      
      Regards
      Suman Pramanik
      2 people found this helpful
      Like • Show 1 Like1
      Actions
      - Robert Ensinger @ Suman Pramanik on Feb 7, 2017 5:48 PM
        Mark Correct
        Correct Answer
        Thank You Suman!
        Like • Show 0 Likes0
        Actions
        NamitaMish @ Robert Ensinger on Jul 2, 2017 9:42 AM
        Mark Correct
        Correct Answer
        Our investigation has determined that this issue is in code owned by TIBCO Jaspersoft. As a result, we have logged case 01467237 with them.
        According to TIBCO Jaspersoft, this defect is scheduled to be fixed in one of the JSFT v6.2.1. hotfixes. CA will validate the fix and will incorporate it in the next applicable Jaspersoft patch released by CA.
        1 person found this helpful
        Like • Show 1 Like1
        Actions

All Scheduled Jaspersoft Reports are Blank

Attachments

Outcomes

Attachments

Related Content

Recommended Content