Latest Contributions by JeremyRead1

‎05-07-2019

That did it! Thank you!

‎05-07-2019

I am using a Python script to query an ArcGIS Online feature service, and then I want to create records in an on-premise feature class based on the results. I've done this many, many times with point features, but never with polygon features. I cannot seem to figure out how to create a polygon shape from the JSON parameters (coordinates/rings). for feat in agolQueryJson['features']: feature_coords = feat['geometry']['rings'] For the first record, the value of feature_coords is as follows: [[[3119080.82716037, 10062393.2323891], [3119167.33715791, 10062378.1910806], [3119165.12029902, 10062150.6820212], [3119136.04194509, 10062115.4521047], [3119109.98523858, 10062106.2047479], [3119106.03478733, 10062060.0765594], [3119080.82716037, 10062393.2323891]], [[3119080.82716037, 10062393.2323891], [3119079.78123078, 10062393.4141472], [3119079.72545653, 10062407.7937117], [3119080.82716037, 10062393.2323891]]] I have not figured out how to take this and turn it into a polygon shape that can be used in an insert cursor. I've tried using arcpy.AsShape and just arcpy.Polygon, but no luck with either method: poly = arcpy.AsShape(feature_coords) poly = arcpy.Polygon(arcpy.Array([arcpy.Point(*coords) for coords in feature_coords])) Any suggestions would be most appreciated!

‎08-18-2017

Well, I never did figure out why this was happening, but I finally have a work-around that was successful. I wanted to share it in case anyone else runs into this issue: Do not use the built in database connections; create a .sde connection file somewhere on the server (C:\MyConnections\connection.sde) and use that to load data into the GP tool. Run the tool and publish it. After publishing, navigate to the staging folder and find the toolbox in there: C:\Users\username\AppData\Local\ESRI\Desktop10.5\Staging\arcgis on server.domain.com_6080 (admin)\sddraftToolboxes\MyToolbox.tbx Copy the above toolbox, then navigate to the export folder for the service: C:\arcgisserver\directories\arcgissystem\arcgisinput\MyService.GPServer\extracted\v101\MyToolbox.tbx Paste the copied toolbox from the staging folder over the same toolbox in the export folder and replace it. Restart the published GP Service so that it pulls in the change. The GP Service should now run correctly. I am not sure why this is happening, but the above steps seem to fix it. Something is happening to the toolbox when it is published that is causing its parameter validation to fail. I was looking in the Python code for the tool until I realized that the code never actually ran; it was failing at parameter validation. Also, it did not like if I used a connection file within the systems "Database Connections" path; it wanted a .sde file sitting on the C: drive that it could easily find. I hope this helps someone else.

‎08-16-2017

One more thing I've noticed: When navigating to the copied .sde file: C:\arcgisserver\directories\arcgissystem\arcgisinput\Tool.GPServer\extracted\v101\connection.sde I noticed that it is setup as an "Application Server" connection under "Database Platform" in the connection properties, and has this weird string in the "Service:" field. This was not how it worked in ArcGIS Server 10.3.1 as it just created a regular SQL Server connection file. I changed the .sde file back to a regular SQL Server connection and verified that it worked, but when re-running the tool I ran into the same issue as before.

‎08-16-2017

Hi Michael, I do not have any others that I have tested yet. Both of the ones I'm testing work with network datasets. Below are the details of the servers/environments I'm using: ArcGIS Server Machine: Windows Server 2012 R2 ArcGIS Server 10.5.1 ArcGIS Desktop 10.5.1 Geodatabase Machine: Windows Server 2012 R2 SQL Server 2014 Geodatabase version 10.5.1 (was originally trying on a 10.3.1 geodatabase, but both versions produce the same error) I am interested to know if you run into the same issue. Thanks, Jeremy

‎08-16-2017

Thanks Micah, I will check the validation logic but I don't remember it being anything too crazy. Even on the really simple tool I still had this issue. I wonder if this is actually a bug of some sort, but there just aren't enough people using 10.5.1 yet to run into it. Either way, I appreciate your help and I will update this thread with the solution if I ever find one.

‎08-15-2017

I am using ArcGIS Desktop 10.5.1 to publish the service.

‎08-15-2017

Hi Micah, Thank you for the great suggestions. The geodatabase only has the DEFAULT version and no others. I also verified that the 64-bit version of the database client is installed. Also, I would assume that none of the other services would work if anything was amiss here, but they are all working correctly. Only the GP services get this error. Thanks, Jeremy

‎08-15-2017

Hello Adrian, Thank you or the suggestion to move the question to the correct space. As for the tech support articles, I have read those as well and my issue seems to be unrelated to what they are describing, however I will try a few of the solutions again to make sure I didn't miss anything. I'm still not sure what changed between 10.3.1 and 10.5.1 that would cause this to occur, but it seems to be specific to GP services. All of my regular map/feature services work perfectly fine. I tried adding a few messages in the Python code to see if it gets to them, and it never does. It fails almost instantly, as if it's doing a parameter verification before even running the Python code, and in this verification it can't find the data it is looking for.

‎08-08-2017

Ok, here was the solution in my particular case. We had to change the function in the widget that returns the Sublayer Id's to be able to return "undefined". See below where "return '1=1';" was commented out and changed to "return = undefined;" filterLayer: function filterLayer(layer, whereClause) { var layerDefinitions = layer.layerInfos.map(function (layerInfo) { if (layerInfo.subLayerIds == null) { return whereClause; } else { // return '1=1'; return undefined; } }); layer.setLayerDefinitions(layerDefinitions);‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

‎08-07-2017

So, I've been working with a really smart developer at Esri, and he's discovered that if you have sublayers within layers, and those sublayers are turned off by default, then that makes this error show up. It's requesting the sublayers and since they are off, it cannot find them to display on the map. He modified the request to exclude these layers, and it worked correctly and returned the .png image. Not sure of the final solution, but it's probably going to either be a code modification for it to avoid sending the sublayers which are off to the request, or just having all the sublayers turned on in the map service. Just wanted to pass this along in case it may help you. I will also update with the final solution for this once it is in place. Wanted to note that version 10.3.1, which we were on before, did not care about the invalid sublayers and just ignored them. 10.5.1, however, does care about this and will fail on these.

‎08-07-2017

I have a GP tool that I had no issue running on ArcGIS Server 10.3.1, but when trying to setup the service on a 10.5.1 machine, I am running into an issue that I've been unable to resolve: The tool runs in ArcMap fine and publishes successfully, but when I run it I get the following error: Error 000732 Network: Dataset ______ does not exist or is not supported. I thought that for some reason the arcgis user could not access the folder, so I gave it permissions on the entire C:\arcgisserver directory That did not fix it, so I navigated to the copied .SDE connection file in ArcCatalog at: C:\arcgisserver\directories\arcgissystem\arcgisinput\Tool.GPServer\extracted\v101\connection.sde I was able to connect and view the data with no issues. So then I tried a simpler tool that just lists the feature classes in a geometric network. Same issue. I noticed in the error, though, that it is automatically stripping out the "Database.SchemaOwner" heading on the data. I manually entered these back in and the tool worked. Going back to the first tool, I noticed the same thing. The tool is looking for this and failing: \connection.sde\FeatureDataset\Network_Net When it is supposed to be looking for: \connection.sde\Database.SchemaOwner.FeatureDataset\Database.SchemaOwner.Network_Net Why is it stripping these values out? It seems to do this on its own without me telling it to. I even went into the extracted copy of the python script and explicitly added the paths into the code, and it is still doing this at runtime anyway. Since it is doing this, it cannot find the data it is looking for and thus failing to run.

‎07-24-2017

I am having this same issue, but in 10.5.1 where it was supposedly fixed. The frustrating part is that it only happens on one of my services but is fine on the others. I've tried republishing this service, etc., and have had no luck.

‎06-15-2017

Hello Randall, Thank you for your response, and great idea to check the maxTokenExpirationMinutes. I checked for this on our org site using the method you outlined above, and the value is set to -1 as expected.

‎06-14-2017

Hi Rebecca, Thank you very much for your reply! We haven't had any licenses come due for renewal, no password change for the AGOL user, ArcGIS Server admin or service accounts. Like you, we have a service user with a static password. We are using WAB Developer Edition, version 2.1. We have the ArcGIS Server services registered/linked through AGOL.

Online Status	Offline
Date Last Visited	‎02-07-2024 09:10 AM

My Ideas

Latest Contributions by JeremyRead1

Re: Need help with creating a Polygon from JSON

Need help with creating a Polygon from JSON

Re: Can publish GP Service but cannot run it on ArcGIS Server 10.5.1

Re: Can publish GP Service but cannot run it on ArcGIS Server 10.5.1

Re: Can publish GP Service but cannot run it on ArcGIS Server 10.5.1

Re: Can publish GP Service but cannot run it on ArcGIS Server 10.5.1

Re: Can publish GP Service but cannot run it on ArcGIS Server 10.5.1

Re: Can publish GP Service but cannot run it on ArcGIS Server 10.5.1

Re: Can publish GP Service but cannot run it on ArcGIS Server 10.5.1

Re: imageparameters.layerDefs does not work with 10.5

Re: imageparameters.layerDefs does not work with 10.5

Can publish GP Service but cannot run it on ArcGIS Server 10.5.1

Re: imageparameters.layerDefs does not work with 10.5

Re: ArcGIS Online login prompt randomly displaying

Re: ArcGIS Online login prompt randomly displaying

Re: Can publish GP Service but cannot run it on Ar...

Re: imageparameters.layerDefs does not work with 1...

Re: imageparameters.layerDefs does not work with 1...