Solutions to some strange problems in IIS 7.5

This article introduces some solutions to some strange problems in IIS 7.5. If you need to know more about these solutions, refer to the introduction section.

Problem description:

If you deploy the WCF Service file ---. svc in IIS 7.5 for the first time, you may encounter the following problems:

404-Not Found-The page you are requesting cannot be served because of the extension of the configuration. if the page is a script, add a handler. if the file shoshould be downloaded, add a MIME map.
Solution:

404. You are familiar with it. The file is not found.

In fact, this problem is very simple. The main cause of the error is that the virtual directory in the default configuration of HTTP Handler does not map (mapping) to the file name suffixed with. svc. Svc we all know the importance of the WCF mechanism. If none of the directories are found, an error will be reported !~.

Steps:

Step 1: Open the command prompt box. That is, cmd.

Step 2: In the black screen window, navigate to the directory through cd:

C: WindowsMicrosoft. NetFrameworkv3.0Windows Communication Foundation
Step 3: Enter:

ServiceModelReg-I

II. Window Authentication (window authorization) cannot be seen in IIS)
We all know that in IIS 7.0, there are three authorization methods by default:

Anonymous (Anonymous, enabled by default)

Impersonation (simulated identity, disabled by default)

Forms (close in tacit understanding)

Some children's shoes may feel wrong. It seems that there is still a missing one. Yes, the Authentication method "Windows Authentication" is missing. So some people will ask, is there no more? Or is it hidden by passerby?

It's actually hidden !~~ Microsoft does not use it as the default. If you really need this verification method, you can do the following:

Open the Control Panel, find "Programs and Features", and click "Turn Windows Features on/off", as shown below:

Then...

Select the check box ~~~~

3. Login failed for user 'iis APPPOOLClassic. NET
This occurs when Windows Credentials is used to access the database. The Host Server has an SQL 2008 database and an HTTP request is routed ).

This is mainly because the Classic is changed.. NET Application process attribute identifier. If this happens, you need to map your virtual directory (mapped) to Classic. NET Application.

The process is as follows:

Step 1: Open your IIS Manager (I like to directly input inetmgr in "start"> "run", and then open it. It feels cool !~ Hey .)

Step 2: Select "Application Pools (Application pool)" in the IIS manager, and select "Class. NET AppPools" in the list on the right"

Solutions to some strange problems in IIS 7.5

By the wind, 200 visits, favorites, Edit

Preface

I think any one is based on. NET's Miyagi division will agree to Microsoft products, especially this IIS, which often throws exceptions when you hate accidents, such as when your main products are to be upgraded. Then you will spend a lot of time looking for it and finding it. Sad reminder !~.

The goal of this article is to solve IIS 7.5 in some situations. I hope this will help you.

I. IIS issues with the WCF host (hosting)

Problem description:

If you deploy the WCF Service file ---. svc in IIS 7.5 for the first time, you may encounter the following problems:

The Code is as follows:	Copy code
404-Not Found-The page you are requesting cannot be served because of the extension of the configuration. if the page is a script, add a handler. if the file shoshould be downloaded, add a MIME map.

Solution:

404. You are familiar with it. The file is not found.

In fact, this problem is very simple. The main cause of the error is that the virtual directory in the default configuration of HTTP Handler does not map (mapping) to the file name suffixed with. svc. Svc we all know the importance of the WCF mechanism. If none of the directories are found, an error will be reported !~.

Steps:

Step 1: Open the command prompt box. That is, cmd.

Step 2: In the black screen window, navigate to the directory through cd:

The Code is as follows:	Copy code
C: WindowsMicrosoft. NetFrameworkv3.0Windows Communication Foundation

Step 3: Enter:

The Code is as follows:	Copy code
ServiceModelReg –i

In this case, OK.

II. Window Authentication (window authorization) cannot be seen in IIS)

We all know that in IIS 7.0, there are three authorization methods by default:

Anonymous (Anonymous, enabled by default)

Impersonation (simulated identity, disabled by default)

Forms (close in tacit understanding)

Some children's shoes may feel wrong. It seems that there is still a missing one. Yes, the Authentication method "Windows Authentication" is missing. So some people will ask, is there no more? Or is it hidden by passerby?

It's actually hidden !~~ Microsoft does not use it as the default. If you really need this verification method, you can do the following:

Open the Control Panel, find "Programs and Features", and click "Turn Windows Features on/off", as shown below:

Then...

Select the check box ~~~~

3. Login failed for user 'iis APPPOOLClassic. NET

This occurs when Windows Credentials is used to access the database. The Host Server has an SQL 2008 database and an HTTP request is routed ).

This is mainly because the Classic is changed.. NET Application process attribute identifier. If this happens, you need to map your virtual directory (mapped) to Classic. NET Application.

The process is as follows:

 Step 1: Open your IIS Manager(I like to directly input inetmgr in "start"> "run", and then open it. It feels cool !~ Hey .)

 Step 2: Select "Application Pools (Application pool)" in the IIS manager )"In the list on the right, select "Class. NET AppPools"

Step 3: Open "Advanced Setting (Advanced Settings )".Change the Identity attribute under Process Model to LocalSystem, for example:

4. HTTP Error 500.23-Internal Server Error
Why is such an error? This is largely because it is related to the Managed Pipeline Mode settings.

There are two solutions:

First, change the Managed Pipeline mode of the Application Pool mapped to your virtual directory. By default, your virtual directory will map to the Integrated Managed Pipeline mode in the DefaultAppPool. OK. We need to enable it from the Integrated to the Classic mode.

Method 2: Create a new Application for your virtual directory

Right-click your webpage directory and add an "Application", as shown below:

Select Classic. NetAppPool under Aplication Pool...