Skip to main content
K
Kanghyun
Participant
January 23, 2020
Question

There was a problem reading this document(117)

  • January 23, 2020
  • 1 reply
  • 15725 views

I'm using Adobe Acrobat X.

Yesterday I found some error when I convert DWG(Autocad drawing file)to PDF and tried to open it with acrobat X. But the image dosen't come out to the screen and the message "There was an error processing a Page. There was a problem reading this document(117)" was on the screen. So I Clicked 'OK' with control key to see more information then I got this ununderstandable message. I have no idea what I have to do to solve this problem so I'm asking for help to this community. I will be very happy if you guys help me to get this problem fixed. Thank you:)

This topic has been closed for replies.

1 reply

ls_rbls
Community Expert
ls_rblsCommunity Expert
Community Expert
January 23, 2020

Hi,

 

To work around that 117 error you can try a few things, like disabling Portected Mode and Enhanced Security (just for troubleshooting purposes), and see if the problem happens again.

 

A screenshot of what you get would be very helpful and also a brief description of the steps that you were taking when (exporting to) converting the file to PDF

 

K
KanghyunAuthor
Participant
January 28, 2020

Hi, you mean the protected mode of acrobat itself or turning off the security system of window?

zornitzad80431241
zornitzad80431241
Inspiring
December 5, 2023

I turned off every security system of MS window and try to open PDF with acrobat but I got the same message just like pictures

I posted above. I think this solution is not appropriate one for my issue.

But I'm very appreciate for your help. Thank you.


Hi there,

 

I had the same error 117 with Adobe Acrobat Standard 32 bit.

I had  very large file 17,497 KB generated from Framemaker and when I attempted to replace a picture, the error 117 appears.

I did exactly as suggested :I went to Edit > Preferences > Security (Enhanced) and cleared Enable Protected Mode At Startup. Then, I restarted the application and the error did not appear anymore.

 

Thanks for the post.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices