Failed to connect to OLAP Source

[JB_]

Hi,

We are currently facing an issue with the following scenario (BI 4.1, SP2).

- Webi report over Bex; user logs on via LDAP authentication and is SSOed to BW via STS

- For a single-user refreshing one report, all functionality works as described and we do not face any issues

- For a single-user refreshing many reports, or many users refreshing many reports, we get an error 'Failed to Connect to OLAP Source'.

- If we disable the SSO in the OLAP connection, and hard-code user and password, the problem appears to go away (however this is a business requirement as different users will have different data).

- Has anyone had this issue or similar issues with STS?

[Former Member · Accepted solution]

This looks like STS is not configured properly. Would recommend to check the STS setup in the BW end as well.

Please refer to Import SAP BO BI4.0 certificate into SAP BW - Business Intelligence (BusinessObjects) - SCN Wiki

Regards,

Upendra.

[JB_]

Hi,

What we are doing is performance testing a large-scale environment which will be used for upwards of 100+ active concurrent users.

Each report is based on the same OLAP connection created in the CMC which is SSO-enabled.

To get the error, we have tried: having multiple users logging on to the platform and refreshing one report each.

[JB_]

Hi all,

Thank you for the responses, but STS was originally configured as per the post above.

SSO does work for a single user refreshing a report, or even a few users refreshing reports, but we hit a limit after which users are unable to refresh reports and encounter the error.

Question is: are there any settings on the BW / gateway side that could affect this functionality?

[Former Member]

Hi,

Do you still get the same error?

A screen shot may help us here.

can you give me exact steps when you say, user is trying to refresh the multiple report at the same time? how user is trying to do that?

All those reports are based on the same OLAP Connection?

Regards,

Upendra.

[JB_]

hello,

Thank you for the responses; it is a cluster environment.

We do appear to be making progress. In the cluster, I had one instance per 2 webi servers and per 2 DSL bridges.

I have now added int one STS per DSL Bridge to give a total of

3 STS, 2 DSL Bridge, 2 Webi Processing Severs per node.

This appears to have reduced the bottleneck somewhat.

We are now facing new errors (as per note 1938768)..... it does appear as if this is near to solving the original issue

[Former Member]

Can you perform the below test:

1)  Stop SIA in Node 2

2) Stop all the APS distributed services in Node 1. Start only the default APS which came up with the installation.

Now check the reports.

If it works fine,

do the same steps in Node2 bystopping node 1 SIA.

This will narrow down your issue to find the exact cause where you are having issue.

[Former Member]

Hi James,

Most of the times this issue will occur, If the users BW Pwd is expired and user don't have sufficient rights on the BW Side.

Try to find the user who is having issue and change his SAP alias to some other working SAP alias.

Then you can confirm that this issue with the BW side only.

[JB_]

Hi JRK Prasad,

Thank you for the response; we can confirm that the user in BW has the correct authorisations, though, as it works fine on a single report refresh. Do you know of any other things that might cause this issue?

[Former Member]

Do you have cluster environment ? or Single system?

If it is cluster, have you configured STS in all the systems