Latest Contributions by ModyBuchbinder

Hi I am not sure I understand. Is this in the EB setting? There is nothing wrong with the gp service, it works from all the other applications. ... View more

Hi Derek There are some dat-i and dat.u files there. If you open them in notepad you can see some information on the services action (not sure what it say but the service name is there.. I checked a few systems, there are thousands of them for each system I checked. It does not looks like there is any process that delete them, I saw some files from 3 years ago. The total size is changing from less then 1 Gb to 8-9 Gb. Deleting some old files have big affect on how the server manager statistics response and it looks like on monitor too. I am not sure if it is the number of files or the size. Even if there is no monitor it does not make sense that this directory just keeping bigger and bigger for serve. Thanks ... View more

There are some news. Upgrade to 2025 did not solved the problem. Then we found this: https://community.esri.com/t5/arcgis-monitor-questions/metrics-for-arcgis-server-not-displaying/td-p/1578044 Checking the statistics dir found 2600 files with total size of 3.6Gb. After I understood that the monitor way to get the number of requests and response time is similar to the way in server manager where you open the Logs->statistics I made some tested there too. Any operation on server manager statistics took about 2 minutes (open a report, turn on one service etc.) So then I dropped all the files before 1/1/2025. It left about 900 files with 3Gb volume. Now the server manager report open in about 20 seconds and the monitor return to give the info.  The unusual thing about our machine is that it mainly run GP services. We only have 4-5 map services but about 70 gp services. About 20 of them is build in (System and Utilities libraries). Out of the other 50, I just stopped (but not deleted) about 20 so I left with 30 running gp services. Can somebody explain what these files are for? It looks like they have info about each run of each gp service. What do I loose if I drop anything but the last 3 months and why are they do not get deleted automatically?    ... View more

Hi @Ke_Xu  It is very simple. Create a Python script that get one parameter The script should not do anything else, the problem is before the script is running. You can open a cursor on the FeatureSet and print the coordinates (just for check). In a atbx I created a new script tool, the first parameter is a feature set that get point only (filter in the parameter screen) and pointing to my script. Run and publish. Try to use in experience builder As I said it works in REST, Pro, WebMap, old WAB and EB developer ... View more

Hi all The license is permanent. The table of data have 21m records and more records (host information but not services information) are keep coming. I will try to upgrade to 2025.0 next week ... View more

I am using atbx file, that is the default toolbox. This toolbox have no python code in it (The validation code does not published anyway). I found it the easiest way. ... View more

Hi all Why use python toolbox when regular toolbox where the python script saved separately is so much better. You can use IDLE like pycharm to edit your code. you just save the script and the toolbox see it immediately without need of any refresh.  You can run it within the IDLE for testing using the debug tools and you can use source control to keep history. None of this is easy to do in python toolbox. ... View more

Hi all I will check both suggestions next time I am in client site. Please remember that CPU, memory and disk space statistics continue to be monitored without any problem Thanks ... View more

Hi all You used python toolbox where the python code is embedded into the toolbox. I use simple toolbox where the tool is pointing (by reference) to the script (py separate file). Then when you publish you get the same structure where you have a py file with the script. It is easier to handle and you can use IDLE like pycharm that really help you get your code right. Move to simple  py file mean only to copy the execute function into a different file and define new toolbox. You might deleted something by mistake while editing the toolbox. Sometime when there is a strange error the problem is really in one of the previous lines. ... View more

The publish process change the script. You can find the published script under C:\arcgisserver\directories\arcgissystem\arcgisinput (after the changes) Sometime the publishing process add some single quote somewhere (I have no idea why). It is not supported to change the published script directly but if you go there, find the extra quote and delete it you should get it up and running. Have fun   ... View more

Is the first parameter to the tool (ducts) a layer in pro or a FC on disk? It must be a layer in Pro since the spatial join is on a layer and not on the real data. You can always use the Gp tool once and then copy the code from the History window. ... View more