Hi All - I'm trying to set up a SQL Agent job step (pics below, SQL 2016) that runs a .py geoprocessing script built using Pro (3.6.5) on our test server. So far, the job step only works IF I specify my Windows AD account as the SQL Agent Service Logon. However, our group needs to run these using a common AD account OR by using the combination of a Local System Account (as Logon) and SQL Agent Proxies...I have tried running this scenario with Pro set as Single Use, Named User, Authorized for Offline Use, Signing In Automatically, etc. ArcGIS Pro (2.2.1) was admin-installed for all users on the server and the script (.py) runs successfully when called in Task Scheduler, IDLE, other environments etc. My guess is that the job step fails on "import arcpy" because I'm getting successful print messages from the script before that line occurs.
Any assistance or suggestions appreciated!
Job History Error:
"...import arcpy File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\__init__.py", line 72, in <module> from arcpy.geoprocessing import gp File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\geoprocessing\__init__.py", line 14, in <module> from ._base import * File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\geoprocessing\_base.py", line 14, in <module> import arcgisscripting RuntimeError: Not signed into Portal. Process Exit Code 1. The step failed...."