You are not logged in.
We used to have a scheduled report, which ran every Monday, that had errors due to column values when it ran. We archived the scheduled report, but still get an error message as if the report was being run each week. We've now "deleted" the scheduled report, which we hope will fix the issue. Here is the error we were receiving:
The execution of a scheduled report has failed. We know what was causing the "Illegal hour value", it was a mysql column that returns a "time" instead of a string. Our query returned a "time span" using time diff functions, and when the time span was over 24 hours, java choked on it. We now have the query force the result to a string, which isn't ideal since sorting won't work properly.
Report: Customer Session Usage Report
Error message: net.datenwerke.rs.core.service.reportmanager.exceptions.ReportExecutorException: The report could not be executed: Could not ascertain object at position: 5
Recipient: XXXXXXXXX
Error-Details: net.datenwerke.scheduler.service.scheduler.exceptions.JobExecutionException: net.datenwerke.rs.core.service.reportmanager.exceptions.ReportExecutorException: The report could not be executed: Could not ascertain object at position: 5
at net.datenwerke.rs.scheduler.service.scheduler.jobs.report.ReportExecuteJob.doExecute(ReportExecuteJob.java:126)
at net.datenwerke.scheduler.service.scheduler.entities.AbstractJob.execute(AbstractJob.java:184)
at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.executeJob(SchedulerTask.java:527)
at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.safeCall(SchedulerTask.java:206)
at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.call(SchedulerTask.java:101)
at net.datenwerke.scheduler.service.scheduler.tasks.SchedulerTask.call(SchedulerTask.java:1)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source) Caused by: net.datenwerke.rs.core.service.reportmanager.exceptions.ReportExecutorException: The report could not be executed: Could not ascertain object at position: 5
at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:218)
at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:119)
at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:106)
at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:101)
at net.datenwerke.rs.scheduler.service.scheduler.jobs.report.ReportExecuteJob.doExecute(ReportExecuteJob.java:121)
... 9 more
Caused by: net.datenwerke.rs.core.service.reportmanager.exceptions.DatabaseConnectionException: Could not ascertain object at position: 5
at net.datenwerke.rs.base.service.datasources.table.impl.TableDBDataSource.getFieldValue(TableDBDataSource.java:146)
at net.datenwerke.rs.base.service.reportengines.table.TableReportEngine.createReport(TableReportEngine.java:280)
at net.datenwerke.rs.base.service.reportengines.table.TableReportEngine.doExecuteNormal(TableReportEngine.java:191)
at net.datenwerke.rs.base.service.reportengines.table.TableReportEngine.doExecuteNormal(TableReportEngine.java:151)
at net.datenwerke.rs.base.service.reportengines.table.TableReportEngine.doExecute(TableReportEngine.java:88)
at net.datenwerke.rs.core.service.reportmanager.engine.ReportEngine.execute(ReportEngine.java:148)
at net.datenwerke.rs.core.service.reportmanager.ReportExecutorServiceImpl.execute(ReportExecutorServiceImpl.java:186)
... 13 more
Caused by: java.sql.SQLException: Illegal hour value '38' for java.sql.Time type in value '38:29:13.
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:957)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:896)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:885)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:860)
at com.mysql.jdbc.TimeUtil.fastTimeCreate(TimeUtil.java:286)
at com.mysql.jdbc.ResultSetImpl.fastTimeCreate(ResultSetImpl.java:976)
at com.mysql.jdbc.ResultSetRow.getTimeFast(ResultSetRow.java:882)
at com.mysql.jdbc.ByteArrayRow.getTimeFast(ByteArrayRow.java:232)
at com.mysql.jdbc.ResultSetImpl.getTimeInternal(ResultSetImpl.java:5602)
at com.mysql.jdbc.ResultSetImpl.getTime(ResultSetImpl.java:5372)
at com.mysql.jdbc.ResultSetImpl.getObject(ResultSetImpl.java:4593)
at com.mchange.v2.c3p0.impl.NewProxyResultSet.getObject(NewProxyResultSet.java:112)
at net.datenwerke.rs.base.service.dbhelper.DatabaseHelper$1.getObject(DatabaseHelper.java:120)
at net.datenwerke.rs.base.service.datasources.table.impl.TableDBDataSource.getFieldValue(TableDBDataSource.java:144)
... 19 more
Offline
Hi bpeikes,
pls check the following terminal commands:
scheduler daemon [start, stop, restart, enable, disable, status, wdstatus, wdshutdown, wdstart, wdrestart]
--lists jobid , type and nextFireTime
scheduler list
-- listFireTimes lists next 10 fireTimes if no number is specified
scheduler listFireTimes jobid NumberofFireTimes
-- removes jobid
scheduler remove jobid
-- unschedules jobid
scheduler unschedule jobid
sometimes its hard to get rid of running scheduled jobs. They can be sticky. Best here is to use the above mentioned terminal commands to get rid of them.
wbr jan
Offline
We are still having the issue, and the job does not appear in the terminal.
Offline
Hi bpeikes,
I am investigating this issue and created the RS-2857 ticket for this purpose. I will update here when I have more information.
Regards,
Eduardo
Offline
Hi bpeikes,
which reportserver version are you having the issues with? Do you have an enterprise edition / enterprise evaluation / community ?
Regards,
Eduardo
Offline
Hi bpeikes,
you can check the next_scheduled_times of your jobs with this query:
select *
from RS_SCHED_JOB
left outer join RS_SCHED_EXECUTE_REPORT_JOB on
RS_SCHED_JOB.entity_id=RS_SCHED_EXECUTE_REPORT_JOB.id
cross join RS_SCHED_TRIGGER
where
report_id = 87003Filter by your report_id. This should be the report that causes the error. What do you get in the column : next_scheduled_fire_time ?
Regards,
Eduardo
Offline
I don't know the id of the report because we deleted the report a while ago, and it's not listed in the error email.
Offline
I've tried all sorts of queries to figure this out. These are weekly reports, if that helps. I expect to see these reports run again next Monday. Right now, this query returns nothing even though I know that report server is going to run these mysterious reports next Monday:
SELECT * FROM rs_sched_trigger WHERE next_scheduled_fire_time > '2018-02-04'
Offline
Hi bpeikes,
could you check with SELECT * FROM rs_sched_trigger if you can identify the job being scheduled?
Are you completely sure you don't have a second reportserver installation that may be causing this ? E.g. some earlier test server, bitnami, etc?
Where do you see the error logs you posted? In the email you get or in the reportserver logs ?
Regards,
Eduardo
Offline