How do I fix a System.TypeInitializationException error when I don't have access to the source code?

Question

0.00/5 (No votes)

See more:

I installed a software application compiled by our developers, which was successful. However, when I launched the application, it crashed. Looking at the crash log file, I noticed the error was isolated to:

132821 [Error] [AppName]: System.TypeInitializationException: The type initializer for '[ObjectName]' threw an exception. ---> System.NullReferenceException: Object reference not set to an instance of an object.

Why did this happen? The developers swear that it worked successfully on their PCs, but that's because they have a development environment and I don't.

I ran a tool called Dependency Walker, which showed several dlls that were not on my system.

Could you please advise as to how I can resolve the missing dll issue and/or the System.TypeInitializationException message?

Thanks.

V/R,
John

Posted 9-May-14 9:49am

jbottiger2367

Add a Solution

Comments

[no name] 9-May-14 15:59pm

Quite frequently, Dependency Walker is less than truthful when it shows you that some DLLs are missing. It will tell you DLLs are missing if they are loaded dynamically for instance. Try each DLL one at a time and see if you get lucky. You can try Process Explorer to see which DLL your application is trying to access at the time it is running. Short of finding the DLL(s) that is missing or getting your devs to tell you what is going on at the time the application crashes, I don't know that there is a whole lot you can do. Your devs should be looking into it not you, sounds like.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

jbottiger2367 · Answer 1 · 2014-05-09T10:04:00

Thanks Wes for your prompt response. Incidentally, as I received your response, one of the developers managed to fix the issue within the application installer package. Apparently there was an unnecessary (and malformed) copy of an xml file included in the installer according to one of the developers. If that file had been removed, this issue would never have happened.

But I got the application working fine now. Thanks again.

V/R,
John