The type initializer for '' threw an exception

Question

1.58/5 (5 votes)

See more:

I have a c++/cli project and it's a windows application. In debug mode we didn't have any problems but after taking it to release mode this error start up. I searched and found some forum-answers but couldn't help me solve this problem.
Please help me ....

Error :

An unhandled exception of type 'System.TypeInitializationException' occurred in Unknown Module.

Additional information: The type initializer for 'Module' threw an exception.

Posted 22-Mar-10 3:06am

Member 3648847

Updated 16-Nov-21 13:06pm

Hans Dietrich

v2

Add a Solution

Comments

sharifani 1-Nov-12 11:40am

who can i resolve error " the type initializer 'MODUl' threw an exception.i can install microsoft visual studio 2010 ultimate,but that error ocured and vs not running.please help me.

Member 14504152 18-Jun-19 9:57am

I have also this type of error in my code

using Nexmo.Api;
using System.Web.Mvc;
using System.Diagnostics;
using System.Web.Http;
using Newtonsoft.Json;
using System.IO;

namespace NexmoDotNetQuickStarts.Controllers
{
// For more information on enabling MVC for empty projects, visit http://go.microsoft.com/fwlink/?LinkID=397860

public class SMSController : Controller
{

public ActionResult Index()
{
return View();
}

[System.Web.Mvc.HttpGet]
public ActionResult Send()
{
return View();
}

[System.Web.Mvc.HttpPost]
public ActionResult Send(string to, string text)
{

var results = SMS.Send(new SMS.SMSRequest
{

from = Configuration.Instance.Settings["appsettings:NEXMO_FROM_NUMBER"], //in this line
to = to,
text = text
});
return View("Index");
}

[System.Web.Mvc.HttpGet]
public ActionResult Recieve([FromUri]SMS.SMSInbound response)
{

if (null != response.to && null != response.msisdn)
{
Debug.WriteLine("-------------------------------------------------------------------------");
Debug.WriteLine("INCOMING TEXT");
Debug.WriteLine("From: " + response.msisdn);
Debug.WriteLine(" Message: " + response.text);
Debug.WriteLine("-------------------------------------------------------------------------");
return new HttpStatusCodeResult(200);

}
else
{
Debug.WriteLine("-------------------------------------------------------------------------");
Debug.WriteLine("Endpoint was hit.");
Debug.WriteLine("-------------------------------------------------------------------------");
return new HttpStatusCodeResult(200);

}

}

[System.Web.Mvc.HttpGet]
public ActionResult DLR([FromUri]SMS.SMSDeliveryReceipt response)
{

Debug.WriteLine("-------------------------------------------------------------------------");
Debug.WriteLine("DELIVERY RECIEPT");
Debug.WriteLine("Message ID: " + response.messageId);
Debug.WriteLine("From: " + response.msisdn);
Debug.WriteLine("To: " + response.to);
Debug.WriteLine("Status: " + response.status);
Debug.WriteLine("-------------------------------------------------------------------------");

return new HttpStatusCodeResult(200);
}

}

}

10 solutions

Solution 3

I recently had the same problem, and it was because I was using Date.Parse on a missing element in the config file:

Date.Parse(System.Configuration.ConfigurationManager.AppSettings.Get("frex"))

Posted 5-May-11 8:08am

J. Moreno

Comments

Farhat Khan 18-Apr-23 0:01am

public partial class MDI : Form
{
public MDI()
{
InitializeComponent();
}

private void eXITToolStripMenuItem_Click(object sender, EventArgs e)
{
Application.Exit();
}

private void MDI_Load(object sender, EventArgs e)
{
string Path = Environment.GetFolderPath(Environment.SpecialFolder.MyDocuments);
if(File.Exists(Path+"\\connect"))
{
login log = new login();
MainClass.showWindow(log, this);
}
else
{
settings set = new settings();
MainClass.showWindow(set, this);
}
}
please solution
An unhandled exception of type 'System.TypeInitializationException' occurred in ims.exe

Additional information: The type initializer for 'ims.MainClass' threw an exception.
run and this error accur

Solution 4

change your .net framework to lower ;)

Posted 6-Apr-12 20:13pm

mohsensamiey

Comments

Abdelrahman Othman Helal 24-Apr-17 6:43am

Thank you, You saved my whole day :).

Solution 11

In my case (so many different cases where this shows up) I was initializing some static fields in their declaration, like this:

C#

public class MyHelperClass
{
    readonly static SolidColorBrush BlueBrush = new SolidColorBrush(Colors.Blue);
    
    public static void ApplyBrush()
    { 
      // do something with brush 
    }
}

When I moved the initialization into a static constructor, the exception was no longer thrown:

C#

public class MyHelperClass
{
  readonly static SolidColorBrush BlueBrush;
  
  static MyHelperClass
  {
    BlueBrush = new SolidColorBrush(Colors.Blue);
  }
}

Posted 2-Sep-14 5:57am

mldisibio

Solution 7

XML

look the repository container in unity.config
<pre><pre lang="xml">
<unity xmlns="http://schemas.microsoft.com/practices/2010/unity">
  <alias type="App.Core.Interfaces.IRepositoryConfiguration, App.Core" alias="IRepositoryConfiguration" />
  <alias type="App.Repository.Mappings.SqlServer.SqlRepositoryConfigurer, App.Repository.Mappings.SqlServer" alias="SqlRepositoryConfigurer" />

  <container name="RepositoryContainer">
    <register type="IRepositoryConfiguration" mapTo="SqlRepositoryConfigurer" >
      <lifetime type="singleton"/>
    </register>
  </container>
</unity>
</pre></pre>

Posted 23-Aug-13 9:38am

Pablo Mereles

Solution 9

I was making an assignment in a constructor that didn't have an error handling.

VB

fileInfo = My.Computer.FileSystem.GetFileInfo(logDirLoc & logFileName)
writer = fileInfo.AppendText()

When I removed it the issue was solved.

tip: I looked through the error details and saw that a file couldn't be found. That was it.

Posted 5-Mar-14 11:17am

gahintz

Solution 10

I faced the Same error that is "System.TypeInitializationException". This error is raised due to Static constructor .

Actually in my case i am accessing some value from the App.config and assigning that value in a static variable . The error is because of the App.config file . That means the app.config file is not well formed (I just missed some tag on app.config ). After putting the missing tag it works fine.

Posted 2-Sep-14 4:54am

Bimaln

Comments

Bimaln 24-Sep-14 9:53am

Actually it was fixed my error.

Solution 13

The type initializer for 'Module' threw an exception.
Just Run IISRESET

Posted 22-Feb-15 2:12am

fathy_s

Solution 19

I had this problem also, but my solution wasn't any of these. It was because I had an unmanaged class with a virtual function that returned a managed pointer.

class A
{
    virtual ManagedType^ Foo();
};

Apparently the C++/CLI runtime can't handle this. Removing the virtual fixed the problem (luckily for me the virtual wasn't needed in my case).

Posted 16-Nov-21 13:06pm

dleclerc

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)

gbybee · Accepted Answer · 2012-11-20T08:37:00

Solution 5

I had the same error and found that the class I was referencing was not the problem, but it had a static variable of another type declared that required another assembly to load. That assembly was built for a target platform of x86 (see Properties-->Build tab) however the main project was compiled for Any CPU. I rebuilt the older assembly for Any CPU... problem solved.

Here are some helpful steps for finding the root cause of this problem...

Click Debug--> Exceptions and check ON all the Thrown checkboxes. This will cause the debugger to stop on all first chance exceptions and will help you find the error under the Type Initializer error that you're seeing. If it is related to another assembly, as mine was, you can use Microsoft's Assembly Binding Log Viewer tool to help determine the problem.

Posted 20-Nov-12 8:37am

gbybee

Comments

benben88 20-Jun-14 12:12pm

This helped me! Initializing all of the "thrown" actually gives you a better insight as to what is happening to get this bigger error. Many thanks!

thenem 12-Aug-14 13:34pm

Thanks! Ticking all of the "thrown" checkboxes under Debug --> Exceptions was a great help!

Member 10273358 8-Dec-14 20:49pm

Very good solution. It fast helped me find the error that I declared a const std::set with incorrect initialization arguments. It occurs before main() entry, so without this, it's really hard to find it out!

hamidsadegh 31-Dec-15 13:57pm

thanks for your answer

pratibhas 3-Mar-16 7:14am

thanx

Emmablakes 30-Jul-16 11:18am

thanks bro..reading your solution actually helped me too.
good to have people like you around

Member 14605063 17-Oct-19 16:13pm

Worked for me! Got right to the heart of the problem.

PratapBhaskar · Accepted Answer · 2010-03-22T03:20:00

Solution 1

Does the machine where the application is running has all the required dlls??

Maybe you are missing some interops in the local directory

Posted 22-Mar-10 3:20am

PratapBhaskar

Comments

Prasad_Kulkarni 5-Jun-12 1:24am

Good one +5