Select to view content in your preferred language

Identify Task returns wrong layer info after removing layer from map service

2765
8
11-02-2010 10:14 AM
DanJensen
Deactivated User
All,

I have removed a layer from a map service then deleted and recreated the map service, then cleared the rest cache.  Still when I use my custom identify tool the indentify task acts as if the layer where still there?  When removing layer 28, layer 32 (perhaps the old layerID of the county polygon layer) becomes layer 31(new layerID of county polygons).  The rest service end point shows this correctly (county polygon layerID=31) , but when I use the identify tool if layer 32 (new layerID of some other layer) is visible info from layer 31 (the former layer 32) is displayed.  Layers below 28 are unaffected and identify correctly.

Has anyone encountered this or have a resolution for this issue?

Thanks,
-Dan
Tags (2)
0 Kudos
8 Replies
RobertScheitlin__GISP
MVP Emeritus
Dan,

   I have seen this before, the best thing to do is reboot the server.
0 Kudos
DanJensen
Deactivated User
Unfortunately I am getting the same result after rebooting the server.  Any other ideas out there?

Thanks,
-Dan
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
Dan,

   Is it a MSD or MXD that is actually published? If an MSD did you re-save the MSD and then republish?
0 Kudos
DanJensen
Deactivated User
It is an mxd.  I have deleted the map service and then recreated the service.  I have also cleared the cache of the rest service.

-Dan
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
Dan,

   What about your browser, have you cleared it's cache? Have you accessed the REST Services directory from another machine to see if the changes took?
0 Kudos
Drew
by
Frequent Contributor
Dan,
Assuming you don't have others consuming this service and require it to be named XYZ, you might want to delete the current one and recreate it with a new name.  That might clear it up (for now 🙂 )

Drew
0 Kudos
DanJensen
Deactivated User
Yup, I deleted anything I could on my browser and when I look at the service from another computer it looks correct.

I will try the new name idea as soon as I can.

-Dan
0 Kudos
DanJensen
Deactivated User
All,

I finally found the problem in my code.  The result of having both a production and a development environment with slightly different names.

Thanks,
-Dan
0 Kudos