Did anybody else experience an issue with their scheduled reports this morning?
A number of reports are dependent on a schedule event that is triggered after a blank report runs every day at 8am. Today that report never kicked off the event and all the reports were held up.
I then tried to run a one-off version of the report to trigger the event, but it held in pending status. I then restarted our “Desktop Intelligence Job Server” and the report ran and fired off the event.
I’m thinking that the daylight savings adjustment affected our environment, but it seems odd because we waited an hour (to see if we were just an hour ahead of scheduled) and everything remained inactive…
I had a similar issue. My reports that were supposed to run on Sunday morning did not run. I also have them triggered off an event. They ran as scheduled this morning but its like they did not even try to run yesterday. I can not find any errors in any of the logs either.
we experienced this issue over the weekend as well, same error on all jobs "Object could not be scheduled within the specified time interval
"
…70,000 schedule failures. We think is has something to with the time change…we are investigating…did anyone else have this issue?
update:
found SAP KB Article 1568239
After DST change Schedules fail in Business Objects Enterprise XI 3.1 with: Object could not be scheduled within the specified time interval
Yes, we had the same issue. All the jobs would fail, but keep trying. Then, an hour after they should have run, they ran successfully. I ended up rescheduling each and every job manually, replacing the recurring instance. The schedules that finally ran yesterday failed again today, because I did not reschedule them yesterday.
Can you tell us where you saved the updater .jar file? We tried saving it on both the C:\ drive and also the path listed in the KB and when we run the command from the KC it says “Unable to access jarfile tzupdater.jar”
which are to save the file to somewhere like c:\ open cmd prompt and change to the directory where the file is and then run “C:\Program Files\Business Objects\javasdk\bin\java” -jar tzupdater.jar -v -u
This did not fix the instances with this problem for me…on the phone with SAP now.
-stop the job servers (cyrstal webi destination, etc)
-download the tool that allows you to reschedule jobs
-login to your CMC
-list all scheduled jobs
-reschedule all jobs for 1 hour earlier
-reschedule them all back to 1 hour later
-restart job servers
SAP was quite helpful. I attached the file so yall wont have to track it down. Call SAP for help with it if needed EDST_Tool_v1.2.zip (3.0 KB)
we have not rescheduled andy jobs yet…our jobs look to be running ok now after we deleted all of the failed jobs from instance manager, applied patch, and rebooted
To avoid confusion: there are two separate KB articles addressing different daylight savings time issues:
1448881 - Multiple instances spawned after daylight savings time change
And
1568239 - After DST change Schedules fail in Business Objects Enterprise XI 3.1 with: Object could not be scheduled within the specified time interval
The steps that you listed* [apparently you have to
-stop the job servers (cyrstal webi destination, etc)
-download the tool that allows you to reschedule jobs
-login to your CMC
-list all scheduled jobs
-reschedule all jobs for 1 hour earlier
-reschedule them all back to 1 hour later
-restart job servers]*
are for 1448881, not 1568239 which was being discussed above. 8)
To be slightly more clear…the issue which I personally was experiencing was scheduled instances failing with the status of “Object could not be scheduled within the specified time interval” which was resolved by following the steps I mentioned. The steps may apply to other situations but it does not follow that they do not apply here.
We were still having some reports fail with the error message “Object could not be scheduled within the specified time interval”, but some were working.
As a precaution we ran the reschedule tool anyway and did as instructed…rescheduled one hour before and then one hour after…we shall see tomorrow morning if it worked
@krjoyner
…thanks for the file. Did this come from SAP?
very easy to use…we can use this a lot in the future to do some mass rescheduling!
Sounds useful, but the same can’t be done on our side. We have close to 1000 reports that a scheduled. If we reschedule them, it’s gonna be another headache for us. We applied the fix and still we’re getting the errors. Guess we have to reboot the servers eventually.
we have over a 1000 scheduled reports as well…The tool will just set the schedule back one hour on ALL of the reports (or the ones you individually select), and then it will set them ALL back one hour ahead. So in the end you are back with your original schedule.
I think what happened was this…if you look at your Failed jobs the expiration time is one hour behind the start time, so the jobs fail right away…I think by “rescheduling” them it fixes the issue once you have applied the patch
Same issue had with my server as have thousands of failed instances. Yesterday installed the Java DST updater thinking it will solve the issue. Didn’t do anything same problem have today. Now decided to use the tool to reschedule the instances. Let’s see…
My problem now is to cleanup all those failed instances…
We had no issues this morning…everything ran fine. These are the steps we did.
After pausing are jobs for that morning …we deleted all 70,000 Failed instances.We just manually selected 500 at a time in the instance Manager and deleted…took about 3 hours.
Then applied the java patch…and rebooted servers.
Then I ran the tool and set all scheduled jobs back an hour and then ahead an hour…the tool is real easy to use.
We are also facing the same issue since yesterday!! Some reports run but some dont. All the posts here and the two SAP notes seem to be a fix for Windows installation.
Has anybody with Linux BOE installation resolved this error??
(BOB member since 2010-12-08)
(BOB member since 2011-01-28)
(BOB member since 2010-06-07)