Live Office Errors

[Former Member]

Anyone else having any similar errors? or have any resolutions?

BOE Version: BOE XI 3.0

Live Office Version: XI 3.0 FP2

Xcelsius Version: 2008 SP1

Description of Dashboards

· Dashboard pulls about 22 tables that have been built within a WEBI report into Excel via a Live Office connection

· I updated web services URL for each connection and set each to u2018Update on Loadu2019

· I then exported the dashboard both to a local SWF and to InfoView

So on to the issues:

· Issue #1: Iu2019ve noticed when I load the dashboard for the first time in the day that I get error LO26000, but then it doesnu2019t show up for subsequent loads during the day

· Issue #2: About 20-40% of the time, I will get errors LO26315 (one error popup is generated for each table that does not get loaded), however, I always get varying numbers of this error in one load (i.e., different numbers of tables are not getting loaded) but usually it is around 3-4 errors u2013 in addition, it is always different tables within the dashboard that donu2019t get loaded

So in other words, when loading the dashboard, about 20-40% of the time I will get these LO26315 messages, but it canu2019t be caused by specific tables that are causing errors (since different numbers of tables donu2019t get loaded AND it is different tables each time)

Re: Issue #1 u2013 I have already troubleshot the servers not being running with support and I showed them that the servers were all running, but I was still getting this error

Re: Issue#2 u2013 I originally thought this could be caused because the WEBI Processing Servers that Live Office was using to download the tables were at capacity and therefore were faulting because they did not have enough memory to allocate to the requests, so I tried assigning the WEBI source report to a WEBI Processing Server Group that we have that gets very little traffic. This seems to have reduced the number of times that I get the error messages, but hence, I am still getting them.

BTW u2013 The dashboards that Iu2019ve created that consume less tables (5-6) seem to give me errors much less frequently, if at all. So I am convinced, perhaps incorrectly, that these errors have something to do with the number of tables that Iu2019m trying to pull.

[Former Member · Accepted solution]

Hello James,

Pulling 22 report objects via LiveOffice into Xcelsius is a tough challange...i would suggest to rethink your architecture / report-design.

Is it possible to sum the data up i less report objects (tables)?

LiveOffice Connections are highly optimized, but they work as serial connections. One after the other...so best practice

would be to reduce the number of LiveOffice connections as much as possible.

The "Refresh on Load" options sometimes causes trouble.

In Xcelsius 2008 there two ways to refresh data of on load. check: http://www.xcelsius-insight.com/index.php/2008/09/27/secrets-of-refresh-on-load

For interpreting LiveOffice errors check the following link: http://help.sap.com/businessobject/product_guides/boexir3/en/xi3_error_message_guide_en.pdf

Regarding error LO26315 i have observed that there a 3 typical types of causes.

- The WebI Processing Server is not running. It hangs with state initalizing.

- The structure of WebI-Report objects has changed. If you change the structure of the report objects it could be refreshed by LiveOffice.

(e.g. you have some kind of metadata (refresh time ...) which you load into your dashboard. If you add a row in the report table and

refresh the connection the error LO26315 will occur.If you change report structure you have to reinsert you LiveOffice connections in

Excel.

- The LiveOffice connection may be corrupted. Sad but true, sometimes this happens. I noticed that in some cases parameters disappear

of are set to wrong references. => Export your Excel-Model from Xcelsius and open it in Excel. Try to refresh LiveOffice Connections.

If the error still occurs. Check all LiveOffice Connection properties and reinsert the ones that don't work.

I hope this may help.

Best Regards

Ulrich

http://www.xcelsius-insight.com

[Former Member · Accepted solution]

Hi Ulrich -

Thanks so much for the reply - and very prompt too. I really appreciate you taking the time to read through the long post.

I couldn't agree with you more regarding consolidation of the reports. Unfortunately, I think you would understand that this comes at the cost of a much more complex Excel model. As my client is currently comfortable building WEBI and working within its environment, it's great for long term maintenance of the dashboard if they can build the reports in WEBI and levergae it's inherent functionality rather than building complex Excel logic (of which can cause other issues for Xcelsius). For example, if you have to build INDEX functions on top of INDEX functions on top of INDEX functions. Would be great if there was a way to leverage the 'INDIRECT' function in Excel, but unfortunately it isn't supported yet, so you have to build INDEX on top of INDEX (which works, but I've heard isn't officially supported either).

So, anyways, to your point, I'm definitely with you in terms of consolidating tables, but I'm hesitant if it means building extremely complex Excel logic....

In terms of the 'Refresh on Load' - I can test the other option that you mention, but my gut would tell me that I'd get the same errors, since I'm getting Live Office errors (since the Live Office routines would be the same in both cases) and not Xcelsius errors with the Initialization freezing, etc.

I have had the same experiences with you regarding LO26315, but unfortunately neither of these causes are the answer to my problem.

Suggestion #1:

We have 11 WEBI processing servers, and yes, while some of them may be stuck in the state of 'Starting', etc. that is definitely not the case for all of them (they are usually in 'Starting' mode because the server failed because of a capacity issue that cause it to fail).

Anyways, I've heard from Business Objects engineers that the dashboard Live Office connections will use the same servers that the WEBI source report is scheduled to. So, I scheduled the WEBI source report to 4 of the 11 servers that get utilized very little (hence they never fail). This should essentially eliminate this as being a cause.

Furthermore, with BO support on a webinar, I have checked to make sure all servers were running, then loaded the dashboard, and then still gotten the LO26315 errors.

Suggestion #2:

There are no changes to the report that have been made. As I mentioned, the LO26315 errors only show up about 20% of the time that the dashboard is loaded, in this time there have been no updates made to the WEBI report. Here is a typical scenario.

1st Dashboard Load: Get error LO26000

Close Dashboard

2nd Dashboard Load: No errors

Close Dashboard

3rd Dashboard Load: Get Error LO26315 x 3 (meaning that 3 tables of the 22 didn't load - let's say table 1, 2, and 3)

Close Dashboard

4th Dashboard Load: No errors

Close Dashboard

5th Dashboard Load: Get Error LO26315 x 2 (meaning that 2 tables of the 22 didn't load - except this time it could be tables 4 and 6)

Close Dashboard

Basically, it is always a different set of tables that don't load (give errors) and it doesn't happen everytime the dashboard is loaded.

Because of this, I'm strongly thinking this is an issue with the Live Office product and how the data is retrieved, but hoping it isn't....

After all - if Live Office works for pulling 3-4 tables (simple dashboard), then it should also be built to handle complex Enterprise dashboards as well (15-20 tables)....

[Former Member]

I'm having this issue too. I've been trying to solve it following the methods listed in this thread, but I haven't been able to find a resolution.

The fact is I have just one LO WebI query embedded on the Excel spreadsheet. From the Prompt tab of the LO object properties I have set a few filters, each one of those points to a specific cell (some of them are mandatory, some just optional).

When I launch the SWF preview, after I filled the logon screen, I receive the LO 26315 message error. If I try to update the query manually, modifying the cells I set as prompts, the query updates properly and with no errors. The error appears just when I'm trying to preview the dashboard (I tried using the "Refresh on load" option from the LO connection, then I disabled it and inserted the "Refresh on connection load" button, but as soon as I'm connected to the data server, I receive that error).

[Former Member]

Hi Guys,

So I'm tryingto solve this 26315 error as I get it also...

I'm in the same environnement as you (XI3.0) but I'm using only LO and Xcelsius.

Just to explain, my Excel file contains...... 41 LO queries !

Without speaking about changing the way I'm using Xcelsius and LO, I just wanted to share something with you :

launching the 41 LO queries trhough one unique Refresh button (linked to the LiveOffice quesries through DataConnector ) returns 8 to 10 LO 26315 error messages.

Now, if you create 4 different Refresh Buttons and that you attach only 10 queries to each one of them, hten it works fine... For me at least. So it's more time consuming as I have to click, wait... click again, wait again and so 4 times but at least it works.

Why I donnot know, but I just wanted to share...

Bye

[Former Member]

Hey Etienne -

Interesting idea, I like it.

Have you tried changing the Connection Refresh buttons to 'Refresh on Load' to see if they all refresh at the same time simultaneously.

I've learned that when you have multiple connections, then Live Office retrieves them serially (one after the other, in pairs of two).

So for 41 queries, there will be 21 retrievals one after the other.

But, perhaps breaking them into seperate buttons you can achieve more than two at once.

If you try, can you let me know the results.

Thanks!