IIS Publishing site error collection (continuous update)

This article primarily collects errors that IIS encounters during the publishing site and provides workarounds. And the pro-test is feasible. If you are also having problems with IIS publishing your site, please leave a message to ask.

(1.)HTTP Error 500.21-internal Server errorhandler "webservicehandlerfactory-integrated" has an error module "Managedpipelinehandler" in its module list

Possible cause: Due to first installation. NETFramework 4.0, which is caused by IIS 7.5 after installation.

Solution: Execute the Command "CD C:\Windows\Microsoft.NET\Framework\v4.0.30319" and Go to "C:\Windows\Microsoft.NET\Framework\v4.0.30319" Directory
Then execute the command "aspnet_regiis.exe-i", register "aspnet_regiis", wait a moment, aspnet_regiis success. Problem is solved.

(2.)failed to load file or assembly "xxx.xx" or one of its dependencies. An attempt was made to load a program that is not properly formatted.

Possible cause: The operating system is 64-bit, but the published program refers to some 32-bit DLLs, so there is a compatibility issue.

Solution (a): if it is a 64-bit machine,iis--> application pool--Advanced settings--enable 32-bit applications: true.

Solution (ii): Modify the project Properties--to the target platform (e.g., x86\x64).

(3.)

Cond

IIS Publishing site error collection (continuous update)