Schedule Webi to Inbox

[DellSC]

In BI 4.1 SP 5 I'm getting a (500) Internal Server Error when trying to schedule a webi report to inbox.  Prior to doing the POST for the schedule, I'm able to successfully login to get the token and then to get the parameters for the report (the report I'm testing doesn't have any parameters, but the call to get them is successful.)

URL:  http://<server>:6405/biprws/raylight/v1/documents/11552/schedules/

XML:

<schedule>

  <name>Charting Samples</name>

  <format type="webi" />

  <destination><inbox /></destination>

  <once retriesAllowed="0" retryIntervalInSeconds="60">

    <startdate>2015-12-23T10:12:27.232-05:00</startdate>

    <enddate>2016-01-23T10:12:27.232-05:00</enddate>

  </once>

</schedule>

I've been fighting with this for about a week now and can't seem to get it working.  Does anyone have any thoughts?

Thanks!

-Dell

[daniel_paulsen · Accepted solution]

Hi Dell,

does it work if you remove the <once> and start / end date tags?  ie:  schedule Now?

I heard recently that the time offsets aren't needed for scheduling but are required when doing on-demand stuff.  I haven't looked into it, but can you give it a try?

Dan

[daniel_paulsen · Accepted solution]

Hi Dell,

Just to follow up, when scheduling, try using Zulu Time (no offset specified)

http://help.sap.com/saphelpiis_sbo41sp5wi-sdk/frameset.htm?ec56e3d56fdb101497906a7cb0e91070.html#

  <destination><inbox /></destination>

  <once retriesAllowed="0" retryIntervalInSeconds="60">

    <startdate>2015-12-23T15:12:27Z</startdate>

    <enddate>2016-01-23T15:12:27Z</enddate>

  </once>

Dan

[DellSC · Accepted solution]

Schedule Now is throwing the same error.   Here's the XML I used:

<schedule>

  <name>Charting Samples</name>

  <format type="webi" />

  <destination><inbox /></destination>

</schedule>

-Dell

[former_member197386 · Accepted solution]

Hi Dell!

Please, could you enable the "Show stack trace error" in CMC > WACS > Properties and rerun the failing RESTful call?

That will send back more information on the error root cause.

Best regards,

Anthony

[DellSC · Accepted solution]

Thanks Anthony.  Doing this I was able to see that the session had been logged out prior to the call to schedule (code originally written by someone else...), which enabled me walk back through it and fix the issue.  It's working now!

Thanks again!

-Dell