Cloned Environment broken after updating to 2.4

2621
15
Jump to solution
07-23-2019 08:14 AM
JamesBurton1
New Contributor III

I updated to 2.4 a couple weeks ago and yesterday I went to use the python window and I kept getting errors. Then I go to the Python Package Manager and find that my cloned environment is 'broken' and now after deleting that bad environment I can't clone my default environment. It fails every time, even if I change the install location. Anyone having this issue? I know it has been a problem with previous updates as well. Personally, I am so sick of troubleshooting python environments and trying to get Spyder to actually run code. I deal with this every time I try and do some automation. It's getting ridiculous.

1 Solution

Accepted Solutions
JoeBorgione
MVP Esteemed Contributor

Jo Belanger‌; You will need to re-clone at every release update.  I don't think you need to for the incremental updates like 2.6 to 2.6.1.  Personally I typically wait for a full version release before I upgrade but that's just me.  There are a few threads about the 2.6 upgrade and cloning problems such as this one of mine.  Not sure what the problem was but it took a few tries to get the clone straightened out.  

That should just about do it....

View solution in original post

15 Replies
DanPatterson_Retired
MVP Esteemed Contributor

Do you have full admin rights?

/blogs/dan_patterson/2018/12/28/clone 

or are you following some other approach?

On a side note, I never update, I uninstall the old and install the new in the same folder.  Spyder finds itself after you reinstall it, which doesn't take much time, and all your preferences will be kept from the prior installation.

JamesBurton1
New Contributor III

Hey Dan, thanks for the reply. I do have admin rights and I can go through your walk-through in more detail soon. Maybe the uninstall/reinstall is the best option for me considering I can't even clone my environment now. 

0 Kudos
DanPatterson_Retired
MVP Esteemed Contributor

James... make sure you uninstall anything related to Arc* as well, sometimes the tentacles run far and wide

DanPatterson_Retired
MVP Esteemed Contributor
JoeBorgione
MVP Esteemed Contributor

James-  when I upgraded to 2.4 I had to re-clone.  Seems like that's just the way of it and it seems pretty lame to me, but what do I know....

That should just about do it....
JamesBurton1
New Contributor III

Oh, thanks Joe. That's what I figured. Ya I wouldn't mind re-cloning but unfortunately it just fails every time...

0 Kudos
JoeBorgione
MVP Esteemed Contributor

Oh shoot... didn't realize that....

That should just about do it....
DanPatterson_Retired
MVP Esteemed Contributor

Guess what...

https://community.esri.com/docs/DOC-13844-arcgis-pro-24-patch-2-is-available 

perhaps the clone will live through the update...

if anyone needs the update functionality and uses clones, perhaps you could report on whether the clone survived

0 Kudos
DaniInterrante
New Contributor III

Did anyone experience this issue when upgrading to 2.5?  My teammate and I lost the cloned environments on our local workstations.  This scares me since we have ETLs setup on Virtual Machines which run off a cloned ArcGIS Pro Python Environment. 

0 Kudos