nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Pro crashes when trying to open a specific project

IngridMans

I have a primary Arc Pro project which contains all of my main content that I use on a daily basis. Ever since upgrading to 2.2, Pro crashes whenever I open that project on startup of Pro, with the error message that ArcGIS Pro encountered a serious issue and could not continue and the option to send an error report.

If I open a different project, however, and from there open the problem project, it is fine. I have been unable to identify what the issue is with that project file or contents.

Find more posts tagged with

Accepted answers

All comments

GabrielFM

"They do acknowledge that your error report has been submitted when you submit it. "Dan Patterson

I've never gotten an acknowledgement. Maybe something is broken for me, or you are just special?

DanPatterson_Retired

Gabriel, they don't actually respond/reply/email you unless they need more information.

In fact, when they do need more information, they do contact you. I have had that situation and they can tell me the complete record of the reports I have submitted on a particular incident. Once they get a 'fix' for an issue, it gets rolled out to a patch.

They do acknowledge that your error report has been submitted when you submit it. I don't think getting another email or a personalized response is the best use of time.

Just keep submitting... they aren't ignored for sure.

Now if anyone from esri wants to dispute my assertion… step in

GabrielFM

Really? 0 of mine get attention. I generated 8 of them today. Do I need to use spicier language in my error description?

ThomasColson

I used to believe the submitting the crash report to the automatic ESRI thing was like pushing the close door button on an elevator: a twisted social experiment to see how many suckers actually believed it functioned. I have since learned, with Pro at least, those error reports, each one of them, get attention. So keep pushing Submit!

mvolz47

Is is a feature class in an SDE geodatabase or a file geodatabase?

If it's in an SDE geodatabase, is it SQL Server, Oracle or other?

Did these crashes occur in previous versions of Pro?

kathyhardinwalker

Yes Pro 2.2

Data type: feature class

I don't know (always occur with the same data source type). It seems to always happen when editing.

It is on a network.

Yes, I will try copying to see if that stops the problem.

Thank you,

Kathy

mvolz47

Are you also working with Pro 2.2?

What kind of data are you editing when the document crashes (e.g. SDE database, file gdb, shapefile, other)? Do the crashes always occur with the same data source type?

If the data you are having problems editing is on a network, can you try copying the data local to see if that prevents Pro from crashing? If that is the case, then you would have a use case to show ESRI so they can work on the fundamental issue of using Pro to edit data on a network.

kathyhardinwalker

I have a similar issue, when editing, my document crashes over and over. Does anyone experience this as well?

Kathy

XanderBakker

It is best to contact Esri Support directly and create a case and not just submit the error report.

IngridMans

I've submitted the error report numerous times now when the the crash happens, but I cannot tell if it is getting pushed through.

DanPatterson_Retired

And try saving the project with a new name and location in case it becomes completely unuseable. Exporting the data to new copies would also be prudent

XanderBakker

I guess the best thing to do is report the issue with Esri support.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.