The type initializer for 'X64' threw an exception.

[nsutariya9393]

hello,

I am using magick.net to convert psd to png images for my web application project with .net framework 4.0 and works perfectly on my local machine but when I deploy on server, it started giving error "The type initializer for 'X64' threw an exception." I have tried all the solutions I found but none of them worked for me. The application is running on x64. I have tried adding 64 and anycpu dlls for magick.net.

can anyone please help me? I am stuck from a week.

[dlemstra]

Is it possible to get the complete stack trace of the exception?

[nsutariya9393]

yes, I put native in all 3 folders and restarted IIS but didn't work. I wonder, is it something wrong with native? I copied it from my local. cause Local works fine just deployed doesn't work.

[gh658804]

I sympathize. I had faced such issues when i was battling with this problem. At the end it just worked.

What i did was to

1. Copy the native dll in all 3 folders
2. Make sure 32bit support (in my case, the site was 32-bit) was enabled in the app pool
3. I had created a specific app pool with a local user because i wanted it to have access to certain resources.

That's all i can remember at the moment. I do hope you figure it out.

[nsutariya9393]

thanks for your time. I did all those but none of them worked for me.
I am not sure what you mean by specific app pool with a local user?
also, can you tell me from where did you get native dll?

[gh658804]

I had downloaded it from the site, along with the main package. I made sure they were from the same version.

In the App pool of the site, in its advanced settings i had changed the identity to a local user of the server. I'm not sure if i had also set the "load user profile" to true and if it had played any role in this.

[nsutariya9393]

thank you for your help! I tried this too but no luck :-(

[gh658804]

Have in mind that the error i faced was the "The specified module could not be found", not the "The specified procedure could not be found" one you mentioned. This is a different issue which i don't think i can be of much help. One wild guess i can think off would be something like "the version of the native dll is different than the expected one".

In any case, i'm guessing that when the module in the message turned into procedure, your program managed to find the native dll but failed for another reason.

I hope this will somehow help.

[nsutariya9393]

I was getting "The specified module could not be found" before and after adding native dll to bin folder, the error turned into "The specified procedure could not be found". One thing I would ask is, if you can send me the link to download native dll package from the website, I have downloaded it from nuget package manager console from visual studio.

[nsutariya9393]

yes my native dll and magick.net dll versions are different but not sure where I can get it. Help would be really appreciated.

[nsutariya9393]

I download a package and package version is 7.23.2.1 and the native inside is 7.0.11.2. I couldn't find same version native.

[gh658804]

Another thing i have stumbled upon several times is that the user running a .NET program must have write access to folder "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files" (or the respective \Framework\ one for 32-bit apps. Perhaps you should try that?

[nsutariya9393]

This I already have. but as you said, something is wrong with native dll.