Optimizing PDF converts File into .tmp file

[AR201593293]

As the subject describes, optimizing PDF files yields the error message "The document could not be saved. Cannot save to this filename. Please save the document with a different name or in a different folder." and the file gets turned into a .tmp file. Optimizing the .tmp file and saving it to the previous name correctly saves it as a PDF, however, this wasn't necessary before. Due to the work environment, these files must stay within this folder and follow a certain naming convention that cannot be changed. Is there a reason these files keep converting into tmp files? Any help is appreciated. Thank you!

Views

[Karl Heinz Kremer]

There probably is a reason, but not an obvious one. Is the file you are trying to write to write protected? Is the folder stored on a server? Is the folder linked to an online storage service like DropBox? What you are seeing is not normal, so we need to figure out what makes your setup different.  

[AR201593293]

Thank you for your response. It is occurring with multiple files, they are not protected nor are they linked to an online storage service. They are pdf files scanned and saved from a copier, then we recognize text via Scan & OCR tool, then try to compress the pdf via the Optimize tool. Some of these files are saved on a shared/group drive on our network. 

[Karl Heinz Kremer]

Do you get the same results when you drag such a file to your desktop, and then open it from there? 

[AR201593293]

After some testing, I seem to only get this error message when compressing files and trying to save it with the same name in shared folders. I tested compressing the same files in a local folder, and they compressed successfully without the error and tmp file.  I don't think this was the case before, this issue started happening within the last few months, maybe January. It is happening to others I work with as well. Is this something Acrobat changed? Or something on our end?

[Karl Heinz Kremer]

You can find out what has changed in Acrobat (at least the things that were deliberately changed) in the release notes. They also list a date of when the update was released: https://helpx.adobe.com/acrobat/release-note/release-notes-acrobat-reader.html

You very likely wont find somethink like "broke behavior when saving to a shared folder" 🙂 But at least this gives you some dates to work with. 

When you say "shared folder", is that something like DropBox, OwnCloud, OneDrive or similar service? If so, you have another player between the document in the folder and Acrobat. I've seen odd behavior in similar situations. The problem here is that the application (regardless of whether it is Acrobat or any other application) does not know that the file is not stored locally (or not only locally), and that the DropBox/OwnCloud/OneDrive... application is making a remote file look like a local file. Sometimes that does not work 100%.

[AR201593293]

Yea, unfortunately I don't see anything mentioning this issue or fixing it in the patch notes. Thank you for your help. They're shared folders on network drives and I believe we access different shared folders via different security/permissiong groups (group policy management on Active Directory).

[AR201593293 · Accepted solution]

Tested different settings and found a solution, just in case someone else has this issue in the future. Unchecking the box/setting "Enable Protected Mode at Startup" under Security (Enhanced) preferences seemed to resolve the issue. We no longer receive the error message and the file does not get turned into a tmp file when saving in the same shared folder under the same name. I know this is the same setting that gives another issue with CommonLook plug-in.

[Karl Heinz Kremer]

Thanks for the update. This should probably be my #1 reply: Does changing the protected mode checkbox make it work"? 🙂 I have this always turned off, just because it has caused a number of problems in the past.