Skip to main content
A
Anonymous
April 7, 2015
Answered

Error 16 in Windows Event logging Acrobat Reader DC

  • April 7, 2015
  • 8 replies
  • 16493 views

Hello,

I uninstalled Acrobat Reader XI.0.10 today (that had no eventlog-errors at all for my desktop Win 7 x64, nicely updated), and did a clean install of the new Acrobat Reader DC Dutch.

The reader works perfectly, but everytime I start the application, it creates a red error 16 in the windows event logger. The only information the event contains reads that "the acobat reader tries to reach a component that is not installed or corrupt on my computer. Try to re-install it...."

I did so, but the error 16 keeps on coming... I completely de-installed Reader DC, and reinstalled the former Acrobat Reader XI.0.10 again, and all errors 16 are gone, so there must be a bug in the new Reader DC-application/installer.

Does anyone has the same problem or a solution ??

Thanks, Rik (Belgium)

    This topic has been closed for replies.
    Correct answer ashutoshmehra

    This issue must now be fixed in the July 2015 quarterly.

    8 replies

    C
    carloss62532695
    Participant
    December 30, 2015

    I uninstalled Adobe acrobat XI Standard because we started getting error 16 after opening a pdf file, then reinstalled it and still getting the same message error 16. I have followed the troubleshooting for c:\programdata\adobe and did all steps on the 2 folders mentioned restarted the computer and made no difference. I have adobe reader on that pc and it works fine, only acrobat is giving trouble, please advise.

    ashutoshmehra
    Adobe Employee
    ashutoshmehraCorrect answer
    Adobe Employee
    July 15, 2015

    This issue must now be fixed in the July 2015 quarterly.

    ashutoshmehra
    Adobe Employee
    ashutoshmehra
    Adobe Employee
    May 21, 2015

    We have analyzed and found a bug where an event is being unnecessarily getting logged always when shutting down the Reader DC process; the intent obviously was to log the error only in case the application launch was unsuccessful.

    We'll get this fixed in the quarterly patch.

    Thank you for reporting this issue and apologies for any confusion these bogus entries may have caused.

    - Ashutosh

      A
      A__Nizoux
      Participant
      May 19, 2015

      Adobe Reader DC works on my computer without any error, but Adobe Acrobat DC won't work at all. Displays error 16 and asks to uninstall/reinstall... which does not fix anything.

      Would be glad to see some update on the issue.

      Thanks

      pwillener
      pwillener
      Legend
      May 20, 2015

      This topic & forum is about Adobe/Acrobat Reader.  Your issue is not only completely different ("Adobe Acrobat DC won't work at all"), but also about a different product.

      Please start a new topic in the appropriate Acrobat forum, and provide some details!

      D
      davids41629036
      Participant
      May 13, 2015

      Recently installed adobe reader dc.  same as everyone else error 16 in events log.  Tried to fix according to their support.  Could not find the 2 folders SLStore or Adobe PCD.  It seems to be working for what I use it for, but I do check my event logs and it is annoying having errors as this.  I have uninstalled and reinstalled several times also.

      Thanks

      David

      Manustif
      Manustif
      Participant
      April 8, 2015

      Same red event log with id 16 here every time I close my acrobat reader dc (german). The reader works fine and without failures or errors, but on closing the program the red event was logging. The same log occurs on my Win 8.1 32bit and Win 10 preview 32bit systems.

      Main System Win 7 SP1 64bit

      Still waiting also for a solution ...

      Thanks, Thomas

      A
      Anonymous
      April 8, 2015

      Hi

      I have the same issue using 32 and 64 bit win 7 pro, I have removed and gone back to the version 11.10

      as for the message below yours he should respect no two people use their computer and info the same I am with you.

      I hope that Adobe read this

      Tony

      pwillener
      pwillener
      Legend
      April 8, 2015

      I have no problems using Reader DC, but out of curiosity I went to check my Event Logs.  And yes, there I see it: Event ID 16, with not much info to go on.

      But I am sorry to say that it does not bother me much; Reader DC works, no delays, hangs, or other problems, so why should an Event Log entry bother us?

      If I were seriously concerned about it, I would probably use Process Monitor to find out what exactly is going on.  But even if I found that out, what would I do about it?

      A
      Anonymous
      April 8, 2015

      hello pwillener,

      cc. MillerAnthony & Manustif

      thanks for your check & reaction, but concluding from also the other posts from MillerAnthony & Manustif, the new Reader DC generates the same major red error to Windows Event Log to WIN 7-system-users.

      It was my first purpose to check if I was the only one or if it was general : so it's clear now it's an Adobe Reader DC - issue.

      Apart from the fact that the new Reader DC program works indeed very fine at first sight (I totally agree & also wrote that in my first post), there must be something wrong anyway, maybe in a functionality we didn't tried yet, and which will come across to the surface sooner or later....

      Every self-respecting software-company tries to avoid red errors generated in the Windows Event logs : that's the reason why béta-testing concentrates not only on functionality/user-experience, but also on "under-the-hood" errors to be fixed before general release - the reason why the technical crew of companies always ask for print-screens of those windows event-log, the reason also why I described it in my first post. I do myself a lot of Béta-testing for major companies as Microsoft, Norton-Symantec, Nero and also Adobe's Flash-player, ..... and it is my general experience that red errors are taken seriously by software-companies, even if there's no user-problem at first sight.

      So I hope the Adobe will read , analyse & fix this, to avoid possible hidden future troubles.

      Thanks for cooperation to everyone

      Rik

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