Latest Contributions by MattWilkie3

This sounds relevant: bug NIM003653, dating back to v9.2 (2006), citing upstream limitation of Microsoft GDI sub-system. The recommended response is to a) increase default printer page size or b) print from ArcGIS Pro instead which doesn't rely on the same export mechanism. Be aware that font substitution fall back does not happen (boxes may show for unsupported characters). More details in knowledge base article Bug: Picture symbol legend patches, inserted images, and objects fail to draw when exported to PDF, EPS, AI, and SVG  When images or objects (such as JPEGs, BMP files, or Excel spreadsheets) are inserted in an ArcMap layout with a page size that is larger than the default printer's default page size, they fail to draw or draw incorrectly when exported. Picture marker symbols, or areas with a picture fill, may also fail to render properly on export. Legend patches of web map service layers may become pixelated or fail to draw on export, as well. Note: At ArcGIS version 9.2 and later, picture marker symbols that are converted to vector with the 'Vectorize layers with bitmap markers/fills' option may also fail to render properly outside of the default printer's default page size. Additionally, certain cartographic representations that draw as an inserted EMF can also be affected by this issue. Cause If the inserted object, image, or legend patch falls outside the default page size of the Windows default printer, Windows GDI drawing calls used by ArcMap may not properly draw the object or image on output. ... View more

What we've done in this situation is compose and export the map at 50% of final print size, output at 600dpi, and then double the scale in Adobe reader/acrobat when printing. It took some careful calculating to get the font, graphic sizes, etc. correct but worked. ... View more

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

For us: yes it stops work often. A full close and restart of ArcMap is needed. Moving to Pro is not a solution. We use Pro, but ArcMap is still the primary and will be for at least a few more years. ... View more

Related thread: https://community.esri.com/thread/213095-one-or-maore-layers-failed-to-draw-general-function-failure  ... View more

Related threads: Fail to Draw Error  Anyone getting random General Function Failure error's with Windows 10 and ArcMap 10.4.1?  ... 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. ... View more

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/ ) ... View more

Updated to save as 10.4 instead, which was my actual goal to begin with. The earlier version of this saved as 10.3, which wasn't necessary because 10.3 is available from ArcPy. (Doh!) It's only versions 10.4 and 10.5 which are unavailable. ... View more

Here's an AutoHotKey script to make saving old versions with ArcMap slightly less painful: Key sequence for ArcMap 10.6 to save copy of current map as 10.3 · GitHub  ... View more

Bug still there in 10.6. A comment on GIS Stack Overflow says it's BUG-000103896: Saving copy of 10.5 MXD to 10.4 using ArcPy at 10.5? - Geographic Information Systems Stack Exchange  I've given our Esri tech support rep a nudge to see what's going on with it. Later: BUG-000103896 is Assigned and in the product plan. [...] You can use my.esri.com to follow the status of the bug. ... View more

Jupyter speaks arcpy? Cool. I didn't know that, Jupyter is one of those things on the perennial "I must learn about that!" inbox that somehow never gets any love ... View more

One experience to contribute: As concluded in the blog post, for quite awhile PyScripter was also my best tool --lightweight, feature rich, performant, free and open source. However it stagnated with only one release between 2012 and 2017 and I started experiencing more and more problems with it. After trying and discarding many the IDE's including the awesome PyCharm (excellent tool, just too heavyweight for me) I finally settled on the almost unknown Pyzo which allowed me to switch between python 2.7 and 3.x seamlessly in the same session and was conda aware. Today I'm happy to see PyScripter is back under active development and advertises switching environments also without exiting. I haven't tried it again at this point though as I'm still happy with Pyzo. ... View more

In our experience (early 2018) commodity hardware in terms of motherboard, cpu, ram, etc. is fine for Pro, but commodity graphics cards -- as found in enterprise bulk buys -- are likely not to be, even when only using 2D. Installation and initial trial runs were fine, but as soon as we started anything moderately complex, like importing an ArcMap mxd with ~30 layers and page size of Arch D we'd get plagued with errors like "GPU resources exceeded. Consider closing some views or modifying layer settings to reduce the amount of data being displayed.". The ArcMap compositions were created and used on that same hardware without issue. [update]: Our graphics cards met the minimum of 2GB un-shared memory as posted in the min requirements. I don't remember the other specs, but the "Can I run it?" tool said the card was ok, not great, but ok. Given that, it could have been driver issues, but upgrading to current didn't help. ... View more