++ EDITED REPLY, added more information to backup some tips
Hi,
Can you confirm if this issue could be related to Adobe Type1 fonts end of support:
I think that the method that you're employing to export from PDF to an image file is the issue.
In which case, I wouldn't use the export or Save As method. I'd recomment to use instead print file to image.
"Save As", "Print" and "Export to" are three different methods that manipulate and handle the file conversion differently.
For instance, postscripting, distilling and interpreting layers are involved when using the Export method.
I emphasize in assuming that end of support for Type1 fonts could be your case because of the export method that you are currently using.
I've compiled two recent duscussions that may share additional insights:
My other suggestion is to check if the file that you are trying to export have any type of restrictions; more specifically at the font level (i.e. copyrighted fonts that doesn't allow embedding) or postscripting level.
Are you getting any postscript job messages during the export action?
If you are (or even if you're not getting any messages), try to use print PDF to image instead, which will bypass all the font embedding and file interpreting that is involved during the layer conversion processes.
See this quick guidance from Adobe Help Center:
Last, also verify that the default system folder (or directory) in which the exported file is written to allows read/write permissions to that folder (which is handled at the operating system level, not directly from the Adobe Acrobat program).
OR,
Also check that the exported file is not syncing automatically with a cloud space service.
If that would be the issue, you may need to be signed off completely from the cloud service that is responsible for the file snychronization service.
In my opinion, having the file synchronization enabled allows for that cloud service to interfere with the exported file.
You can test this easily by turning off the file sync feature directly from the responsible app, OR by removing that service directly from Acrobat, OR, simply observe if this issue occurs only when your computer is online.
Just try the export action when your computer is completely offline to compare if the ghost file (or cached file) disappears when you are offline.
Otherwise, you may want to go online via web browser and sign in with your Adobe ID to the Adobe Creative Cloud and see if the default destination folder is actually caching the output file in the cloud (not locally in your computer).
In the same context, evaluate if the current user account have the permissions to read/write to the destination folder.
You may rule this out quickly by executing your current export method as the Administrator instead of performing the same export action with the regular current user profile (in which case, you may need to tweak the file handling permissions for that user profile).
1
Reply
AdChoices