Solutions to some of the weirdest problems in IIS 7.5

Problem Description:

If the first time you are in the IIS 7.5 WCF service file---. svc, you will likely experience the following problems:

404–not found-the page You are requesting cannot is served the because of the extension. If the page is a script, add a handler. If the file should be downloaded, add a MIME map.
Solution:

404, very familiar with it. Just can't find the file.

In fact, the problem is simple, and the main reason for the error is that the virtual directory in the HTTP handler default configuration does not have a mapping (mapping) to the filename with the. svc suffix. Svc We all know the importance of the WCF mechanism. Since the directory can not find, of course, will be the error of Oh! ~

Steps:

First step: Open the Command Prompt box. which is CMD.

Step two: In the black screen window, navigate to the table of contents via CD:

C:windowsmicrosoft.netframeworkv3.0windows Communication Foundation
Step three: Then enter:

Servicemodelreg–i as pictured

Two. Window Authentication (window licensing) not visible in IIS
As we all know, in IIS 7.0, by default there are the following authorization methods in 3:

Anonymous (anonymous, open by default)

Impersonation (analog identity, closed by default)

Forms (Close in tacit agreement)

As shown in figure:

As shown in figure:

Perhaps some children's shoes will feel, wrong ah, as if there is a lack of one. Yes, what is missing is the "Windows Authentication" method of authentication. Then, some people will ask, is not it? Or is it hidden by a passerby?

Oh, is actually hidden! ~ ~ Microsoft This child has turned it off as default appears. If you really need this type of validation, you can do the following:

Open Control Panel, and then locate "Programs and Features" and click "Turn Windows Features On/off" as follows:

And then...

You can check it out.

Three. Login failed for user ' IIS apppoolclassic. NET
This occurs primarily when using Windows Credentials to access a database. The host server (host server) has a SQL 2008 database and has HTTP requests routed (routed).

The main reason for this is to change the process attribute identity for this Classic. NET application, so if this happens, then you need to map your virtual directory (mapped) Classic. NET application.

The process is as follows:

The first step: Open your IIS Manager (I like to be directly in the "start" → "run" in the typing inetmgr, and then open, feel very cool!) ~ Xi Hee. ）

Step two: In IIS Manager, select "Application pools (application pool)" and in the list on the right, select "Class. NET AppPools"

Solutions to some of the weirdest problems in IIS version 7.5

2012-06-12 09:36 by the wind roaming, visits, Collection , Edit

Objective

I want any one based. NET's Miyagi division will agree to Microsoft's products, especially the IIS, often when you hate surprises, such as when your main product is being upgraded. Then you will spend a lot of time looking for, find the everlasting. Sad reminders! ~

The goal of this article is primarily for IIS 7.5 solutions in some cases. I hope this will help you.

One. IIS about WCF Host (hosting) issues

Problem Description:

If the first time you are in the IIS 7.5 WCF service file---. svc, you will likely experience the following problems:

The code is as follows	Copy Code
404–not found-the page You are requesting cannot is served the because of the extension. If the page is a script, add a handler. If the file should be downloaded, add a MIME map.

Solution:

404, very familiar with it. Just can't find the file.

In fact, the problem is simple, and the main reason for the error is that the virtual directory in the HTTP handler default configuration does not have a mapping (mapping) to the filename with the. svc suffix. Svc We all know the importance of the WCF mechanism. Since the directory can not find, of course, will be the error of Oh! ~

Steps:

First step: Open the Command Prompt box. which is CMD.

Step two: In the black screen window, navigate to the table of contents via CD:

The code is as follows	Copy Code
C:windowsmicrosoft.netframeworkv3.0windows Communication Foundation

Step three: Then enter:

The code is as follows	Copy Code
Servicemodelreg–i

As shown in figure

That's OK.

Two. Window Authentication (window licensing) not visible in IIS

As we all know, in IIS 7.0, by default there are the following authorization methods in 3:

Anonymous (anonymous, open by default)

Impersonation (analog identity, closed by default)

Forms (Close in tacit agreement)

As shown in figure:

Perhaps some children's shoes will feel, wrong ah, as if there is a lack of one. Yes, what is missing is the "Windows Authentication" method of authentication. Then, some people will ask, is not it? Or is it hidden by a passerby?

Oh, is actually hidden! ~ ~ Microsoft This child has turned it off as default appears. If you really need this type of validation, you can do the following:

Open Control Panel, and then locate "Programs and Features" and click "Turn Windows Features On/off" as follows:

And then...

You can check it out.

Three. Login failed for user ' IIS apppoolclassic. NET

This occurs primarily when using Windows Credentials to access a database. The host server (host server) has a SQL 2008 database and has HTTP requests routed (routed).

The main reason for this is to change the process attribute identity for this Classic. NET application, so if this happens, then you need to map your virtual directory (mapped) Classic. NET application.

The process is as follows:

The first step: Open your IIS Manager (I like to be directly in the "start" → "run" in the typing inetmgr, and then open, feel very cool!) ~ Xi Hee. ）

Step two: In IIS Manager, select "Application pools (Application pool)"and in the list on the right, select "Class. NET AppPools"

Step Three: Open its Advanced Setting (Advanced settings). Change the IDENTITY property below the process model to LocalSystem, as shown in the following figure:

Four. HTTP Error 500.23-internal Server error
Why is there such a mistake? This is largely because it is related to the managed piping mode (Managed Pipeline mode) setting.

This has 2 main solutions:

First: Change the managed Pipeline mode of the application pool (application pool) for your virtual directory mapping. By default, your virtual directory will map to the integrated Managed pipeline mode under DefaultAppPool. Okay, we need to get it from integrated to Classic mode.

Method 2: Create a new application for your virtual directory

In your page directory, right-click, add a "application", as follows:

Choose Classic.netapppool under Aplication pool ...