False configured layer does not exist errors

Permanently deleted user

February 26, 2016 19:02

I am getting false "configured layer does not exist in map service" errors with sites when opening them in Essentials Manager.  The services and layers do exist and are on in arcgis server; they show on the rest endpoint; and the related viewers show them until I try to open the site in Manager, then they disappear from the viewer (without me removing the layer's configuration from the site).  If I open the associated mxd and republish the service, I no longer get the error opening the site in Manager.  If I cancel out of the site in Manager, when getting the error and making no changes, then go back in, I get a different layer does not exist error (not the same layer each time).  The selection of which layer and service has the problem seems to be random.  I also find that republishing a service may need to be repeated before opening any other site that uses it.  To make things more confusing, this problem occurs intermittently, lasts for a few days, then goes away on its own.  I am using Essentials 4.4.2 and arcgis server 10.2.  The data is coming through SDE.  Does anyone recognize what might be causing this problem?  Thanks.

0

• 

  Permanently deleted user

  June 30, 2016 19:35

  I am having the same problem and would like to know what's causing it.  Basically I cannot make any changes tio a site unless i first agree to remove the layers that are "missing".  By adding them back, I have to repeat the thrash of setting up all of the properties.

  As you said, it's very random and republishing seems to work, but then another one shows up as "missing".  It's counter productive to hae to republish every service in the application just to get these false errors to stop popping up.

  0
• 

  Stefan Schweigert

  June 30, 2016 21:13

  Hello Douglas and Scott,

  The issues that you are both experiencing are unusual. This warning can appear when Manager attempts to connect with the service and it takes longer than expected. When the warning appears, does the dialog provide a list of layers to replace, or simply that the layers are missing? Also, can you check to see if there are any errors present in the ArcSDE which might be affecting the service?

  If possible, can you provide a link to one of your services or layers for us to be able to reproduce this issue?

   

  Thanks, Stefan

  0
• 

  Permanently deleted user

  July 05, 2016 20:59

  I think I was only getting a message that the layers are missing.  I haven't seen this error for 3 or 4 months.  In my case, I think the problem was with my network causing very slow arcgis server response times.

   

  Doug

  0

Please sign in to leave a comment.