Silverlight 1.9 Viewer ClientAccessPolicy.xml issue
Hi,
We have 3.14 Essentials installed and are able to display our map services from our local server in the HTML5 viewer, but get an error displaying map services in the Silverlight 1.9 viewer. The error points to the ClientAccessPolicy.xml, but we've run over that and the CrossDomain.xml files on our ArcGIS Server IIS instance and nothing stands out in error. I have run Fiddler and the Silverlight viewer call for the xml file never seems to happen when pointed at our services. If I run the Charlotte example, I see the xml call and it works correctly. Also, I can display these same services in ArcExplorer Online (a Silverlight viewer) without issue. Is there a way to direcly point the viewer to the access policy file? Or do you see an error in the policy file below.
Below is the text of our ClientAccessPolicy.xml file
<?xml version="1.0" encoding="utf-8"?>
<access-policy>
<cross-domain-access>
<policy>
<allow-from http-request-headers="SOAPAction">
<domain uri="*"/>
</allow-from>
<grant-to>
<resource path="/" include-subpaths="true"/>
</grant-to>
</policy>
<!--Enables Silverlight 3 all methods functionality-->
<policy>
<allow-from http-methods="*">
<domain uri="*"/>
</allow-from>
<grant-to>
<resource path="/api" include-subpaths="true"/>
</grant-to>
</policy>
<!--Enables Silverlight 2 clients to continue to work normally -->
<policy>
<allow-from >
<domain uri="*"/>
</allow-from>
<grant-to>
<resource path="/api" include-subpaths="true"/>
</grant-to>
</policy>
</cross-domain-access>
</access-policy>
Thanks!
Brian
-
We had something like this happen to us... but with us it was to do with a group policy in Windows 7 and DNS issues.
Have you tried your Silverlight Viewer in Windows XP? or have you tried using IP addresses in of domain names for your services?
0 -
If this isn't resolved yet, go to your Geocortex Post Installation Configuration and click on Configure Cross Domain Support and select your Web Site and check to see if your clientaccesspolicy.xml is enabled. If it isn't, click the enable button. We had a similar problem when configuring the use of our proxy site. I hope this helps.
Aron
0 -
Thanks Aron. We got it resolved by using the specific domain name vs the server name. Even though the server name works for the HTML5 viewer and we are testing internally, the Silverlight viewer needed the domain extention to find the service.
Thanks!
Brian
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
3 Kommentare