The option to disable SharePoint Integration via registry entry disables all of SharePoint integration. There is no way to "disable" the check-out prompt only. I'm not sure what you mean by just disabling the prompt, but i'm guessing that you mean something like "Always check out on open" type of functionality should be supported. If that's the case, you may submit a feature request for it.
Thanks for your response, this confirms what I thought.
Sorry I wasn't totally clear in the first instance, the article I was referring to used the phrase "Disable Check-Out Prompt" which sounds like it is specific to the Check-Out prompt, not all of the SharePoint integration features.
What I mean is that Adobe Acrobat X prompts for check-out, regardless of whether the relevant SharePoint document library is set to "Require documents to be checked out before they can be edited". Users find it confusing that they have set this option to "No", but Acrobat still prompts them to check-out documents when they attempt to edit them.
It seems that Acrobat does not take this setting into account when editing documents from SharePoint document libraries, is this correct?
If this is the case, I will submit a feature request to have this functionality enabled.
I'm facing the same problem. We use Acrobat Reader X for adding comments to PDf-files, but most of the time the user only wants to read the document.
So he likes to open the document without the dialog to checkout the document or just open it.
After opening the PDF the Sharepoint Integration must be available to check out the document.
Disable the SP Integration in the registry also removes the Sharepoint Integration menu in the Acrobat Reader X.
Is there some news on this issue or how can we configure this requirement ?
The fact that we can't disable the check-out option has actually become such a big nuisance that we had to invest in other PDF reading software. People continually select the default action of checking out, thereby blocking other organisation users! this places huge pressure on IT to run around and force uncheck-out files.
this is the worst feature I've ever seen with Adobe, since it cannot be disabled in any setting anywhere!!
What we have found that has made some difference with SharePoint 2013 and Adobe XI, was also having MS Office 2013. Now, why would having MS Office 2013 make a difference? I do not know but it seems to make things a bit easier.
Also - what I have done to bypass the check out (even if the doc library is not set to check-in, check-out) is after opening the pdf document (opens as a temp internet file), make my changes, then File, Save As, and then save either by saving to the shortcut I made under Favorites (to the SP Library) in Window Explorer or by Saving to Online Account (location already mapped) after clicking on Save As.
Still don't know what the fix is to not have it open as a temporary internet file.
Have you ever had an answer regarding this issue??
Best work-around I've found is to use the "send to" and publish it to a library the audience can reach. That seems to work.
Does anyone know if the Adobe dev team is working on an option that one can select to turn off the default behaviour of prompting users for check out and edit?
Has there been any update on this? I would also like to have some feature in place to stop lots of people who "continually select the default action of checking out, thereby blocking other organisation users"
I am having the same problem. Any progress on the case anyone? People are checking documents out in a library were none is supposed to be and it is greatly troublesome.
At the very least all they need to do is change the order to 'Open' 'Check out & Open' 'Close'
and change the default button to 'Open'
How hard is that I mean really my cat could make that change.
Sadly this is increasingly typical of Adobe, how long has this been going on for, definitely not a listening company.
SharePoint has a lot of users checked out by users just because they opened the document for viewing.
This is an issue when trying to quick print from File Explorer in Windows.
When printing a PDF (or several PDFs in one go) from File Explorer (using right-click -> Print), if the files are located locally or on a file server they will print normally without the need to open Acrobat or FoxitPDF etc. But if the PDFs are in Sharepoint, the "Check out & Open....etc" prompt interrupts the print process and forces the user to open the PDF in Acrobat, for every file selected, and to respond to the prompt on each document before the PDF will print.
So in effect, the quick print option from File Explorer for Sharepoint PDFs no longer works.
We have a similar problem. The goal of our setup is to make the use of writeable PDFs that inexperienced users fill with information. We want the experience for these users to be a simplistic as possible, so asking questions like "Do you want to check-out this document?" and "What are the check-in comments" causes much questioning; especially since these prompts are unnecessary. But we do need SharePoint support for these documents.
There is a way to suppress the check-out prompt if you are willing to do a moderate amount of programming and use the SharePoint client DispEx call; you can force the check-out. But since the final three prompts are encoded completely within Acrobat (1 - "Do you want to save your changes?", 2 - "Do you want to check-in this document?" and 3- "What are your check-in comments?"...all of which we would love to completely supress) we currently have no choices.
Even patching Acrobat would not be an option, because we would have to force everyone to patch their client copy of Acrobat.
4 years later after the original poster and we still have this issue...
This is not an Adobe Acrobat issue. Acrobat has nothing to do with the user being asked about checkouts for editing. The library where you're storing the PDF is configured to require a checkout before editing. There is no way around that. Period. If you want the document to simply open, then you need to setup a SharePoint Library without that setting.
Not Adobe's problem. Ask Microsoft to implement a more granular "checkout for editing" feature. If they did that by file/mime type it would make many people's live very much simpler.
Trent, I wish that was true. For all libraries (including the libraries NOT using check-in check-out) the popup is shown. What is worse, eventhough the library is configured to NOT use checkout, documents get checked out. Disabling the complete SharePoint integration does prevent users to check documents out... but it also removes the option to save updates (comments etc).
I'm also looking for a solution... Is there anyone of Adobe that can comment on this thread? If the functionality is never going to get in place, I'll start looking for another PDF writer.
I agree, that many users open file only for viewing/reading not for editing and I am sure SharePoint users are aware of Check-in/check-out functionality.
While you try to open SharePoint doc via Acrobat/Reader, it prompts you following three options:
1.) Check Out & Open
- If you want to open a file for editing, go with option 1, this will stop other users to edit the document while you are making changes to the file, Once you are done with editing, Save it and discard check-out/Check-in the file(these options are shown to user when you try to close the file) which will make file to available for editing to other users.
- And if you want only to read/view the document, go with option 2.
So as per your requirement, you can use available options.
Please let us know if required.
Thanks for this, but do you know if there is a permanent way of actually disassociating Adobe Acrobat Reader with SharePoint? I've tried the first solution suggested by the creator of this topic, and it works on my computer, but for some reason won't work on my clients' PC. I've recently tried other options like [HKEY_CURRENT_USER\Software\Mainsoft\Prefs\OpenPDFWithWebDav] @="false", but these do not work on my clients' PC either.
I'm particularly having this issue from opening PDFs through Harmon.ie, which is essentially a mini-SharePoint tucked in your Outlook as a plug-in, but disabling AAR from SharePoint will work the same.
I want to completely disable SharePoint from Adobe; how is this possible?
The Adobe staff answer does not meet the needs of our user community. As stated above, many libraries end up with multiple documents checked out because users don't understand or don't read the prompt. I am now advising users to uninstall Acrobat Reader and use a different product because of this issue.
This reply is not helpful at all, you clearly did not read the actual question.
I'm sorry Adobe that is a totally uninformed response from @Sunil2201who clearly is not a SharePoint user.
If you are using SharePoint properly, you do NOT check files out. All Microsoft Office apps now support co-authoring, and checking them out disables this important feature.
For that reason, NOBODY should be checking documents out/in of SharePoint, and anybody suggesting that users should be checking out documents needs to go back to the last decade where they came from, and that also goes for the applications that "support" SharePoint (i.e. Adobe Acrobat, which I love, but I hate the way it is totally broken with SharePoint).
All these years and still this issue persists. Do note that Adobe prompts user even if the doc library has disabled check out, set versioning as "No Versioning". It also highlights the checkout option which tends to push the regular user to click on the checkout option.
If Adobe really wants to enable this feature, at bare minimum, try not to highlight the check out option to mislead the end user!!
Recent revisions of Acrobat seem to have made Acrobat work better with SharePoint when Acrobat's SharePoint integration is disabled. It's now a bit more useful without SharePoint integration enabled, and permits saving to SharePoint webdav paths without returning save failures all the time.
However one BIG problem that remains when SharePoint integration is disabled is that Acrobat clobbers PDF file versioning & custom metadata within SharePoint when saving.
What it's doing when you save a PDF that's in SharePoint is saving to a temporary file (e.g. tempfile.tmp), and then once it's finished, it deletes the old file and then renames the temp file to the old file name. The new file loses all of the custom SharePoint metadata, and has a "0.1" (or 1.0" version) - losing all previous versions.
This is BAD behaviour and harkens back to the 1980s DOS days of file handling.
One way to get around this is using OneDrive - when Acrobat edits local copies of SharePoint files that are synced with OneDrive, then OneDrive handles that versioning properly, and will upload the new file as a next version, instead of deleting the old file, versions and metadata. I've done this when I wanted to do a "recognise text" across a large collection of PDF files, but wanted to retain the original version in document history, rather than lose the original (along with retaining all of the important document metadata attached to each file). Using OneDrive isn't a very good long-term / generic solution though - as it completely fails on complex libraries, and breaks many other things like co-authoring on Office files.