Wildfly 8.2.0 Final Windows service not starting

[sakbar]

Hello all!

Wildfly 8.2.0 Final standalone.bat runs without problems, but the installed Windows service does not start. It is installed as "wildfly-service.exe" //RS//Wildfly.

Error message (Windows event protocol) only says: "Unzulässige Funktion" / "Incorrect function".

What might be the reason?

Thanks in advance.

[lafr]

The user calling standalone.bat from cmd.exe and the user account for the service are the same?

[sakbar]

I have tried to start the service with system account as well as as administrator. same error in both cases. But standalone.bat can be run as administrator.

[nickarls]

Can you output any console/service/boot log?

[sakbar]

Where can a find or how can I generate a log file? As already mentioned, the Windows system protocol only says "Incorrect function".

[nickarls]

Check if there are anything in the log or bin directories (console, boot, stdout logs etc). I'm interested to know if it has time to write anything or is it the binary itself that doesn't run.

[sakbar]

I've only found a server.log in the directory .\standalone\log\. But this file only contains log data from standalone.bat. The Windows service obviously doesn't find the time to log anything.

[lafr]

We had the same problem some weeks ago when installing WildFly 8.1 on a Windows 2012R2 server.

I remember my colleague and I spent some hours to find the cause.

But we both are not 100% sure which customer it was and the exact reasons.

But we think it was at a customer where the they had a Domain\User and Server\User. So the the same login name as Windows-Domain-User as well as local server user.

Wildfly software and service installed as Domain\User. Starting the wildfly server from cmd.exe as user Domain\User worked just fine.

But service was installed to run as local user User and therefore the service did not start.

[sakbar]

Thanks, Frank. But in my case it must be another reason. I've tried it with exactly the same user, but no chance to get it working.

[sanjay05222]

Syed Akbar wrote:

Thanks, Frank. But in my case it must be another reason. I've tried it with exactly the same user, but no chance to get it working.

Have you tired already existing out of the box way of running the wildfly as service ? in the bin folder there is folder init.d and one more one is for linux and other is for Windows have you tried that ?

Please let me know just incase you are using the same service and it is not working ,

thanks

Sanjay Gautam

[sakbar]

SANJAY GAUTAM schrieb:

Syed Akbar wrote:

Thanks, Frank. But in my case it must be another reason. I've tried it with exactly the same user, but no chance to get it working.

Have you tired already existing out of the box way of running the wildfly as service ? in the bin folder there is folder init.d and one more one is for linux and other is for Windows have you tried that ?

Please let me know just incase you are using the same service and it is not working ,

thanks

Sanjay Gautam

Hi Sanjay, sorry but I don't understand what you want me to try out. I have installed the service with .\bin\service\service.bat install. I also tried to install it manually, but makes no difference.

[sakbar]

Nicklas Karlsson schrieb:

Check if there are anything in the log or bin directories (console, boot, stdout logs etc). I'm interested to know if it has time to write anything or is it the binary itself that doesn't run.

I've found a log file with following content:

[2015-03-21 10:58:54] [info]  [ 2180] Running 'Wildfly' Service...

[2015-03-21 10:58:54] [info]  [ 2492] Starting service...

[2015-03-21 10:58:54] [error] [ 2492] Missing service ImageFile

[2015-03-21 10:58:54] [error] [ 2492] ServiceStart returned 1

[2015-03-21 10:59:33] [info]  [ 2180] Run service finished.

[2015-03-21 10:59:33] [info]  [ 2180] Commons Daemon procrun finished

So obviously an ImageFile is missing. But don't know how to fix this.

[sakbar]

Okay, finally got it working. The service.bat file only works properly, when the Wildfly path doesn't contain any white spaces. By trying to fix this, I messed service.bat file up a little bit. I added some quotation marks, which finally lead to a corrupt installation command.