topic Re: Can't clone Py environment in 2.3.2 in ArcGIS Pro Questions

Can't clone Py environment in 2.3.2

GabrielMarcus1 — Wed, 03 Apr 2019 01:53:34 GMT

I should say I _still_ can't clone the Py environment, but my home machine gives me a different error message than my work machine.

What work around is there for 2.3.2? Dan Patterson

Is it finally fixed in 2.4?

ERROR conda.core.link:_execute_actions(337): An error occurred while installing package 'defaults::ipykernel-4.9.0-py36_0'.
LinkError: post-link script failed for package defaults::ipykernel-4.9.0-py36_0
running your command again with `-v` will provide additional information
location of failed script: C:\Users\...\AppData\Local\ESRI\conda\envs\arcgispro-py3-clone2\Scripts\.ipykernel-post-link.bat
==> script messages <==
<None>

Attempting to roll back.

LinkError: post-link script failed for package defaults::ipykernel-4.9.0-py36_0
running your command again with `-v` will provide additional information
location of failed script: C:\Users\...\AppData\Local\ESRI\conda\envs\arcgispro-py3-clone2\Scripts\.ipykernel-post-link.bat
==> script messages <==
<None>

Re: Can't clone Py environment in 2.3.2

DanPatterson_Retired — Wed, 03 Apr 2019 02:15:17 GMT

ipython seems a bit dated, but I have Spyder installed and I upgraded python (3.6.8) and a few other packages

so that may be the reason.

ipykernel 5.1.0            py36h39e3cac_0
ipython    7.2.0            py36h39e3cac_0
ipython_genutils          0.2.0            py36h3c5d0ee_0
ipywidgets 7.4.2    py36_0

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

If you want to clone, then quit using C:\Users ... is one recommendation. I do my cloning through conda... although on my machine, I just update and/or the packages in the initial installation, which I install in its own folder outside of the C:\Programs Files folder. I have no issues... can't help you with your work situation

Whatever you do always have a look at

>>> conda update "whatever" --dry-run

dry-run gives you the opportunity to check to see if anything is going to affect anything else.

When you download your Arc*, save the *.exe to disk and run it from there, and keep the *.msi and *.cab files in a safe location should you need to take a coffee break and reinstall everything

Re: Can't clone Py environment in 2.3.2

BrandonBatt1 — Fri, 12 Jul 2019 19:35:24 GMT

I had to run ArcGIS Pro as administrator to resolve this issue.

Re: Can't clone Py environment in 2.3.2

LauraTateosian — Fri, 07 Feb 2020 16:24:56 GMT

I'm having this problem with my 2.4 version of ArcGIS Pro. Reinstallation did not help.

Re: Can't clone Py environment in 2.3.2

GabrielMarcus1 — Fri, 07 Feb 2020 17:57:46 GMT

I'm sorry to hear that Laura. It's frustrating!

I went through uninstalling, reinstalling, uninstalling again and erasing all the registry keys, folders, etc, then reinstalling again, running ArcGIS Pro as an admin, etc.

For my situation at work, network security was interrupting the cloning process. The word clone implies (to me anyway) that the existing libraries are being simply copied, but that isn't all that's going on when working through the interface in Pro. Some of Dan Patterson's suggestions worked for me, but I didn't use Spyder.

I met with success when I began working through conda directly in the command line environment. There are a few how-to posts on this site.

Re: Can't clone Py environment in 2.3.2

LauraTateosian — Fri, 07 Feb 2020 19:51:39 GMT

Thanks, Gabriel. I was able to get the clone to work when I selected "Run as administrator". My only regret is the many hours I wasted troubleshooting this problem! Fingers crossed for the next steps. Thanks for the additional information.

Re: Can't clone Py environment in 2.3.2

LauraTateosian — Wed, 12 Feb 2020 20:55:45 GMT

I was able to clone the environment once. Now I can no longer do so, even when running as administrator. The error is back!

Re: Can't clone Py environment in 2.3.2

GabrielMarcus1 — Wed, 12 Feb 2020 21:16:17 GMT

Are there any error messages (other than straight 9s)?

Re: Can't clone Py environment in 2.3.2

JoeBorgione — Wed, 12 Feb 2020 21:27:47 GMT

I just fought through a 2.5 'upgrade' yesterday; see my chronicles here: ArcGIS Pro 2.5 New Env but...

Ended up doing a total uninstall and install from scratch. Didn't go into the registry but searched and deleted any folders with esri or arcgis in the name. Fairly painful but it's in the rear view mirror now....

Re: Can't clone Py environment in 2.3.2

LauraTateosian — Wed, 12 Feb 2020 21:30:02 GMT

Hi Gabriel,

I think the error I receive is the same as what you posed at the beginning of this conversation. Here are the details I get when I hover over the "exclamatory stop sign":

ERROR conda.core.link:_execute_actions(337): An error occurred while installing package 'defaults::ipykernel-5.1.0-py36h39e3cac_0'.
LinkError: post-link script failed for package defaults::ipykernel-5.1.0-py36h39e3cac_0
running your command again with `-v` will provide additional information
location of failed script: C:\Users\lgtateos\AppData\Local\ESRI\conda\envs\arcgispro-py3-clone7\Scripts\.ipykernel-post-link.bat
==> script messages <==
<None>

Attempting to roll back.

LinkError: post-link script failed for package defaults::ipykernel-5.1.0-py36h39e3cac_0
running your command again with `-v` will provide additional information
location of failed script: C:\Users\lgtateos\AppData\Local\ESRI\conda\envs\arcgispro-py3-clone7\Scripts\.ipykernel-post-link.bat
==> script messages <==
<None>

Re: Can't clone Py environment in 2.3.2

Anonymous User — Sat, 15 Feb 2020 16:56:14 GMT

Add another one to the list-

If these updates invalidate old clones each time Pro is upgraded, it is going to be a pain to keep rebuilding them each time. Especially if you have specific environments for processes and can't remember what packages you have installed in them... being able to rename the clones at the time of cloning would be a lot better than the default clone1, clone2 etc... add the option to export the env to a yml or something that the users can use to rebuild the env's when needed, without having to go through conda to do so.

Running as administer didn't work- my pkg folder is empty with exception of cache. Still get the failed to clone env error:

ERROR conda.core.link:_execute_actions(337): An error occurred while installing package 'defaults::ipykernel-5.1.2-py36h39e3cac_0'.
LinkError: post-link script failed for package defaults::ipykernel-5.1.2-py36h39e3cac_0
running your command again with `-v` will provide additional information
location of failed script: C:\Users\Mine\AppData\Local\ESRI\conda\envs\arcgispro-py3-clone1\Scripts\.ipykernel-post-link.bat
==> script messages <==
<None>

Attempting to roll back.

LinkError: post-link script failed for package defaults::ipykernel-5.1.2-py36h39e3cac_0
running your command again with `-v` will provide additional information
location of failed script: C:\Users\Mine\AppData\Local\ESRI\conda\envs\arcgispro-py3-clone1\Scripts\.ipykernel-post-link.bat
==> script messages <==
<None>

Re: Can't clone Py environment in 2.3.2

JoeBorgione — Sun, 16 Feb 2020 02:13:16 GMT

...it is going to be a pain to keep rebuilding them each time. Especially if you have specific environments for processes and can't remember what packages you have intalled...

Yep. It's a pain alright. I keep all my clones in a directory in my C: drive named EnvClones. Each clone itself is then named after the version like 24, 242, and now I have 25. You can use the conda list command and redirect the returns to a readme file in the clone## directory so your next iteration isn't such a guessing game.

Re: Can't clone Py environment in 2.3.2

GabrielMarcus1 — Mon, 17 Feb 2020 17:24:08 GMT

There was a good post by someone like Dan or Kory that listed the steps to create a new environment with your existing library. I can't find it now though.