topic Re: Running arcpy script from Powershell after updating to ArcGIS Pro 3.1.0 gives error in Python Questions

Running arcpy script from Powershell after updating to ArcGIS Pro 3.1.0 gives error

KevinCheriyan — Mon, 27 Feb 2023 17:04:37 GMT

I have been running my python script that uses arcpy, from Powershell without any problems. But in the middle of a session, I thought to update ArcGIS Pro from 3.0.1 to 3.1 and my script immediately stopped working. I run my script from Powershell using propy (the propy.bat file location is added to my environmental variables). The following error is produced:

Unhandled exception. System.IO.FileNotFoundException: Could not load file or assembly 'ArcGIS.Core, Version=13.1.0.0, Culture=neutral, PublicKeyToken=8fc3cc631e44ad86'. The system cannot find the file specified. File name: 'ArcGIS.Core, Version=13.1.0.0, Culture=neutral, PublicKeyToken=8fc3cc631e44ad86' at ArcGIS.Core.Internal.PluginWorkspaceFactoryShim.FinalConstruct(PluginWorkspaceFactoryShim* ) at ATL.CComPolyObject<ArcGIS::Core::Internal::PluginWorkspaceFactoryShim>.FinalConstruct(CComPolyObject<ArcGIS::Core::Internal::PluginWorkspaceFactoryShim>* ) at ATL.CComPolyObject<ArcGIS::Core::Internal::PluginWorkspaceFactoryShim>.CreateInstance(IUnknown* pUnkOuter, CComPolyObject<ArcGIS::Core::Internal::PluginWorkspaceFactoryShim>** pp) at ArcGIS.Core.Internal.PluginWorkspaceFactoryShim.CreateInstance(IAddInRecord* pAddinRecord, IUnknown* controllingUnknown, IUnknown** ppPluginWorkspaceFactory) at PluginFactory.CreateObject(PluginFactory* , IAddInRecord* pAddinRecord, IUnknown* pUnkOuter, IUnknown** ppPluginWorkspaceFactory)

This only happens when a method that takes a file name or location as a parameter is run. For instance, the following doesn't produce an error:

arcpy.env.overwriteOutput = True // no error

But this does:

arcpy.env.workspace = "location of gdb" //error

and so does this:

arcpy.Exists("location of gdb that exists") //error

but the following doesn't produce an error; just prints False.

arcpy.Exists("") //no error

I've tried restarting my Windows and rechecking environmental variables in Systems Settings. The same commands run fine from within ArcGIS Pro's python window. As far as I could tell, this started happening after I upgraded to Pro 3.1

Anyone have any idea what could be wrong here? I need to use propy or python to run my script from the shell.

Both python or propy commands from shell give same error

Re: Running arcpy script from Powershell after updating to ArcGIS Pro 3.1.0 gives error

ShaunWalbridge — Mon, 27 Feb 2023 18:15:14 GMT

Hello Kevin,

Could you provide some information on how you start PowerShell and whether you have any integration with e.g. Python.NET being used? When I start a new Windows Terminal session with Powershell, I can use the scripts and it seems to work without issue. I wouldn't expect to see .NET exceptions being raised from a Python perspective, so am not sure where these are entering into the picture.

Cheers,
Shaun

Re: Running arcpy script from Powershell after updating to ArcGIS Pro 3.1.0 gives error

KevinCheriyan — Tue, 28 Feb 2023 00:21:51 GMT

Hi @ShaunWalbridge ,

Thank you for your reply. Testing further, this issue can be replicated for me in Powershell, Command Prompt or any other shell. If I can start python in the shell, then import arcpy and run any command that requires a filepath, the above error is produced.

I do separate work with the Pro SDK for .NET and some other Maps SDK for .NET projects, but I don't use console or shell for them, if that answers your question.

Thanks!

Re: Running arcpy script from Powershell after updating to ArcGIS Pro 3.1.0 gives error

ShaunWalbridge — Tue, 28 Feb 2023 19:20:51 GMT

Got it. It sounds like there may be some cross-talk between ArcPy and the .NET SDK that I'm not aware of. Do you have the Pro 3.1 version of the Pro SDK installed? I might check that is installed, and see if it has an effect. Also, see if (temporarily) uninstalling the Maps SDK changes things.

Re: Running arcpy script from Powershell after updating to ArcGIS Pro 3.1.0 gives error

JuliusDobravolskas — Mon, 06 Mar 2023 12:43:33 GMT

Hi,
I can add up to this issues. Simple example of listing domains from here: https://pro.arcgis.com/en/pro-app/latest/arcpy/data-access/listdomains.htm gives same error.

I have only ArcGIS PRO 3.1 installed.

Re: Running arcpy script from Powershell after updating to ArcGIS Pro 3.1.0 gives error

ShaunWalbridge — Thu, 16 Mar 2023 21:37:19 GMT

Can you log a request through support? I'm not aware of what would cause this issue and don't know of any existing reports of it. Thanks!

Re: Running arcpy script from Powershell after updating to ArcGIS Pro 3.1.0 gives error

Wolf — Tue, 21 Mar 2023 22:48:48 GMT

I am experiencing the same problem .... in 3.0 i was able to run my python scripts without any errors, but after i upgraded to 3.1 and later I am getting only errors. I run my scripts from within a .NET Module add-in (by calling a process to invoke propy.bat) or simply from a command line. Neither works anymore.

I attached my Python script (change the extension back to .py). It needs an input FileGeodatabase with a polygon feature class and a non-existing feature class for the output. The script is doing buffer operation.

So this what i get when i run the script using 3.0 (I only show the command line here):

Next i uninstalled 3.0 and installed 3.1 and the same script can't be run. I get this error from the command line:

"C:\Program Files\ArcGIS\Pro\bin\Python\Scripts\propy.bat" "C:\Users\wolf2125\AppData\Local\ESRI\ArcGISPro\AssemblyCache\{31d7f807-1dfe-44c3-9c8b-6ffc8263159e}\test1.py" "C:\Data\FeatureTest\FeatureTest.gdb\TestPolygons" "C:\Data\FeatureTest\FeatureTest.gdb\TestPolygons_Buffer" Input: C:\Data\FeatureTest\FeatureTest.gdb\TestPolygons Output: C:\Data\FeatureTest\FeatureTest.gdb\TestPolygons_Buffer Unhandled exception. System.IO.FileNotFoundException: Could not load file or assembly 'ArcGIS.Core, Version=13.1.0.0, Culture=neutral, PublicKeyToken=8fc3cc631e44ad86'. The system cannot find the file specified. File name: 'ArcGIS.Core, Version=13.1.0.0, Culture=neutral, PublicKeyToken=8fc3cc631e44ad86' at ArcGIS.Core.Internal.PluginWorkspaceFactoryShim.FinalConstruct(PluginWorkspaceFactoryShim* ) at ATL.CComPolyObject<ArcGIS::Core::Internal::PluginWorkspaceFactoryShim>.FinalConstruct(CComPolyObject<ArcGIS::Core::Internal::PluginWorkspaceFactoryShim>* ) at ATL.CComPolyObject<ArcGIS::Core::Internal::PluginWorkspaceFactoryShim>.CreateInstance(IUnknown* pUnkOuter, CComPolyObject<ArcGIS::Core::Internal::PluginWorkspaceFactoryShim>** pp) at ArcGIS.Core.Internal.PluginWorkspaceFactoryShim.CreateInstance(IAddInRecord* pAddinRecord, IUnknown* controllingUnknown, IUnknown** ppPluginWorkspaceFactory) at PluginFactory.CreateObject(PluginFactory* , IAddInRecord* pAddinRecord, IUnknown* pUnkOuter, IUnknown** ppPluginWorkspaceFactory)

I can't run test1.py from my add-in either - since it's executing the exact same script.

It looks to me like arcpy is unable to find / load its underlying assemblies (ArcGIS.Core, Version=13.1.0.0). I added the ArcGIS Pro bin to the Path environment, but that didn't help.

Re: Running arcpy script from Powershell after updating to ArcGIS Pro 3.1.0 gives error

Gerry_S — Wed, 22 Mar 2023 06:13:03 GMT

This is something I have experienced too after upgrading to Pro 3.1. However, and curiously, a small script I made that would fail elsewhere with this error did run inside the ArcGIS Pro python window.

It does look like ArcGIS.Core is part of the ArcGIS Pro SDK (see Home · Esri/arcgis-pro-sdk Wiki (github.com)) so I tried uninstalling and reinstalling the ArcGIS Pro SDK in Visual Studio to see if it needed to be re-installed after a Pro update. No joy, still the same error.

Looking like I'll need to downgrade to Pro 3.0.x for now until there's a fix.

Re: Running arcpy script from Powershell after updating to ArcGIS Pro 3.1.0 gives error

Anonymous User — Wed, 22 Mar 2023 12:42:32 GMT

This is a mess... I started to notice that Pro 3.0 will sometimes load the Add-ins I created to execute python scripts. I had to update to 3.1 as the 'solution' to test three other bugs I found and reported to esri... 3.1 just doesn't load a dockpane Addin I created at all, and I still have the 3 bugs.

Re: Running arcpy script from Powershell after updating to ArcGIS Pro 3.1.0 gives error

Wolf — Wed, 22 Mar 2023 14:24:00 GMT

@Anonymous User i can probably help you with your add-in / dockpane issues. I am working with the ArcGIS Pro SDK team. I will probably need to see your code though ... you can send me a private message, or report your issues under 'ArcGIS Pro SDK Questions' ArcGIS Pro SDK Questions - Esri Community

Re: Running arcpy script from Powershell after updating to ArcGIS Pro 3.1.0 gives error

Wolf — Wed, 22 Mar 2023 14:36:15 GMT

@Gerry_S In ArcGIS Desktop (ArcMap, ArcCatalog, etc.) you needed to install the SDK in order to be able to use the API, however, in ArcGIS Pro the API is part of the ArcGIS Pro installation. ArcGIS.Core is one of the core assemblies used by ArcGIS Pro. When you install the Pro SDK in Visual Studio you only get the Project / Item templates and some utilities to manage your Pro SDK add-ins & configuration projects. The Pro SDK doesn't install any part of the API since it's part of ArcGIS Pro (actually ArcGIS Pro is using this API as well). When running a python script, arcpy is also trying to use the ArcGIS Pro API (which ArcGIS.Core is part of) but can't find the assembly. This worked in 3.0 so i assume there is part of the environment that tells arcpy where to find the Pro assemblies changed in 3.1.

Re: Running arcpy script from Powershell after updating to ArcGIS Pro 3.1.0 gives error

KevinCheriyan — Wed, 22 Mar 2023 14:43:39 GMT

Does downgrading to Pro 3.0.x solve the issue? I'm hesitant to go through the effort so far until I know this can solve it for sure

Re: Running arcpy script from Powershell after updating to ArcGIS Pro 3.1.0 gives error

ShaunWalbridge — Wed, 22 Mar 2023 14:45:49 GMT

Does your Python script work from the command line without the Pro SDK installed? It'd be good to see if this only happens specifically in an interaction with that component or is more broadly occurring. Thanks!

Re: Running arcpy script from Powershell after updating to ArcGIS Pro 3.1.0 gives error

KevinCheriyan — Wed, 22 Mar 2023 14:48:39 GMT

I will try to find some time in the next couple of days to do this @ShaunWalbridge . Before I uninstall the Pro SDK, I need to tie up a few loose ends in the Pro SDK project I'm working on 😅

Re: Running arcpy script from Powershell after updating to ArcGIS Pro 3.1.0 gives error

ShaunWalbridge — Wed, 22 Mar 2023 14:56:31 GMT

Got it. That would be great, once we have a clear set of interactions causing this we can get a reproducible case together and start debugging it. I don't think we have had anything like this happen before and wouldn't normally expect any interaction between the two "worlds" of .NET and Python.

Re: Running arcpy script from Powershell after updating to ArcGIS Pro 3.1.0 gives error

Wolf — Thu, 23 Mar 2023 15:29:50 GMT

The errors that i encountered when running a python script (either from .Net out of process, or from a Windows command prompt) were caused by Plugin Datasource extensions that i had installed at one time. It appears that arcpy is now initializing Plugin datasource extensions (to support custom data imports) in 3.1 even if those Plugins are not used in the script. i was able to fix my problem by deleting any plugins with a ".esriPlugin" file extension in my Documents\ArcGIS\Addins folder. After i removed those plugin extensions my python scripts worked without any problems and without throwing any 'dll file not found' errors. The dev team is working on a fix for this specific issue.

Re: Running arcpy script from Powershell after updating to ArcGIS Pro 3.1.0 gives error

KevinCheriyan — Sun, 02 Apr 2023 22:00:12 GMT

I uninstalled the Pro SDK and related extensions from Visual Studio, restarted my machine and tried running the same script from Powershell. Much to my surprise, this gives me the same error. I still have Pro installed.

Re: Running arcpy script from Powershell after updating to ArcGIS Pro 3.1.0 gives error

ShaunWalbridge — Mon, 03 Apr 2023 21:30:35 GMT

Have you tried removing the plugins as Wolf described? Based on our internal testing, this is the cause of the issue, we are working toward a solution but don't have something available in software yet.

Re: Running arcpy script from Powershell after updating to ArcGIS Pro 3.1.0 gives error

EvanThoms — Wed, 10 May 2023 16:34:10 GMT

Just confirming that removing XTools Pro (installed by default with all instances of AGP in my agency) resolved the problem for me.

Is there a bug number so we can track this?

Re: Running arcpy script from Powershell after updating to ArcGIS Pro 3.1.0 gives error

JoshuaFlickinger — Tue, 16 May 2023 12:08:59 GMT

Thanks @KevinCheriyan for bringing up this issue, and to @Wolf and @EvanThoms for some insight. I was experiencing the same issue and removing XTools Pro solved it. I'd also be interested in seeing a bug number if available, to forward to the GIS community in my organization.