Develop Reference

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 configSections section on top, no additional references besides log4net, supportedRuntime tag 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 DispatcherUnhandledException and in the AppDomain.UnhandledException handlers
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?

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.

C# application using Microsoft.Office.Interop.Excell dll throws exception(error: 80080005) when Windows trusted apps is installed with OS installation

Issue:
I am facing an issue in Win10 PC while running a C#application created in VS 2013. The application always throws exception when it tries to create excel instance.
Microsoft.Office.Interop.Excel is added in project reference(:\Program Files (x86)\Microsoft Visual Studio 12.0\Visual Studio Tools for Office\PIA\Office15\Microsoft.Office.Interop.Excel.dll)
The below Exception is obtained:
Retrieving the COM class factory for component with CLSID {00024500-0000-0000-C000-000000000046} failed due to the following error: 80080005 Server execution failed (Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE))
From event viewer I see the error related to excel.exe version 16 bing called:
Faulting application name: EXCEL.exe, version: 16.0.8528.2136, time stamp: 0x59d6c372
Faulting module name: KERNELBASE.dll, version: 10.0.16299.371, time stamp: 0xee297154
Exception code: 0xc06d007f
Fault offset: 0x00103ef2
Faulting process id: 0x2c8c
Faulting application start time: 0x01d41f1db8e05601
Faulting application path: C:\Program Files\WindowsApps\Microsoft.Office.Desktop.Excel_16000.8528.2136.0_x86__8wekyb3d8bbwe\Office16\EXCEL.exe
Faulting module path: C:\windows\System32\KERNELBASE.dll
Report Id: 5c23fa18-770c-4233-b803-e57c2bf68174
Faulting package full name: Microsoft.Office.Desktop_16000.8528.2136.0_x86__8wekyb3d8bbwe
Faulting package-relative application ID: Excel
Code snippet:
The application is trying to create an instance of Microsoft.Office.Interop.Excel.Application:
public ExcelReader()
{
try
{
m_excelApplication = new Microsoft.Office.Interop.Excel.Application();
}
catch(System.Exception Exp)
{
MessageBox.Show( Exp.Message );
}
}
Environment details:
During OS installtion there is something called trusted apps which is installed by default. We can see the icons related to Excel 2016, Word 2016 etc in Windows option.
But in my machine only Office 2013(64 bit) is installed after fresh OS installation.I have the exe for MS office 2013 present in "C:\Program Files\Microsoft Office\Office15\EXCEL.EXE"
Why is the excel.exe version 16(C:\Program Files\WindowsApps) called when application launches
Issue is observed in machines which have MS office 2016, MS office 2013 installed which has the trusted apps(2016) installed by default.
Could somebody help me out on this.

After hours and hours of searching the web for an answer regarding this issue, I have found that under Component Services > Computers > My Computer > DCOM Config > Microsoft Excel Application >> Properties panel - [Identity tab], the default setting for Windows 10 is The launching user, while on Windows 7 the default one is The interactive user. Changing the identity setting on Windows 10 to The interactive user solved this issue for me.
Hope this will save other people the amount of time it took me to find an answer.

This issue happens because of Interop libraries. The Interop libraries have different methods in different versions. You have to check the version of Interop libraries that you currently have and use appropriate libraries that you need for current Office that is installed.
On that Microsoft page you can see the information where you can get Introp libraries for installed office version.
If you want to support multiple office versions, you have to install the minimal version that you clients can have (2010 for example) and then write proxy classes that will detect version of MS Office and use their functionality and methods via CLSID.

Windows Application crashes due to CLR.dll - Windows 2008 R2 Server

I have a Dot Net Framework 4.0 based application developed on Visual Studio 2010 Professional which is running as a Windows Service on Windows Server 2008 R2 Enterprise Version with Service Pack 1, 64 bit Operating System.
The application seems to crash intermittently and the reason is as below :
Faulting Module name: clr.dll, version: 4.0.30319.1026
Exception Code: 0xc0000409
Fault Offset: 0x002b79d8
Faulting module path: C:\Widows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Can you kindly let me know if there is any HOTFIX for this CLR.dll crash issue? If yes can you let me know regarding the same?

Install this HOTFIX from windows.

SQL Server CE 4.0 deployment issue--which files are necessary?

I'm trying to deploy a small Windows Form app that uses a SQL Server CE 4.0 database. I don't want every system running this application to have to install SQL Server CE 4.0, so I'm trying to get any required DLLs included with the application.
When I check the references list, the only reference for SQL Server CE 4.0 is System.Data.SqlServerCe. Including the DLL for that, System.Data.SqlServerCe.dll, still leads to the following error when attempting to connect to the database:
Unable to load the native components of SQL Server Compact corresponding to the ADO.NET provider of version 8876. Install the
correct version of SQL Server Compact. Refer to KB article 974247 for
more details.
I've seen a few articles talking about this for different versions of SQL Server CE, but they listed DLLs for other versions, as far as I could tell. The systems the app will be running on should all have at least Windows 7 with .NET 4.0 installed, if that makes a difference.
I tried the steps located here to add the files as shown in the link: http://erikej.blogspot.com/2011/02/using-sql-server-compact-40-with.html
With those files included in the build, the program compiles without any errors, but when run on a secondary system, the GUI never appears (part of the public Form1() includes a method that grabs data from the SQL CE database) and the program just closes after a couple of seconds. The event viewer shows this error:
Faulting application name: Dispatch Review Assistant.exe, version: 1.0.0.0, time stamp: 0x50915d3c
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17932, time stamp: 0x503285c2
Exception code: 0xe0434352
Fault offset: 0x000000000000caed
Faulting process id: 0x1028
Faulting application start time: 0x01cdb78c10761c73
Faulting application path: C:\Users\deLucain\Desktop\Release\Dispatch Review Assistant.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 4e4f45e3-237f-11e2-bd76-14dae92102de

We had the same error message showing up when doing a private deployment (ie including libraries in application folder) of SQLCE 4.0 application.
When adding references to our project, we had added the x64 and x86 folders (and associated dlls) as per the documentation.
At this point, we got the error :
Unable to load the native components of SQL Server Compact corresponding to the ADO.NET provider of version 8876. Install the correct version of SQL Server Compact. Refer to KB article 974247 for more details.
In our environment, we found that the amd64 folder found under :
%Program Files%\Microsoft SQL Server Compact Edition\v4.0\Private
was also needed.
After adding it to the project and referencing the contained dlls, our issue was resolved.

Faulting application <app_name>, version <version number>,faulting module kernel32.dll

I have one windows application built using C# and .net framework 2.0 and its installed on Windows Server 2003.
I have tested application on my machine and it works perfectly on my machine. Only difference between two machines is that, my machine has Windows Vista OS and machine on which error occured has Windows Server 2003 OS.
When I start application, it works correctly for some time but then gives one error as
Faulting application ,
version ,faulting
module kernel32.dll,version 5.2.3790.4480, stamp , debug? 0. fault address 0x000bef7.
Source : .NET Runtime 2.0 Error
Category : None
Event ID : 1000
Does anyone knows why this error is coming? I googled for this error but most of the solutions were for either explorer.exe or internet explorer.

Use windbg or adplus to attach to the process and get the process crash dump. This would help you to identify the offending part of the code with symbols loaded. In most cases, it shows the last exception and hence gives a very good view of what could have gone wrong.