Recently developed a problem where ArcGIS Pro 1.4.1 will not load the tools/tool boxes. Have completed several iterations of uninstall/install but problem persists. Anyone have any ideas how to solve this?
did it always do this? for all projects? do you remember installing anything between when it worked and when it didn't? how about for a new project?
This one is a new one
Thanks for the reply Dan.
No, it has not always done this. It worked fine last week. Pro started
acting up on me yesterday when searching for a tool. I would search for a
tool and it would not find it thus forcing me to manually go through each
toolbox to look for the tool I wanted to use. So I did an
uninstall/reinstall. Now it doesn't give me any tools, just gives the
popup error message stating that it failed to load system tools and to
restart ArcGIS Pro. It does this for both previous and new projects.
-EA
normally I would say... reset your application profile... but I suspect this doesn't apply. There is a default toolbox history folder, but I would not fool with it and suggest you contact tech support given the lack of history on this issue. Post back if you do get resolution and not one else has any insight.
Dear Ed (and Dan)
Ed, I have the same problem after purchasing a new laptop and then upgrading windows 10 from home to pro version, and then experienced some GPU driver issues. This may be the cause but I cant figure out how to work around it. After uninstalling Pro 1.4 a couple of times, I then chose to install Pro 1.3 and this runs perfectly, but as soon as I update to Pro 1.4, I get the same error "Failed to load system tools. Please restart ArcGIS Pro".
Dan, I tried resetting my application profile as suggested but that did not work. But even though I had uninstalled Pro 1.4, my computer knew what colour scheme I last used and my recent projects. So uninstalling and changing profile did not remove all pro 1.4 system information. It is storing my setting somewhere else.
Any assistance will be most welcome. I am loath to run Pro 1.3 until the next release of Pro.
Thanks
Hello all,
You should absolutely not need to uninstall all Esri or Python-related software on your machine - this is not by design and I'm sorry to hear you're experiencing it. One thing that can cause problems with the geoprocessing cache is if you have a PYTHONPATH system environment variable set to a non-Pro Python installation. This was the cause of the crashes described here. ArcGIS Desktop and Server since 10.2 hasn't required the use of the PYTHONPATH system variable, so if you are still using it I suggest to clean it up.
Drew
Thanks Drew but in my situation this was a relatively fresh install of Esri
software on a new laptop using Pro 1.4 and Desktop 10.5 only (together with
ArcGIS Earth and Add Studio). No custom installations or changes made to
python. Server not running on laptop.
Pro was initially installed on a laptop where the graphics card had a
faulty driver. Every time Pro need to work hard and access the GPU, I woudl
get a Windows error message saying that Pro was being blocked from
accessing my GPU. Googling this error resulted in a fresh install of the
NVIDIA driver (after even cleaning it from registry) and then error message
disappeared, but then I experiences the new failure to load system tools
error that is now under discussion.
I was therefore under the impression that Pro and ArcMap are somehow tied
to the GPU installation and any substantial changes to the GPU or
configurations could compromise the installation of the Esri software.
I haven't seen issues with the GPU cause geoprocessing to fail to load before, that is an interesting theory. If anyone is still having the problem, can they try to delete any files from the folder C:\Users\{yourusername}\AppData\Local\ESRI\Local Caches then restart Pro to see if it is able to load the system tools? Restarting Pro should generate two files that start with g* in the above directory, one ~50kb and one ~400kb. If it is still failing to load the system tools, please try to execute a simple arcpy command from the Python window in Pro, and see if the method fails - something simple like arcpy.GetInstallInfo(). If this fails, there is a serious problem with the Python environment, and this knowledge will help with further troubleshooting.
So this just happened to me, I'm thinking that it is because of adding Python packages. Maybe arcgis api? Could've been Jupyter. Anyway, to fix it you have to rename or delete the Python folder (C:\Program Files\ArcGIS\Pro\bin\Python) in the ArcGIS Pro install, then repair Pro. This will give you a fresh python install without whatever the bad package is. I'm hoping it isn't arcgis api, because I need to use it to automate some tasks, but all indications are that it might be the culprit.
Update:
After initially thinking this solution was working, it seems that it is not. Pro keeps crashing. I had to uninstall everything again and completely delete every directory involved in an Esri installation, delete every python installation and every environmental variable that has anything to do with python, then run a registry cleaner, then reinstall. It seems ok for the moment.
Drew. I followed your suggested actions. Only one file is regenerated in the ....\Local Caches folder ~50kb. Running a python command crashes the application to the Serious Application Error Window. I upgraded Pro version 1.2 to version 1.4.1 about two days ago using the Project>About>Update route.
I had the same issue. Probably this cause adding a python package arcgis. I uninstall ArcGIS Pro and manually delete rest of the folder "ArcGIS Pro" in Program Files. Then it's working normally.
I am also having this same issue. The problem is coming from python for sure. I created separate conda environment because I needed some specific package versions, and that is when this problem began. Overall updating/removing/installing packages in Pro seems to cause issues even when it is done in a separate conda environment from the Pro default environment. This occurs in 1.4 and 2.0 (beta). Any resolution to this would be great, thanks!
Ethan
The ArcGIS PRO conda package is 'special'. I only use it when it need to use pro. I created a totally different distribution to work with more recent versions of python etc. The PRO distribution is quite finicky about what is where and what versions of other packages are supported. Tread carefully or you will end up with a mess
Very true I noticed it is finicky immediately. But, correct me if I am wrong, creating a new anaconda environment shouldn't mess with the default Pro environment and therefore shouldn't cause any issues. I will check things again, but it seems like it is still affecting it. You have had no trouble doing this?
The Pro distribution's is totally separate from that I installed from Continuum.
This link shows a fairly recent blog post on the new Anaconda Navigator for accessing package installation, updating and some of the more common packages like R, Spyder, Orange etc etc. One nice feature is that you can work with MatPlotLib 2.0 which you won't likely see in the Arc Pro distribution for some time.
The top part of the post is recent... the latter section is left for legacy information
https://community.esri.com/blogs/dan_patterson/2016/07/17/anaconda-spyder-and-arcgis-pro
If anyone continues to have problems with crashes in Pro, please try this workaround. Workaround: installed package crashing Pro 1.4.1
Note that the issue described in this workaround, and the original problem with the system toolboxes not loading, have been resolved in Pro 2.0 which is coming out soon.
Thanks,
How soon is soon? JK. It's always super top secret. LOL
At the moment, arcpy and thus the underlying Python functionality in Pro is not a true site-package, the code in arcpy is laid down with the installation of Pro in the Resources directory. As such there are a few special files within Pro environments to temporarily set the OS PATH to include the location of arcpy when python.exe from within a Pro env is run.
If those aren't present in a newly created environment then arcpy won't run successfully. You are correct that creating an additional environment will not affect the one which has the arcpy functionality - you should be able to switch between these without issue - however if you've installed Anaconda alongside Pro you have to be mindful of which conda.exe, python.exe etc you are calling. Since there are essentially two installations of the same program, you will only be able to access the envs associated with the executable that is being run. This is based off the system's PATH variable.
The conda installation in Pro, including its envs, exists within Pro's folders. Any envs outside of that folder structure will not work with arcpy (we are working on improving this, but as of Pro 1.4 it is the case) Anaconda is aggressive in changing the PATH, so if you've installed it after installing Pro your PATH likely points to the non-Pro installation's executables.
A handy command in the cmd prompt is 'where conda' - this will show a list of all the locations conda shows up on your PATH. The topmost one will be executed by calling that command on its own.
I just ran into this problem with ArcGIS Pro 2.0.
First, it said that the system tools could not be loaded. Then, when I tried to fire up the python CLI, it said "Failed to Initialize Python Interpreter."
ArcGIS Pro's python instance is not my system python, nor do I want it to be. What are my options?
This specific issue should be fixed for 2.0, since we updated the .dll - however there are still some potential quirks.
Let me know and we'll get it figured out!
Hi Clinton,
I put a more thorough question in place here: Upon loading ArcGIS Pro 2.0 I get "Failed to initialize python interpreter"
I had ArcGIS Pro 1.4 installed to C:\ArcGISPro because it gave me an option of where I wanted to install it.
When I installed ArcGIS Pro 2.0, it did not give me an option of where to install it. It just put it under my local profile. So there are some issues with consistency between the installer packages.
If memory serves... there is one tiny question about whether you want Pro available for all people... or just you. If you specify 'all' then Pro gets installed in the Program Files folder. If you are the only user, then you can put it where you want... mine is installed in a 'ArcPro' folder
Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
