Arcpy in Geoprocessing Service

Question

I'm currently working on a python script that I will be publishing as a geoprocessing service in ArcGIS Enterprise.  I'm running into an issue with an arcpy function that works when debugging and when executing the script from ArcGIS Pro, but when it is published as a geoprocessing service the arcpy.ListTables() return None.  I've set the arcpy.env.workspace to the same URL of a feature service in all of my testing, but only when it executes from the geoprocessing service does it fail.  Any thoughts what's going on here? Is there certain arcpy functions that don't work in a geoprocessing service?

ArcGIS Enterprise 10.9.1
ArcGIS Pro 2.9.5

Code snippet

And here is the error, failing because arcpy.ListTables is None in the geoprocessing service context

esriJobMessageTypeError: Traceback (most recent call last): File "E:\arcgis\arcgisserver\directories\arcgissystem\arcgisinput\InformationFromSAMS.GPServer\extracted\p20\geoprocessors\Common.py", line 62, in LogMessageInDatabase integrationLoggingTable = FindTable(IntegrationFeatureServiceURL, "IntegrationLogging"); File "E:\arcgis\arcgisserver\directories\arcgissystem\arcgisinput\InformationFromSAMS.GPServer\extracted\p20\geoprocessors\Common.py", line 93, in FindTable for table in tables: TypeError: 'NoneType' object is not iterable

Anonymous User · Answer

Nice to see you are making progress. The workspace is more of local folder location or geodatabase from which inputs are taken and outputs are placed when running tools. Url's are invalid.  You could set it to a folder/ gdb on the server, but would that be needed?

KrisFoster1 · Answer

Update.... The arcpy.GetSigninToken() does have a token provided to arcpy so the appropriate log in credentials seem to be provided in the geoprocessing service for that portion.  I can at least use that token for direct rest service calls now, but would be ideal to be able to use the other arcpy calls with the appropriate credentials provided.  I tried setting the arcpy.env.workspace to the URL with the token provided, but that line crashed with the token specified.

KrisFoster1 · Answer

It's not shared to everyone.  The script is published as a geoprocessing service and that geoprocessing service is shared the same way as the feature service is.  To be able to execute the geoprocessing service you need to authenticate in the first place, so those credentials should be passed to arcpy (like it is when executed from ArcGIS Pro), but it doesn't appear to be doing that.