System.ServiceModel.Activation.HttpModule error

Question

what is the cause of this error on below line?

<system.web>
    <globalization fileEncoding="utf-8" requestEncoding="utf-8" responseEncoding="utf-8" culture="fa-IR" uiCulture="fa-IR" />
    <compilation targetFramework="4.0" debug="true">
      <assemblies> <add assembly="System.Data.Entity, Version=4.0.0.0, Culture=neutral,  PublicKeyToken=b77a5c561934e089" />

Could not load type 'System.ServiceModel.Activation.HttpModule' from assembly 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.TypeLoadException: Could not load type 'System.ServiceModel.Activation.HttpModule' from assembly 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' — Negar, Dec 07 '10 at 08:28

score 33 · Answer 1 · answered Mar 20 '13 at 12:43

33

Everywhere the problem to this solution was mentioned as re-registering aspNet by using aspnet_regiis.exe. But this did not work for me.

Though this is a valid solution (as explained beautifully here)

but it did not work with Windows 8.

For Windows 8 you need to Windows features and enable everything under ".Net Framework 3.5" and ".Net Framework 4.5 Advanced Services".

Thanks Neha

answered Mar 20 '13 at 12:43

Neha

331
3
2

Thanks, that helped me, I was baffled seeing as every search I ran the response was that aspnet_regiis fixes it, but this is not the case for Windows 8 – andrewm Jun 05 '13 at 12:00
On Windows Server 2008 R2 you do not get the option ".Net Framework 4.5 Advanced Services" Instead, enable all the roles and features required then install/repair .NET 4.5 framework. See http://stackoverflow.com/q/20784908/536546 for details – ghostJago Apr 11 '14 at 12:21
Thanks, after much hassle and search, this worked for me – devC Jun 10 '14 at 10:03
Voting early and often to get this to the top of the list. – THBBFT Mar 04 '15 at 19:11
GENIUS .. you saved my remaining hairs – Karim AG Jul 23 '16 at 14:52
Thank you. That was a life saver! – John Bonfardeci Jan 27 '17 at 17:07
Awesome!! Also Works for Windows 10. Thanks – Pacheco Nov 13 '18 at 13:57

score 22 · Accepted Answer · answered Aug 19 '11 at 10:26

This happens when you install .Net 4 before enabling IIS, or if you register WCF after registering .Net 4. In either case, your App Pools will be running .Net 2.0 (which is the CLR version required for .Net 3 if you have registered WCF, which installs ASP.Net 3.5, or the default if you have installed IIS after .Net 4)).

There are many references to this on the web, e.g. the MSDN blogs: http://blogs.msdn.com/b/webtopics/archive/2010/04/28/system-typeloadexception-for-system-servicemodel-activation-httpmodule-in-asp-net-4.aspx

The fix is to re-register ASP.Net 4 from the correct (32 or 64 bit) Framework folder (Framework64 on a 64bit server), using the aspnet_regiis.exe tool, e.g.

aspnet_regiis.exe -iru

We tried this, and are still getting the same error, "Failed to find the RegisterModule entrypoint in the module DLL C:\Windows\Microsoft.NET\Framework\v4.0.30319\System.ServiceModel.Activation.dll." — Bryan, Aug 31 '15 at 14:53

score 8 · Answer 3 · edited Feb 11 '14 at 22:58

8

For Windows 8 you need to Windows features and enable everything under .Net Framework 3.5 and .Net Framework 4.5 Advanced Services -> Enable Everything

edited Feb 11 '14 at 22:58

Andrei Sfat

8,440
5
49
69

answered Feb 11 '14 at 22:36

Innovation Wang

199
1
2
6

score 2 · Answer 4 · answered Apr 22 '13 at 09:21

2

For windows 8 the above configuration in Control panel->programs->windows features on/off enable every thing under".net Framework3.5" and ".net Framework 4.5 advanced Services" Working fine for me.

Thanks Madhavi.B

answered Apr 22 '13 at 09:21

user2306751

21
1

score 2 · Answer 5 · answered Mar 27 '15 at 11:37

I had this problem on a server managed by one of our clients. I didn't have the access to run the aspnet_regiis.exe tool. As a workaround I did the following:

I removed aspNetCompatibilityEnabled="true" from the <serviceHostingEnvironment> tag in the web.config
removed [AspNetCompatibilityRequirements] from the webservice.cs file

Unfortunately this means that for example HttpContext.Current becomes null, I could fix my webservice by rewriting all my HttpContext.Current.Server.MapPath calls to System.Web.Hosting.HostingEnvironment.MapPath

Hope this helps someone.

score 0 · Answer 6 · answered May 09 '13 at 18:53

This problem surfaced for us immediately after we installed the Windows Management Framework 3.0/PowerShell 3.0 sp1 (KB2506143) on a Windows Server 2008 R2 x64. Windows Update then also installed KB2736422, KB2756921, and KB2656411 immediately after.

Our solution was to first uninstall KB2506143 (and the three updates that accompanied that), then run aspnet_regiis.exe -iru as suggested in Ed209's response above. Both steps were necessary to resolve the problem. Thank you, Ed209.

score 0 · Answer 7 · answered May 13 '15 at 09:26

0

appcmd.exe set config -section:system.webServer/modules /[name='ServiceModel'].preCondition:"managedHandler,runtimeVersionv2.0" /commit:apphost

worked for me

answered May 13 '15 at 09:26

Pecan

350
3
14

System.ServiceModel.Activation.HttpModule error

7 Answers7

Linked