[
https://issues.jboss.org/browse/WFCORE-1379?page=com.atlassian.jira.plugi...
]
Jay Rostosky commented on WFCORE-1379:
--------------------------------------
Still doesn't work, sorry. I grabbed service.bat from GitHub link, replacing original
one, then copied service directory to bin. It needs to be in bin. Fails.
Then I grabbed *all* the service-related files from GitHub, just to be safe (in case any
of the exes had changed) - still fails. See details below.
Service installs fine - or appears to...
Tried running command prompt as Administrator - no luck.
Tried all of:
Windows Service Controller UI
Windows "sc start" command
Our script's "service start" command
None work.
When attempted via Windows Service Controller UI: The Wildfly service terminated with
service-specific error code 1.
When attempted via "service start" (even as Administrator):
The data area passed to a system call is too small.
Failed to start serviceService Wildfly starting...
ERROR: Failed to load service Wildfly configuration
Event Log: The Wildfly service terminated with service-specific error Incorrect
function..
service.bat points user to wrong directory
------------------------------------------
Key: WFCORE-1379
URL:
https://issues.jboss.org/browse/WFCORE-1379
Project: WildFly Core
Issue Type: Bug
Components: Scripts
Affects Versions: 2.0.10.Final
Reporter: Nicklas Karlsson
Assignee: Tomaz Cerar
Priority: Trivial
Fix For: 2.2.0.CR1, 3.0.0.Alpha1
Running service.bat from the docs/contrib/scripts/service dir tells user to run the
script under bin/service*s* but the binary paths to the services expects bin/service,
resulting in service install failure with file not found
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)