Working on webI desktop client but not via the BI launch pad

[Former Member]

Hi Experts,

My reports it webI 4.0 desktop client work perfectly but when I try to view the same report via the BI launch pad online there are errors; not all of the data comes through and the months no longer appear in chronological order (even if a sort if applied!)

Please help?

Sara

[Henry_Banks]

Hi,

This is unexpected behaviour. But which problem do you want to eliminate first? (Sorting is low priority..)

What are these Errors ?

Are your Client and Server on the same Patch level? You have to be on Patch2.5 (General Availability version) or above (Patch2.11 is available)

What's your connectivity and datasource type and version?

Regards,

H

[Former Member]

Hi,

Thank you for your quick repsonse.

Via the 'about' on the desktop client I can see I have version 14.0.2. I do not know about the server but have left the question with our IT department.

The data has come from BPC 10 through Bex query deisgner via an OLAP connection. The connection was created using Information design tool Version: 14.0.2.v20111024-0507.

Sara

[Henry_Banks]

OK, you need to ensure that the Adaptive Processing Server is up and running in the CMC.

there is a service contained inside the APS called the DSL_Bridge. That's probably your breakpoint.

In BI4.0, it is this service specifically that uses the JCo for OLAP BICS connections to BEx queries in BW.

Regards,

H

[Former Member]

Hi,

The Adaptive Processing Server is 'healthy' according to it's properties in the CMC.

The properties of the DSL Bridge service are all unticked and in the box 'DSLBridge Engine Cleanup Timeput(in seconds)' there is 1200.

Sara

[Henry_Banks]

Hi,

Stil; curious to know what these errors are, explicitly...

- NExt, you should enable a HIGH tracelog on the DSL_Bridge in the APS . (First, create a new APS containing ONLY DSL, and remove DSL from the default APS)

- and also set HIGH tracelog on a WebIprocessingServer (shut down any other instances).

--> reproduce your workflow - and analyze the logs for any screaming |E| (errors)

- on the BW-side in parallel, you might want to do some ST05 SQL and RFC traces, and also RSTT trace for your user.

- Then analyze those too for Errors. Post back here with findings.

By then, you'd also have a good body of evidence to take to Support as a Incident Message, if required.

Regards,

H