WPF application crashing on Windows Server 2008
I received an error report regarding a WPF app that wouldn't start up in a Windows Server 2008 Service pack 2 server (the application is an administration tool we're distributing to our customers). Since this application has a lot of external references, I tried to simplify the problem by creating a simple WPF application using Visual Studio 2013: a plain white window with "hello world" showing and nothing more. I tried to make it run in the production server, with no luck: it always crashes immediately.
Here's what I have:
- the application was created with the standard VS 2013 template for WPF, so it had 3.5 as the target framework; i changed it to 4.6
- the server has the 3.5 SP1 and 4.6 versions of the .net framework installed
- the app.config is well-formed, with the
configSectionssection on top, no additional references besides log4net,supportedRuntimetag set according to the target framework version - I already checked that there are no project references from version 3.5 left in the project
- I already tried logging in the
DispatcherUnhandledExceptionand in theAppDomain.UnhandledExceptionhandlers - the application runs in my development environment
- the application runs in production environment only if I change the target framework to 3.5. In this case, the WPF windows shows up and the log file is correctly produced
- I already tried producing a dump and trying to debug it in Visual Studio: I just get a "Source not available" message and a stack trace ending with ntdll.dll!NtWaitForSingleObject()
Here are the error details:
Description:
Stopped working
Problem signature:
Problem Event Name: APPCRASH
Application Name: MyApp.exe
Application Version: 1.0.0.0
Application Timestamp: 5bfc07f1
Fault Module Name: KERNEL32.dll
Fault Module Version: 6.0.6002.24367
Fault Module Timestamp: 5ae3dcd9
Exception Code: e0434352
Exception Offset: 000000000001667d
OS Version: 6.0.6002.2.2.0.272.7
Locale ID: 1033
The Windows event log shows little information:
Faulting application MyApp.exe, version 1.0.0.0, time stamp 0x5bfc07f1, faulting module KERNEL32.dll, version 6.0.6002.24367, time stamp 0x5ae3dcd9, exception code 0xe0434352, fault offset 0x000000000001667d, process id 0x%9, application start time 0x%10.
Application: MyApp.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code e0434352, exception address 0000000077A6667D
Stack: [this is empty]
Any suggestions?
c# .net wpf windows
asked Nov 26 '18 at 15:48
Sue MaurizioSue Maurizio
421613
|
show 12 more comments
I received an error report regarding a WPF app that wouldn't start up in a Windows Server 2008 Service pack 2 server (the application is an administration tool we're distributing to our customers). Since this application has a lot of external references, I tried to simplify the problem by creating a simple WPF application using Visual Studio 2013: a plain white window with "hello world" showing and nothing more. I tried to make it run in the production server, with no luck: it always crashes immediately.
Here's what I have:
- the application was created with the standard VS 2013 template for WPF, so it had 3.5 as the target framework; i changed it to 4.6
- the server has the 3.5 SP1 and 4.6 versions of the .net framework installed
- the app.config is well-formed, with the
configSectionssection on top, no additional references besides log4net,supportedRuntimetag set according to the target framework version - I already checked that there are no project references from version 3.5 left in the project
- I already tried logging in the
DispatcherUnhandledExceptionand in theAppDomain.UnhandledExceptionhandlers - the application runs in my development environment
- the application runs in production environment only if I change the target framework to 3.5. In this case, the WPF windows shows up and the log file is correctly produced
- I already tried producing a dump and trying to debug it in Visual Studio: I just get a "Source not available" message and a stack trace ending with ntdll.dll!NtWaitForSingleObject()
Here are the error details:
Description:
Stopped working
Problem signature:
Problem Event Name: APPCRASH
Application Name: MyApp.exe
Application Version: 1.0.0.0
Application Timestamp: 5bfc07f1
Fault Module Name: KERNEL32.dll
Fault Module Version: 6.0.6002.24367
Fault Module Timestamp: 5ae3dcd9
Exception Code: e0434352
Exception Offset: 000000000001667d
OS Version: 6.0.6002.2.2.0.272.7
Locale ID: 1033
The Windows event log shows little information:
Faulting application MyApp.exe, version 1.0.0.0, time stamp 0x5bfc07f1, faulting module KERNEL32.dll, version 6.0.6002.24367, time stamp 0x5ae3dcd9, exception code 0xe0434352, fault offset 0x000000000001667d, process id 0x%9, application start time 0x%10.
Application: MyApp.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code e0434352, exception address 0000000077A6667D
Stack: [this is empty]
Any suggestions?
c# .net wpf windows
asked Nov 26 '18 at 15:48
Sue MaurizioSue Maurizio
421613
Does it work withoutlog4net?
– Rekshino
Nov 26 '18 at 15:58
With as little information as you have, I suspect that the only people who might help you work for Microsoft. Consider opening a support case (particularly if you have Premier Support)
– Flydog57
Nov 26 '18 at 15:59
1
0xe0434352 is a .NET exception. Load the crash dump in WinDbg, load the SOS extension and use!peit should give you the exception and a call stack. Or load the crash dump in Visual Studio and choose managed debugging.
– Thomas Weller
Nov 26 '18 at 16:03
@Rekshino it crashes with or without log4net
– Sue Maurizio
Nov 26 '18 at 16:06
1
It's likely a missing dependency. Perhaps something installed on Windows that's missing on Windows Server. You could use Dependency Walker to make sure it can find all the required DLLs. There is also a similar post on SO stackoverflow.com/questions/6244939/…
– bwing
Nov 26 '18 at 16:14
|
show 12 more comments
I received an error report regarding a WPF app that wouldn't start up in a Windows Server 2008 Service pack 2 server (the application is an administration tool we're distributing to our customers). Since this application has a lot of external references, I tried to simplify the problem by creating a simple WPF application using Visual Studio 2013: a plain white window with "hello world" showing and nothing more. I tried to make it run in the production server, with no luck: it always crashes immediately.
Here's what I have:
- the application was created with the standard VS 2013 template for WPF, so it had 3.5 as the target framework; i changed it to 4.6
- the server has the 3.5 SP1 and 4.6 versions of the .net framework installed
- the app.config is well-formed, with the
configSectionssection on top, no additional references besides log4net,supportedRuntimetag set according to the target framework version - I already checked that there are no project references from version 3.5 left in the project
- I already tried logging in the
DispatcherUnhandledExceptionand in theAppDomain.UnhandledExceptionhandlers - the application runs in my development environment
- the application runs in production environment only if I change the target framework to 3.5. In this case, the WPF windows shows up and the log file is correctly produced
- I already tried producing a dump and trying to debug it in Visual Studio: I just get a "Source not available" message and a stack trace ending with ntdll.dll!NtWaitForSingleObject()
Here are the error details:
Description:
Stopped working
Problem signature:
Problem Event Name: APPCRASH
Application Name: MyApp.exe
Application Version: 1.0.0.0
Application Timestamp: 5bfc07f1
Fault Module Name: KERNEL32.dll
Fault Module Version: 6.0.6002.24367
Fault Module Timestamp: 5ae3dcd9
Exception Code: e0434352
Exception Offset: 000000000001667d
OS Version: 6.0.6002.2.2.0.272.7
Locale ID: 1033
The Windows event log shows little information:
Faulting application MyApp.exe, version 1.0.0.0, time stamp 0x5bfc07f1, faulting module KERNEL32.dll, version 6.0.6002.24367, time stamp 0x5ae3dcd9, exception code 0xe0434352, fault offset 0x000000000001667d, process id 0x%9, application start time 0x%10.
Application: MyApp.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code e0434352, exception address 0000000077A6667D
Stack: [this is empty]
Any suggestions?
c# .net wpf windows
asked Nov 26 '18 at 15:48
Sue MaurizioSue Maurizio
421613
I received an error report regarding a WPF app that wouldn't start up in a Windows Server 2008 Service pack 2 server (the application is an administration tool we're distributing to our customers). Since this application has a lot of external references, I tried to simplify the problem by creating a simple WPF application using Visual Studio 2013: a plain white window with "hello world" showing and nothing more. I tried to make it run in the production server, with no luck: it always crashes immediately.
Here's what I have:
- the application was created with the standard VS 2013 template for WPF, so it had 3.5 as the target framework; i changed it to 4.6
- the server has the 3.5 SP1 and 4.6 versions of the .net framework installed
- the app.config is well-formed, with the
configSectionssection on top, no additional references besides log4net,supportedRuntimetag set according to the target framework version - I already checked that there are no project references from version 3.5 left in the project
- I already tried logging in the
DispatcherUnhandledExceptionand in theAppDomain.UnhandledExceptionhandlers - the application runs in my development environment
- the application runs in production environment only if I change the target framework to 3.5. In this case, the WPF windows shows up and the log file is correctly produced
- I already tried producing a dump and trying to debug it in Visual Studio: I just get a "Source not available" message and a stack trace ending with ntdll.dll!NtWaitForSingleObject()
Here are the error details:
Description:
Stopped working
Problem signature:
Problem Event Name: APPCRASH
Application Name: MyApp.exe
Application Version: 1.0.0.0
Application Timestamp: 5bfc07f1
Fault Module Name: KERNEL32.dll
Fault Module Version: 6.0.6002.24367
Fault Module Timestamp: 5ae3dcd9
Exception Code: e0434352
Exception Offset: 000000000001667d
OS Version: 6.0.6002.2.2.0.272.7
Locale ID: 1033
The Windows event log shows little information:
Faulting application MyApp.exe, version 1.0.0.0, time stamp 0x5bfc07f1, faulting module KERNEL32.dll, version 6.0.6002.24367, time stamp 0x5ae3dcd9, exception code 0xe0434352, fault offset 0x000000000001667d, process id 0x%9, application start time 0x%10.
Application: MyApp.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code e0434352, exception address 0000000077A6667D
Stack: [this is empty]
Any suggestions?
c# .net wpf windows
c# .net wpf windows
asked Nov 26 '18 at 15:48
Sue MaurizioSue Maurizio
421613
asked Nov 26 '18 at 15:48
Sue MaurizioSue Maurizio
421613
edited Nov 26 '18 at 15:56
Sue Maurizio
asked Nov 26 '18 at 15:48
Sue MaurizioSue Maurizio
421613
asked Nov 26 '18 at 15:48
Sue MaurizioSue Maurizio
421613
asked Nov 26 '18 at 15:48
Sue MaurizioSue Maurizio
421613
421613
Does it work withoutlog4net?
– Rekshino
Nov 26 '18 at 15:58
With as little information as you have, I suspect that the only people who might help you work for Microsoft. Consider opening a support case (particularly if you have Premier Support)
– Flydog57
Nov 26 '18 at 15:59
1
0xe0434352 is a .NET exception. Load the crash dump in WinDbg, load the SOS extension and use!peit should give you the exception and a call stack. Or load the crash dump in Visual Studio and choose managed debugging.
– Thomas Weller
Nov 26 '18 at 16:03
@Rekshino it crashes with or without log4net
– Sue Maurizio
Nov 26 '18 at 16:06
1
It's likely a missing dependency. Perhaps something installed on Windows that's missing on Windows Server. You could use Dependency Walker to make sure it can find all the required DLLs. There is also a similar post on SO stackoverflow.com/questions/6244939/…
– bwing
Nov 26 '18 at 16:14
|
show 12 more comments
Does it work withoutlog4net?
– Rekshino
Nov 26 '18 at 15:58
With as little information as you have, I suspect that the only people who might help you work for Microsoft. Consider opening a support case (particularly if you have Premier Support)
– Flydog57
Nov 26 '18 at 15:59
1
0xe0434352 is a .NET exception. Load the crash dump in WinDbg, load the SOS extension and use!peit should give you the exception and a call stack. Or load the crash dump in Visual Studio and choose managed debugging.
– Thomas Weller
Nov 26 '18 at 16:03
@Rekshino it crashes with or without log4net
– Sue Maurizio
Nov 26 '18 at 16:06
1
It's likely a missing dependency. Perhaps something installed on Windows that's missing on Windows Server. You could use Dependency Walker to make sure it can find all the required DLLs. There is also a similar post on SO stackoverflow.com/questions/6244939/…
– bwing
Nov 26 '18 at 16:14
Does it work without
log4net ?– Rekshino
Nov 26 '18 at 15:58
Does it work without
log4net ?– Rekshino
Nov 26 '18 at 15:58
With as little information as you have, I suspect that the only people who might help you work for Microsoft. Consider opening a support case (particularly if you have Premier Support)
– Flydog57
Nov 26 '18 at 15:59
With as little information as you have, I suspect that the only people who might help you work for Microsoft. Consider opening a support case (particularly if you have Premier Support)
– Flydog57
Nov 26 '18 at 15:59
1
1
0xe0434352 is a .NET exception. Load the crash dump in WinDbg, load the SOS extension and use
!pe it should give you the exception and a call stack. Or load the crash dump in Visual Studio and choose managed debugging.– Thomas Weller
Nov 26 '18 at 16:03
0xe0434352 is a .NET exception. Load the crash dump in WinDbg, load the SOS extension and use
!pe it should give you the exception and a call stack. Or load the crash dump in Visual Studio and choose managed debugging.– Thomas Weller
Nov 26 '18 at 16:03
@Rekshino it crashes with or without log4net
– Sue Maurizio
Nov 26 '18 at 16:06
@Rekshino it crashes with or without log4net
– Sue Maurizio
Nov 26 '18 at 16:06
1
1
It's likely a missing dependency. Perhaps something installed on Windows that's missing on Windows Server. You could use Dependency Walker to make sure it can find all the required DLLs. There is also a similar post on SO stackoverflow.com/questions/6244939/…
– bwing
Nov 26 '18 at 16:14
It's likely a missing dependency. Perhaps something installed on Windows that's missing on Windows Server. You could use Dependency Walker to make sure it can find all the required DLLs. There is also a similar post on SO stackoverflow.com/questions/6244939/…
– bwing
Nov 26 '18 at 16:14
|
show 12 more comments
1 Answer
1
active
oldest
votes
Just in case someone else stumbles on the same problem, looks like the KB4457921 update from Microsoft somehow solves the issue. If an update is not possible, consider porting the code back to .net framework v. 3.5.
answered Nov 28 '18 at 7:35
Sue MaurizioSue Maurizio
421613
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53484687%2fwpf-application-crashing-on-windows-server-2008%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Just in case someone else stumbles on the same problem, looks like the KB4457921 update from Microsoft somehow solves the issue. If an update is not possible, consider porting the code back to .net framework v. 3.5.
answered Nov 28 '18 at 7:35
Sue MaurizioSue Maurizio
421613
add a comment |
Just in case someone else stumbles on the same problem, looks like the KB4457921 update from Microsoft somehow solves the issue. If an update is not possible, consider porting the code back to .net framework v. 3.5.
answered Nov 28 '18 at 7:35
Sue MaurizioSue Maurizio
421613
add a comment |
Just in case someone else stumbles on the same problem, looks like the KB4457921 update from Microsoft somehow solves the issue. If an update is not possible, consider porting the code back to .net framework v. 3.5.
answered Nov 28 '18 at 7:35
Sue MaurizioSue Maurizio
421613
Just in case someone else stumbles on the same problem, looks like the KB4457921 update from Microsoft somehow solves the issue. If an update is not possible, consider porting the code back to .net framework v. 3.5.
answered Nov 28 '18 at 7:35
Sue MaurizioSue Maurizio
421613
edited Nov 30 '18 at 8:36
answered Nov 28 '18 at 7:35
Sue MaurizioSue Maurizio
421613
answered Nov 28 '18 at 7:35
Sue MaurizioSue Maurizio
421613
answered Nov 28 '18 at 7:35
Sue MaurizioSue Maurizio
421613
421613
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53484687%2fwpf-application-crashing-on-windows-server-2008%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Does it work without
log4net?– Rekshino
Nov 26 '18 at 15:58
With as little information as you have, I suspect that the only people who might help you work for Microsoft. Consider opening a support case (particularly if you have Premier Support)
– Flydog57
Nov 26 '18 at 15:59
1
0xe0434352 is a .NET exception. Load the crash dump in WinDbg, load the SOS extension and use
!peit should give you the exception and a call stack. Or load the crash dump in Visual Studio and choose managed debugging.– Thomas Weller
Nov 26 '18 at 16:03
@Rekshino it crashes with or without log4net
– Sue Maurizio
Nov 26 '18 at 16:06
1
It's likely a missing dependency. Perhaps something installed on Windows that's missing on Windows Server. You could use Dependency Walker to make sure it can find all the required DLLs. There is also a similar post on SO stackoverflow.com/questions/6244939/…
– bwing
Nov 26 '18 at 16:14