Participant

Answered

AUSST 404 Errors - tried different ISPs

3 replies
5152 views
Translate

Please download the attached file to view this post

This topic is closed to new replies. Start a new post to keep the conversation going.

swaadobeCorrect answer

Participant

Hello,

i`ve found the solution for our problem:

First I've uninstalled all CC-Programs
I've used AdobeCreativeCloudCleanerTool and cleaned everything he found
After that I' renamed the Adobe folder to Adobe.old in the system libary and the user libary aswellSystemwide: /Library/Application Support/Adobe
User: /Users/yourusername/Library/Application Support/Adobe
Checked the Application Dir that everything of the Adobe programs are gone espacially /Applications/Utilities/Adobe Application Manager
Made a restart
Made a fresh install of Adobe CCP from the Creative Cloud Deployment Tools I downloaded from the CC Team Webside
After that I started AUSST from Terminal and made a fresh sync with the Adobe Servers
That done the trick, as you see below ...

osxserver:AUSST administrator$ sudo ./AdobeUpdateServerSetupTool --root="/Library/Server/Web/Data/Sites/Default/adobe_repo/"

Password:

Choose one of the following options :

1. Fresh Synchronization.

2. Incremental Synchronization.

3. Generate Client Configuration XML.

4. Exit.

Your choice: 1

Fresh Synchronization chosen.

Folder exists at given root path! All the contents of the folder will be deleted.

Enter 'Y' to continue or any other key to exit: y

Started processing for Acrobat \

Finished processing for Acrobat successfully

Processed 439 out of 439 items.

Error in 0 items.

AdobeUpdateServerSetupTool returned with code: 0.

Inspiring

You may find this thread useful.

Also:

Using the Adobe Update Server Setup Tool (AUSST)

Translate

Participant

Thanks for the infos but I dont think that will help me cause I allready checked thats stuff:

@Thread - Installing AUSST 4.0 on Win2012 R2 Server

The mime types are not our problem because we have no problem in open updaterfeed.xml

All files on the web server are accessible and all directory listings are working.

I assume that the mime types have nothing to do with 404 download errors generated by AUSST4?

Sad but true the files from the adobe server never hits our web server. Anyway I will check the Apache config for the mime types only to be sure.

@Thread Using the Adobe Update Server Tool (AUSST)

I already checked and used this document. After the problems started I also worked through the troubleshooting section

Any other hints why the AUSST generates so many 404 on the Adobe Server?

Next step for me will be a complete cross check on a fresh installed OSX 10.11.6 Server System with a fresh installed AUSST4.

I will keep you all informed ...

Best regards

Sebastian

Translate

swaadobeAuthorCorrect answer

Participant

Hello,

i`ve found the solution for our problem:

First I've uninstalled all CC-Programs
I've used AdobeCreativeCloudCleanerTool and cleaned everything he found
After that I' renamed the Adobe folder to Adobe.old in the system libary and the user libary aswellSystemwide: /Library/Application Support/Adobe
User: /Users/yourusername/Library/Application Support/Adobe
Checked the Application Dir that everything of the Adobe programs are gone espacially /Applications/Utilities/Adobe Application Manager
Made a restart
Made a fresh install of Adobe CCP from the Creative Cloud Deployment Tools I downloaded from the CC Team Webside
After that I started AUSST from Terminal and made a fresh sync with the Adobe Servers
That done the trick, as you see below ...

osxserver:AUSST administrator$ sudo ./AdobeUpdateServerSetupTool --root="/Library/Server/Web/Data/Sites/Default/adobe_repo/"

Password:

Choose one of the following options :

1. Fresh Synchronization.

2. Incremental Synchronization.

3. Generate Client Configuration XML.

4. Exit.

Your choice: 1

Fresh Synchronization chosen.

Folder exists at given root path! All the contents of the folder will be deleted.

Enter 'Y' to continue or any other key to exit: y

Started processing for Acrobat \

Finished processing for Acrobat successfully

Processed 439 out of 439 items.

Error in 0 items.

AdobeUpdateServerSetupTool returned with code: 0.

Translate