Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Thu, 29 Jun 2017 19:36:00 +0000 (UTC)
From: "Bernd Eckenfels (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.13083386.1498723886000.137543.1498764960277@Atlassian.JIRA>
In-Reply-To: <JIRA.13083386.1498723886000@Atlassian.JIRA>
References: <JIRA.13083386.1498723886000@Atlassian.JIRA> <JIRA.13083386.1498723886742@jira-lw-us.apache.org>
Subject: [jira] [Commented] (DAEMON-367) Windows service fails to start
 after Windows 10 Creators Update
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 29 Jun 2017 19:36:07 -0000


    [ https://issues.apache.org/jira/browse/DAEMON-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16068836#comment-16068836 ] 

Bernd Eckenfels commented on DAEMON-367:
----------------------------------------

Can you show us the command line you used to install the service or a dump of the Registry? What start time and ImageFile parameters do you have? What service user?

> Windows service fails to start after Windows 10 Creators Update
> ---------------------------------------------------------------
>
>                 Key: DAEMON-367
>                 URL: https://issues.apache.org/jira/browse/DAEMON-367
>             Project: Commons Daemon
>          Issue Type: Bug
>          Components: Procrun
>    Affects Versions: 1.0.15
>         Environment: Windows 10 Home and Pro after Creators Update. Windows version 10.0.15063 Build 15063
>            Reporter: Dave Bennett
>              Labels: prunsrv, windows10
>
> I have been running windows services via prunsrv for quite a long time without any problem. Since updating my PC (Windows 10 Home) recently with the Creators Update version of Windows 10 any new service that I install will not start. Similar services that were installed prior to the update work ok as before. When I try to start a new service, the system event log contains the message "The BSS2SRVB2 service terminated with the following service-specific error: Incorrect function". The service was initially configured with PR_LOGLEVEL set to "Error" and no log files were created. When I set the level to "Debug", the following log files were created,
> - stderrb2.txt contains,
> 2017-06-29 08:45:34 Commons Daemon procrun stderr initialized
> - stdoutb2.txt contains,
> 2017-06-29 08:45:34 Commons Daemon procrun stdout initialized
> - commons-daemon.2017-06-29.log contains,
> [2017-06-29 08:45:34] [debug] ( prunsrv.c:1679) [20104] Commons Daemon procrun log initialized
> [2017-06-29 08:45:34] [info]  ( prunsrv.c:1683) [20104] Commons Daemon procrun (1.0.15.0 32-bit) started
> [2017-06-29 08:45:34] [info]  ( prunsrv.c:1596) [20104] Running 'BSS2SRVB2' Service...
> [2017-06-29 08:45:34] [debug] ( prunsrv.c:1374) [19220] Inside ServiceMain...
> [2017-06-29 08:45:34] [debug] ( prunsrv.c:844 ) [19220] reportServiceStatusE: 2, 0, 3000, 0
> [2017-06-29 08:45:34] [info]  ( prunsrv.c:1127) [19220] Starting service...
> [2017-06-29 08:45:34] [error] ( prunsrv.c:1190) [19220] Missing service ImageFile
> [2017-06-29 08:45:34] [error] ( prunsrv.c:1536) [19220] ServiceStart returned 1
> [2017-06-29 08:45:34] [debug] ( prunsrv.c:844 ) [19220] reportServiceStatusE: 1, 1066, 0, 1
> [2017-06-29 08:45:34] [info]  ( prunsrv.c:1598) [20104] Run service finished.
> [2017-06-29 08:45:34] [info]  ( prunsrv.c:1764) [20104] Commons Daemon procrun finished
> The service processes have been written by myself in Java. 
> I have also seen the same problem on another PC (Windows 10 Pro) so this suggests that it is not specific to my PC.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)