Published report does not run on a schedule

 11 Replies
 1 Subscribed to this topic
 22 Subscribed to this forum
Sort:
Author
Messages
Donna
Veteran Member Send Private Message
Posts: 110
Veteran Member
The KRONOS database is on a different server than the Lawson database but that is not an issue when I run the report from the dashboard.

The error message from the scheduler is as follows:

com.crystaldecisions.sdk.occa.report.lib.ReportSDKServerException: The system cannot find the file specified. ---- Error code:-2147467259 [CRSDK00000000] Error code name:failed
Description: Report Request Failed For: REHAB SCHED KRONOS Employee Daily Summary for Rehab_16.rpt

Skip123
New Member Send Private Message
Posts: 3
New Member
I would verify that the report actually runs when you select "View with Data Refresh?
Matthew Nye
Veteran Member Send Private Message
Posts: 514
Veteran Member
what is the link on the dashboard? As skip eluded to it may be that the dashboard is pointing to a historical instance and that now the report or data connection is no longer valid.
If any of my answers were helpful an endorsement on LinkedIn would be much appriciated! www.linkedin.com/pub/matthew-nye/1a/886/760/
Greg Moeller
Veteran Member Send Private Message
Posts: 1498
Veteran Member
We've also had issues when too many reports were scheduled for the exact same time. Try adjusting the time up or down by a couple minutes. Or validate by going to Report Administration | Maintain Report Schedules --- I've copy/pasted this screen into Excel to allow for a little better sorting.

Also, LBI used to let you create schedules with the exact same name. Not sure if it still allows this or not. LBI does NOT like two schedules with the same name.
Donna
Veteran Member Send Private Message
Posts: 110
Veteran Member
QuoteReplyAlert
Matthew,
Thank you for your quick response.
The report actually runs when you select "View with Data Refresh" and it is set up to run without parameters. The same report also runs when invoked from the dashboard tab in LBI.
This is really peculiar.



Donna
Veteran Member Send Private Message
Posts: 110
Veteran Member
Greg,

Thank you. I have experimented with the times but I did not think about naming conventions. I will revisit both.

Donna
Matthew Nye
Veteran Member Send Private Message
Posts: 514
Veteran Member
what about parameters? Are you testing using the same parameters that are used in the schedule? What version of RS are you using?
If any of my answers were helpful an endorsement on LinkedIn would be much appriciated! www.linkedin.com/pub/matthew-nye/1a/886/760/
Greg Moeller
Veteran Member Send Private Message
Posts: 1498
Veteran Member
Donna:
Be aware that if the report has ever had a schedule on it (even if you remove it) the dashboard link is only rendering the last instance of the report from the server, not generating a new report. (At least that's the way it used to work).
Skip123
New Member Send Private Message
Posts: 3
New Member
You may want open the crystal report and see if 'Save Data with Report' is enabled or not. Probably best to keep it disabled (turned off).
Donna
Veteran Member Send Private Message
Posts: 110
Veteran Member
ok. I republished the report. tested the report. Added a new schedule. Just for the heck of it I named the instance but that was not helpful. Then I removed the name of the instance.
I changed run times.

Is there any possiblity that the server is not recognized by the scheduler even though the report runs on the LBI dashboard tabs and in the report area immediately after publishing?

Thank you.

Donna
Donna
Veteran Member Send Private Message
Posts: 110
Veteran Member
Skip123,
The saved data with report is not selected.
Greg,
I republished the report and created a new schedule which I hope would avoid the prior instance issue.
Matthew,
The report does not require parameters to execute, i have currentdate -1 in the report filter. Do you think that might be an issue?

Thank you.

Donna
Donna
Veteran Member Send Private Message
Posts: 110
Veteran Member
The issue is resolved and it appears that the parameters were the problem. Even though the report select was not using parameters there were some parameters built that were not being used in the report. I deleted them and set up the schedule again with success.

Thank you all again for your help. This community is so valuable to the Lawson clients. Greg and Matthew are star members who give amazing amounts of their time to the cause. Skip123, I thank you for your assistance as a new member.

Donna