Skip to main content
Participant
July 15, 2013
Répondu

Error while saving a .PDF File to a mapped drive

The issue I am having is similar to the one found on this older post. http://forums.adobe.com/message/3066663#3066663

The issue is as follows. I have a small company about 15 users divided into a couple of departments with different networking access needs. They each have Adobe Acrobat version XI installed on a Windows 7 Platform. Each user has a set of mapped drives that correspond to their department. The Disk mappings are all directed to the main shared Network Attached Storage (NAS) device. At any time there can be a number of PDF files open and being worked in. The same PDF is usually not opened at the same time from two different locations.

The issue is that two users who do a large amount of the work, IE. Scanning documents and adding them to documents that have been previously created, are reporting the same issue. The issue is when they have the PDF document opened and they are adding new content. Once the new content is added they go to save the document and then receive the following error:

The document could not be saved. Cannot save to this filename. Please save the document with a different name or in a different folder.”

In order to save the file the user has to use the save as function and then browse to the original file location to save the document with the changes that have been made.

Along with the above error we have noticed that Adobe Acrobat is renaming the file that has been changed to aae##### or aak##### or aan#####. The file name is changed causing the normal save function to not work correctly.

Is there a reason Acrobat would be doing this?

I am not using Microsoft SharePoint.

Meilleure réponse par KevinCur

My users started to experience this issue for files on network shares as well once Adobe Reader was updated to 11.0.10

It has to do with Protected Mode being turned on.  I don't know if it was off by default & now it is on with the update but turning it off changes Adobe Reader's behavior back to what the users expect - a prompt warning you if you want to overwrite the existing file & then selecting Yes to overwrite.

To disable Protected Mode:

Start Adobe Reader

Edit - Preferences - Security (Enhanced)

Uncheck Enable Protected Mode at Startup

Close Preferences & Close Reader


Now open a file from a network share & you Adobe saves as it used to.

16 commentaires

Participant
January 13, 2015
KevinCurRéponse
Participant
January 7, 2015

My users started to experience this issue for files on network shares as well once Adobe Reader was updated to 11.0.10

It has to do with Protected Mode being turned on.  I don't know if it was off by default & now it is on with the update but turning it off changes Adobe Reader's behavior back to what the users expect - a prompt warning you if you want to overwrite the existing file & then selecting Yes to overwrite.

To disable Protected Mode:

Start Adobe Reader

Edit - Preferences - Security (Enhanced)

Uncheck Enable Protected Mode at Startup

Close Preferences & Close Reader


Now open a file from a network share & you Adobe saves as it used to.

Dbarahona
Participant
January 8, 2015

I can confirm that this solution works; I will be passing this along to the users that were receiving the same error. Thanks for your input!

CJBVT
Participant
January 6, 2015

I hope this will help:

I have found a workaround on my part while saving to a network drive.

When a user saves the document it will give a temp name for it.

I had them save it as a temp, then save it again with the original filename and it allows it.

For some reason on my issue, adobe has to save as a temp first.

BRD CEO
Participant
December 31, 2014

Same issue.  Any news of an update to fix this?  Some of our workstations have an older version of Reader and this does not happen.  As soon as the most recent update is done the problem returns.  Our current version that is causing the issue is 11.0.10. 

December 31, 2014

No updates yet. I assume Adobe is working on some betas but I'm not in the know. In the meantime the following options have worked for me:

1) Save to a local drive (instead of a network drive).

2) After it gives you the error, "save as" and then select the file you were initially saving.

December 18, 2014

I've just experienced this issue too, but it hasn't been an issue until just this week. I don't know what caused the change. Any solutions?

AndiOl
Participant
August 14, 2014

Did you ever get this figured out? We are having the same renaming issue and it's driving me crazy. Any insight you can provide would be greatly appreciated.