Showing results for 
Search instead for 
Did you mean: 

Error java.lang.IllegalArgumentException when using getFromUserInstance

0 Kudos

Hi everyone,

We have several Dashboards with data connections to Web Services, which have been published via Web Intelligences, and based on BEx Queries from BW.

Some of these web services are quite slow so we want to instance them so users don't have to wait 60 seconds or more just to open the dashboard.

The problem is that each User has different authorizations in BW for data and each user will see dashboards with different sets of data.

For this purpose we're using the "getFromUserInstance" parameter in the webservices data connection. We've created a publication and sent the reports to each user's inbox, where they are appearing correctly and with correctly filtered data.

The problem is that when we open the Dashboards we get one "java.lang.IllegalArgumentException" error message per data connection present in the dashboard.

Funny thing is that if I have a dashboard with only one data connection to a webi report and that report is the first one (sorted ascending by date) in the user inbox, the dashboard works fine. All other data connections and dashboards fail with this java error message.

Has anyone had previous experience using the "getFromUserInstance" parameter, and has anyone experienced these issues?

Note: We already have an open message in SAP Support for almost 20 days, but they've been unable to identify the problem.


Jose Luis Leitao


SAP BO 4.0 SP02 Patch Level 21

Dashboard Designer 4.0 Patch 21

View Entire Topic
0 Kudos

Hi everyone,

Only after escalating the issue to the SAP level 1 support team did we finally have a diagnosis.

Apparently when a Publication is executed with multiple documents, all the documents instances share a single ID for that publication.

The problem is that Xcelsius will select the first available document within that ID causing a mismatch between the webservice and the publication, causing an "IllegalArgumentException".

This is clearly a software bug which has no patch identified for now. I have no indication if this issue occurs also in later SP, so this might also occur in the latest BO versions.

Workaround? Yes, at least there's that.

We had to create multiple Publications, one for each WebIntelligence report. Not the nicest thing to manage but at least it works.

Again, support from SAP was atrocious and overall ineffective. They only showed real concern and involvement when the message was upgraded to Very High.


Jose Luis Leitao