I have been trying to run a ModelBuilder model in a project package to be able to create a model output. I hope to send the model to a client, with the model still functional. The model works fine in the project itself, but not in the project package. When I try to run the model, a message saying “Failed to execute (Clip)” comes up. When I validate the model, all of the shapes turn gray, except for ‘Clip’ and all immediately adjacent features. When I validate THEN run the model, I get these errors.
I recently updated to ArcPro Version 2.9, so I think I made these attempts in Version 2.8 (hopefully that doesn't make things too complicated)
I'm having this same problem now in 2025 in ver 3.5.3. The tools run fine when I run them outside of modelbuilder, but they're showing the same errors when I run the modelbuilder. Were you ever able to solve the issue?
The transformation warning has to do with the coordinate systems of the inputs. Some transformations between horizontal datums are simply not supported. You can probably turn this message off by turning off the geotransformations in the backstage (settings).
I have seen this when I have an old incompatible extension installed (ie my uninstall of the old version did not include everything ArcGIS).
Error: Failed to load system tools (esri.com)
You got one without a trackback, but it probably means you have a bad install
I also have gotten these transformation warnings (in both the project and project package). I get the one on the left below upon opening the project, as well as when I open the project package.
Sometimes, I get a message that says "Failed to load system tools", as shown below. This is in the map project.
I have never been a big fan of packages, which work by unzipping a bunch of cruft into a users's documents folder (with the aforementioned long, nasty paths with spaces, which have a bad habit of breaking spatial analyst tools.). I would know more about if I hadn't have had problems like this whenever I have tried it.
I have been more successful just making sure relative paths are set in the model tool properties and zipping the entire project folder. Even then I have had problems with hard-coded paths in my models this term working with students. I need to spend more time on this to figure out the best practices in Pro (vs ArcMap).
Another tip to make model tools more portable is to make liberal use of memory (in_memory in ArcMap) (as long as data not too big) and environment based paths (%workspace%, %scratchGDB%, %scratchFolder%) so my model tools aren't as dependent on paths that may not be there.
not me, waiting for Curtis to chime in
I did these tests in the project package. Does that help anything?
To clarify, I did these tests in the project package.
Tech Support
But, your file paths are long and contain spaces, neither which is good.
If moving your data to a new folder (eg c:\MB_test) and recreating your sub_folders, and renaming featureclasses with spaces in their names, doesn't work, then first line.
@curtvprice anything pop out at you?
I just redid the tests with ArcGIS Pro Version 2.9.0. These are the results, along with a picture of the model.
Did you look at the parameters link? Your model shouldn't rely on specific data unless it has to
I also tried creating a geoprocessing package of the model, though I am not sure if it worked.
I found this about sharing geoprocessing packages.
https://pro.arcgis.com/en/pro-app/latest/help/sharing/overview/geoprocessing-package.htm
I attempted to make it so it would work outside my organization.
Did you package your project to work outside your organization or just inside?
Package Project (Data Management)—ArcGIS Pro | Documentation
and in either case it looks like your data are set as defaults to the model
since you don't allow one to vary the inputs etc
Model parameters—ArcGIS Pro | Documentation
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
