Skip to main content
joeln78231135
Participant
February 14, 2018
Answered

RUM not updating Acrobat to 18.011.20035

  • February 14, 2018
  • 1 reply
  • 937 views

Here is my log and this is happening across the board on multiple OSX Sierra (10.12.6) and High Sierra (10.13.3) installations when running "sudo RemoteUpdateManager"

RemoteUpdateManager version is : 2.2.0.2

Starting the RemoteUpdateManager...

**************************************************

Following Acrobat/Reader updates are applicable on the system :

(AdobeAcrobatDC-18.0/18.011.20035)

**************************************************

**************************************************

*** Installing (AdobeAcrobatDC-18.0/18.011.20035) ...

*** Failed to install (AdobeAcrobatDC-18.0/18.011.20035) ...

**************************************************

No new applicable Updates. Seems like all products are up-to-date.

Following Updates failed to Install :

(AdobeAcrobatDC-18.0/18.011.20035)

**************************************************

RemoteUpdateManager exiting with Return Code (2)

Contrary to Adobe's belief all products are not up to date nor open during installation and the update remains available. If I update via the GUI it works fine, we just have hundreds of machines so this isn't really feasible. Anyone else running into this?

Thanks!

    This topic has been closed for replies.
    Correct answer rpandita

    Hi joeln78231135 ,

    1. Please make sure you run RUM as SUDO.

    2. Run the log collector tool and upload the file to google drive and share the link with us - Log Collector Tool

    ~Rohit

    1 reply

    rpandita
    rpanditaCorrect answer
    Inspiring
    February 15, 2018

    Hi joeln78231135 ,

    1. Please make sure you run RUM as SUDO.

    2. Run the log collector tool and upload the file to google drive and share the link with us - Log Collector Tool

    ~Rohit

    joeln78231135
    Participant
    February 15, 2018

    I'm running as SUDO, you have to otherwise it won't run at all. Seems to be working now however after yesterdays update and a few reboots to the machines in question. Thanks!