Skip to Content

Increase Expiry Time

expiry.png

Hi Team,

We are having this error "object could not be scheduled withing the specified time interval"

the current scheduled run Start time is expired before the actual run.
Kindly advise the ways to fix this issue or if there is a way to increase Expiry Time.

Regards,

Pol Cuaresma

expiry.png (19.4 kB)
Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Feb 18 at 04:05 PM

    The reason that you're getting this message is that you have too many reports trying to run at around the same time. There is no setting as such to fix this, but you have a couple of options.

    1. In the Servers section of the CMC., go to the properties of the Adaptive Job Server and find either "Crystal Reports Scheduling Service" (if you're using Crystal for Enterprise) or "Crystal Reports 2016 Scheduling Service" (if you're using "classic" Crystal). Increase the "Maximum Concurrent Jobs" number, but I wouldn't increase it to more than 10. Processing Crystal reports can be very memory and disk IO intensive, so you need to balance this number based on the resources that are on your server so that you don't end up with other issues.

    2. Add a new server to your cluster to use when scheduling reports.

    Finally, how are you scheduling these reports? Are the "Run Now" or run on a schedule? If they're run on a schedule, you might need to spread out the times when they are scheduled.

    -Dell

    Add comment
    10|10000 characters needed characters exceeded

  • Mar 26 at 03:56 AM

    Hi Christy,

    We schedule the reports with the EVENT trigger. (upon loading the ETL DATA PROCESS), it will place a file event trigger to the server that will trigger all the reports.

    This causes all the reports to run at the same time.
    Even tho it has a spread schedule, if the trigger is late, some reports will expire.

    Add comment
    10|10000 characters needed characters exceeded