[
https://issues.apache.org/jira/browse/DAEMON-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17516140#comment-17516140
]
Brian Andle edited comment on DAEMON-441 at 4/1/22 9:38 PM:
------------------------------------------------------------
And from what I can tell the OS is blocking the attempt (killing the
application) before the logging can occur to indicate what the issue is.
was (Author: JIRAUSER287474):
And from what I can tell the OS is blocking the attempt (killing the
application) before the logging can occur to indicate what the issue is.
Windows 10 still throws an error regardless, but my concern is around server
> When installing a Windows service using Commons Daemon 1.3.0 the errorlevel
> is -1073741819
> ------------------------------------------------------------------------------------------
>
> Key: DAEMON-441
> URL: https://issues.apache.org/jira/browse/DAEMON-441
> Project: Commons Daemon
> Issue Type: Bug
> Affects Versions: 1.3.0
> Environment: Windows 2016 Datacenter
> Reporter: Brian Andle
> Priority: Major
> Attachments: Command_Prompt.png
>
>
> When attempting to use prunsrv.exe on Windows 2016 to create a service a
> Windows Event error is logged and the errorlevel is returned as -1073741819
> Running the following command:
> {code:java}
> prunsrv.exe //IS/MyService --Startup=auto --Description=My Service
> --DisplayName=My Service {code}
> Results in the following Windows Event Log entry
>
> {code:java}
> Faulting application name: prunsrv.exe, version: 1.3.0.0, time stamp:
> 0x622b3ac0
> Faulting module name: prunsrv.exe, version: 1.3.0.0, time stamp: 0x622b3ac0
> Exception code: 0xc0000005
> Fault offset: 0x0000000000006e70
> Faulting process id: 0x1d88
> Faulting application start time: 0x01d845f90eb4351a
> Faulting application path: C:\myfolder\prunsrv.exe
> Faulting module path: C:\myfolder\prunsrv.exe
> Report Id: 409b7098-42bd-4036-aa61-b19eecdb1bd7
> Faulting package full name:
> Faulting package-relative application ID: {code}
> Doing an echo %errorlevel% shows -1073741819 instead of the expected 0
> On Windows 10 an Access Is Denied error is returned
> Version 1.2.4.0 works correctly on both Windows 10 and 2016
> *NOTE:* The service does appear to actually install on 2016, however most
> deploy scripts will expect an error level of 0 and will fail if a non 0 value
> it returned.
> h3. Workaround
> Define a --LogPath value and
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
