I'm trying to create new environment using ArcPro 2.4 and also trying using command prompt but it shows error and that is.
There was an announcement that there was some maintenance going on which would affect My Esri
Maybe it it affects access to a variety of places. Were you within that time window?
I tried it just now Kuwait (UTC+3) 13:07 HRS. But Am trying from last few days same issue
details of how you are creating it shafi trumboo might help.
Are you using conda? or creating a new environment within Pro itself?
Also paths and environment name as well.
I had the same problem today. Trying to clone the default conda environment from within ArcGIS Pro 2.4.1.
When I copy the URL that is giving the issue (https://conda.anaconda.org/esri/win-64/arcgispro-2.4-0.tar.bz2 ) and paste it into chrome the file downloads fine.
Did you try conda?
/blogs/dan_patterson/2018/12/28/clone
just follow the clone part, if you are familiar with conda... otherwise just wait until Kory gets back to the thread in case it is system wide rather than user specific.
I found that article a little hard to follow. My default user is not an administrator on the machine, but I can run processes as an admin if required. I tried to clone the env on the command line like this:
But the errors are clearly the same.
It creates the following folder structure:
C:\Users\mgg\AppData\Local\ESRI\conda\envs\marc
etc
jupyter
nbconfig
Lib
site-packages
Menu
Scripts
etc etc
and a few files are populated.
If conda and the package manager are having issues... wait for Kory to respond to see if it was update related.
Also ArcGIS Pro 2.5 is about to roll out. Beta 2.5 ended on Friday, soooo, it may be that background work is affecting access to the 2.4 package set for now.
Besides... you should really wait for 2.5 (it is sweet! )
Dan Patterson wrote:
Besides... you should really wait for 2.5 (it is sweet! )
This is the story of all Esri users' lives... always waiting for the next update 😉
Jokes aside, even if you are updating the backend to support a new version, your team should be providing service continuity for everybody still on the current version.
Not my team... I am a retired user, who just finished shoveling snow