nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Running python using server

ModyBuchbinder

I have a machine that has Pro 3.1.4 & server 11.1

When I run in CMD the python from server ("C:\Program Files\ArcGIS\Server\framework\runtime\ArcGIS\bin\Python\envs\arcgispro-py3\python.exe") and try to import arcpy I get an error (see attachment) When I do it with the Pro python ("C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\python.exe") it works.

Both python version are the same (3.9.16)

I have tested it on a few machines that have both Pro & server installed. Some of them works, others do not.

Opened a case but the support does not have it on his machine.

Anybody have any idea?

When using the server python we should use the server license - this is the reason to use it.

Thanks

py.png

Encuentra más publicaciones etiquetadas con

Accepted answers

All comments

GrahamWood-HWC

THANK YOU!

I'm using ArcGIS Server basic on a machine that had pro on it. For use as our FME Flow Engine Server

once I had authorised Server Basic I still couldn't run python.exe and "import arcpy"

I was getting the error.

RuntimeError: The software is not authorized for use.

Work around was to rename the reg folder
Computer\HKEY_CURRENT_USER\Software\ESRI\ArcGISPro\Licensing to Computer\HKEY_CURRENT_USER\Software\ESRI\ArcGISPro\Licensing2

alex_friant

Background: I was gratefully advised by Pro-West Associates that they have seen this issue before, and it appears to be related to if the user account experiencing the RuntimeError has signed into ArcGIS Pro before. The issue is tied to the Windows Registry, and while I can confirm that's the case with our user experiencing issues, it's not always the case, only that the fix lies in the registry. I had two other User accounts on the same server that had also opened ArcGIS Pro, but import arcpy worked just fine for them when using the ArcGIS Server Python 3 environment. So, replicating the issue is difficult.

These are the steps taken to solve the RuntimeError for that one user we needed to be able to use arcpy in the ArcGIS Server Python 3 environment:

Make sure ArcGIS Pro is uninstalled (I also had ArcGIS Desktop 10.8 uninstalled as well, so if you still have that installed, you may want to take that into consideration at step 5 below)
Sign in as user that was experiencing the issue of RuntimeError during import arcpy
Open the Windows Registry Editor
Danger! Only do these steps in an environment you can recover catastrophic failures with, as Windows Registry is a core component of the Windows OS and can cause instability or corrupt the Windows OS. Proceed at own risk and if you know what you are doing!
Note the settings for [Computer\HKEY_CURRENT_USER\Software\ESRI\ArcGISPro] are:
Make those > ArcGISPro settings look like so:
Close Registry Editor
Sign out the user from Windows, Sign the user back in
Test using Server’s Python 3 command prompt:

Reinstalling ArcGIS Pro after this point still results in a success as above. We will not have that user sign in to ArcGIS Pro out of concern that it might cause issues again (we've burned too much time on this issue at this point and must march forward.)

I hope this solution works for others - it was hard to discover!

alex_friant

@ShaunWalbridge - Great suggestion, because I looked for it and bingo:
https://support.esri.com/en-us/bug/running-python-scripts-from-within-the-arcgis-enterpris-bug-000128742

I haven't tested the work around, but I'm about to try...

UPDATE: Resolved

The work around in that bug report didn't work for our situation. The issue persisted, even after uninstalling ArcGIS Pro all together.

However... I was able to resolve the issue and document it. I'll post that next...

ShaunWalbridge

I would appreciate a bug being logged on this, or sufficient detail for us to reproduce it in house. While the products and their registry keys should not interact, Python environments are a fairly special case. Why? Because once you create custom environments, they can be located anywhere on disk, and potentially map back to either Pro or Server or one of the other four products that also produce custom environments. In that case, mixing between environment types installed with different products can be problematic, because the versions won't align between those cases, and I suspect there is some interaction in that area at play here.

alex_friant

Thanks for the tip - that seems strange if true. The Pro installation should have nothing to do with the ArcGIS Server installation. If it does, then that means Pro is interfering with the normal operations of ArcGIS Server, which is concerning.
I'll give it a shot to see what I can figure out/duplicate the suggested work around.

ModyBuchbinder

As far as i understand the order of installations (Pro and server) define if this will be a problem or not.

If you remove Pro from the server it works for me every time.

Sometime uninstall the Pro and then reinstall (if you must have it) works too

alex_friant

Did you ever figure this out?

I'm running into the same issue with propy.bat in ArcGIS\Server\framework\runtime\ArcGIS\bin\Python\Scripts

One machine, two different accounts. Account#1 Server propy.bat works just fine when I try to import arcpy. Account #2 Server propy.bat opens but import arcpy has RunTimeError: The software is not authorized for use.

Being signed into ArcGIS Pro has zero effect on the outcome, on either account. Server should just be licensed to use arcpy, right?

DarylHochhalter

I have the same issue with the same versions Python 3.9.16 Server 11.1 and Pro 3.1, works on the Pro desktop machine not when I run it via remote desktop on the server machine. The very same script from the same location.

ERROR 000732: Input Table: does not exist or is not supported

The server is Standard the pro is advanced but this script uses arcpy.conversion.ExportTable which is available in either license.

One more thing, it was running on the server at 11.0, just upgraded to 11.1 and now doesn't run.

ModyBuchbinder

Hi Shaun

In most cases the reason to run server python is that we need to run python by scheduler a few times a day so the interactive mod does not help.

I tested the propy.bat at least on one machine and it did not worked. I will test it on other machines too.

Thanks

ShaunWalbridge

Can you try to run the propy.bat included with the Server installation and see if the issue reproduces there? The documentation at https://enterprise.arcgis.com/en/server/latest/develop/windows/scripting-service-publishing-with-arcpy.htm provides some additional information. You can also try running the Python 3 Command Prompt from the start group shortcut and start your Python session from that to confirm it works when activated through conda.

Cheers, Shaun

ModyBuchbinder

Hi Allen

Thanks for your answer.

When I use the Pro python and the Pro have any licenses it works.

Many users does not want to use Pro license for this and would like to use Server license.

In ArcMap python you should do "import arcserver" (https://desktop.arcgis.com/en/arcmap/latest/analyze/arcpy-functions/setproduct.htm) This does not exists in Pro arcpy.

The solution is to use the server python.exe that should use the server license automatically.

It does work on many machines but sometime does not on machines that have both Pro and Server installed.

AllenDailey1

I had a similar problem a while ago. Are you trying to use geoprocessing tools, and do you use Concurrent Use licenses for Pro? Do you have a License Manager? Through working with Esri, with a LOT of calls and back-and-forth, I learned that arcpy geoprocessing tools require that you're connected to the license manager in Pro. It sounded like it's not possible to use arcpy geoprocessing tools via ArcGIS Server python... which just doesn't make any sense to me...

I don't know if any of that is relevant to your situation, but I thought I'd mention it just in case.

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.