Dashboard Design 4.0 error 2170 cross domain issue

[Former Member]

I've created a dashboard against a query in 4.0 (so that it queries a universe directly) and when I publish it up, I get a 2170 error.

I've tried adding a cross domain policy file into the root of tomcat, but it doesn't seem to change anything. I can see the error clearly in the flash message, it's finding the file URL at SERVER1.MYDOMAIN.COM:8080, but it's trying to connect to the external data URL at SERVER1:8080. Obviously this is the issue, and it works on the server if I RDP into it, but not from any client, since they can't resolve SERVER1:8080, as its not in the DNS.

I can't specify the FQDN in Dashboard Designer, so I was thinking that maybe its using the connection that the universe already has, but when I check the connections in Infomation Design Tool, although I log into server1.mydomain.com, it shortens it down to server1 in the GUI. I'm thinking this is the root of my problem.

If I add Server1 to my workstation's hosts file, it frequently fails the first attempt with a 2170, then works after that, but this is no solution as I can't have everyone coming into infoview messing about with their hosts file.

Any way to force the external data URL to use its FQDN? Or any other workaround?

[Former Member · Accepted solution]

Hi,

I once encountered the cross domain error too. That time I updated the host file to have the server details in the below format as:

IP server1 server1.domain.com

Try it. It may help. In case you are executing on local - update host file of local machine, host file of BO server may also need to be updated.

Not sure how much this can help you but let us know.

Regards,

Dhanesh

[Former Member]

Finally rebooted the server, apparently just stopping and restarting tomcat wasn't enough, it seems to work now.

[Former Member]

quick update, I changed my hosts file again by removing the SERVER1 reference and saved it. The file still runs, so I'm now wondering if it caches it, and cached the copy before the cross domain policy file was installed. I'm figuring here that my workstation should have no knowledge of "server1" by itself anyway, as its the server's job to make sure it gets the data, not the workstation.

Otherwise, seems to be working, but a bit flakey.

Edited by: Matthew Randolph on Nov 3, 2011 3:31 PM

[Former Member]

And now, 10 minutes later, it's throwing the 2170 again every time I run the swf file. Not Ready For Prime Time?