Select to view content in your preferred language

Unable to create Project Template in ArcGIS Pro 3.0 - Error HRESULT E_FAIL

679
1
01-06-2023 05:53 AM
hngorin
New Contributor

I am trying to export a project template in ArcGIS Pro 3.0.3. No error warnings were found when I analyzed the project. When I go to create the project template, the process fails with the following warning: "Error HRESULT E_FAIL has been returned from a call to a COM component. 

hngorin_0-1673012085590.png

Before the 3.0 upgrade, I was able to create and use this template without an issue. Does anyone have insight on what this error means and why it is preventing me from creating a project template?

For context, I am saving the template to a file over a shared network. My share and download settings are set to file paths to the shared network as well. The project contains a lot of data, and the total size of the project and its components is 31.0 GB. I successfully created a project template with a different ArcGIS Pro project with version 3.0.3. Is there a size limit for project templates? 

0 Kudos
1 Reply
LanceCole
MVP Regular Contributor

I have seen this occur when accessing data and using projects saved on network shares. You do not indicate how the data is stored - such as fGDB, Enterprise GDB, shapefiles etc.

  1. Most commonly seen when PGDB, shapefiles or needed file being either write protected or located in a directory where the user does not have the permission to edit.
  2. Are you using mapped drives or FQDN paths to the data?  I typically only use FQDN for anything I will be sharing with others.  I have too often ran into issues with drives being mapped differently between users and causing issues 
  3. Try moving the template (not the data) to your local system and see if the issue persists.  You may need to remap the data paths in the template and I recommend FQDN.

Regarding a size limit for project templates.  A template does not actually contain the data but references to the data.  There should not be any issues with the template size.  However, there may be an issue with where the template is pointing to access the data or permissions.

 

0 Kudos