Issues Signing / Saving Digital Signatures in Adobe 9.0

Can anyone tell me if this post is in the correct forum?

This one issue is causing us to go to Nitro PDF. Does anyone have any ideas on how to bypass this new 'save as' feature without giving users modify permissions.

Hi,

When you say that you are using Acrobat on the network, do you mean something akin to Citrix where there is one cop of Acrobat on the Citrix server and it's access by multiple users, or, is it a local copy of Acrobat but you are signing a PDF file that is in a server based repository?

Thanks,
Steve

We don't use Citrix. Acrobat is installed locally on each PC. The drawings that the users are signing are on a Windows 2003 server - so yes, the files are server based so they are receiving their permissions through the network.

Using 'save as' to change the file name sounds like an easy fix but the engineering dept is wanting to switch to Nitro PDF as a solution. Very frustrating.

Are you signing your document within a browser or just within Acrobat? If you're using a browser such as Internet Explorer is it configured as a Helper application? Are you using Acrobat 9.3?

We're using Acrobat 6.0 Pro and Adobe 9.3 to sign documents.

I have been seeing this problem for the past few months and I'm not sure what's changed.
I usually sign documents that have been created using CutePDF print driver.
The files are on a network drive.
I use Acrobat 9.3.3 on Windows 7 to do the signing.

Here's the sequence I work through:
1. I open a PDF document and attempt to sign it.
2. When asked to overwrite the original file, I get the error message reported above.
2. After the error, it leaves a file on the drive named something like "aaaa06236".
3. If attempt the add the signature again, it askes if I want to overwrite "aaaa06236".
4. If I now click on the original .pdf file, it signs and saves it.

I guess I can still sign but have to do it twice.
I'll experiment a bit more and let you know what happens.

Chris M

I have documents in .pdf format that were created months ago and not changed, but the digital signature indicates that they have and shows "problems" with some of the signatures. New documents created in word and converted to .pdf using v9.0 will not allow digital signatures by individuals who have signed many of the previously-mentioned documents using the certificate issued internally for digital signatures... Documents simply don't react to someone attempting to sign.

My firm uses Adobe Acrobat 9.0. We too have experienced the intermittent 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.' When this error occurs, Adobe creates a temporary copy of the file and renames it "aaa#####" (the #s are randomly generated digits).

To fix the issue, we save the "aaa#####" file to a local drive, open it, and save over the network file we were originally trying to amend. Or, the user will wait a few minutes, reopen the network file, make their changes and save it without getting an error message.

I have no idea why this is occurring. Each user has an Acrobat 9.0 license loaded on their local machine. These files being amended were originally created by the users who are trying to access them. Furthermore, these users have full permissions to the network drives. Can anyone tell me why this error is occurring and how to prevent the "aaa#####" files from being created?

Thanks,
Teresa