Expand my Community achievements bar.

SOLVED

Configuration issue with AEM 6.4 on Windows Server 2019

Avatar

Level 1

Hi folks, I'm attempting to install AEM 6.4 on a new Windows 2019 server.  The installation appears to go fine, but when I run the Config Manager, it stops on an error during the Express setup.  Any ideas? 

I'm running Java 1.8 

 

 

 

daPoppa_0-1722016726820.png

 

[2024-07-26 10:17:54,132], INFO, Thread-7, com.adobe.livecycle.lcm.feature.expressTurnkey.ExpressModeDialog,      Sub Task Progress: [5%, Verifying JBOSS_FOR_ADOBE_EXPERIENCE_MANAGER_FORMS_6.4 service is installed]
[2024-07-26 10:17:54,132], INFO, Thread-7, com.adobe.livecycle.lcm.util.process.ProcessExecutor, Running: sc query "JBOSS_FOR_ADOBE_EXPERIENCE_MANAGER_FORMS_6.4"
[2024-07-26 10:17:54,213], INFO, Thread-7, com.adobe.livecycle.lcm.util.process.ProcessExecutor, Return value: 1060
[2024-07-26 10:17:54,213], INFO, Thread-7, com.adobe.livecycle.lcm.util.ServiceUtils, State: -2,The specified service does not exist as an installed service
[2024-07-26 10:17:54,213], INFO, Thread-7, com.adobe.livecycle.lcm.util.ServiceUtils, Service 'JBOSS_FOR_ADOBE_EXPERIENCE_MANAGER_FORMS_6.4' exists: false

 

1 Accepted Solution

Avatar

Correct answer by
Level 1

Thanks.  Turns out that I had installed a version of Java that was too new - had to roll it back to a previous version before the configuration manager would run properly. 

cheers!

 

View solution in original post

2 Replies

Avatar

Employee

Hi @daPoppa ,

Seems like an installation issue rather than Configuration Manager issue.

Please confirm if Windows Service is actually created, if not check below things -

  1. If installation was performed in admin mode.
  2. If UAC settings was set to minimum.
  3. Check install.log file for any issue, default path is <AEM_Forms_Installation_Folder>\log\install.log.
  4. Check "createJBossService.log" file, for any issue during JBoss service creation, available at <AEM_Forms_Installation_Folder>\log\createJBossService.log

Avatar

Correct answer by
Level 1

Thanks.  Turns out that I had installed a version of Java that was too new - had to roll it back to a previous version before the configuration manager would run properly. 

cheers!