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; } } }

one or more layers failed to draw: general function failure

matthewallen5

Hi. I am using ArcMap 10.4.1. Since our company upgraded to Windows 10 I have been getting this General function failure. It typically happens when you sit idle for a while and then come back to working on it, such as going to lunch and coming back. Closing the map and opening a new one clears it up, but if you haven't saved then you lose everything you were working on. Our data is stored on a network server so maybe that is the issue? Any help or thoughts would be greatly appreciated.

Thanks

Najděte více příspěvků označených jako

Accepted answers

All comments

MattWilkie3

Thanks Micheal. That's the first thing I've read that has the smell of something on track. I will definitely follow up.

mvolz47

Check out below thread to see if it might provide a solution to your problem:

Anyone getting random General Function Failure error's with Windows 10 and ArcMap 10.4.1?

It looks like this issue occurs at newer version of ArcMap (10.5.1) and Pro, so upgrading your GIS software might not solve the problem.

MattWilkie3

Related threads:

Purposely left out: threads about where change in file format, definition query, or symbology are the likely culprit. There are several of those, including the one Esri KB article on the subject I've located so far (Error: One or more layers failed to draw ).

I'll continue to update this post with related threads as they come to light.

MattWilkie3

We've been getting these errors too. They've also increased noticeably since moving to Windows 10 and ArcMap 10.6, sometimes multiple times an hour. The data we've seen this in so far have been file geodatabases on Windows network shares. The data have not changed in any significant manner for many years so I highly doubt it's the data itself.

It hasn't been correlated in time across workstations -- meaning workstations A & B in the same room connected to the same f-gdb aren't getting the errors at the same time. (So it's not a network line being disconnected momentarily.) It's also occurred on at least 2 servers in different towns. (So it's not a hardware failure like a bad drive.)

...

My hunch, based on nothing other than I had heck of a time with it in a completely different software environment and context, is that something has shifted with the change from SMB v2.x to SMB v3.x network protocols (https://www.performancevision.com/blog/5-things-know-before-start-troubleshooting-smb-performance/ )

Připojte se k diskusi

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

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