commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Bennett (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DAEMON-367) Windows service fails to start after Windows 10 Creators Update
Date Sun, 09 Jul 2017 08:53:00 GMT

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

Dave Bennett commented on DAEMON-367:
-------------------------------------

I found what the problem was, eventually. After performing the windows update, the new service
was installed via a command prompt that was NOT in administrator mode. When repeated in admin
mode, the service started successfully.

Prior to the windows update, I always opened the command prompt via the File Explorer, ie.
from the 'Open Command Prompt as Administrator' on the File menu. After the update, the Command
Prompt options have disappeared and replaced by the equivalent Powershell options. I used
another way to open the Command Prompt (entering 'cmd' in the search box) but I hadn't realised
that it wasn't opened in admin mode. Interestingly, if you right-click on the Command Prompt
option that shows and select 'Run as Adminitrator' nothing happens. The only way that I found
to run the Command Propmpt in admin mode was via CTL+ALT+DEL, select Task Manager, select
'File', select 'run new task', enter 'cmd', tick 'create this task with administrative privileges'.

> 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)

Mime
View raw message