Skip to main content
Participant
October 20, 2017
Answered

Trouble Exporting PDF to Server

  • October 20, 2017
  • 1 reply
  • 271 views

I frequently export PDFs from INDD CC 2017.1 to a folder located on an NAS (the queue for the digital print department). It has worked fine until about two weeks ago. Now, I get the background task alert "Export" > "Failed to Export the PDF file." Saving from Illustrator, it reads "The file may be read-only, or another user may have it open. Please save the document with a different name or in a different folder." It is true for a variety of types (sizes, color profiles, transparencies. complexities, et cetera) of files. In fact, I can export anywhere else, including my desktop and other directories on the same NAS. I can also access (save to, pull from) this problem directory by other means. My workaround has been to export the PDFs to my desktop then drag them to the problem directory. It works, but I'd like to get this solved. The problem directory is a queue for the digital print department, which means I can't scrap it and create a new folder from scratch.

The odd thing is that I was able to export a PDF without bleed to the problem directory this morning, but then checked the bleed feature on and it gave me this error. I then tried exporting other PDFs without bleed. I found this was only about 75% duplicable–even when a file worked once without bleed, it was a gamble whether it would again. Still the only constant for the ones that did work was that it was exported with no bleed.

Lastly, it may help to know I'm working from an iMac and the NAS is Windows operated.

Any ideas?

    This topic has been closed for replies.
    Correct answer BobLevine

    There is some sort of permissions issue, but I’d be surprised to find out if this is InDesign related at all.

    1 reply

    Participant
    October 24, 2017

    Just learned I can also export directly into a folder within the problem folder on the NAS without issue.

    BobLevine
    Community Expert
    BobLevineCommunity ExpertCorrect answer
    Community Expert
    October 24, 2017

    There is some sort of permissions issue, but I’d be surprised to find out if this is InDesign related at all.

    Participant
    October 24, 2017

    That's what I figured after this morning's update. Thank you for the reply. Hope I can get it sorted with our IT then.