Skip to main content
dvdbornPXL
dvdbornPXL
Participating Frequently
August 23, 2017
Answered

RUM 2.1.0.11 not working, RUM 2.0.0.15 still works

  • August 23, 2017
  • 3 replies
  • 3036 views

We've been using the RemoteUpdateManager version 2.0.0.15 without a problem on our Macs.

RUM gets called using a command like this:

/usr/local/bin/RemoteUpdateManager --productVersions=AEFT --action=install

This works fine with version 2.0.0.15. However, in RUM version 2.1.0.11 I get an error message:

Starting the RemoteUpdateManager...

RemoteUpdateManager exiting with Return Code (1)

The log entry is:

08/23/17 14:56:23:938 | [INFO] |  |  |  |  |  |  | 1841797 | *******************start of Download****************

08/23/17 14:56:23:938 | [INFO] |  |  |  |  |  |  | 1841797 | GDE Version is 9.0.0.7 (BuildVersion: 6.0; BuildDate: Tue Mar 22 2016 07:36:18 )

08/23/17 14:56:23:939 | [INFO] |  |  |  |  |  |  | 1841797 | The file to be downloaded is https://swupmf.adobe.com/webfeed/oobe/aam20/mac/updaterfeed.xml

08/23/17 14:56:23:939 | [INFO] |  |  |  |  |  |  | 1841797 | Going to download the file at /private/var/root/Library/Application Support/Adobe/AAMUpdater/1.0/Data/webfeed.xml

08/23/17 14:56:23:986 | [INFO] |  |  |  |  |  |  | 1841797 | *******************End****************

Now when I visit the URL https://swupmf.adobe.com/webfeed/oobe/aam20/mac/updaterfeed.xml I get a web page telling me:

This page contains the following errors:

error on line 1 at column 1: Document is empty

Below is a rendering of the page up to the first error.

This doesn't look right.

How can we use the latest RUM version to update specific Adobe applications?

David

This topic has been closed for replies.
Correct answer Ric5

dvdbornPXL,

I experienced similar issues about a year ago when attempting to install a newer version of RemoteUpdateManager.  I found out directly from the Adobe Creative Cloud Packager developers (Karl Gibson's team) via the Adobe channel on the MacAdmins Slack team that you should no longer install RUM by manually copying the RemoteUpdateManager binary to /usr/local/bin/ because RUM now has dependencies on the Adobe Update Manager (or Adobe Application Manager, can't remember which for sure).

I was told that you should build an "empty" package via Creative Cloud Packager with the "Enable remote update manager deployment" checked and no Creative Cloud applications selected.  Since the latest CCP now copies down the newest RUM version on the fly, this creates an installer that installs the latest RemoteUpdateManager binary along with any AUM/AAM dependencies.  You can then install this package to upgrade RUM.  Unfortunately, this creates a rather large 400+ MB package just to update RUM.

Since this has been known for a while I am surprised Adobe Support hasn't changed their documentation/procedures to no longer recommend copying the RemoteUpdateManager binary.


dvdbornPXL​,

This worked for me, though I added a small package (Extension Manager CC) just in case what Oliver said was true for me. Like most people here, the older version of RUM was downloading but not installing some updates. A drag-and-drop replacement of the latest version only checked Acrobat and finished up. Using the install package built by CCP downloaded and installed the updates that were failing. This is very good to know and I'm a little surprised that there aren't a lot of other people getting bopped by this.

Thanks and kudos for Karl Gibson & co. for passing this along.

Ric

3 replies

O
Oliver Hetzner
Participant
October 23, 2017

Hi there,

I found out, that you need at least one Application of CC 2018 to run the 2.1.0.11 successful, even on an old application.

If you only have CC 2017 Apps the 2.1.0.11 updates only the Acrobat DC.

Even if you install an CC 2018 App and uninstall it at once the 2.1.0.11 works.

So I think Adobe leaves something behind in the System.

Hope this helps.

OH

    dvdbornPXL
    dvdbornPXLAuthor
    Participating Frequently
    September 6, 2017

    Thanks for the clarification!

    rpandita
    rpandita
    Inspiring
    August 23, 2017

    Hi David,

    Run the command using SUDO, that should take care of the Error code 1

    In terminal type - Sudo and then drag and drop the RemoteUpdateManager file.

    ~Rohit

    dvdbornPXL
    dvdbornPXLAuthor
    Participating Frequently
    August 24, 2017

    Hi Rohit,

    I had RemoteUpdateManager already running as a sudo user.

    Running RemoteUpdateManager v2.1.0.11 without the --productVersions option works OK. However it doesn't work with the --productVersions option.

    RemoteUpdateManager v2.0.0.15 works with and without the --productVersions option.

    I'd like to use the --productVersions option in v2.1.0.11 without getting the error as described in my original post.

    David

    rpandita
    rpandita
    Inspiring
    August 24, 2017

    Hi again,

    I tested it on my Mac machine and was successfully able to update After Effects.

    Can you re-download RUM version 2.1.0.11 from this link -

    Remote Update Manager update

    ~Rohit

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