Failed to load type 'System.ServiceModel.Activation.HttpModule' from the assembly 'System.ServiceModel

I am running my web project in IIS.

This is the 4.0 Framework APP.

I have Service.svc and I get this error when starting the application.

"Failed to load type" System.ServiceModel.Activation.HttpModule "from the assembly" System.ServiceModel, Version = 3.0.0.0, Culture = neutral, PublicKeyToken = b77a5c561934e089 "

I tried this -> aspnet_regiis.exe -iru, which I found in many forums, and this did not solve my problem.

Does anyone know a different method?

+86
iis service svc
Mar 28 '13 at 17:58
source share
13 answers

Try

c:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -iru 

When multiple versions of the .NET Framework run side-by-side on the same computer, the version of ASP.NET ISAPI associated with the ASP.NET application determines which version of the common language runtime is used for the application.

The Above command will install the version of ASP.NET associated with Aspnet_regiis.exe and only register ASP.NET in IIS.

https://support.microsoft.com/en-us/help/2015129/error-message-after-you-install-the--net-framework-4-0-could-not-load

+153
Jul 24 '13 at 7:58
source

I have Windows 8 installed on my computer, and the aspnet_regiis.exe tool did not work for me either.

The solution that worked for me is posted on this link to Neha's answer: System.ServiceModel.Activation.HttpModule Error

Throughout the problem, this solution was referred to as re-registering aspNet with aspnet_regiis.exe. But that did not work for me.

Although this is the right decision (as explained here beautifully)

but it did not work with windows 8.

For Windows 8, you need the Windows features and enable everything in the ".Net Framework 3.5" and ".Net Framework 4.5 Advanced Services" sections.

Thanks neha

+48
Apr 30 '13 at 16:01
source

Hi Thanks for the question; To solve: "Failed to load type" System.ServiceModel.Activation.HttpModule "from the assembly" System.ServiceModel, Version = 3.0.0.0, Culture = neutral, PublicKeyToken = b77a5c561934e089 ""

In Windows functions, check everything for .NET 4 Advanced Services and .NET 3.5

enter image description here

Like Nicholas Gago, I tried aspnet_regiis.exe -iru, but that didn't work. After the features were turned on, the yellow screen error disappeared. Thank;

+34
Nov 19 '13 at 15:13
source

You can install these features on a Windows 2012 server using powershell using the following commands:

 Install-WindowsFeature -Name NET-Framework-Features -IncludeAllSubFeature Install-WindowsFeature -Name NET-WCF-HTTP-Activation45 -IncludeAllSubFeature 

You can get a list of functions with the following command:

 Get-WindowsFeature | Format-Table 
+9
Jul 05 '16 at 9:13
source

Okay, finally got it.

Change this line in %windir%\System32\inetsrv\Config\ApplicationHost.config

 <add name="ServiceModel" type="System.ServiceModel.Activation.HttpModule, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" preCondition="managedHandler" /> 

to

 <add name="ServiceModel" type="System.ServiceModel.Activation.HttpModule, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" preCondition="managedHandler,runtimeVersionv2.0" /> 

If this is not enough

Add this next line to Web.config

 <system.webServer> <modules runAllManagedModulesForAllRequests="true"/> </system.webServer> 
+4
Apr 11 '13 at
source

In Windows Server 2012. Go to ISS โ†’ Modules โ†’ Uninstall ServiceModel3-0.

+4
Aug 12 '13 at 22:01
source

In node server manager functions, you can also remove some subelements in the .NET Framework 3.5.1 that are installed by activating some other roles.

For example, they removed the WCF activation features as follows, and our websites returned:

  • [x] Features of the .NET Framework 3.5.1
    • [x] .NET Framework 3.5.1
    • [] Activation of WCF
      • [] HTTP activation
      • [] Activation without HTTP.

Note: a reboot is not required for us.

+4
Feb 09 '15 at 13:31 on
source

More details

http://msdn.microsoft.com/en-us/library/hh169179 (v = nav.71) .aspx

"This error may occur if there are several versions of the .NET Framework on the computer running IIS ..."

+1
May 20 '14 at 17:07
source

I got this error after accidentally publishing one website in another websiteโ€™s directory. Two sites had different versions of .net. For me, changing the application pool has been fixed. To do this, in IIS Manager:

click on the website => Advanced Settings ... (right) => click to the right of the application pool => a button will appear with "..." => select ".NET v4.5 Classic",

If this application pool does not work, try others.

+1
Jun 17 '15 at 15:17
source

We use the web service next to the website, and when we publish the website, it returns the same error. We found that by going to IIS and removing the ServiceModel from the modules and svc-Integrated from the handler mappings, the error disappeared.

0
Feb 04 '16 at 17:21
source

After you have done everything, and if it still does not work, please do https://www.codeproject.com/Articles/613812/Solve-IIS-8-Error-Could-not-load-type-System -Servi

0
Dec 17 '18 at 19:11
source

remove the module that is indicated in the message .Net error, 1 down vote

In Windows Server 2012. Go to ISS โ†’ Modules โ†’ Uninstall ServiceModel3-0. (worked without me)

-one
Nov 04 '14 at 10:12
source

start-> Run -> c:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -iru

-one
Dec 07 '18 at 2:57
source



All Articles