Error 1602 Adobe Reader Update
Contents |
Acrobat 9 Reader 8 Reader 9 Issue When you adobe reader update error 1612 choose Help > Check For Updates in Acrobat or adobe reader update error 1625 Reader, the Ready To Install dialog box appears. However, when you click Install, the error adobe reader update fehler 1602 Error 1602 appears. Solution Delete the ARM folder under the appropriate directory hierarchy. Acrobat 9 Win XP: C:\Documents and Settings\All Users\Application Data\Adobe\Acrobat\9.2Vista: C:\ProgramData\Adobe\Acrobat\9.2 adobe reader update error 1635 Reader 9 Win XP: C:\Documents and Settings\All Users\Application Data\Adobe\Reader\9.2Vista: C:\ProgramData\Adobe\Reader\9.2 Acrobat 8 Win XP: C:\Documents and Settings\All Users\Application Data\Adobe\Acrobat\8.1Vista: C:\ProgramData\Adobe\Acrobat\8.1 Reader 8 Win XP: C:\Documents and Settings\All Users\Application Data\Adobe\Reader\8.1Vista: C:\ProgramData\Adobe\Reader\8.1 Additional information Error 1602 appears if the ARM (Acrobat Refresh Manager) self-update MSI files are missing from the
Adobe Reader Update Error 1321
Adobe Reader's Application Data folders. Twitter™ and Facebook posts are not covered under the terms of Creative Commons. Legal Notices | Online Privacy Policy Acrobat < See all apps Learn & Support Get Started User Manual Tutorials Ask the Community Post questions and get answers from experts. Ask now Contact Us Real help from real people. Start now ^Back to top Was this page helpful? Yes No Submit No Comment By clicking Submit, you accept the Adobe Terms of Use. Change regionUnited States (Change) Choose your region Selecting a region changes the language and/or content on Adobe.com. Americas Brasil Canada - English Canada - Français Latinoamérica México United States Europe, Middle East and Africa Africa - English België Belgique Belgium - English Česká republika Cyprus - English Danmark Deutschland Eastern Europe - English Eesti España France Greece - English H
Installation) is still occuring in Adobe Reader XI. PDQ Deploy Pro mode users can create a first step in the deployment to kill all Reader
Adobe Reader Update Error 1327
processes before proceding with the installation. It sounds like something out of adobe reader update error 1648 a ‘B' grade horror movie. You're deploying Adobe Reader X silently which, it hardly needs stating, means that adobe reader update error 1310 your users aren't aware of the push. You suddenly see a failed distribution with the error "User cancelled installation". A quick flash back. The year was 1998. We had https://helpx.adobe.com/acrobat/kb/error-1602-update-acrobat-reader.html just setup a T1 (I know, I know) for our office. On top of that Adam had a most coveted home DSL connection. With his new 128 KB connection we decided to setup a VPN to our office so that Mr. Ruth could work remotely. It was shortly after this period that I was at the office working late. Alone. http://www.adminarsenal.com/admin-arsenal-blog/adobe-reader-x-error-1602-and-why-we-keep-our-users-in-the-dark/ All of a sudden the silence of the office was shattered by our main printer as it started shooting out a large print job. After using our inner-office defibrillator on myself, I quickly realized that it was just Adam working from home. These two stories share something in common. They were both unexpected and ever so slightly disconcerting. Back to the Reader X deployment. This happened to one of our users this week when using PDQ Deploy to install Adobe Reader X. The situation, discovered through logging the installation, was that Adobe Reader 8 was currently running on the target machine and had locked files. The Adobe installer decided that throwing an error 1602 (User cancelled installation) was an appropriate error code (we humbly disagree). Again, logging saved the day. Here's a quick refresher on logging installations when pushing out an MSI. To enable logging add /log to the command-line options. Be sure to include the full path to the log file because the installer directory gets deleted at the end of the install taking any log
Windows Installer 1602 (originally titled "How does a user cancel a silent install?") Jason Riker September 21, 2011 16:59 None How can a user cancel a silent install? I'm pushing Acrobat Reader X to my workstations. I chose the silent install option, but https://support.adminarsenal.com/hc/en-us/community/posts/211668427-Error-1602-from-Adobe-causes-confusion-with-Windows-Installer-1602-originally-titled-How-does-a-user-cancel-a-silent-install- some of the deployments are failing due to "User cancelled installation." Thanks, Jason Facebook Twitter LinkedIn Google+ Date Votes 11 comments 0 Shawn Anderson September 21, 2011 20:13 That's odd, Jason. All GUI activity should be suppressed, and I wonder if there is a timeout occurring that the Adobe installer reads as a user denied request. Will you please export your PDQ Deploy installer and attach it here. Also, is there a minor version on the Adobe X? adobe reader I want to download the exact match and use your installer in our lab. Thanks! Permalink 0 Jason Riker September 21, 2011 20:18 Shawn, Thanks for your help. As to the minor version number, I'm not sure. I'm download this file from Adobe's FTP site - AdbeRdr1011_en_US.exe . I've attached the deploy file. Regards, Jason Permalink 0 Adam Ruth September 21, 2011 20:32 "User cancelled installation" is MSI error code 1602 which it appears Adobe has (annoyingly) decided to also adobe reader update use for some other problem, but it's necessary to get a log file to find out what it is. http://documentation.adminarsenal.com/PDQDeploy/1.2/msi_logging.htm Send us the log file and we can help to decipher it. Permalink 0 Jason Riker September 21, 2011 20:55 Adam, Not to sound too dumb, but where do I find the log file you need? Jason Permalink 0 Jason Riker September 21, 2011 21:02 Wow, I'm even worse than I thought. I just clicked the link you provided, Adam. Sorry about that. I'll re-run a workstation and attach the file. Permalink 0 Jason Riker September 21, 2011 21:08 This is what I have in my installer's Parameters section, "TRANSFORMS=AcroRead.mst /log c:\readerx\temp\log.txt" Unfortunately, it's not producing a log file. Permalink 0 Adam Ruth September 21, 2011 21:15 Try putting the /log parameter first and see if that helps. Permalink 0 Jason Riker September 21, 2011 21:17 My log file issue was that I didn't know the path was for the remote machine. I assumed local. I was able to get a good log and am attaching it here. Permalink 0 Adam Ruth September 21, 2011 21:33 It looks like Reader is currently running on the computer and the installer can't continue while its locking some files: ADelRCP logging: : In Process : AcroRd32.exeADelRCP logging: : AppsInUseEx targeted module is in use: C:\Program Files\Adobe\Reader 8.0\Reader\AcroRd32.dllADelRCP logging: : Setup terminated because critical files are i