Sven Vanleke

Thank you Olga for your feedback! I added com.jaspersoft.jasperserver.api.engine.scheduling.quartz in de Log Setting with "Debug" as an option. When I checked the logfiles (tomcat7-stdout.log & Jasperserver.log)I noticed the following errors: 2012-09-10 10:50:06,784 DEBUG ReportJobsQuartzScheduler,http-apr-8080-exec-3:196 - No trigger found for job 15856 2012-09-10 10:50:06,790 DEBUG ReportJobsQuartzScheduler,http-apr-8080-exec-3:196 - No trigger found for job 15856 2012-09-10 10:50:06,796 DEBUG ReportJobsQuartzScheduler,http-apr-8080-exec-3:196 - No trigger found for job 4964 2012-09-10 10:50:06,801 DEBUG ReportJobsQuartzScheduler,http-apr-8080-exec-3:196 - No trigger found for job 4964 2012-09-10 10:50:06,807 DEBUG ReportJobsQuartzScheduler,http-apr-8080-exec-3:196 - No trigger found for job 15797 2012-09-10 10:50:06,811 DEBUG ReportJobsQuartzScheduler,http-apr-8080-exec-3:196 - No trigger found for job 15797 2012-09-10 10:50:06,816 DEBUG ReportJobsQuartzScheduler,http-apr-8080-exec-3:196 - No trigger found for job 15915 2012-09-10 10:50:06,819 DEBUG ReportJobsQuartzScheduler,http-apr-8080-exec-3:196 - No trigger found for job 15915 Apprently the jobs are still there with definitions, parameters en schedule but somehow the link between them is corrupt. I still hope that recreating the definitions again is not the only solution since the upgrade has gone smoothly without errors and hope to use the same upgrade-procedure in the future. Does the error ring a bell for someone so that I can reinstate my existing report jobs? Regards. Post Edited by svenvanleke at 10/09/2012 11:05

Anyone to guide me to the proper info? Tnx!

Hi, We recently performed the upgrade to get our server from v4.5.0 to v4.7.0. Everything went wel without any visible error and the online interface came up nicely as expected. Even all report jobs were there as before (online check + "http://{host}:{port}//jasperserver/rest_v2/jobs?") Unfortunaltely all schedules for these jobs have a state "unknown" (cf. attachment) As we execute them manually (run) everything is OK, but the schedule, which was set in v4.5.0, has that state "unknown" Could anyone point me in the right direction in order to have these schedules active again or to be able to debug/log them? The system involved: Windows Server 2008 R2, Tomcat 7.0 and PostgreSQL 9.0.4 Kind regards, Sven Vanleke

Hi, Dealing with exact the same problem. Hopefully someone can give us the proper advice. Regards, Sven?

Since the upgrade to v4.5 it seems that we no longer can save user-id/password in the browser. Is there a way to reactivate this feature since it is very handy in test environments. If this matter had been discussed before please point me to the posted topic please. Hopefully I didn't overlook it somewhere. Regards, Sven.