Skip to main content
G
gskibum
Inspiring
July 31, 2026
Question

Error When Scheduling Runs of AdobeUpdateServerSetupTool. Folder already exists. Could not delete folder /Volumes/AUSST/ACC/services/ffc/icons/

  • July 31, 2026
  • 1 reply
  • 1 view

I've spun up an AUSST server on an Intel Mac.

How are ya'll scheduling your incremental runs? I am getting clobbered with scheduling the incremental runs. I can use the AdobeUpdateServerSetupTool tool successfully day in and day out with fresh and incremental runs manually executed with Terminal.app. It just works. Clients update against it perfectly too.

However, I am running into a problem when trying to schedule the incremental runs with a LaunchDaemon, crontab or Lingon. I get the following error:

7/29/26 21:36:18:766 | [INFO] |  | AAMEE | Utilities | AUSST |  |  | 1087475 | 0 | ************************* START Adobe Update Server Setup *************************
07/29/26 21:36:18:766 | [INFO] |  | AAMEE | Utilities | AUSST |  |  | 1087475 | 0 | Adobe Update Server Setup Version: 6.3.0.1
07/29/26 21:36:18:766 | [INFO] |  | AAMEE | Utilities | AUSST |  |  | 1087475 | 0 | Rootpath = /Volumes/MAMP-Sites/ausst.pretendco/AUSST
07/29/26 21:36:18:766 | [INFO] |  | AAMEE | Utilities | AUSST |  |  | 1087475 | 0 | Incremental is true.
07/29/26 21:36:18:853 | [INFO] |  | AAMEE | Utilities | AUSST |  |  | 1087475 | 0 | Starting HD Workflow
07/29/26 21:36:18:853 | [INFO] |  | AAMEE | Utilities | AUSST |  |  | 1087475 | 0 | Going to create download structure for HD
07/29/26 21:36:18:863 | [FATAL] |  | AAMEE | Utilities | AUSST |  |  | 1087475 | 0 | Folder already exists. Could not delete folder /Volumes/MAMP-Sites/ausst.pretendco/AUSST/ACC/services/ffc/icons/.
07/29/26 21:36:18:863 | [ERROR] |  | AAMEE | Utilities | AUSST |  |  | 1087475 | 0 | Failed to create directory structure
07/29/26 21:36:18:863 | [ERROR] |  | AAMEE | Utilities | AUSST |  |  | 1087475 | 0 | Failed in syncing latest updates for AUSST.
07/29/26 21:36:18:863 | [ERROR] |  | AAMEE | Utilities | AUSST |  |  | 1087475 | 0 | Internal error occured.
07/29/26 21:36:18:863 | [ERROR] |  | AAMEE | Utilities | AUSST |  |  | 1087475 | 0 | Failed while preparing jobs
07/29/26 21:36:18:863 | [INFO] |  | AAMEE | Utilities | AUSST |  |  | 1087475 | 0 | AdobeUpdateServerSetupTool Returned with code: 2.
07/29/26 21:36:18:864 | [INFO] |  | AAMEE | Utilities | AUSST |  |  | 1087475 | 0 | ************************* END Adobe Update Server Setup *************************

I’m doing a fresh run now and I deleted the logs so I don’t have the exact error at my fingertips, but when I renamed that ACC/services/ffc/icons/ directory before doing an --incremental run, it barked about not being able to create the directory. If requested I’ll do that directory rename test again when the fresh run completes.

    1 reply

    T
    Community Manager
    Tariq Ahmad DarCommunity Manager
    Community Manager
    July 31, 2026

    Hi ​@gskibum,

     

    Thank you for the detailed write-up and for sharing the logs.

    Based on the information you have provided, the FATAL error when running scheduled incremental syncs while manual runs work perfectly points to a permissions mismatch between the two execution contexts. When run manually AUSST executes under your logged-in user context which has full access to the AUSST root directory. When scheduled via LaunchDaemon, crontab or Lingon it runs under a different system context which may not have the same ownership or write permissions on the directory structure, preventing AUSST from deleting and recreating the icons folder during incremental sync.

    Based on this, please verify the following:

    • Confirm which user context your scheduled job is running under and ensure that account has full read/write ownership of the entire AUSST root path and all subdirectories: sudo chown -R [serviceaccount] /Volumes/MAMP-Sites/ausst.pretendco/AUSST/

    • If using a LaunchDaemon plist, confirm the UserName key matches the user who runs AUSST successfully when executed manually

    If the issue persists after addressing permissions, please run a one-time fresh sync to rebuild the directory structure cleanly before resuming scheduled incremental runs.

     

    Please let us know how it goes and we will be happy to assist further.
     

    ~Tariq

    Firefly Community Gallery
    Adobe Firefly

    Remix with Firefly Community Gallery

    Thousands of free creations to fall in love with and remix in Firefly.

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