Quantcast
Channel: SCN : Discussion List - BI Platform
Viewing all articles
Browse latest Browse all 5403

Design Studio won't Display on BI Launchpad

$
0
0

Hello,

 

First of all, please try to open the attached xml files on microsoft word. it didnt allow me to post docx.

 

We have BO 4.1 SP4 fresh installation on windows server 2008. We also installed BI Add-on 1.3 (SP1) for design studio and BO explorer. Everything is supposed to be installed with no error messages.

 

We developed some very basic design studio dashboards (with data sources and without data sources). We have no problem executing them locally. However, when we publish them to BI launchpad, it displays a very long error message.

 

I realized, this may be due to BO explorer-BI add on for DS conflict and BI add-on possible didn't create the necessary servers. Initially when we opened the published dashboards, it gave the attached error1.xml . I digged the error message and on CMC/servers tried creating Analysis Application Service (APS) under Analysis Services server group. After that, the error message on BI Launchpad turned to attached error2.xml .

 

I did some digging and tried to create an Adaptive Connectivity Service under Connectivity Services server group but it didn't create initially. There was a bug and we followed note (http://service.sap.com/sap/support/notes/2003628 ) worked around it and finally created the server. However, the error message is still the error2.

 

I tried repairing BI Add-on installation, it didn't change anything. I also went in to modify installation and made sure everything is chosen to be installed.

 

One more thing: published dashboards are also not visible on SAP BI Mobile application.

 

Does any one know how to solve this issue? Are we on the right track that this is a server issue that the BI Add-on setup forgot create?

 

Thank you all in advance


Viewing all articles
Browse latest Browse all 5403

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>