topic Re: project_service_aprx_object.save() Error from Pro 2.8.x to 2.9 upgrade in Python Questions

project_service_aprx_object.save() Error from Pro 2.8.x to 2.9 upgrade

Min-DongChang — Tue, 23 Nov 2021 22:26:52 GMT

I have a code that a developer created that no long works for me. With a recent upgrade from 2.8.x to 2.9, the script no errors out at a line " project_service_aprx_object.save()". What I believe the code is trying to do update the source of feature layers in a map ("1_Service_Status_On"). However, when it comes to the project_service_aprx_object.save() line, it gives me the following error:

Traceback (most recent call last):
File "<string>", line 686, in <module>
File "A:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\_mp.py", line 285, in save
return convertArcObjectToPythonObject(self._arc_object.save(*gp_fixargs((), True)))
OSError: G:\SDE_User_Connections\Projects\UnitedStates\US_Test01\Web_Services\Test01_Project_Services.aprx

I'm running the code in an empty APRX file so I don't even have the Test01_Project_Services.aprx open. I'm a novice at python so any I can provide more of the code if necessary.

Re: project_service_aprx_object.save() Error from Pro 2.8.x to 2.9 upgrade

IhabHassan — Wed, 24 Nov 2021 04:21:20 GMT

project folder/files access permissions?
I would try to do manually in Pro what they code is trying to do, you might get more descriptive error message.

Re: project_service_aprx_object.save() Error from Pro 2.8.x to 2.9 upgrade

Min-DongChang — Wed, 01 Dec 2021 02:51:08 GMT

Ihab thanks for responding, my user has admin rights to all the project folders. Also I'm not sure why it's still referencing the default python library. In Pro, I cloned the default python library and use it as the default library, which is saved on the C: drive. One other note is that the code was written in python 2.7.16. Not sure if that makes a difference. These are the lines to the line 686 error:

for project_service_map_object in project_service_map_list:
if project_service_map_object.name == r"1_Service_Status_On":
print("Captured -- " + project_service_map_object.name)

print("Creating a List of Layers in " + project_service_map_object.name)
project_service_layers_list = project_service_map_object.listLayers("*")

print("Updating Data Source for All Layers in the 1_Service_Status_On Map")
for layer in project_service_layers_list:
if not (layer.isGroupLayer or layer.isBasemapLayer):
print("Before: " + str(layer.name))
pprint.pprint(layer.connectionProperties)
layer.updateConnectionProperties(
current_connection_info=project_energizer_sde_workspace,
new_connection_info=p_userconnection_workspace_full_path,
auto_update_joins_and_relates=True,
validate=True,
ignore_case=True)
project_service_aprx_object.save()

Re: project_service_aprx_object.save() Error from Pro 2.8.x to 2.9 upgrade

HenriqueJoner — Sun, 26 Dec 2021 22:55:05 GMT

Hello!

I'm into this too. We are running and uploading analysis from the past year every single day. Today decided to upgrade ArcGIS PRO to 2.9 version, and now i'm getting this error in all my scripts, every time when i run "aprx.save()". There is a way to downgrade to 2.8 version, i need this stuff working has it was in the past year.

Thanks

Re: project_service_aprx_object.save() Error from Pro 2.8.x to 2.9 upgrade

MarceloRosensaft — Sun, 06 Feb 2022 17:36:13 GMT

Hello,

I'm having the same problem and it has nothing to do with access permissions or anything else. I run the same python in two computers that deal with the same files in our internal network. The one with the Pro 2.7 works and the one with the Pro 2.9 doesn't.

Besides, you don't need much code to show the problem. Two lines are enough to make the python crash:

# p_Pro_project is the path of an existing project

o_Pro_project = arcpy.mp.ArcGISProject(p_Pro_project)

o_Pro_project.save()

Any ESRI people can confirm the bug or the "by design feature"? It would be nice at least to hear a YES or a NO.

Thanks,

Marcelo

Re: project_service_aprx_object.save() Error from Pro 2.8.x to 2.9 upgrade

ChrisZumwalt — Thu, 10 Feb 2022 18:12:29 GMT

I am experiencing this same issue.

I try to save an aprx after loading some layouts using:

aprx.save()

and then I get the error.

File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\_mp.py", line 285, in save
return convertArcObjectToPythonObject(self._arc_object.save(*gp_fixargs((), True)))

ESRI please advise. Are we doing something wrong?

Re: project_service_aprx_object.save() Error from Pro 2.8.x to 2.9 upgrade

ChrisZumwalt — Thu, 10 Feb 2022 19:01:35 GMT

My Current work around is to use

aprx.saveACopy()

Re: project_service_aprx_object.save() Error from Pro 2.8.x to 2.9 upgrade

NicholasRolstad2 — Thu, 10 Feb 2022 20:54:28 GMT

Yep. aprx.save() throws an OSError for me, every single time. v. 2.9

Re: project_service_aprx_object.save() Error from Pro 2.8.x to 2.9 upgrade

JoeLemeris — Thu, 10 Feb 2022 21:35:48 GMT

I will second this workaround! I had a similar issue where aprx.save() threw an OSerror, which began after we upgraded from ArcPro 2.8.3 to 2.9.1. We also had the same error on thrown on a GP service after upgrade from arcgis enterprise 10.8.1 to 10.9.1. altering the code to aprx.saveACopy() resulted in normal functionality on both pro and enterprise/server. Thanks for the tip!

Re: project_service_aprx_object.save() Error from Pro 2.8.x to 2.9 upgrade

greg_eam — Tue, 05 Apr 2022 23:31:44 GMT

Looks like this is still an issue in Pro 2.9.2

I also get an OSError when calling aprx.save() in my script to replace project data sources

Any word from Esri about this?

Re: project_service_aprx_object.save() Error from Pro 2.8.x to 2.9 upgrade

JoeLemeris — Wed, 06 Apr 2022 13:46:01 GMT

Following up from my previous response to a post in this thread: a bug has been created for this issue, i received a notification a few weeks ago: in addition to adding the del statement they suggest, we found success just using aprx.saveACopy() instead of aprx.save().

BUG-000145915 - An OSError message is returned when using the ArcGIS Pro project's Save function in the Python window.

Current Information:

Status: Known Limit.

Public Explanation: This is a read/only issue. They reference project A, saveACopy to Project B, then try to reference Project B and save. BUT project B is already "open" in memory.

https://support.esri.com/en/bugs/nimbus/QlVHLTAwMDE0NTkxNQ==

By adding the "del aprx_template" statement below, I believe the issue is addressed.

Workaround: Add the 'del aprx_template' statement.

Re: project_service_aprx_object.save() Error from Pro 2.8.x to 2.9 upgrade

Anonymous User — Wed, 13 Apr 2022 13:41:03 GMT

I have the same issue and have been using saveACopy() as a workaround for now.

Re: project_service_aprx_object.save() Error from Pro 2.8.x to 2.9 upgrade

JustinReynolds — Thu, 19 May 2022 17:48:24 GMT

Seeing this as well in a GP tool. After updating some layout elements we save the aprx. Getting an OSError as reported above 2.9.2 and persists in 2.9.3 (also no relevant bug fix listed in the release notes for 2.9.3).

Re: project_service_aprx_object.save() Error from Pro 2.8.x to 2.9 upgrade

codergrl — Tue, 28 Jun 2022 08:59:28 GMT

Ran into the same issue in 2.9. It's happening because you still have a reference to the object. Make sure to call del aprx every time you're done with the object so it gets garbage collected. And this is also why saveACopy works because you get a new reference to a new object. With a lot of calls to saveACopy, you can run into a memory leak issue. See code below for example:

# this works fine for i in range(3): aprx = arcpy.mp.ArcGISProject(PRO_PROJECT_PATH) aprx.save() del aprx # this fails after the first run for i in range(3): aprx = arcpy.mp.ArcGISProject(PRO_PROJECT_PATH) aprx.save()

Please mark as resolved if this solves your problem.

Re: project_service_aprx_object.save() Error from Pro 2.8.x to 2.9 upgrade

MichaelMorisette — Tue, 02 Aug 2022 15:50:03 GMT

I've ran into this bug after upgrading from 2.8.x to 2.9.x. Using the saveACopy(aprxPath) workaround worked for me as well.

Re: project_service_aprx_object.save() Error from Pro 2.8.x to 2.9 upgrade

Anonymous User — Thu, 08 Sep 2022 15:03:03 GMT

This is still present in 3.x. Note if you have any references to objects in the project you will get this error. So you may also need to cleanup any references to maps, layouts, etc. Not only the project object.

Re: project_service_aprx_object.save() Error from Pro 2.8.x to 2.9 upgrade

David_Lindsey — Mon, 17 Oct 2022 20:57:44 GMT

I was encountering the same issue. However, all solutions above did not work for me. Turns out, my issue was that I had somehow corrupted my .aprx project file through previous (and albeit numerous!) script test cycles. Once I deleted the corrupted .aprx and replaced that file with a backup copy of itself, the script proceeded to save the .aprx as expected.

Re: project_service_aprx_object.save() Error from Pro 2.8.x to 2.9 upgrade

PeterMilenkovic — Mon, 07 Nov 2022 22:53:38 GMT

Thanks for the tip, this worked for me

I thought deleting the aprx would be enough... i had to delete the elements and layouts as well.

Re: project_service_aprx_object.save() Error from Pro 2.8.x to 2.9 upgrade

KevindeSouza — Thu, 23 Mar 2023 16:37:25 GMT

How do you handle to copies of the project you are saving? I have a script that is using save() frequently throughout - changing it to saveACopy() results in the a read only project being written over and over again. Any advice?

Re: project_service_aprx_object.save() Error from Pro 2.8.x to 2.9 upgrade

ThomasBaconlol — Mon, 24 Apr 2023 19:56:57 GMT

I noticed that save functions without indentation were throwing the error for me and that save functions inside of a loop were not always throwing an error after reading your comment.

I chained two scripts together however and then it threw the error again so now I'm really stumped.

saveACopy does not work for my purposes either just as a note for anyone reading.