Error with toolboxes in ArcGIS Pro 2.2

BUG-000112192 - Unable to activate a new Project Environment using the Python Package Manager

work around: rename files with extensions .pyt to .pyt_xyz, close and open ArcGIS pro, the toolboxes are loaded

All comments

MalcolmWilliamson

Hi Ghislain,

Thanks for the correction, you've put me on track to a solution! Upon "import arcpy", it seems that it's referencing a stray python path with a problematic version of numpy:

>>> import arcpy
Traceback (most recent call last):
File "C:\Users\malcolm\AppData\Roaming\Python\Python36\site-packages\numpy\core\__init__.py", line 16, in <module>
from . import multiarray
ImportError: cannot import name 'multiarray'

(and more stuff)

I list the paths:

>>> import sys
>>> for p in sys.path:
... print(p)
...

C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\python36.zip
C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\DLLs
C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\lib
C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3
C:\Users\malcolm\AppData\Roaming\Python\Python36\site-packages
C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\lib\site-packages
C:\Program Files\ArcGIS\Pro\bin
C:\Program Files\ArcGIS\Pro\Resources\ArcPy
C:\Program Files\ArcGIS\Pro\Resources\ArcToolbox\Scripts
C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\lib\site-packages\future-0.16.0-py3.6.egg
C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\lib\site-packages\pytz-2018.3-py3.6.egg
C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\lib\site-packages\sympy-1.1.1-py3.6.egg

(Highlighted bad path in red)

So, I can fix the problem just by renaming or removing the rogue Python location. But I am curious how the ArcGIS Pro Python installation found that path in the first place. Is C:\Users\%USERNAME%\AppData\Roaming\Python a standard path that a new Python installation looks for, or was this stored somewhere?

Again, my ArcGIS Pro problem is cured once I've removed the problematic files - just curious how the ArcGIS Pro Python installation got crosswise with it. Thanks very much for your help!

gprince

Hi Malcolm,

that's the error you'd get if you forgot to import arcpy. Try this instead pls...

1. windows start button , select "Python Interactive Terminal"

2. import arcpy

3. print(arcpy.GetInstallInfo())

MalcolmWilliamson

Drew, I have the same problem as the OP, which started under 2.1.x and has carried over to my 2.2 installation (I actually did an uninstall on 2.1.2 prior to installing 2.2). When I run arcpy.GetInstallInfo(), I get the following:

Traceback (most recent call last):
File "<string>", line 1, in <module>
NameError: name 'arcpy' is not defined

I assume that there is a problem with a python installation on this computer, but I do not know how to fix it. I currently have Desktop 10.5 installed, along with lots of other software. The problem does seem to be tied to my Windows user account - a freshly created local user doesn't have the same problem. Thanks for any suggestions.

George_Thompson

I just got a response from technical support and they are aware of the issue, in relation to Python package manager, not the toolboxes.

My recommendation if for anyone encountering this issue to contact Esri Technical Support and get attached to the defect(s) that apply.

BUG-000111732 - Failed to activate a newly created Python environment in ArcGIS Pro

BarbaraDabney_0-1759524334813.png

BarbaraDabney_1-1759524707079.png

Marco... I tried and I can confirm what you have found

Dan, nothing gets "uninstalled", your old environment gets "backed up" when you upgrade to the official 2.2 release, that is exactly what the Help describes, and what I saw happening with my customized Python environment (I actually only installed one extra package - pyodbc - in Pro 2.1, and I see it listed in the "backup" copy of the old environment):

The Python Package Manager—ArcPy Get Started | ArcGIS Desktop (see the "Notes")

If your "2.2 beta" did not do this, than ESRI may have hastily added this inbetween 2.2 beta and the official 2.2 release, that haste might actually explain the bug being introduced... but that is just mere speculation.

DrewFlater

Mark Tukman‌ did you upgrade to Pro 2.2 from a previous version? Were you using customized Python environments? The PYTs can fail to initialize when there is a corrupt Python environment, which can also stop you from running ArcPy or other Python commands in the Python window. Can you try a simple arcpy command like arcpy.GetInstallInfo() in the Python window?

I check python packages, python-dateutil is already installed

Somehow untools cannot load dateutil module. Any ideas?

I have installed untools 2.2.0 using this command: conda install -c esri untools

and the untools shows up on the Installed list, as shown below

However, I don't see the tools in my toolbox.

I added the tool manually, this is the error I got:

Any ideas how to fix it?

MarkTukman

Thanks Hung. That works.

mark

It seems like Pro 2.2 has problems loading .pyt files

work around: rename files with extensions .pyt to .pyt_xyz, close and open ArcGIS pro, the toolboxes are loaded

Marco... everytime I have upgraded, the previous packages that I have installed came with it. I installed Spyder and other stuff once (back in 1.??). So I am not sure what is going on... This last update I was on Beta 2.2... maybe that is why I still have everything and didn't need to reinstall. But when I was on 2.1 and moved to beta 2.2, nothing was 'uninstalled' when I arrived. I would have rapidly exited/rolled back if that had been the case

Well, I guess here we have (the)/a bug: look at the two images, notice how the file path of the environment contains an underscore, while Pro omits it in its interface:

@George Thompson ?

The Python Package Manager—ArcPy Get Started | ArcGIS Desktop

Dan: I think that is normal, the Help clearly states that the old environment is backed up with a name <OLD_ENVIRONMENT_NAME>_backup, see here:_

"When updating from an earlier version of ArcGIS Pro, if an older arcgispro-py3 environment exists, it will be renamed to prevent overwriting. The existing environment's folder name will be appended with _backup. A new default arcgispro-py3 environment will be created and activated automatically."

And if you look at the image the OP posted in that other thread you linked, you can see he has the <OLD_ENVIRONMENT_NAME>_backup visible in his package manager.

I also had a look at my backup environment, and it did have the one package I installed in it.

Remains the problem that you cannot even switch to the old environment, because the change / selection doesn't stick: once you open the package manager again, it is back to square one on the new - read-only - default environment. It just won't let you change the environment to anything else from the default.

One interesting things though: I now notice the "backup" version lacks the supposed "_" underscore, it is listed as:

<OLD_ENVIRONMENT_NAME>backup

instead of

<OLD_ENVIRONMENT_NAME>_backup

This is not according to the Help, it should have the underscore in the name.

https://community.esri.com/thread/217048-arcgis-pro-220-and-python-package-manager

The problems seems to run deeper than just the frozen package manager.

At least one report of previously installed packages not being carried over in the new update

This is the error message I got:

seems like the Spatial Statistics Tools.pyt is corrupted

I've experienced the same issues. uninstalled and re-installed doesn't fix the issue. I found all the tools available under installation folder C:\Program Files\ArcGIS\Pro\Resources\ArcToolBox\Toolboxes

Is there any fixes to this issue?

George_Thompson

Marco Boeringa‌ I have the same issue and opened a case with technical support. I will let you know the end results.

Glad it was not just me that had that issue.

MarkTukman

Hi Theodore:

New and existing.

mark

I saw that error message about the Spatial Statistics Tools toolbox popping by as well at one point when opening Pro. However, after another restart of Pro, this seems resolved and I can see the toolbox:

A more disconcerting issue for me though, is that I cannot seem to get the Conda managed Python environment to switch. At 2.2, the default Pro environment has become read-only according to the Help, and you are forced to create a clone or new environment to make changes and install packages. However, I for the life of me, cannot get this to work:

- As the Help stated, I cannot change or install a package to the default environment in 2.2

- Creating a Clone seems initially to work, but once I select the clone and close the dialog, I am left with an empty enviroment dialog:

- When I restart Pro, as the dialog warned me to do, the "test" environment I created and that IS visible in my user profile as a new folder, is not recognized by Pro:

So I am currently stuck with the default environment, that I cannot change because it is now read-only at 2.2...

I have no problem with new or existing projects... I suspect your update didn't go well, that is what I was referring to.

TheodoreF

This is concerning. I cancelled my update download as I read this.

Does it only happen in new projects? Or also with existing projects?