Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Refresh of Webi in BI Launch Pad : "Failed to connect to the olap source"


Dear all,

I have a Web Intelligence document based on a BEx Query (BICS connectivity via an OLAP Connection configured with SSO)

Behaviour :

  • in Web Intelligence Rich Client (2 tier and 3 tier) : refresh is OK
  • in BI Launch Pad : refresh is not OK :

What can be the reason ? In my opinion SSO to BW is working fine because :

  • refresh in Web Intelligence Rich Client is OK
  • refresh of an Analysis Application (Design Studio) based on the same OLAP connection is working fine in Design Studio and in BI Launch Pad

Do I miss something at server level ?

In the log file of the APS running the DSLBridge Service, I found :

|BFCA5F821928450BBBE73F2614F437D5134|2013 03 07 16:59:43.174|+0100|Error|Error|>>|E| |aps_SIA_I_DEV.APS_DSL| 3712|796189|Transport:Shared-8074/34| |1542|0|2|0|Webi SDK.CorbaServerImpl.doProcess()|IDIRBLOCKAP010V:2960:207.7025:1|webiserver_SIA_I_DEV.WebIntelligenceProcessingServer.openDocumentMDP|localhost:12164:11488.145650:1|.doIt|IDIRBLOCKAP010V:3712:796189.292728:1|Ci8H06XT2kMZvL7KIxC6cuQ1b23|||||||||||Exception caught in SL Service: Cannot connect to the olap source

com.businessobjects.mds.services.helpers.OlapUniverseHelperException$ConnectionToOlapSourceFailedException: Cannot connect to the olap source

at com.sap.sl.edp.dataprovider.olap.AbstractOlapDataProvider.createOlapClient(AbstractOlapDataProvider.java:490)

at com.sap.sl.edp.dataprovider.olap.DirectOlapAccessDataProvider.generateProtoUniverse(DirectOlapAccessDataProvider.java:216)

at com.sap.sl.edp.dataprovider.olap.DirectOlapAccessDataProviderBuilder.generateProtoUniverse(DirectOlapAccessDataProviderBuilder.java:91)

at com.businessobjects.dsl.services.universe.impl.UniverseServiceImpl.provideProtoUniverse(UniverseServiceImpl.java:291)

at com.businessobjects.dsl.services.universe.impl.UniverseServiceImpl.getProtoUniverse(UniverseServiceImpl.java:181)

at com.businessobjects.dsl.services.datasource.impl.DataSourceServiceImpl.getDataSourceHeader(DataSourceServiceImpl.java:182)

at com.businessobjects.dsl.services.datasource.impl.DataSourceServiceImpl.getDataSourceHeader(DataSourceServiceImpl.java:130)

at com.sap.sl.proxyconsumption.services.datasourceservice.DataSourceServiceImpl.getDataSourceHeader(DataSourceServiceImpl.java:516)

at com.sap.sl.proxyconsumption.services.datasourceservice.DataSourceServiceImpl.getDataSourceHeader(DataSourceServiceImpl.java:480)

at com.sap.sl.proxyconsumption.protobuf.rpc.DatasourceRpc$dataSource.callMethod(DatasourceRpc.java:207)

at com.sap.sl.proxyconsumption.services.server.DSLBridge.callService(DSLBridge.java:236)

at com.sap.sl.proxyconsumption.services.server.DSLBridge.doIt(DSLBridge.java:161)

at com.businessobjects.cdz_ext.slproxybridge.corba.ServerServant.doIt(ServerServant.java:119)

at sun.reflect.GeneratedMethodAccessor168.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at com.businessobjects.framework.servers.platform.adapters.ebus.orb.CommonTransportInterceptor.invokeHelper(CommonTransportInterceptor.java:118)

at com.businessobjects.framework.servers.platform.adapters.ebus.orb.CommonTransportInterceptor.invoke(CommonTransportInterceptor.java:87)

at com.businessobjects.framework.servers.common.proxy.cglib.MethodInterceptorChain.intercept(MethodInterceptorChain.java:136)

at com.crystaldecisions.enterprise.ocaframework.idl.OCA.OCAcdz.slproxybridge.serverPOA$$EnhancerByCGLIB$$66b9c148.doIt(<generated>)

at com.crystaldecisions.enterprise.ocaframework.idl.OCA.OCAcdz.slproxybridge.serverPOA._OB_op_doIt(serverPOA.java:107)

at com.crystaldecisions.enterprise.ocaframework.idl.OCA.OCAcdz.slproxybridge.serverPOA._invoke(serverPOA.java:83)

at com.crystaldecisions.thirdparty.com.ooc.OBPortableServer.ServantDispatcher.dispatch(ServantDispatcher.java:234)

at com.crystaldecisions.thirdparty.com.ooc.OBPortableServer.POA_impl._do_OB_dispatch(POA_impl.java:1977)

at com.crystaldecisions.thirdparty.com.ooc.OBPortableServer.POA_impl._OB_dispatch(POA_impl.java:1913)

at com.crystaldecisions.thirdparty.com.ooc.OB.DispatchRequest_impl.invoke(DispatchRequest_impl.java:75)

at com.businessobjects.framework.servers.platform.adapters.ebus.orb.ThreadPoolDispatchStrategy$Dispatcher.run(ThreadPoolDispatchStrategy.java:271)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)

at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)

at java.util.concurrent.FutureTask.run(FutureTask.java:138)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

at java.lang.Thread.run(Thread.java:743)

Caused by: com.businessobjects.mds.olap.OlapException: [Internal] SSO token or User password is empty.

at com.businessobjects.mds.olap.protocol.sap.jco.JCOConnection.connect(JCOConnection.java:259)

at com.businessobjects.mds.olap.protocol.bics.internal.BICSClientImpl.initialize(BICSClientImpl.java:407)

at com.businessobjects.mds.olap.OlapClientFactory.Create(OlapClientFactory.java:93)

at com.businessobjects.mds.services.helpers.OlapClientHelper.createOlapClient(OlapClientHelper.java:409)

at com.businessobjects.mds.services.helpers.OlapClientHelper.createNamedOlapClient(OlapClientHelper.java:361)

at com.businessobjects.mds.services.helpers.OlapClientHelper.createNamedOlapClient(OlapClientHelper.java:234)

at com.sap.sl.edp.dataprovider.olap.AbstractOlapDataProvider.createOlapClient(AbstractOlapDataProvider.java:487)

... 32 more

Many thanks for your help

Hans

replied

we fixed the issue by resetting the password of the Entitlement Systems User : remove special characters from the password

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question