.net 3.5 simple win application error - c#

I have a .net win app that seems to work for all our of test machines but the client is getting this error after installation. So the install seems to be working but the app running creates an issue.
The exception unknown software exception (0xc06d007e) occured in the application at location 0xfd96aa7d
Any ideas how to fix or troubleshoot without going back to the customer for techie debug

Idea for troubleshooting - there may be an entry in Administrative Tools->Event Viewer (look inside Windows Logs->Application) that could help you narrow down the reason for the failure.

The issue was that some of the resources where being blocked by the end user downloading from the web. FTP solved it

Related

Code Cop App just hangs

I written an test application using a Code Cop, a method interception approach.
However, as soon as I ran my first application I hit a snag whereby the application would fire up and hang with no information as to what was happening.
I had followed the code exactly and was able to run the same code on another machine.
There is no error information being output, it just hangs.
Does anyone know how I may be able to solve or debug this issue?
My solution was to contact Ricardo Barbosa at CodeCop who proceeded to help me solve this issue promptly and explaining why this was occurring.
My issue was due to not having the correct CLRJIT.dll on my machine
C:\Windows\Microsoft.NET\Framework
A Windows update solved the issue.
What's Happening
When the CodeCop application runs it creates a folder in %temp%/CodeCop and downloads symbol files from Microsoft to calculate method addresses.
The version I had was 4.6.57.0 in my v4.0.30319 framework folder.
For some reason there was no symbol file from the Microsoft public symbol server for this version of the CLRJIT.dll
Running Fiddler while starting the application showed this to be the case.
After I performed a Windows update I got version 4.6.100.1 of the clrjit.dll the application built and performed as expected.
Thanks to Ricardo for spending the time to solve this issue for me.

Interactive Brokers API issue with adding the ActiveX Control

Every time I try to add the Interactive Brokers API control on my computer it gives me an error that sais....
The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail. (Exception from HRESULT: 0x800736B1)
I have been looking for an answer and trying different things for a week now and I can not seem to figure it out. I tried it on my laptop and it worked. I thought it was my windows or my visual studio so i re-installed everything on my PC. I'm not running a Windows 7 Professional x64 with Visual Studio 2013 with the newest update. At this point I have no idea what to try to make it work. Does anybody know what is this error.
Sorry-very late for an answer to this but in case someone else comes across it. There are a number of reasons why Visual Studio might not be able to add the control to your application. For 64-bit windows, one of the main issues is that the ActiveX control (tws.ocx) is not registered properly when the API is installed. I have a web page dedicated to installing IB API on Windows and I list out many of the issues that can happen when working with the ActiveX control on 64-bit windows: http://holowczak.com/ib-install/
I just posted a very simple tutorial on my website that starts at the very beginning and walks you through getting the API to work with interactive brokers using Visual Studio and C# : Get Real-Time Stock data from Interactive Brokers API
If that doesn't help I would consider:
Turn off Windows Firewall and give it a try.
Ensure you have Traders Workstation setup to allow incomming connections for ActiveX/.NET.
Ensure Traders Workstation works on your machine. Try downloading it from IB and launching it. If it works, then the problem is on the .NET or connection from .NET to TWS which is Java.
Also when you say "Interactive Brokers Control" do you mean the API package that you can download? If so to build it into your program all you need is the .DLL file as shown in the tutorial link I posted above.

I have a .NET app impossible to debug because when I install the SDK it works. Any suggestions?

I have a .NET application that regularly works on all the machines with .NET installed.
When I try to launch it on a PC with no .NET framework installed this happens:
it opens, i can change tab (my app has 4 tabs), it reads the computer IP without any problem, but then crashes somewhere when it receives a message from another terminal (i have a terminal that communicates with the PC via ETH-TCP/IP).
The message I get is just:
DESCRIPTION: stopped working.
The big deal is that I cannot debug it because if I install the .NET framework it magically works like a charm.
Obviously I'm asking this because we prefer not to install .NET on all the machines in the office (they run different Windows versions and plenty of them don't have the .NET installed).
My question can be similar to this one, but in my case the .exe starts (as I explained above).. the crash comes when I start the communication between the PC and the terminal.
Anybody has a hint for my problem? Thank you
EDIT : thank you for the answers, in the end I decided to do Remote Debugging by running the app on a virtual machine with no .NET at all. Now, when it crashes, I can catch the bad instructions inside VS2010 installed on the host machine.
Btw, the problem was on a .dll that couldn't be loaded
You must have the .NET Framework installed on a machine in order to run a .NET application. The .NET Framework is both a runtime and the SDK, not just an SDK. All versions beyond Windows XP come with some version of the .NET Framework installed.
If you are saying that installing Visual Studio corrects the issue (which is what the question you linked to describes), that is a different problem altogether. Unfortunately, your question doesn't provide enough information to troubleshoot it. You can check the Event Viewer on the machine experiencing the issue, then look for two errors next to each other in the Application event log. One of these errors will contain exception detail, which will aid us (or you) in tracking down the problem.

Customize Error message for when ClickOnce application notices wrong version of .Net installed

When you try and run a .Net 4 ClickOnce application on a machine running .Net 3.5, it pops up the following error:
Unable to install or run this application. This application requires your system
to be updated to Microsoft Common Language Runtime Version 4.0.30319.0.
Please contact your system administrator.
My question is, is there any way to customize the body of this error message, so that I could put in a custom phone number to call, instead of displaying the above?
Note: I can't just include the prerequesites for the user to install, because the user does not have sufficient rights to install it by themselves anyways, hence why I want to add a phone number to our tech support staff in the error message.
Let's think about this: the manifest file launches the deploy file launches the executable, I think the error message is coming from the deploy file as the executable cannot run without the proper framework. Thereby the answer to your question would be no in a traditional sense.
Of course, you can use an existing app or service to customize that kind of error message, but you'd be stuck deploying that system as well. What I don't get is my clickonce apps install the framework for you resolving the problem themselves, if yours don't for some reason, I'd recommend putting an executable of .NET 4 FW on a share and linking people from there.
Another hackish way you can do it, is if your setup is like mine, you have a web page that clickonce installs off, maybe you could check in that web page? You'd have to change from .htm to .aspx, but that's not a problem on an iis server.
Is this an exception you can catch in code? If so, you can just create and throw an exception with your own message.
throw new Exception("your message here");
You can also check the value of Environment.Version on your initialization sequence to see what version of .NET is installed on the system, then display a message accordingly.

Fatal Execution Engine Error

All,
I have a console application which is written in .NET 3.5 which retrieves data from a database, does some calculations and post messages in a message queue.
I run the .exe on my PC which runs without any problems. Deploying the .exe in a 64 bit server the application suddenly stops without any errors and when I use the DebugView utility I can see the below error.
[6276] Fatal Execution Engine Error (7A09C12F) (80131506)
I tried compiling with x64, x86 and Any CPU but still the same problem. I tried deploying to another server and still same situation. Anyone has an idea how I should proceed to determine the root cause?
Many Thanks,
MK
Capture a crash dump and analyze it for the root cause.
Link
If you like, open a support case via http://support.microsoft.com

Categories

Resources