Skip to main content
Level 1
Aug 26, 2026 3:12 PM UTC
Question

Repository Modernizer - AEM Dispatcher Converter

Hi All,

 

Getting the below issue - 

C:\Users\admin\AppData\Local\@adobe\aio-cli>aio aem-migration:dispatcher-converter -t=ams

********** Executing Dispatcher Converter **********
Converting Dispatcher Configurations...
Found usage of undefined variable:
target/dispatcher/src/conf.d/available_vhosts/aem_publish.vhost:${PUBLISH_DEFAULT_HOSTNAME}

Apache configuration uses non-whitelisted directives:
target/dispatcher/src/conf.d/available_vhosts/aem_publish.vhost:63 LogLevel
target/dispatcher/src/conf.d/available_vhosts/projA_publish.vhost:63 LogLevel
target/dispatcher/src/conf.d/available_vhosts/projB_portal_publish.vhost:64 LogLevel
target/dispatcher/src/conf.d/available_vhosts/projB_publish.vhost:63 LogLevel
target/dispatcher/src/conf.d/available_vhosts/projC_publish.vhost:63 LogLevel
target/dispatcher/src/conf.d/available_vhosts/brandD_publish.vhost:63 LogLevel
target/dispatcher/src/conf.d/available_vhosts/brandE_publish.vhost:63 LogLevel
target/dispatcher/src/conf.d/available_vhosts/brandF_publish.vhost:63 LogLevel
target/dispatcher/src/conf.d/available_vhosts/brandG_publish.vhost:65 LogLevel
FileOperationsUtility: Commented out all usages of non-whitelisted directives listed above.
Error: EEXIST: file already exists, mkdir 'C:\Users\admin\AppData\Local\@adobe\aio-cli\target\dispatcher\src\conf.dispatcher.d\enabled_farms'
Code: EEXIST

So it does create symlinks in enabled_farms but not sure why the error keeps coming up.

Any input on this?

5 replies

Level 2
Sep 5, 2026 12:46 PM UTC

Hi ​@EPAMerG ,

Have you deleted the target folder? Try deleting it and then re run the cmd aio aem-migration:dispatcher-converter -t=ams.

For more troubleshooting, you can refer here: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/content-delivery/validation-debug

Translate
EPAMerGAuthor
Level 1
Sep 7, 2026 3:22 PM UTC

I did, but no luck! Same output!

Translate
Jineet_Vora
Adobe Champion and Community Advisor
Adobe Champion and Community Advisor
Sep 13, 2026 7:33 PM UTC

​@EPAMerG - looks like this is a known open issue as mentioned here https://github.com/adobe/aio-cli-plugin-aem-cloud-service-migration/issues/23 

Also, looks like the converter copies your SDK’s src into target/dispatcher/src. Your AMS source config has an enabled_farms too and that gets copied in as well, so by the time it tries to create that folder it’s already there.

Can you try to empty enabled_farms and enabled_vhosts in your SDK's src folder before pointing sdkSrc at it.

Translate
A_H_M_Imrul
Community Advisor
Community Advisor
Sep 15, 2026 4:43 PM UTC

Hello ​@EPAMerG 

I would handle the issues in this order:

  1. Delete target/
  2. Run the converter again.
  3. Check whether PUBLISH_DEFAULT_HOSTNAME is still reported.
  4. If yes, fix that variable in the source dispatcher configuration.
  5. Review the generated configuration before using it for AEM as a Cloud Service / SDK deployment.

The EEXIST error itself is not an Apache/Dispatcher configuration problem; it's a local filesystem/generated-output issue.

Translate
Level 2
Oct 27, 2026 7:37 AM UTC

One more thing to check once the EEXIST error is cleared: run the Dispatcher validator from the AEM SDK on the converted output locally before pushing. The converter output often still contains rules the Cloud Manager pipeline rejects, such as directives that aren’t on the allow list or custom log levels. Fixing these locally saves a lot of pipeline round trips.

Translate