Skip to main content
Participant
September 16, 2021
Question

Check out/in pdf in SharePoint 2013 not working

  • September 16, 2021
  • 1 reply
  • 776 views

In our SharePoint 2013 environment, we have a library of documents that contains pdf's, excel's, and word docs. Our excel's and word docs work fine but when it comes to pdf's they do not. 

 

The way that it should work, and it works for microsoft docs, is that when you click a pdf document it should:

1. Launch Adobe Acrobat

2. Prompt Check-Out of document

3. Allow the user to edit the pdf

4. The user closese the document

5. A prompt to Check-In is given

5. The document is updated with the newly edited version in SharePoint. 

 

Unfortunately this is not how it's working. At the moment when you click a pdf it just opens within the browser with no check-out/in prompts and you can't edit. This issue is only occuring in Chrome and Edge. It does work in internet explorer but our users do not want to have to use IE. We do have a work around at the moment that they can copy the url to the file and open it through acrobat with the direct url but that's just a temporary solution. 

 

Any help would be appreciated. Thanks!

This topic has been closed for replies.

1 reply

Amal.
Legend
September 16, 2021

Hi there

 

Hope you are doing well and sorry to hear that. As described, when you click a pdf it just opens within the browser with no check-out/in prompts and you can't edit. This issue is only occurring in Chrome and Edge and it works fine in IE.

 

- Would you mind sharing the version of the Adobe Acrobat DC you are using? To check the version go to Help > About Acrobat.

 

- Have you started experiencing this issue after the recent update of Adobe Acrobat/Reader DC application?

 

Please try to clear the cache memory of Chrome and Edge web browsers and try resetting them and see if that helps.

 

We are here for help, just need more information

 

Regards

Amal

NosterWAuthor
Participant
September 16, 2021

I'm currently using Acrobat Pro 2017 | version 2017.011.30202 .

 

This issue arose a couple months back so I don't really remember if it was due to an update or not. 

 

We have tried to clear the cache memory of Chrome and Edge with no success unfortunately.