cancel
Showing results for 
Search instead for 
Did you mean: 

Error refreshing multiple Live Office connections

0 Kudos

I'm having an issue refreshing a Dashboard Design model that contains multiple Live Office connections against WebI docs built on Bex queries (No Universes).

If I use a single Connection Refresh Button to refresh all connections, one of the connections will refresh and the others will fail with error:

Cannot Access External Data

Failed to get the document information. (LO 26325)

If a use one Connection Refresh Button for each connection and refresh them one at a time, everything works as expected.

The LiveOffice connections all refresh properly within XLS as well.

Some of the WebI reports have prompts, which are being passed by bound cells.

Products used:

BI 4 Edge Server with SP2 Patch 5

SAP Dashboard Design SP2 Patch 5

Live Office SP2 Patch 5

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Richard,

                Delete all the connection from data manager, and add all the connection again.. try this, hope this will work

Regards,

Russel.

Former Member
0 Kudos

Hi Richard,

May i know for what field prompts are available?

Regards,

G.Sainath

Former Member
0 Kudos

Hi Richard,

How many live office connections are there in the dashboard? It is possible to have too many LO connections run simultaneously which can make the refresh unstable.

Also, queries with prompts need to be fully satisfied before the connection is executed. This can be an issue if the LO connections are set to "refresh before components are loaded." For this reason try the following:

1. In the Data Manager, uncheck all connections for "refresh before components are loaded."

2. With all the connections in 1 refresh button. Manually click the button to refresh instead of automatically triggering via calc event.

3. If there are a large number of connections, use more than one connection refresh button to divide the connections so there's fewer calls being made per connection request. You can use the trigger behavior to chain them to fire after each other.

Regards,

Jon

0 Kudos

Thanks for your input Jon.

I've tried all the combinations of refresh on load, multiple buttons, etc, but the issue remains if I try to refresh more than one connection at a time. The only scenario where I don't have failure is when I run them sequentially, which I did manually with multiple refresh buttons.

Your suggesting of chaining the refreshes together was also suggested to me on the BoB forums. It's a great tip, am going to try that next.

In some other testing, I did isolate my issue to only occur when the source WebI docs are against Bex. When I recreate the same test of 5 connections against WebI with Universes, there is no error, the connections run in parallel successfully.