topic Re: AttributeError: ToolValidator object has no attribute 'isLicensed' message? in Python Questions

AttributeError: ToolValidator object has no attribute 'isLicensed' message?

MichaelTorbett — Wed, 31 Jul 2019 16:31:22 GMT

I have a model created in ArcGIS Pro that I'm trying to run with a python script. The model runs fine in Pro but when I run it as a script i get the message in the title above. What does this mean? I have an advanced license, so all tools should be good to go.

I've used the python/model method several times before and haven't had this issue.

Thanks,

Michael

Re: AttributeError: ToolValidator object has no attribute 'isLicensed' message?

HaydenHinton — Tue, 06 Aug 2019 14:22:32 GMT

I have the same issue.

However, I am not trying run a model converted to python, rather, I am writing a script in Jupyter Notebook. Likewise, I have an advanced license.

All I have in the script so far is:

Import arcpy

arcpy.ExcelToTable_conversion(...

I am noticing that even though I get an error after running arcpy.ExcelToTable_conversion, it still completes the task can create an output.

Re: AttributeError: ToolValidator object has no attribute 'isLicensed' message?

JoeBorgione — Mon, 12 Aug 2019 15:46:33 GMT

Hello Hayden- were you able to get a solution to this? I am experiencing the exact same issue in a script I wrote prior to upgrading to Pro 2.4. Today is the first time I've gone back to the project, and I get:

AttributeError: 'ToolValidator' object has no attribute 'isLicensed'

In my case I am executing the script as a standalone in python; the first function in the script uses arcpy.ExcelToTable_conversion

Kory Kramer‌

Re: AttributeError: ToolValidator object has no attribute 'isLicensed' message?

KoryKramer — Mon, 12 Aug 2019 15:50:55 GMT

Looks like this was logged as a bug recently: https://support.esri.com/en/bugs/nimbus/QlVHLTAwMDEyNDI4Ng==

Re: AttributeError: ToolValidator object has no attribute 'isLicensed' message?

JoeBorgione — Mon, 12 Aug 2019 15:52:06 GMT

So.... just ignore the warning for now and carry on?

Re: AttributeError: ToolValidator object has no attribute 'isLicensed' message?

KoryKramer — Mon, 12 Aug 2019 15:55:17 GMT

Yes, given that there is no license requirement for the tool (https://pro.arcgis.com/en/pro-app/tool-reference/conversion/table-to-excel.htm#L_) just ignore and move on. I've pinged the gp team to make sure they can take a look at this recently reported issue. I apologize you're running into it, but looks like it isn't major...

Re: AttributeError: ToolValidator object has no attribute 'isLicensed' message?

JoeBorgione — Mon, 12 Aug 2019 16:10:38 GMT

No big problem; I'm good so long as it runs and doesn't bail out. Just caught my attention this morning...

Re: AttributeError: ToolValidator object has no attribute 'isLicensed' message?

MichaelTorbett — Mon, 12 Aug 2019 18:59:18 GMT

Good deal. Glad to know my script is working correctly. Thanks!

Re: AttributeError: ToolValidator object has no attribute 'isLicensed' message?

KostasAlexandridis — Tue, 03 Sep 2019 15:22:09 GMT

I got the same message, and my script is failing when trying to run a Jupiter Notebook for

arcpy.gapro.FindPointClusters(fclyr, fcout, 'DBSCAN', 2, '20 Feet')

It works fine when running it through the python window in ArcGIS Pro.

Re: AttributeError: ToolValidator object has no attribute 'isLicensed' message?

JoeBorgione — Wed, 04 Sep 2019 21:42:21 GMT

Kory Kramer‌ : has there been any movement on BUG-000124286 ?

Thanks!

Re: AttributeError: ToolValidator object has no attribute 'isLicensed' message?

KoryKramer — Thu, 05 Sep 2019 12:45:46 GMT

Hi Joe,

No, I don't see it assigned to a milestone yet. Have you subscribed to it at that link you included? BUG-000124286: Executing the script for the ExcelToTable function f..

Re: AttributeError: ToolValidator object has no attribute 'isLicensed' message?

JoeBorgione — Thu, 05 Sep 2019 13:45:32 GMT

Subscribed....

Re: AttributeError: ToolValidator object has no attribute 'isLicensed' message?

MichaelAndres — Mon, 09 Sep 2019 19:54:53 GMT

fyi... this error also appears while using the "AddGeometryAttributes_management" GP tool

Re: AttributeError: ToolValidator object has no attribute 'isLicensed' message?

corinnebowers — Mon, 16 Sep 2019 22:57:41 GMT

Same with the CalculateGeometryAttributes tool.

Re: AttributeError: ToolValidator object has no attribute 'isLicensed' message?

TheaYoungs2 — Thu, 26 Sep 2019 13:28:48 GMT

This is also occurring with the GeneratePointsAlongLine tool.

Re: AttributeError: ToolValidator object has no attribute 'isLicensed' message?

OleJorgensen — Thu, 31 Oct 2019 15:06:06 GMT

Same with arcpy.gapro.ClipLayer.

Re: AttributeError: ToolValidator object has no attribute 'isLicensed' message?

DelaereMickael — Mon, 25 Nov 2019 16:31:08 GMT

Same problem with : arcpy.management.CalculateGeometryAttributes

AttributeError: 'ToolValidator' object has no attribute 'isLicensed'

Re: AttributeError: ToolValidator object has no attribute 'isLicensed' message?

BobPool1 — Tue, 03 Dec 2019 17:19:00 GMT

This bug appears to be occurring on many tools. Especially the newer ones that use the parallel processing.

I noticed that Esri updated the bug report to say this "medium" bug will not be fixed at until 2.4.6. It looks like an extended wait until these tools are usable in Python.

So far I have been able to work around all of the broken commands by using the older versions of the tools. It is too bad because these new commands are much faster and more functional.

More cool, but broken tools:

arcpy.DissolveBoundaries_gapro

arcpy.OverlayLayers_gapro

Re: AttributeError: ToolValidator object has no attribute 'isLicensed' message?

JoeBorgione — Fri, 13 Mar 2020 14:55:42 GMT

Hey Kory Kramer‌ - I'm using Pro 2.5 and found that arcpy.BatchBuildPyramids_management() tosses the error as well. I subscribed to the bug and don't recall seeing any updates; I guess it's on going?

Re: AttributeError: ToolValidator object has no attribute 'isLicensed' message?

KoryKramer — Fri, 13 Mar 2020 15:54:13 GMT

Right now it appears to be fixed in Pro 2.6 (next version). I'm not sure if it is feasible to be included in a patch, but am checking on that.