I am having the following problem.
Data:
I have a TFS Build Controller+Agent machine. I have there VS2013 Update 5 Installed.
I am running a build step which executes the following code:
using (var coverageInfo = CoverageInfo.CreateFromFile(Path.GetFullPath(cmdArgs.CoverageFile), executableDirectories, executableDirectories))
{
using (var coverageDs = coverageInfo.BuildDataSet())
{
coverageDs.WriteXml(cmdArgs.OutputFile);
}
}
When that steps is executed in the Build Server there is an exception:
Unhandled Exception: Microsoft.VisualStudio.Coverage.Analysis.SymbolsNotFoundException: Symbols for image file "Entities.dll" could not be found.
The thing is that, when I run that same code from my local machine, pointing to the same folders as the build machine, everything runs fine.
Any idea of what I can check?
Regards!
I was able to fix the issue by installing VS 2012. Let me explain. The image below shows the project that was giving problems. As you can see, there are two references to *.Analysis and *.Symbols. These two dlls are referenced by PATH:
C:\Projects\Build\Dev\ActivityPack\References\Microsoft.VisualStudio.Coverage.Analysis.dll
C:\Projects\Build\Dev\ActivityPack\References\Microsoft.VisualStudio.Coverage.Symbols.dll
The thing is that it looks like those DLLs need additional components installed by VS 2010.
I was getting this error:
Faulting application name: secondaryinstaller.exe, version: 14.0.23107.0, time stamp: 0x559b70e4
Faulting module name: KERNELBASE.dll, version: 6.2.9200.17366, time stamp: 0x554d16f6
Exception code: 0xe0434352
Fault offset: 0x00010192
Faulting process id: 0xac0
Faulting application start time: 0x01d12714fefee4bd
Faulting application path: D:\d6da799e8cfbca473168b6f82eb35b\secondaryinstaller.exe
Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll
Report Id: dd1fc757-9308-11e5-9431-005056b4190f
Faulting package full name:
Faulting package-relative application ID:
As you can see, the error is thrown by the Kernel, which makes me thing, in my ignorance, that there got to be a COM somewhere that is being referenced.
Thank you #cece for caring!
Related
I have developed a UWP app and uploaded it to Windows Store. Everything was working perfectly fine until I created a new self-signing certificate after the previous one expired and re-published the new changes to the store. The application after downloading and installing from the store crashes immediately after opening and leaves an event log with the below error in the Windows Event Viewer. The same issue occurs when installing through a side-loading build.
I have tried all methods suggested online(running system scan for corrupted files, register dll, use dll file from another system, etc). I have also uploaded an image showing my windows version. Any help will be appreciated. Thank you.
Faulting application name: XYZWindowsApps.exe, version: 1.0.1.0, time stamp: 0x61e99c28
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1466, time stamp: 0xe01c7650
Exception code: 0xc000027b
Fault offset: 0x000000000010b362
Faulting process id: 0x2d0c
Faulting application start time: 0x01d80e24b18250ad
Faulting application path: C:\Program
Files\WindowsApps\NameXYZ.AppName_1.0.13.0_x64__tesn1012p7f1y\XYZWindowsApps.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 07e3f487-1127-4f89-ba1b-1e1cb032168c
Faulting package full name: NameXYZ.AppName_1.0.13.0_x64__tesn1012p7f1y
Faulting package-relative application ID: App
I run my program in visual studio and it works great, but when i publish it and installed it dont start. I checked the problem on the event viewer and it's the information that comes with the error:
Faulting application name: Screen recorder.exe, version: 1.0.0.0, time
stamp: 0x59f8f3ad
Faulting module name: KERNELBASE.dll, version: 6.1.7601.23915, time stamp:
0x59b94abb
Exception code: 0xe0434352
Fault offset: 0x0000c54f
Faulting process id: 0x22f8
Faulting application start time: 0x01d35294634fde75
Faulting application path: C:\Users\jmarin\AppData\Local\Apps\2.0\LAHCHL75.EB9\PJ1V31LT.BZW\scre..tion_b46dd58387405837_0001.0000_c9a5ed0df210aa7f\Screen recorder.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: a1aed905-be87-11e7-849a-989096bc2875
Application: Screen recorder.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
at ScreenRecord.Form1..ctor()
at Screen_recorder.Program.Main()
Exception Info: System.IO.FileNotFoundException
Please look into your code, you are using file which is not available while publishing. you can copy the file into the root directory and try it again
I am working on a VS 2015 MVC C# web application for a client. The application has been stable for a couple of years, but the client has asked me to integrate some C++ DLLs that perform engineering calculations relevant to our web application.
Unfortunately there is no source code and documentation does not exist (don't ask me why...). So I am somewhat blind to how to use these DLLs.
When I load the main DLL and attempt to use it I get the following error:
Failed to load library SQLite3Ex.dll
Event viewer contains this entry:
Faulting application name: iisexpress.exe, version: 10.0.10557.1000, time stamp: 0x560abee8
Faulting module name: MSVCR120.dll, version: 12.0.21005.1, time stamp: 0x524f7ce6
Exception code: 0xc0000005
Fault offset: 0x0000f20c
Faulting process id: 0x1450
Faulting application start time: 0x01d1c6773bd1167d
Faulting application path: C:\Program Files (x86)\IIS Express\iisexpress.exe
Faulting module path: C:\WINDOWS\SYSTEM32\MSVCR120.dll
Report Id: 5d46a86a-2202-4d6e-af41-8426c16966e9
Faulting package full name:
Faulting package-relative application ID:
I'm not sure how to troubleshoot this problem and was hoping someone could point me in the right direction. I think this is a general error - could be a missing .cfg file or even a missing DLL? But I'm not sure how to determine the problem.
Trying to publish my UWP app. I'm able to build Release versions fine (I was actually able to push to the Store), but my app crashes as soon as it's launched. But the debug works fine?
I'm getting this error when debugging a Release build:
Unhandled exception at 0x55BA32F9 (Windows.UI.Xaml.dll) in AppName.exe: 0xC000027B: An application-internal exception has occurred (parameters: 0x00A12450, 0x00000002).
And these errors in Event Viewer if I launch it outside of VS:
1st:
Activation of app AppName failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.
2nd:
Faulting application name: AppName.exe, version: 1.0.0.0, time stamp: 0x560c53bd
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.10240.16431, time stamp: 0x55c9b90a
Exception code: 0xc000027b
Fault offset: 0x007132f9
Faulting process id: 0x1e38
Faulting application start time: 0x01d0fbcba39fec70
Faulting application path: C:\Development\AppName\AppName\bin\x86\Release\AppX\AppName.exe
Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
Report Id: 5c74b39d-98e4-4e89-b2ec-c81cbd5383d1
Faulting package full name: AppName
Faulting package-relative application ID: App
Is there something I'm doing wrong? I don't get any errors or warnings on Debug.
Add some code to the app.xaml.cs files unhandled exception event to send the error text to a web service or something like google analytics so you can see what is happening
Ended up being an issue with Entity Framework when it is compiled in .NET Native. I had to switch to SQLite for what I was using it for. Seems to work fine now.
https://github.com/aspnet/EntityFramework/issues/3293
I created a basic toolkit in .EXE format with ADB and Fastboot commands for my phone in Visual Studio Express 2012 using C#, and it works great on my computer, but when I try and open it on another computer, nothing happens. I have made sure to build it in Release mode, the computers I have tested are all on Windows 8 and have the latest .NET Frameworks, and I have read many other topics on this with no definitive answers. I am also getting errors in Event Viewer, but I'm not exactly sure what they mean. Have a look if you can, and thanks!
.NET Runtime:
Application: HTC One X+ Toolkit.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
Stack:
at HTC_One_X__Toolkit.Form1.InitializeComponent()
at HTC_One_X__Toolkit.Form1..ctor()
at HTC_One_X__Toolkit.Program.Main()
Application Error:
Faulting application name: HTC One X+ Toolkit.exe, version: 1.0.0.0, time stamp: 0x51bf3a29
Faulting module name: KERNELBASE.dll, version: 6.2.9200.16451, time stamp: 0x50988950
Exception code: 0xe0434352
Fault offset: 0x00014b32
Faulting process id: 0x1a8
Faulting application start time: 0x01ce6b7ca5512761
Faulting application path: C:\Users\Dylan\Downloads\Toolkit (2)\Toolkit\HTC One X+ Toolkit.exe
Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll
Report Id: e3254e0e-d76f-11e2-be89-50465d351325
Faulting package full name:
Faulting package-relative application ID:
Windows Error Reporting:
`Fault bucket -606412384, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0
Problem signature:
P1: htc one x+ toolkit.exe
P2: 1.0.0.0
P3: 51bf3a29
P4: 5
P5: 1.0.0.0
P6: 51bf3a29
P7: 13
P8: 6
P9: System.IO.FileNotFoundException
P10:
Attached files:
C:\Users\Dylan\AppData\Local\Temp\WERF566.tmp.WERInternalMetadata.xml
These files may be available here:
C:\Users\Dylan\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_htc one x+ toolk_e8ec446f1f71f1db9137fab138c0ad59c2ef6a1_1abaf806
Analysis symbol:
Rechecking for solution: 0
Report Id: e3254e0e-d76f-11e2-be89-50465d351325
Report Status: 16
Hashed bucket: 93c40e517fd84a9afa8e9156e3471d7b `
it's seems by the look of the stack trace that the code generated by the .net framework is trying to open a file from absolute location rather then a relative location. have you looked over the InitializeComponent method in the class Form1?
if not, please have a look. if you can't find a problem there wrep the call for InitializeComponent in try catch in order to get more information.
i would also recommend to try and debug it on other computer and go step by step. you can attach to a process using the visual studio and pause your program until the user pressed a button (using a message box for example)