Latest Contributions by MukeshVyas

Apology for the late response, but if I am correct, this should have been resolved in the newer version of AGS. Otherwise, this is the only option found for it. ... View more

Hi Everyone, Finally, we were able to convince Esri support that this is a bug. @Tanu Hoque...The bug you have identified is a result of persistence from our team. This is a bug recognised as a 10.7 version, but this is the only way Esri's process work. This bug has been lodged for 10.7 version and a patch will be released soon. However, we have demonstrated that this bug exists in earlier versions as well (i.e. 10.6, 10.5, 10.4 and some other customers have also mentioned the issue for 10.2). I guess customers will have to request a patch for other versions. Esri confirmed that this bug not only affects the rendering, but it also affects other operation such as identify, etc. Issue replication: Following are the steps to replicte the issue; 1. Navigate to the service end point. You might want to use your testing/staging service because this test will cause the SOC to go bad, requiring a restart of the service 2. Click 'Export Map' operation at bottom. You should see export output image. 3. Navigate back to the service's REST endpoint 4. Click 'Dynamic Legend' 5. Copy and paste following JSON block in parameter: 1. [{"source":{"type":"mapLayer","mapLayerId":1},"id":1},{"source":{"type":"mapLayer","mapLayerId":2},"id":2}] //replace 1 and 2 with a sub layer and a group layer id. In other words replace the "mapLayerId" with the sub-layer id first and then the parent layer id. 6. Click 'Get Dynamic Legends' 7. Once legend is generated, navigate back to the service's REST endpoint 8. Click 'Export Map' operation at bottom //this should generate blank image Workaround: Until a patch is released, following is the work around; - Use ArcGIS Pro 2.4 and connect to AGS (this version has the ability to connect directly to the ArcGIS Server). - Import your MXD as a Project and perform sanity checks (such as the symbology has not changed, definition queries, scaling, etc.). - Publish the service to AGS using ArcGIS Pro 2.4. - Once published, try to follow the steps listed under "Issue replication". You will not encounter the issue. Hope this will relieve the grief for most of the friends facing this issue. Regards. ... View more

#Issue resolved Hi Everyone, Finally, we were able to convince Esri support that this is a bug. @Tanu Hoque...The bug you have identified is a result of persistence from our team. This is a bug recognised as a 10.7 version, but this is the only way Esri's process work. This bug has been lodged for 10.7 version and a patch will be released soon. However, we have demonstrated that this bug exists in earlier versions as well (i.e. 10.6, 10.5, 10.4 and some other customers have also mentioned the issue for 10.2). I guess customers will have to request a patch for other versions. Esri confirmed that this bug not only affects the rendering, but it also affects other operation such as identify, etc. Issue replication: Following are the steps to replicte the issue; 1. Navigate to the service end point. You might want to use your testing/staging service because this test will cause the SOC to go bad, requiring a restart of the service 2. Click 'Export Map' operation at bottom. You should see export output image. 3. Navigate back to the service's REST endpoint 4. Click 'Dynamic Legend' 5. Copy and paste following JSON block in parameter: 1. [{"source":{"type":"mapLayer","mapLayerId":1},"id":1},{"source":{"type":"mapLayer","mapLayerId":2},"id":2}] //replace 1 and 2 with a sub layer and a group layer id. In other words replace the "mapLayerId" with the sub-layer id first and then the parent layer id. 6. Click 'Get Dynamic Legends' 7. Once legend is generated, navigate back to the service's REST endpoint 8. Click 'Export Map' operation at bottom //this should generate blank image Workaround: Until a patch is released, following is the work around; - Use ArcGIS Pro 2.4 and connect to AGS (this version has the ability to connect directly to the ArcGIS Server). - Import your MXD as a Project and perform sanity checks (such as the symbology has not changed, definition queries, scaling, etc.). - Publish the service to AGS using ArcGIS Pro 2.4. - Once published, try to follow the steps listed under "Issue replication". You will not encounter the issue. Hope this will relieve the grief for most of the friends facing this issue. Regards. ... View more

Yes we are facing same trouble since past many months. We have tried to troubleshoot in exact same way as explained in the initial post with no luck. We also observed that in our case, this happens especially with grouped layers.   We discussed this issue Esri consultants during the conference recently. Any help to identify the cause and find the resolution will be appreciated as we don't know how long it might take for us to identify the cause and resovle it.   Also it will be good to know if anyone else facing the same issue? ... View more

Hi Michel, Our setup is in cloud, but we haven't seen such a behaviour anytime in past with cloud setup. We used AGS version 10.5.1. We also tested laod, port connection limits, if any temporary network outage may be causing, etc. We have not been able to find any positive outcome so far. We are using SDE. We have approx. 30-50 services running, but we have observed this behaviour with particular services only (not sure if other services may be behaving in similar manner, but haven't observed anything). What is the setup on your side? ... View more

Yes we are facing same trouble since past many months. We have tried to troubleshoot in exact same way as explained in the initial post with no luck. We also observed that in our case, this happens especially with grouped layers. We discussed this issue Esri consultants during the conference recently. Any help to identify the cause and find the resolution will be appreciated as we don't know how long it might take for us to identify the cause and resovle it. Also it will be good to know if anyone else facing the same issue?  ... View more