• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Issue With Self Hosted CC Updates

Community Beginner ,
Jul 17, 2017 Jul 17, 2017

Copy link to clipboard

Copied

I configured a Adobe update server using the instructions on this forum, and it all seemed to operate fine. I tested it on several clients and people were installing photoshop in ~90 seconds and fairly happy.

However after a few reboots CC on all clients is reporting an error on the 'Apps' tab. "Download Error. Press Retry to try again or contact customer support. (404)."

If i remove the updater overrrides file and click 'reload applications', CC will get the list of apps properly, and readding the file allows them to continue to update locally, however come the next reboot it is again broken.

Any suggestions?

Views

1.4K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Aug 01, 2017 Aug 01, 2017

Thanks for confirming this. The most common cause of a 404 error aside from not being able to reach the AUSST server in general is the MIME-types not being correctly configured in the IIS settings; please could you confirm you have the exact settings described in the documentation in terms of the module mappings, app pool pipeline mode and that you have uploaded the web.config from the link on this page:

Use the Adobe Update Server Setup Tool (AUSST)

You will need to restart the webserver after a

...

Votes

Translate

Translate
Community Expert ,
Jul 17, 2017 Jul 17, 2017

Copy link to clipboard

Copied

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jul 28, 2017 Jul 28, 2017

Copy link to clipboard

Copied

Hi DylanBell ,

Greetings.

Regenerate the config file a fresh one and then deploy that.

Once done then check if users are able to update there applications.

If it still does not work, please share the following logs with us.

The following log files are located in the %temp%  folder in Windows and in the ~/Library/Logs in Mac OS:

  1. AdobeUpdateServerSetupTool.log
  2. AdobeAcrobatUpdateServerSetupTool.log

DLM.log is located in the following locations:

Windows:

%Temp%\CreativeCloud\ACC\AdobeDownload

%Temp%\AdobeDownload\

Mac:

~/Library/Logs/CreativeCloud/ACC/AdobeDownload

~/Library/Logs/AdobeDownload/

~Rohit

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jul 30, 2017 Jul 30, 2017

Copy link to clipboard

Copied

Thanks for your response.

The recreated config was identical.

I've uploaded the logs to AUSST Logs - Pastebin.com

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jul 31, 2017 Jul 31, 2017

Copy link to clipboard

Copied

The 404 error suggests a problem with the hostname or downloading the list of products.

Please could you check whether you are able to download an XML file from the server, for example:

http://wsus/Adobe/updates/oobe/aam20/win/AdobeAfterEffectsCS6-11/11.0.4/11.0.4.xml

This should point us in the right direction to find the cause.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jul 31, 2017 Jul 31, 2017

Copy link to clipboard

Copied

Manifest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" CSUVersion="1.0" xsi:noNamespaceSchemaLocation="../../oobe/6.0/installertech/public/Common/xplat/schema/CSUManifest.xsd">

<UpdateID>11.0.4</UpdateID>

<OwningChannel>AdobeAfterEffectsCS6-11</OwningChannel>

<TargetBuildType>2</TargetBuildType>

<DisplayName default="en_US">

And so on.

That seems to work fine.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Aug 01, 2017 Aug 01, 2017

Copy link to clipboard

Copied

Thanks for confirming this. The most common cause of a 404 error aside from not being able to reach the AUSST server in general is the MIME-types not being correctly configured in the IIS settings; please could you confirm you have the exact settings described in the documentation in terms of the module mappings, app pool pipeline mode and that you have uploaded the web.config from the link on this page:

Use the Adobe Update Server Setup Tool (AUSST)

You will need to restart the webserver after any changes.

Please also check the IIS logs for any relevant information, such as whether the client machines are successfully connecting, and downloading XML files and updates (ZIP files).

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Aug 01, 2017 Aug 01, 2017

Copy link to clipboard

Copied

LATEST

The MIME types were fine, but following through the instructions again, I put the web.config in

[AUSST root folder]\ACC\services\ ffc\validation\ but not  [AUSST root folder]\ACC\services\ffc\icons\...

Looks to be sorted now.

Thanks

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines