Description of problem: When using "service.bat install /serviceuser ..." command to install window service, if the account name behind /serviceuser has a whit space inside like ".\JBoss User", it will failed to install windows service. Version-Release number of selected component (if applicable): JBoss Enterprise Application Platform 6.4.0 How reproducible: We can reproduce this issue. Steps to Reproduce: 1. Install EAP6.4.0 on Windows7 which has a username with a white space inside like "JBoss User". 2. According to "https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Installation_Guide/Install_JBoss_Enterprise_Application_Platform_6_Microsoft_Windows_Service.html" to do the preparation. 3. Run command: service.bat install /serviceuser ".\JBoss User" /servicepass "changeit" /startup /debug Actual results: A new service is added on windows with below attributes: Name | Description | Status | Startup Type | Log On As JBossEAP6 | | | Manual | Local System When starting it, an error window poped up: ~~~ Windows could not start the JBossEAP6 on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code1. ~~~ Expected results: A new service is added on windows with below attributes: Name | JBossEAP6 Description | JBoss Enterprise Application Platform6 Status | Started Startup Type | Automatic Log On As | .\JBoss User And it can be started/stopped successfully. Additional info: The workaround is editing "service.bat" and add double quotation marks on %SERVICE_USER% at line 430th: From ~~~ set RUNAS=--ServiceUser=%SERVICE_USER% --ServicePassword=%SERVICE_PASS% ~~~ to ~~~ set RUNAS=--ServiceUser="%SERVICE_USER%" --ServicePassword=%SERVICE_PASS% ~~~ The debug log is changed from: ~~~ ... install JBossEAP6 --ServiceUser=.\JBoss User ... ~~~ to ~~~ ... install JBossEAP6 --ServiceUser=".\JBoss User" ... ~~~
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
both WFLY-7380 and JBEAP-6622 are closed/verified for EAP7, I suggest closing this one too.
Closing, deferred. This is minor and there is a workaround listed here https://access.redhat.com/solutions/1447153 , the issue is resolved in EAP 7.1 JBEAP-6622