Hello,
I am trying to "Specify a Python environment for a single geoprocessing service" following carefully the documentation:
I cloned the default environment in the ArcGIS Server installation's Python environment directory as "newenvname". The cloned environement is functionnal.
Then, after updating the geoprocessing property on the REST Admin interface (ie: adding property "condaEnvironmentPath": "newenvname"), tried to run the tool and it returns "The tool is not valid".
Removing the property "condaEnvironmentPath" and the tool is back functional.
I tried on both a StandAlone ArcGIS Server and part of an ArcGIS Enterprise, same outcome.
I am running ArcGIS Server 11.5 on Windows Server 2022.Tried on WS2025 but the issue remains.
Anybody facing the same issue ? Did I miss anything ?
Thanks
Hello @NicolasGIS
I would like to confirm while running a script tool as a geoprocessing service, the tool fails, does returns the error message: ERROR 000816: The tool is not valid.
If Yes, You can check this document: https://support.esri.com/en-us/knowledge-base/000023081
If No, Could you run the script successfully in ArcGIS Pro?
Hello @Priya_Das,
Thanks for your reply.
I confirm the tool does return "ERROR 000816: The tool is not valid.”.
The thing is that I made a simple toolbox with no additional dependencies as it was not working and the error remains ! It is working successfully with default 'arcgispro-py3' environment configured but as soon as I configure it to run with the clone environment following closely:
It fails.
Anyway, support was able to reproduce and logged the following:
BUG-000180379: ERROR 000816: The tool is not valid.” returned for geoprocessing services published from Python toolboxes (PYT) when using cloned Python environments
Now I am more looking a workaround as I guess I can't hope for a patch for that, can I ?
Thanks