The type initializer '' threw an exception.

Mainly this error occurs when it fails to load a dependent dll/assembly. It couldn't find the dependency, or the version number was different.

This error mostly occurs when you deploy your application to production server. It might work fine in development machine. Things to make sure in this case:

All your dependencies are deployed properly.
Check the version numbers for the dependencies.

I had this issue when my multiple projects where using a logging dll. It worked fine in dev machine, but when deployed to the test server, booommmm..... ended up with this error.

So I made sure that all the projects in my solution are referring to the logging dll from same common location (may be a folder in the solution/GAC to hold common shared assemblies), with same version number. After making these changes and making sure all other dll's are deployed correctly, it worked like a charm.

Hope this tip helps somebody...... njoy..

The Specified Store provider cannot be found in the configuration or is not valid - entity framework

Check your machine.config to see if any providers mentioned in the <DbProviderFactories> section. If not, add the required provider to this section.

This solved mine.

How to install a windows service in a server which doesn't have Visual Studio installed

If you have visual studio installed in a server, it would be easier to install a windows service, by using installutil.exe. However this have to be done from Visual Studio command prompt.

But how can you install if you don't have Visual studio command prompt in the server.

Below is the solution:

SC Create <Service name> binPath= "complete path of the exe file" DisplayName= "MyService"

ex:-  sc create MyService binPath= "C:\temp\Service1.exe" DisplayName= "MyTestService"

The service will be created and will be displayed in services.msc as MyTestService. If you right click and check the properties of the service, it will show the service name as MyService.

IMPORTANT:- Make sure you add a space after the "=" for the arguments.
Like binPath= "C:\temp\Service1.exe" DisplayName= "MyTestService". You can see the space marked in purple color. This has to be there to run the command successfully.

Otherwise, it doesn't even throw error and you will not have a clue of what is happening.

You can use SC Delete command to delete the service from the console.

IIS Error & Solutions - Tips

Got Error: "http error 500.19 <modules runAllManagedModulesForAllRequests="true" />"

Soultion: Deleting this line from web.config solved it.

Got Error: "HTTP Error 404.3 - Not Found  The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map."

Solution: Ran the command "aspnet_regiis.exe -ir" from Visual studio command prompt. This .exe can be found in
%windir%\Microsoft.NET\Framework64\v4.0.30319

Got Error while hosting WCF Web service in IIS:
"the configuration section 'protocolmapping' cannot be read because it is missing a section declaration"

Solution: Please make sure the application pool that is used for the website need to be setup to use .Net 4.0 framework.


More tips on the way...