Skip to main content
Matt-SpaceDiv-Sunnyvale
Inspiring
December 21, 2019
Answered

Internal AUSST server - Spark updates not available to clients

  • December 21, 2019
  • 7 replies
  • 1646 views

Greetings all,

I have an internal update server running (Apache - macOS).

Everything is fine with one exception - Spark updates are not being listed as available on the client machines.

When I have the clients check with Adobe's update server, the Spark updates show up.

When pointing them to the internal server, everything is available except Spark updates.

What's even more puzzling, is the internal server does indeed have the Spark update(s) in place within the normal update repository.

I've already performed numerous update server rebuilds via the "--fresh" argument - made no difference.

Another note - I'm not seeing Spark listed anywhere in the updaterfeed.xml file.

Is there anyone else seeing Spark updates not available?

This topic has been closed for replies.
Correct answer ___Dom___

I've shared replacement libraries from our engineering team at the following link which should resolve this issue - please let me know the result:

 

https://assets.adobe.com/public/322fcebc-c335-4c4b-65e3-bb805d8e1ead

 

Windows:
1) On the client machine where RUM is running, go to C:\Program Files (x86)\Common Files\Adobe\Adobe Desktop Common\HDBox
2) Replace HUM.dll (ver 5.0.0.354) with the one attached ver 5.0.0.363 HUM.dll

 

Mac OS:

1) On the client machine where RUM is running, go to /Librabry/Application Support/Adobe/Adobe Desktop Common/HDBox
2) Replace HUM.dylib (ver 5.0.0.354) with the on attached ver 5.0.0.363 HUM.dylib

7 replies

___Dom___
___Dom___Correct answer
Inspiring
January 8, 2020

I've shared replacement libraries from our engineering team at the following link which should resolve this issue - please let me know the result:

 

https://assets.adobe.com/public/322fcebc-c335-4c4b-65e3-bb805d8e1ead

 

Windows:
1) On the client machine where RUM is running, go to C:\Program Files (x86)\Common Files\Adobe\Adobe Desktop Common\HDBox
2) Replace HUM.dll (ver 5.0.0.354) with the one attached ver 5.0.0.363 HUM.dll

 

Mac OS:

1) On the client machine where RUM is running, go to /Librabry/Application Support/Adobe/Adobe Desktop Common/HDBox
2) Replace HUM.dylib (ver 5.0.0.354) with the on attached ver 5.0.0.363 HUM.dylib

Matt-SpaceDiv-Sunnyvale
Inspiring
January 8, 2020

Thanks for the reply Dominic.

I get a "Error 401: Unauthorized" when I click on that link

Matt-SpaceDiv-Sunnyvale
Inspiring
January 8, 2020

 

Update:  I've updated my test machines to CC 2020, and ran a fresh incremental sync on my internal AUS last night.

See the attached screenshot.  On the left is the test client looking for updates directly from Adobe.  On the right is the same machine looking at my internal AUS.

This is driving me bananas.

Matt-SpaceDiv-Sunnyvale
Inspiring
January 3, 2020

For reference, I've included two screenshots - one showing no updates available when the client is pointing to our internal AUS, and one showing two updates available (SPRK and COSY) when the RUM client is pointing to Adobe's AUS.

Note:  These commands were both run from the same client machine.

Here are the results of the client pointing to the internal AUS:

Here is the other with the same client pointing directly to Adobe's AUS:

___Dom___
Inspiring
December 22, 2019

What looks like Spark on an AUSST server, SPRK, is actually Adobe XD. The product known as Spark is a web-only product, and works entirely through the browser. This is probably why it seems like there are Spark updates on the server.

Matt-SpaceDiv-Sunnyvale
Inspiring
December 22, 2019

Thanks for the reply Dominic.

What's concerning is when I invoke the RUM client on two of my test Macs (both with the exact same CC2019 loadouts) the one pointing directly to Adobe lists "SPRK" as having an available update.  The one pointing to my internal AUS, does not show any SPRK updates availble.  My internal server is up to date, and had completed an incremental update prior to the test.  Just to be on the safe side, I also performed a fresh server update prior to the incremental.