Calling LoadLibraryEx on ISAPI filter failed (v4.0.30319)

Question

User1021933026 posted
I installed .Net 1.1 on a Windows Server 2008 (which already had .NET 4 installed). Afterwards, I started getting the following error: HTTP Error 500.0 - Internal Server Error Calling LoadLibraryEx on ISAPI filter "C:\Windows\Microsoft.NET\Framework\v4.0.30319\\aspnet_filter.dll" failed I have tried running aspnet_regiis without success. I have also tried the suggestions by Rick Strahl (http://www.west-wind.com/weblog/posts/2011/Apr/04/Error-on-64-Bit-Install-of-IIS-LoadLibraryEx-failed-on-aspnetfilterdll) but to no avail. I have also removed .NET 4.0.30319 using the cleanup tool (http://blogs.msdn.com/b/astebner/archive/2008/08/28/8904493.aspx). When I reinstalled it, The error was still there. I have already removed 1.1 but still i get that error. Please help.

Answer 1

User-176674611 posted

Hi,

Do you mean after installing .net 1.1, your 4.0 applications began running into the above issue? Have you tried re-run aspnet_regiis for .net 1.1? Since it happens after .net 1.1 is installed, it's possible the problem is that related with. If the issue persists, could you please post your ISAPI settings here:

%windir%\system32\inetsrv\appcmd list config "Your Site Name" -section:system.webServer/isapiFilters

Thanks.

 

Answer 2

User1021933026 posted
The isapi settings are as follows: >system.webServer> >isapiFilters> >filter name="ASP.Net_2.0.50727-64" path="%windir%\Microsoft.NET\Framework64 \v2.0.50727\aspnet_filter.dll" enableCache="true" preCondition="bitness64,runtim eVersionv2.0" /> >filter name="ASP.Net_2.0.50727.0" path="%windir%\Microsoft.NET\Framework\v2 .0.50727\aspnet_filter.dll" enableCache="true" preCondition="bitness32,runtimeVe rsionv2.0" /> >filter name="ASP.Net_4.0_64bit" path="c:\Windows\Microsoft.NET\Framework64\ v4.0.30319\aspnet_filter.dll" enableCache="true" preCondition="runtimeVersionv4. 0,bitness64" /> >filter name="ASP.Net_4.0_32bit" path="c:\Windows\Microsoft.NET\Framework\v4 .0.30319\aspnet_filter.dll" enableCache="true" preCondition="runtimeVersionv4.0, bitness32" /> >filter name="ASP.NET_4.0.30319.0" path="C:\Windows\Microsoft.NET\Framework\ v4.0.30319\\aspnet_filter.dll" enabled="true" enableCache="true" preCondition="r untimeVersionv4.0" /> >/isapiFilters> >/system.webServer>

Answer 3

User-176674611 posted

The settings is correct. If you add a new asp.net site and assign a new application pool, does this issue also happen?

Answer 4

User1021933026 posted
Works! Not sure why but when i create a new site and new app pool, everything is sorted. Thanks

Answer 5

User-1131243847 posted

Dear Lloydz,

settings are not correct, if you are keen , there is an extra slash on the path for the last setting...:((

Hi All,

 

I got this error, before you do any above stuff, just try below

1. Click on your computer icon in IIS

2. On right side, you see ISAPI filters - Click

3. Pick up the Filter name ASP.Net_4.0_64bit  and its path MIGHT HAVE AN EXTRA \ IN THE PATH,

SO UNABLE TO LOAD THIS DLL,

 %windir%\Microsoft.NET\Framework64\\v4.0.30319\aspnet_filter.dll

 

4. restart IIS - should resolve the error.

 

thanks

HydPhani 

 

 

 

Answer 6

User-307231081 posted

Yep Agree with you.. I was in to the same mess. Your statment helped me. Thanks for sharing this.. Appriciate it..

-Ajit

Answer 7

User-987287576 posted
I had this error too, and it was the extra slash. I have no idea how that typo got there since I didn't type the ISAPI filter path by hand. Thanks everyone for posting to this thread. Pedro

Answer 8

User-511080233 posted

Thanks prasad, your solution worked for me.. and  it helped a lot.

Answer 9

User-1480097481 posted

This double slash issue in the ISAPI Filter exe path for ASP.NET 4.0.30319.0 seems to be a systematic issue. I wonder if this has been captured in a Microsoft KB or has been addressed via some patch.

Answer 10

User-181888624 posted

Hi,

 

I am recieving a similar error message: Calling LoadLibraryEx on ISAPI filter "D:\Program Files\CA\webagent\bin\ISAPI6WebAgent.dll" failed. Any help would be appreciated.