Below are some of the report schedule failure and their resolution.

Below issues were found in BOXI 3  with back end as BEx queries. Below are some of the most repeated Webi report schedule failures.

1) Object could not be scheduled within the specified time interval.

/wp-content/uploads/2015/11/1_840525.png

Cause:

Whenever we create schedule we specify the schedule start and end date. When the specified time period has been expired, this issue occurs.

Resolution:

We need  to create a new schedule for the specific report extending the expiry date.

2) Address Error:


/wp-content/uploads/2015/11/2_840526.png

Cause: This error is caused when the email id is wrongly given while scheduling or semicolon is not given between each email ids.

Resolution: Validate the specified email ids in the schedules.


3) Invalid Prompt identifier

/wp-content/uploads/2015/11/3_840527.png

Resolution: This issue happens when prompt values are not defined properly.  Once scenario is that the prompt value that was used when scheduling is no more exist.


4) Web Intelligence server cannot be  reached


/wp-content/uploads/2015/11/4_840528.png

Resolution:

Recurring schedule request has been failed to refresh in specified time period due to network related issue (or) stack queue might be overloaded.


5) Unable to connect to SAP BW server System


/wp-content/uploads/2015/11/5_1_840529.png

/wp-content/uploads/2015/11/5_2_840530.png

Resolution: Check the process chains would be failed.

Universe connection for respective report needs to be verified

Everything is validated then refresh the schedule once gain.


6) While processing the Job servers

/wp-content/uploads/2015/11/6_840531.png

Resolution: Check the BOBJ servers are running stage (or) Stop status.



I hope these issues and their resolutions will help some of you.



To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply