topic Re: Inaccessible Layers in ArcGIS Explorer Online Questions

Inaccessible Layers

DathenStrine — Tue, 09 Aug 2011 11:03:43 GMT

After creating my maps and having them work in ArcGIS.com I have tried to open the maps on Explorer Online and it continues to say that the source for the layer is inaccessible. I am not sure what I am missing with my set up to make it accessible.

Re: Inaccessible Layers

MikeRudden — Tue, 09 Aug 2011 12:44:03 GMT

The most common reason for this sort of problem is that the server hosting the services is missing a clientaccesspolicy.xml file. See the Troubleshooting section of the Explorer Online Help for more information.

There is also already a similar thread on this topic here .

Mike

Re: Inaccessible Layers

JamesGustine — Wed, 10 Aug 2011 21:43:49 GMT

I am having this issue as well. However, I have copied the clientaccesspolicy.xml and crossdomain.xml to the C:\Inetpub\wwwroot of the AGS machine that hosts my services. I can access these services thru the ArcGIS.com javascript viewer, but can't thru the AGXO silverlight app. I have also tried creating a web map in ArcGIS.com with the services and opening that map in AGXO....no luck. I get an innaccessible layer error.

I am really excited to use this app, but need to load my services. Any other tips?

Below is the contents of the clientaccesspolicy.xml file. Thanks for any help

<?xml version="1.0" encoding="utf-8" ?>
<access-policy>
<cross-domain-access>
    <policy>
      <allow-from http-request-headers="*" >
        <domain uri="*" />
<domain uri="http://*" />
      </allow-from>
      <grant-to>
        <resource path="/" include-subpaths="true"/>
      </grant-to>
    </policy>
</cross-domain-access>
</access-policy>

Re: Inaccessible Layers

MikeRudden — Thu, 11 Aug 2011 07:28:35 GMT

Hi,
Interestingly we came across the same problem yesterday - the user's services worked in the ArcGIS.com viewer but not in Explorer Online. There was a clientaccesspolicy file in the Inetpub root, but some investigation revealed that there were 2 IIS instances on the machine and that the clientaccesspolicy was not in the correct root of the website. Once the file was moved to the correct location the services worked in Explorer Online. To determine this there are a couple of things you can do:
1. Have a look at the IIS installs and configuration using the IIS Manager available in administrative tools
2. Make sure that the clientaccesspolicy can be accessed through http. So from a browser - http://<server name>/clientaccesspolicy.xml

For <server name> fully qualify it using the server.domain

Hope this helps
Mike