Dropping layers
Why does the Essential Manager sometimes tell me that some layers within a map service are not available when nothing has changed? The layers ARE in the service, the names are the same, but I'm being asked to removed them. Or in a recent case, I had 3 layers grouped and everything worked fine, then 20 minutes later when I was trying to make changes to the application (not pertaining to these layers) I'm prompted by the manager that some of those layers have to be removed. This isn't going to work too well in a production environment if layers just get dropped or can't be found even though they were there 20 minutes ago.
-
I have experienced this as well. One thing that is problematic about this is when I tell it which layer to add back in I loose all of the config settings for that layer and everything has to be updated again for the same layer.
0 -
I have also had this happen from time to time. When I click the "Test Connection" button it always comes back successful, and the prompt to remove the layer is removed.
0 -
I also have experienced this happening.
Sometimes clicking test connection resolves the problem, but other times I need to manually clear the ArcGIS rest cache for the connection to be successful.
0 -
I'm with Steven and Mick on this one too... multiple times it has happened, and clicking the test connection or clearing cache seems to do the trick. But why it's happening in the first place is worrying. We make no changes to the services that appear broken in the client, and they come back on line, and or off line. Can't put a pattern to it as yet.
Would rather know the problem than the cure ; )
G0 -
I get this too
Caroline0 -
Ditto....
0 -
To help us diagnose this problem it would be a big help if everyone could provide the version of Essentials they are running. Thanks,
--Ryan
0 -
Also if the affected ArcGIS Server map services are public please post the URLs or email them to support@geocortex.com. Thanks.
--Ryan
0 -
Getting this problemo with 3.7/1.4 combo
0 -
Version this happens with: 3.7/1.4
One of the ArcGIS map services: http://datcpgis.wi.gov/ArcGIS/rest/services/Base/APIBase/MapServer
0 -
3.7 / 1.4 unfortunately our sites aren't outward facing.
0 -
This happens to us all the time. Especially with layer groups.
We use 3.4.1
0 -
Has anyone had any luck in resolving this? I had a user call me this morning saying their app was down. It turns out that Essentials cannot connect to a particular service. The service is running.
If I remove the service from the site and then attempt to re add it, essentials can connect, but cannot generate a preview. I definitely don't want to re add it as I'll then have to reset all the settings for each layer.
0 -
+1
I also get this frequently.
@Latitude - i have secured external services i can provide if it helps but as its an intermittent issue i can't guarantee it will happen. I'm pretty sure it wouldn't take too much (or rather too many logins) to recreate the issue.
Brad
0 -
I see this with 3.9/1.5. If one ignores the error messages, the viewer opens and the allegedly missing services are available, so the concern is for confusing the user, not reduced functionality.
It may be relevant that we are still at ArcGIS Server 9.3.1 (but upgrading this week).
0 -
As I mentioned earlier in this thread, I see this problem on an intermittent basis. Unlike Kim's situation, the services really are missing on our site when that happens.
I was seeing this problem almost every day until I applied the vbs script found in this thread: http://support.geocortex.com/Forums/Thread.aspx?pageid=0&mid=2&ItemID=2&thread=46050&pagenumber=1
Steve
0 -
I was able to resolve my issue.
The service in question is running on a version 10 server. The map that the dropped service was based on had been opened and saved as a 10.1 document. While I could preview the service in ArcCatalog, it caused some confusion with Geocortex. So I backsaved the mxd to 9.3 (for good measure) and republished it as "Basemap_93" and repointed the broken link in the application to the new url. Because it's the same mxd, all of my settings for each layer were retained and everything is working as expected.
0 -
I get this from time to time....but my layers are availble.
I assume it is a network connectivity issue when it happens
Ken
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
18 Kommentare