on 10-08-2012 2:28 PM
Hi all,
I'm having a trouble while viewing or editing a dashboard craeted on dashboard design.
The unx is based on a SQL Server 2008 R2 database. One important thing to consider is that when i restart the Dashboard servers it works fine but after some usage the problems come back again.
Above the screenshot of the issue
Thanks in advance.
Best Regards,
Renan Ribeiro
Hi Renan,
Refer to the SAP Note-
1698180 - Error:"Request processing failed. (XLS 000009)" when dashboard created on universe query with OLEDB connectivity in Dashboard Designer 4.0 is previewed, if helpful !!!
Also, kindly provide detail information if you are trying to connect to ODBC or OLEDB connectivity?
Regards,
Namita
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I found this thread which described the same problem I was having.
I noticed that the SAP note http://service.sap.com/sap/support/notes/1698180 was updated on 7 Jan 2014. It now recommends as a workaround to change the "connection pool mode", under connection settings to "Disconnect after each transaction". I have done that and it seems to have fixed our problem.
We are using BO4.0 SP4 Patch 15 so cannot comment on whether it was fixed in SP5.
After long wait the ADAPT01616267 is still not related on SP5 or any SP5 patch.
I just found a new ADAPT01673874 ("Dashboard can be viewed and refreshed successfully on BI launch pad and dashboard preview mode. There should not be error Request processing failed (XLS 000009) when view dashboard through BI launch pad or dashboard preview mode.) on the last released SP5 patch 3 - 25/01/13.
Maybe this ADAPT01673874 is replacing the apparently unsolved ADAPT01616267 mentioned on SAP Note 1698180 or do i have to keep waiting for the resolution of the last one ?
Thanks again !
Best Regards,
Renan Ribeiro
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Henry, i was waiting for the ADAPT01616267 mentioned on SAP Note 1698180 for resolution but only the ADAPT01673874 comes on the recently released Patch 5.3.
Did you know if this new ADAPT01673874 is enough for solving my problem? I cant make the test because the new SP05 has updated the hardware recommendation and the customer needs approval to make this upgrade.
Thanks for your support !
Best Regards,
Renan Ribeiro
We are running into these errors on a daily basis (in the AM), and the only way we know to make them go away for a period of time is to reboot our main Business Objects server. We run a lot of publications over night and I am suspicious of this is related. We are currently running sp05 patch 4 on a Windows 2008 R2 server.
We have moved some (but not all) of our dashboards to ODBC connections per the reference SAP note, however we are still getting these errors on all of our dashboards.
Any help would be appreciated. I am planning to apply SP5.5 tonight, which was just released, to see if I have better luck.
Thank you.
Hi,
I think this is exactly what i need cause the universe connection is OLEDB and i'm using the query component of Dashboard Desuign. I'm currently working with SP02 P09 so i need to upgrade according to the sap note reffered.
Thank you for the very helpful info's!
I'm coming back soon to provide details of the solution.
Best Regards,
Renan Ribeiro
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
what version you are using as similar issues was solved by upgrading to the latest version of BI 4.0 currently SP4 patch 4 ?
Regards
F.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.