BusinessObjects Board

Error# 2170 - sap business objects xcelsius 4.1 Tool

I have migrate dashboard from XIR2 to 4.1 version. In this dashboard there is parent child linking. i.e. child dashboard calling from parent dashboard. But when child dashboard is open from parent dashboard, it gives error# 2170. I have double check all data connections(WSDL URL, Service URL, Input/Output variables) and but there is no problem. I have explore this error more in details, every article suggest that put crossdomain.xml file in your server’s root directory. I have did it and But still same problem exist. Please find my crossdomain.xml file’s content in below attachment.

So please suggest any solution.

Thanks in advance.
CrossDomainXmlCurr.png


Jigs4u (BOB member since 2015-11-30)

I have always heard that you have to put in the web services root directory (Tomcat root?). FYI: The cross-domain issue has been a pain for our organization for a number of years).


kevlray :us: (BOB member since 2010-06-23)

Yes, I have put crossdomain.xml file in tomcat root.


Jigs4u (BOB member since 2015-11-30)

Hi,

Have you restarted Tomcat after the crossdomain.xml file was copied to the Tomcat root?


Marek Chladny :slovakia: (BOB member since 2003-11-27)

Yes, I have restarted server. Can you please check my attached crossdomain.xml file, is it correct or not? Is there any other possible problem other than cross domain problem?


Jigs4u (BOB member since 2015-11-30)

This is basically what we use. I do not know if it will help.

<?xml version="1.0"?>

kevlray :us: (BOB member since 2010-06-23)

Actually i am new to business object. So can any one explain why this crossdomain.xml file is required? Because my parent and child dashboard are published in same server and same folder.


Jigs4u (BOB member since 2015-11-30)

If it’s SAP Business Objects Dashboards you’re talking about (the one that is essentially Xcelsius rebadged), then it might be to do with the bug I found, since by calling a child dashboard, you are sending data out. Depends on your connections, I guess. I do know that SAP and our support providers spent a long time looking at configuration files and the crossdomain policy files before they admitted there was a problem.

Debbie


Debbie :uk: (BOB member since 2005-03-01)