You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Mark Thomas (Jira)" <ji...@apache.org> on 2019/09/25 11:31:00 UTC

[jira] [Commented] (DAEMON-408) PROCRUN 1.2.x x64 crash on Windows Server 2008 R2

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

Mark Thomas commented on DAEMON-408:
------------------------------------

This looks to be the same as [https://bz.apache.org/bugzilla/show_bug.cgi?id=63767]

The workaround is to install all currently available updates in Windows Update. Or at least one that results in the UCRT being installed.

I have a fix that I'll apply shortly.

> PROCRUN 1.2.x x64 crash on Windows Server 2008 R2
> -------------------------------------------------
>
>                 Key: DAEMON-408
>                 URL: https://issues.apache.org/jira/browse/DAEMON-408
>             Project: Commons Daemon
>          Issue Type: Bug
>          Components: Procrun
>    Affects Versions: 1.2.0, 1.2.1
>            Reporter: Simon Wimmesberger
>            Priority: Major
>
> Since procrun version 1.2.0 the application crashes when executed on Windows Server 2008 R2:
>  Problemsignatur:
> Problem Event Name: BEX64  
>  Application Name: procrun.exe  
>  Application Version: 1.2.1.0  
>  Application Timestamp: 5d6fdd78  
> Fault Module Name: StackHash_25f1  
> Fault Module Version: 0.0.0.0  
> Fault Module Timestamp: 00000000  
> Exception Offset: 00000000004f8aa2  
> Exception Code: c0000005  
> Exception Data: 0000000000000008  
>  OS Version: 6.1.7600.2.0.0.1296.17  
>  Additional Information 1: 25f1  
>  Additional Information 2: 25f1bf9a72a93f5658ee9429e86c7409  
>  Additional Information 3: f2ca  
>  Additional Information 4: f2ca14b6934ede5b7e664f76bc87ba68
>  
> I also have a crash dump available but for security/sensitive reasons I will only provide it privately when necessary.
>  
> With version 1.1.0 I can't reproduce the issue.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)