Run standalone python script outside Arc Pro 2.9

Question

I just want to run a py script standalone e.g. as a batchfile outside of pro.

Exported a model to py script. Doesn´t run outside of Pro. Adjusted File paths but it didn´t run anyway.

No python Pro. (Use IDLE to run script - no error message but no feature class was created)

ASw93 · Answer

Did you figure this out? Mine won't run without actually opening the aprx files themselves. It doesn't like my "input_map" parameters.

MarkReddick · Answer

Just back from the weekend and catching up on some reading i see that the activeView and activeMap will always be None when run from outside of the Pro application. So that is unlikely to be the cause of the issue for the case of SINGLE_LAYER never finding any labels to convert.

MarkReddick · Answer

@DennisWarnat90 I'm wondering if you ever got this working with SINGLE_LAYER?

I am doing something very similar, having published a python toolbox as a Geoprocessing service. The service is running perfectly fine and all the other functions of it work as expected (exporting data from the map etc). One component that is not working is the same example you posted which is the call to ConvertLabelsToAnnotation.

From what I can tell this does not appear to work when run within the context of a geoprocessing service (or standalone in your case).

From within Pro and using the same aprx file I can execute python commands to generate successfully with the SINGLE_LAYER option, however when run from within a SOC process as a geoprocessing service the tool generates this message (which i suspect is what you might also have seen if you added some debug output via arcpy.AddMessage(arcpy.GetMessages())):

Start Time: Thursday, July 27, 2023 9:46:14 AM WARNING 002847: No labels to convert. There are no feature layers that are labeled at the conversion scale. Succeeded at Thursday, July 27, 2023 9:46:16 AM (Elapsed Time: 2.25 seconds)

The layer in question is visible, has labelling turned on and has no scale restriction value that impedes the generation of a label at the map scale I am asking (and which works perfectly with the exact same values when run from within Pro).

When ALL_LAYERS is used for 'which_layers' it does generate but this is not what I need.

I have spun my wheels a lot on this, trying various things and testing in Pro and Enterprise. I feel like it is somehow tied to the fact that when opening the aprx from the Enterprise service context there is no active map (even though the aprx is saved with one). Asking for the activeMap from the ProProject gives None unlike when using from CURRENT within a Pro context. Instead I have to use listMaps()[0].

I'm probably at the point of raising a support issue but just wanted to ask here before I do.

Many thanks,

mark