[
https://issues.apache.org/jira/browse/DAEMON-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16956037#comment-16956037
]
Gary D. Gregory commented on DAEMON-409:
----------------------------------------
No progress from me, no time sadly. On your end, I encourage you to get some
kind of stack trace _if possible_ to see who called who called who to get to
root of the issue. OTOH, if this whole issue is reproducible from the
information you gave for Tomcat, then someone should be able to reproduce it,
assuming this is not dependent on a specific OS version, which it very well may
be. I still encourage you to reproduce this and capture a stack trace, this may
involve catching the fault in a debugger.
> Faulting application name: prunsrv.exe crashes on Windows 10
> ------------------------------------------------------------
>
> Key: DAEMON-409
> URL: https://issues.apache.org/jira/browse/DAEMON-409
> Project: Commons Daemon
> Issue Type: Bug
> Components: Procrun
> Affects Versions: 1.1.0
> Environment: Upgraded Windows 2016 to Windows 2019
> Reporter: Manju
> Priority: Critical
> Attachments: SCVMMAddInServer.2019-10-09.log
>
>
> When attempting to start the Service it crashes on startup and provides this
> entry in the Windows application log:
> Faulting application name: prunsrv.exe, version: 1.1.0.0, time stamp:
> 0x5a022d06
> Faulting module name: ntdll.dll, version: 10.0.17763.719, time stamp:
> 0x6071cf9dException code: 0xc0000005
> Fault offset: 0x000465b8
> Faulting process id: 0x22b0
> Faulting application start time: 0x01d5636553896926
> Faulting application path: <..>\prunsrv.exe
> Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
> Report Id: ba99f326-ea99-4272-b388-cd1b9e9f1cea
> Faulting package full name:
> Faulting package-relative application ID:
--
This message was sent by Atlassian Jira
(v8.3.4#803005)