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

ArcGIS Pro: Can't Share > Export Map from any Layout

MikeGregotski

Hi,

I am not able to use the Share > Export Map function on any Layout that I have in any project in Pro.

I’ve tried exporting to different formats (BMP, JPG, TIF, PDF), used different projects (with just a map in the layout) and also tried two different computers but Pro always crashes during the export. See the attached screen capture.

I can export from a map without error.

Is there something that I need to do before I export the layout?

I’m using 1.0 Prerelease Update, Build 1566.

Thanks,
Mike

Pro.JPG

Trouver plus de publications taguées avec

Accepted answers

All comments

MarcoBoeringa

8MB is nothing, I have successfully created up to 350 MB A0 sized PDFs from within Pro and ArcMap, both as 100% vector data, and with mixed vector / raster. In the latter case, I also used 300 dpi output setting, and the raster layer was the ESRI "Terrain: Multi-Directional Hillshade" from the Living Atlas. Quality setting Best.

I have never had the issue that you describe, needing to reduce the quality setting to "Better" to be able to export.

And yes, maybe surprisingly, Adobe Reader XI can open these monstrous PDFs, albeit with a mild waiting time before display. It only runs out of memory when I open multiple.

This in on a Core i7 HQ quad core laptop with 16GB RAM with dedicated video card.

Anonymous User

It is around 8MB. The image quality seems good, however I would normally keep the setting on "Best" by default unless I had specific reason to drop the quality down.

mvolz47

How large was the 24x36 pdf file that was generated using "Better" Quality?

Anonymous User

This is an old thread, but I also just had this crashing issue when exporting. In my case I am using the latest Pro version (2.1) and was attempting to export a 24x36 pdf map at 300 dpi. It continued to fail until I adjusted the Image Quality setting from "Best" to "Better". It seemed like tweaking the other settings had no effect on the crashing issue. Maybe this is a bug on this latest version. Until this point I have only exported smaller map layouts in Pro so I am unsure if that has to do with it as well.

MikeGregotski

Hi Jeremy,

Thanks for your response. An uninstall and reinstall fixed the save error.

I'm now tackling the export layout problem again.

I can export layouts from new projects that just have a map in the layout. This works fine and is good.

So I've tried adding some more elements to the layouts and exporting. This will either:

-make the exported file on disk and then crash Pro

-crash Pro without creating the file on disk

Do you have any further suggestions or is there any kind of log file that Pro writes to disk? I've looked for one but haven't been able to find it.

Mike

Jeremy Wright

I've seen this error message when you try to save and can't acquire exclusive lock on the aprx (for instance when more than one person has the APRX open). That is a known issue that content management is working on. Let me ping them about this.

MikeGregotski

Thanks for your response Jeremy.

I tried a new layout with nothing in it. Then did the export and I got the same results, a crash.

So I tried creating a new project with just a default map and a blank layout. I got the same results when exporting the layout, a crash.

I've noticed now that I am unable to save my projects anymore as well. Whenever a new project is created or I try to save it I get this error (also below):

ArcGIS Project

Failed to save the current project.

Error:

Project Service::SaveProjectAsync Failed

I was going to uninstall and reinstall but thought that you might have another suggestion. Do you have a suggestion?

Thanks,

Mike

PS. Thanks for your retweets!

Jeremy Wright

Mike,

As I replied on the beta forums dupe of this post - I am unable to repro this problem locally on the PR2 build OR even on current builds. can you try a blank layout (no map frame) and see if that works?

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

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