Welcome to the fourth round of This Week's Picks - ArcGIS Enterprise! This week we're going to be focusing on publishing errors. This topic may be thought of as taboo by some but, if you've been using ArcGIS Enterprise long enough, you've probably encountered some publishing errors along the way. And that's okay because they're often easily fixed, meaning you can be on your merry publishing way.
With that in mind, we're going to talk about some of the most "popular" errors - and their fixes.
- "Packaging succeeded, but publishing failed"
- "Failed to create the service"
- "Failed to extract manifest from uploaded service definition" + "Failed to get basic item metadata for service definition upload"
1. "Packaging succeeded, but publishing failed"
This blog references this infamous error encountered in ArcMap and presents a comprehensive list of ways to troubleshoot the issue: check the logs, GIS Server connection, Publishing Tools, machine resources, and permissions. Even if you're encountering publishing errors in another client, such as ArcGIS Pro, keep this list in your back pocket because it will still be helpful. Check out the details of this comprehensive troubleshooting list here.
2. "Failed to create the service"
This technical article on "ERROR 001369: Failed to Create the Service" builds upon the previous blog. Not only does it go into checking the logs, Publishing Tools, machine resources, and permissions - it also covers tuning and configuring services and Opportunistic Locking (OpLocks). Even if you aren't encountering a publishing error, there are some tips in this technical article that will keep your environment running smoothly. Check it out for yourself here.
3. "Failed to extract manifest from uploaded service definition" + "Failed to get basic item metadata for service definition upload"
This technical article focuses on errors that occur when publishing a hosted feature layer to ArcGIS Enterprise. Both these errors can be caused by one of two things. One possible cause is that the ArcGIS Enterprise components are not able to communicate through the established SSL protocols. The second possible cause is that the account running ArcGIS Server's Temp folder is inaccessible. Look at this article here to read up on how to fix these errors.
Hopefully that helps provide some insight into troubleshooting the popular ArcGIS Enterprise publishing errors. Please feel free to reach out in the comments below if there are any outstanding questions. As always, thanks for reading! Be sure to check out This Week's Picks - ArcGIS Online and ArcGIS Pro - and stay tuned for more This Week's Picks - ArcGIS Enterprise.