When this happens, which is it?
What were you doing?
and does it do it again, when you foolishly think it won't happen again?
or with different data?
or after a reboot?
or on someone else's computer?
after you leave work in disgust, come back tomorrow and it doesn't happen?
That... on those rare occasions ... is the plan that I follow, some days, I just start at the bottom and work up
Not me, another user. She gets errors like this all the time. I've seen it happen and I've seen it NOT happen doing the same operations. It seems to be related to an enterprise database and we created a new instance for her to see if that 'fixes' the problem. This particular time she was back on the original enterprise database, so it's a little difficult to tell if we have provided a solution or not..... sigh....
When this error pops up, no ArcGIS dump file is created, that's why I'm wondering if it's not ArcGIS but the OS or network that's choking...
Sorry I can't help then Joe... can someone else replicate her workflow to see if it is just the one user?
I've tried. Sometimes I get a crash. But usually not...
What version is your ArcMap and Windows?
Could you check if the ArcMap crashes if you run it in compatibility mode (Win 7 maybe)?
Also ensure the video driver is updated.
10.5.1, Windows 10. Driver updated to what?
I doubt it is a video driver unless you are doing 3d rendering in pro.
Windows 10 is totally fine.
It is something in your workflow... aka what you do... I have only had 2 crashes in as many years as I can remember... why? I don't do stuff that causes crashes. I work with locally stored data (you don't). I mostly use tools related to geometry (you don't). The 'user' has been ruled out (unless you have caught the bug)
So the culprit is what is being done with what is being used. Logging manually might be a good idea if you have a vague idea when you suspect it might happen.
Check the DBMS client drivers on the problematic machine and normal machines. If the problem seems isolated to an enterprise geodatabase, but others on different machines don't have problems with that same enterprise geodatabase, it could be conflicting, corrupted, or unsupported DBMS client drivers.
This has been an on going problem with this particular user. It does seem to be related to her accessing an enterprise gdb, which is why we've built a new one. I can't provide any more details of the operations she follows, only because she doesn't provide them to me. For example her last crash was caused "when I changed back to sde.default". but I don't know what transpired prior to that. (I've been in an ESRI online class this week, switching between versions all day: haven't had crash yet, and this is all cloud based!)
Yes; I've pleaded for more details, and I've given what I'm given. Like Dan, I avoid performing operations that cause crashes. I was just hoping that since it's not creating a dump file, there may be some where else to look.
Retrieving data ...