401 Unauthorized - Conda install of arcgis

968
3
Jump to solution
09-05-2017 04:51 PM
PhilLarkin1
Regular Contributor

I had previously upgraded the arcgis package to 1.0.1. When I attempted to upgrade to 1.2.3 I received the error below. Has anyone else experienced this? 

Fetching package metadata .........Warning: you may need to login to anaconda.org again with 'anaconda login' to access private packages(https://conda.anaconda.org/t/<TOKEN>/esri/win-64/, 401 Client Error: UNAUTHORIZED forurl: https://conda.anaconda.org/t/None/esri/win-64/repodata.json)Warning: you may need to login to anaconda.org again with 'anaconda login' to access private packages(https://conda.anaconda.org/t/<TOKEN>/esri/noarch/, 401 Client Error: UNAUTHORIZED for url: https://conda.anaconda.org/t/None/esri/noarch/repodata.json)....

-On Proceed Step-

Fetching packages ...
Error: HTTPError: 401 Client Error: UNAUTHORIZED for url: https://conda.anaconda.org/t/None/esri/win-64/arcgis-1.2.3-py35_1.tar.bz2: https://conda.anaconda.org/t/None/esri/win-64/arcgis-1.2.3-py35_1.tar.bz2

0 Kudos
1 Solution

Accepted Solutions
PhilLarkin1
Regular Contributor

Thanks for your reply Dan Patterson


The problem probably originated from the fact that I was trying to upgrade a package in an environment, and I think the environment was a manual copy of Pro's conda environment ('arcgispro-py3'). There might be a license validation step that appends a token to the upgrade request in conda.

To fix this I upgraded ArcGIS from Pro, and then manually copied the environment folder from C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3 to my env location and renamed. This is awfully hacky, but it doesn't appear that cloning pro's environment is supported. (see post:https://community.esri.com/thread/196691-create-cloned-conda-environment-as-user#comment-694016)

View solution in original post

3 Replies
DanPatterson_Retired
MVP Esteemed Contributor

Just did it... worked for me... did you use proenv.bat from within your conda path?

mine is 

C:\ArcPro\bin\Python\Scripts\proenv.bat

yours will probably differ up to the bin folder

YourDrive:\YourPathToArcGISPro\ bin\Python\Scripts\proenv.bat

0 Kudos
PhilLarkin1
Regular Contributor

Thanks for your reply Dan Patterson


The problem probably originated from the fact that I was trying to upgrade a package in an environment, and I think the environment was a manual copy of Pro's conda environment ('arcgispro-py3'). There might be a license validation step that appends a token to the upgrade request in conda.

To fix this I upgraded ArcGIS from Pro, and then manually copied the environment folder from C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3 to my env location and renamed. This is awfully hacky, but it doesn't appear that cloning pro's environment is supported. (see post:https://community.esri.com/thread/196691-create-cloned-conda-environment-as-user#comment-694016)

DanPatterson_Retired
MVP Esteemed Contributor

As Clinton points out in that thread, perhaps in the future it will be easier

0 Kudos