Layout 2018 can't export PDF error "There was a problem exporting to this file"

the OpenGL settings of SketchUp are valid for LayOut too.

Thanks for clarifying @SketchUp3D_de, I hadn’t realised that Open GL settings in SU apply to LO as well.

As a test I have tried several different open GL configurations, including turning it off completely, but when I tried to export from Layout I still get the same error message. If @daveyspeed is managing to get a PDF file out of layout, despite having the error message, then we might be able to get somewhere - perhaps there is an error log that Trimble can check through. As no PDF is exported there doesn’t appear to be an error log on my system.

As said, I get the error message and no PDF even when I open a blank document and try to export it - not sure how this would relate to viewports as there aren’t any in the blank doc?

@daveyspeed, can you confirm a few things please.

  1. are you exporting from Layout using File>Export>PDF
  2. are you getting an error message that reads “there was an error exporting to this file”
  3. can you confirm that having received that error message, a PDF file is being exported
  4. do you get the error on several Layout files and if so, does deleting the viewport resolve it?

Thanks

Sam

Hi Sam.

  1. Yes exporting from Layout using File>Export/pdf
    2 and 3. If I sit tight, I do get the error message and nothing is generated. However, if I click cancel just before getting the error message (it has to be before the error is displayed), I get a partially complete pdf.
  2. Yes deleting the viewport solved it for me. I then created a new view port and managed to output what I needed.

Can I track this thread by notifications somehow?

below the last post you can switch off/on tracking the thread, it’s automatically enabled if you have written a reply already.

Sorry I meant to say track by email notifications.

Hi @daveyspeed - thanks for coming back. In order to be notified you need to click on the ‘Normal’ button at the bottom of the thread and select ‘watching’ then you will get email notifications.

I’ve tried hitting cancel but the PDF export (attempt) is too fast. I can’t hit the cancel button and stop the process - as soon as I hit save it comes up with the error message.

Can anyone from Trimble advise whether we can shed any light on this issue - as @daveyspeed gets a PDF file at the end of the process, is there any way to capture what’s happened. Can you (@Trimble) analyse this or replicate the issue?

Just realised that, due to the frame rate, the video doesn’t show the box with the cancel button in but regardless, its only there for half a second so impossible to click cancel.

Hi Sam, I have tried same but too fast, so that’s a no here too :frowning_face:

does switching (“Window > SketchUp Model”) the output processing mode (Vector/Raster/Hybrid) change anything for this issue?

No, Im afraid not. It’s something to do with the PDF export process (out of date dll or api file maybe?) – it fails to ‘export PDF’ on a blank template doc with no viewport in; if there’s no viewport, then there’s no option to change the raster / vector / hybrid option…

I read through the whole section. Glad I’m not alone in this goofy glitch.
I have been experiencing this same issue when trying to export.
Some of the facts regarding my trials and errors:
-most of my files can export just fine
-only a few of the newest files isn’t working
-i have found it is based on certain geometry in the file, if i remove the “custom” geometry, works just fine, wont export the custom geometry from my computer, but it will export from my co-worker’s computer after they remove the “custom” geometry from my file, and re-do the “custom work” on their computer.

  • i am using print to PDF in the rare case this occurs as the work-around(thanks to daniel.fisher for the lightbulb idea)
    -i have a feeling it could have something to do with hidden components
    -i have a feeling it could have something to do with windows updates
    -i have a feeling it could have something to do with NVidia updates
    -had a feeling that this came about when i installed trial version of SU 2019, which i am not using as i am not fond of having to pay for a subscription. (i got the 2019 version right around the same time as the windows update and nvidia update, so i cant target the culprit.)
    -i have a conspiracy theory newer versions of SU installed on your machine make older ones slower and more buggy, but that’s just me.
    -because the glitch seems to be based on which geometry is included in the export and which is not, makes me wonder if its RAM thing? Error’s out due to being unable to render geometry that is hidden? even though it shouldn’t be trying to render that anyways?

Let me know if you think I’m off my rocker on this.

i7-4790k
Geforce 970X
Sketchup 2017
16gb Ram

I’d be curious if any of these suggestions would fix the issue:

Also, can we get a roll call of the computer brand and type where this issue is experienced? Like “Dell Laptop”, or “Acer Desktop”?

I haven’t noticed this issue in SketchUp but in older times it was fairly easy to make a page in AutoCad or Archicad that either wouldn’t print to PDF or created a PDF file that wouldn’t print on a printer. This usually happened when I had vector geometry on top of high resolution raster images or otherwise several layers of things on top of each other (for instance, a scanned image, AutoCad “wipeouts” on top of that and lines drawn in front of it all). The probable reason was that the output became too complex for PDF to handle.

it is not the geometry you can try a simple square and it will fail, its deeper than that as Samyell and I have covered earlier. Its happened since the 2018 upgrades and win 10 updates that coincided and maybe Nvidia updates. The only way round is to reinstall Win 10 and all programs again. I would add it is specific to machines for some reason, dell laptop with all updates is fine but the dell desktop has failed now twice on 2 separate HDD and 2 clean Win 10 installs, it is a mystery…

It’s something to do with the PDF export function BUT the error is totally independent of any geometry / complexity / font / colour in the LO file. The error occurs when exporting to PDF from a totally blank A4 document - if I open LO, start a brand new blank doc from a standard template doc (one that ships with LO and has not been altered in any way) and went to export PDF and it gave the error message. Its nothing to do with a referenced SU file or anything else in the LO file - the error is something to do with the actual PDF export function - perhaps a .dll or .api file that has become corrupted during a windows update?

If you go to Printers and Scanners, do you have Microsoft print to PDF and XChange internal driver?

RLGL I have Microsoft print to PDF only on both the good and bad systems no XChange on either, I think its as Sam says in the export part of the LO program conflicting with other updated programs, why a small % of machines I cannot answer but will only clear on a new clean install worst luck as this entails re-installing all other programs.

As you are going to do a fresh install, keep track of what is installed with Windoze then with each additional app. You might find a surprise or two. Also try exporting the pdf at each stage of the install.