Oops! The layer you requested is not available
Running Geocortex Essentials 3.6, Silverlight viewer 1.3
I have been trying to figure this error message out all morning: "Oops! The layer you requested is not available. Perhaps it has been removed." I receive the error when trying to "edit layer" in the 'Maps' section of Geocortex essentials.
In the map service all feature classes are being pulled from the same file geodatabase. The maps service has four layers, two of the four are giving me the errors, and two are working fine. ALSO the two layers that give me the errors in Essentials both draw fine in Silverlight, but return no attribute information when identified with the identify tool. For some reason geocortex is not seeing the attribute information.
I have tried, restarting the map service, re-creating the map service, recreating the .mxd/.msd, removing the service from geocortex and then adding it back.
Any suggestions??
Thanks,
-
Check one thing, when I identify in the Silverlight viewer it DOES return attribute data.
0 -
Craig
I assume it was working - what has changed since then?
Have you checked your SOM logs & also your geocortex SL logs? This may give you some clues as to what is going on. Can you confirm your objectID / shape attributes are being published at ArcGIS server end?
Last but least, can you create a new site & confirm whether the same issue is replicated?
Brad0 -
SOLVED-BUG I think
Not sure if this is a bug. But in the .mxd my layer name was "Zoning Floodlines/Regulation Limit". I found be removing the '/' and naming the layer Zoning Floodlines Regulation Limit it fixed the issue. This problem is with Essentials 3.6 and occurred after we upgraded. I am using the same service on a different server running Essentials 3.5 with no issue
Thanks Brad for the help, it made me think of a few things.
0 -
Hi Craig,
I have just set up a test service with forward slashes in the layer names and I can verify that this is a bug in 3.6. We are looking into this now. I'll post back when I have more information.
--Ryan
0 -
Hi All,
This issue has been resolved and the fix will be available in the next release.
--Ryan
0 -
Perfect,
Many Thanks,
0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
6 kommentarer