Latest Contributions by TanuHoque

@PLadd unfortunately 3.0 is a breaking release that means project or layer file or anything that create in 3x can't be opened in 2x directly. I think this is what you can do this though - have 3.2 install temporarily, open your projects you created in 3.2 before... share them out as project package. Uninstall 3.2, install 2.9 and open project packages. Please note, this will allow you project open in 2.9 -- that said, if you used anything new in 3.x e.g. some new symbology that is only available in 3.x, you won't see them correctly in 2.9 hope this helps ... View more

@abhishek_choudhary  As I mentioned above, you can't enable Feature Access extension when your data lives in file gdb regardless if you chose to publish by reference or 'copy data'. you must have enterprise database in order to turn on Feature Access extension. I hope this help. Otherwise, pls let me know ... View more

@abhishek_choudhary  Thanks for sharing the screenshot. That is very helpful. As you see, the service is pointing datasets inside from a FileGDB. Feature Service (aka the Feature Access extension of map service) can't be enabled when data resides in a FileGDB. It must be in an enterprise database for allowing multi user editing. I see you published with 'copy data' option - that begs the question why do you need support editing capability when this filegdb lives in a managed location and will get deleted when you delete this service? ... View more

@BHK    1- How many service can be published in each shared pool? For example at following set up with 4 shared instance, how many services can I have in all 4 instance and in each of them? TH: The idea behind shared instances is that there is no limit. You can publish as many as you want. The main thing is that how many of them will remain cached. Therefore when a request comes in for a service, it can return the result immediately instead of going thru all initializations.  In this example below, you see you can have up to 50 map services cached per SOC process. If I happened to have 51 map services, when a request comes in for the one service that is not cached in shared instanced, it will kick out one from the cache and make room for the new one, the map service instance starts up and returns results back to the client app. As per an arcgis server doc, The cache size setting controls how many services are cached by each instance in the shared instance pool. Unless you have a large amount of memory and a large number of services that are all regularly receiving requests, it's recommended that you keep the default value of 50 cached services per instance. You may consider raising the cache size value if you have more than 50 services that are regularly receiving requests, you are experiencing performance problems, and you have available memory you wish to use for this purpose.     2- Considering the following settings (4 shared instance), how many ArcSOC will be process at server? TH: There is one SOC process for each shared instance. Since you set '# of shared instances per machine' to 4, you will see 4 SOC processes. That also means at any given time only 4 requests can be processed simultaneously; once the 5th request comes in, it waits until one of the 4 SOC process available to response. To view them, open Task Manager app on you Windows machine >> switch to Details tab >> if not done already, right-click on any column name, choose Select Column command, check Command Line column, click on OK >> you will see 4 SOC processes with -Dservice=System.DynamicMappingHost.MapServer in their values under Command Line column.     3- Considering the following settings (4 shared instance), how many CPU Cores will be needed at server to keep process under control? TH: I can't answer this. I'd defer it to others who are expert in this area. Here is an excerpt from an ArcGIS Server doc: If most or all of your site's services use the shared instance pool, consider setting the number of service instances in the shared pool to twice the number of physical CPU cores on the individual machines in yourArcGIS Serversite (for example, if you're using 4-core machines, consider setting the pool size to eight instances).   also I'm adding a link to this blog post which a future reader might find helpful: https://www.esri.com/arcgis-blog/products/arcgis-enterprise/administration/shared-instances-arcgis-server-107/    i hope this helps ... View more

@MattReeves_SpokaneValley  so sorry, it looks like the notification didn't make it to my radar until now 😞  in case you are still having the issue, first thing is that if you author templates in Pro 3x (or you publish it from Pro 3x), you need to have Server upgraded to 11x. I hope you have already found a solution. So sorry for the delay ... View more

@SCS_ANST  pls check and see if this approach helps https://pro.arcgis.com/en/pro-app/latest/help/mapping/layer-properties/define-parameters-in-a-query-layer.htm  ... View more

Thank you @KarenShaw for upgrading to 3.2 and checking this out. We are very glad that you've found this helpful. ... View more