Help with Preventing Scheduled Instances from Running in Crystal Server

[former_member1143730]

Greetings,

I have been asked to find or create a best practice for preventing scheduled instances of reports from running.

We have approximately 450 reports currently scheduled in Crystal Server 2011.

We have had a couple of incidents recently, which prevented data being loaded to our primary reporting database, resulting in "bad" reports being run.

The good news is that the majority of our reports are scheduled to run between 6:00 and 8:15 am on business days.

Other than logging into the machine running Crystal Server and stopping the SIA, does anyone have any suggestions for a better way?

Yesterday this would have been trying to "pause" 244 report instances.

Is there a single "server" adaptave job server", or the "Core Services" server group that we can disable from the CMC that would prevent the reports from running?

Any advice will be greatly appreciated.

Thank you,

Lynne

[former_member182521]

This is the ideal situation for event driven scheduling.

I would suggest you to convert all your Webi reports that are based on data load and time driven to event driven based on the event that is triggered based on dataload.

1. As soon as the database tables are loaded with latest data, generate a file and put it in a shared location which is accessible from your BusinessObjects server.

2. Create a schedule based on the file generated from data load.

3. Now your schedules will run only when the data load is completed and event file is generated.

Thanks

Mani

[former_member1143730]

Thank you, but that is part of what happened.

Our data load stopped after loading 400 of 470 tables, and marked itself completed successfully.  So the even driven solution won't work in this case.

We need to go to the server and stop the job server(s).

or in a real crunch just power off the virtual box.  Which is not the ideal solution, but until we can find the root of our problem, it is what we need to do.

I do thank you for the suggestion.

Cheers

Lynne

[former_member182521]

If it is so, You should make your correction first in ETL side and come back to BO side.

[Former Member]

You could consider removing grants from the reporting tables while the load is running and only replacing them when the load has finished successfully. This would cause the scheduled reports to fail if the load has not completed successfully, but would not require any intervention on your part to log in and stop/start servers (although this can also be automated). In addition it would stop users from manually running reports against the incomplete data sets.

Once the load completed successfully, you could check for all the reports that failed and easily see which ones needed to be re-run.

[former_member209323]

If you stop or disable the servers, the reports which are to be triggered will go to pending status and might also fail based on the end/expiry time set on the report

[former_member1143730]

Part of what I need to know is which server(s) need to be disabled, please.

Thanks!

[former_member185603]

If you stop AJS, reports will not be delivered.

[former_member185603]

you can pause the schedules from instance manager in CMC.