topic Re: Cloned Environment broken after updating to 2.4 in Python Questions

Cloned Environment broken after updating to 2.4

JamesBurton1 — Tue, 23 Jul 2019 15:14:19 GMT

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.

Re: Cloned Environment broken after updating to 2.4

DanPatterson_Retired — Tue, 23 Jul 2019 20:33:06 GMT

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.

Re: Cloned Environment broken after updating to 2.4

JamesBurton1 — Tue, 23 Jul 2019 21:00:03 GMT

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.

Re: Cloned Environment broken after updating to 2.4

DanPatterson_Retired — Tue, 23 Jul 2019 21:02:35 GMT

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

Re: Cloned Environment broken after updating to 2.4

DanPatterson_Retired — Tue, 23 Jul 2019 21:35:12 GMT

James

Forgot my recent missive

/blogs/dan_patterson/2019/06/28/arcgis-pro-24-installation-package-updates-and-installs

Re: Cloned Environment broken after updating to 2.4

JoeBorgione — Tue, 23 Jul 2019 21:41:28 GMT

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....

Re: Cloned Environment broken after updating to 2.4

JamesBurton1 — Tue, 23 Jul 2019 21:54:53 GMT

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

Re: Cloned Environment broken after updating to 2.4

JoeBorgione — Tue, 23 Jul 2019 21:55:45 GMT

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

Re: Cloned Environment broken after updating to 2.4

DanPatterson_Retired — Fri, 04 Oct 2019 09:25:15 GMT

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

Re: Cloned Environment broken after updating to 2.4

DaniInterrante — Fri, 21 Feb 2020 19:49:58 GMT

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.

Re: Cloned Environment broken after updating to 2.4

JoeBorgione — Fri, 21 Feb 2020 20:37:16 GMT

After updating to 2.5, my 2.4.3 clone is still there, but ArcGIS Pro doesn't recognize it....

Re: Cloned Environment broken after updating to 2.4

MichaelVolz — Fri, 21 Feb 2020 21:02:42 GMT

Was Pro updated to 2.5 automatically outside of your control before you could test whether the upgrade breaks your cloned python environment?

Re: Cloned Environment broken after updating to 2.4

EugenioArima — Mon, 02 Mar 2020 21:30:37 GMT

My experience so far with updates is that you can still run all your cloned installations using an editor (e.g. Spyder) but ArcGIS Pro does not recognize your clone anymore (the red octagon with exclamation point). So essentially I am using the "old" version of Arcpro when scripting/programming. It's just a pain in the neck to delete the old clone, create a new clone, and install all the packages you want every time there is an update.

Re: Cloned Environment broken after updating to 2.4

jblng — Tue, 29 Sep 2020 16:28:21 GMT

I am also having this issue in 2.6, and had the same issue as OP. Seems to be that you have to re-create the clone every time you update.

Re: Cloned Environment broken after updating to 2.4

JoeBorgione — Tue, 29 Sep 2020 19:15:33 GMT

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.

Re: Cloned Environment broken after updating to 2.4

PhilLarkin1 — Wed, 02 Dec 2020 16:23:33 GMT

Clones are worthless after a 2.4 -> 2.6 upgrade.

Re: Cloned Environment broken after updating to 2.4

MrGIS — Thu, 13 Oct 2022 21:15:34 GMT

You just need to copy _arcgisscripting.pyd from site packages in the new default environment to your broken cloned environment.

Re: Cloned Environment broken after updating to 2.4

ChelseaWu5 — Wed, 29 May 2024 20:36:06 GMT

this did not work. .. (when I tried this approach to fix the broken cloned envs - pro 2.9 to 3.1 though)

error said dll not found