My problem is that Acrobat is renaming and also creating a new PDF file with both a random filename, when I save a .PDF file witch is checked out in SharePoint.
I'm trying to find a way around the problem that we cannot save a .PDF file back to SharePoint. Because Adobe Acrobat cannot handle WebDAV, I’m glad that Microsoft SharePoint haves a build-in features that enables us to open files in explorer, just like you access a network dive. So I`m using this option to open a .PDF file and save it back to SharePoint.
This all works but only when a file is not checked out in SharePoint. When a file is checked out (by me) and I save the file. Acrobat gives me the 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.”. It then first creates a new file with the name “aaa04588” (without the .PDF extension). And then it renames the original file to “aab04588”.
The file “aaa04588” contains all the changes I have made. The file “aab04588” is the same (old) file and is still checked out (by me).
I have no clue what Acrobat is trying to do.
When a file in SharePoint is checked-out by another user, adobe acrobat gives me the nice notice “There was an error opening this document. Lock violation.”. It then refuses to show me the document, where I would expect to open in read only mode.
I have tried to simulate this with other programs, but they all handle correctly by just overwriting the file or open in read only mode. This is also what I expect.
I`m using the latest version of Adobe Acrobat 9 Pro Extended, version 9.3.3. I have tested It on MOSS 2007 and SharePoint 2010.
I hope someone could help me find the problem that causing this.