IIS Deployment WebService Issues Collection

I. Add a website

Specific steps: Open the Control Panel, select Administrative Tools, and open the administrative tools.

After you open the Administrative tools, open the second Internet Information Services (IIS) Manager.

The interface after opening is as follows:

Right click on the site, add the site, pop up the "Add Site" tab, for example, where the site name chooses its own site name on IIS, the physical path fills in the local address of its website, the IP address and port number are filled in according to your own needs. After clicking the OK button, complete the site additions.

After adding the finished, we test, the site can not access, right click on the newly created site, select the ' Manage Web ' tab below the ' browse ', can access to the success. If unsuccessful, there are some problems below.

1. HTTP Error 404.3-not Found

The page you requested could not be supplied due to an extended configuration issue. If the page is a script, add a handler. If you should download the file, add a MIME map.

In fact, in IIS7 is also the default support SSI function, but we do not check the "server side contains" feature when installing IIS7 in Vista, the method is as follows:

1. Open Control Panel → programs and features → turn windwos function on or off

2. In the Windows Features window that opens, expand Internet Information Services → world wide Web services → application development features, check the box on the front of the server side Include option to determine the installation, as follows:

2. HTTP error 403.14-forbidden The WEB server is configured not to list the contents of this directory

Server error in Application "DEFAULT WEB site/btwo"

Internet Information Services 7.5

In fact, the solution Error prompt page has

· If you do not want to enable directory browsing, make sure that you have configured the default document and that the file exists.

· Use IIS Manager to enable directory browsing.

1. Open IIS Manager.
2. In the features view, double-click Directory Browsing.
3. On the Directory browsing page, in the actions pane, click Enable.

· Confirm that the Configuration/system.webserver/[email protected] attribute in the site or application configuration file is set to True.

Click the Open function in the Action column on the right

Click Enable. In fact, in order to be safe, you don't need to open Directory browsing, just set up the default document.

3. HTTP error 404.17-not The content of the Found request appears to be a script, and therefore cannot be handled by a static file handler.

Check to see if ASP is installed:

Control Panel programs and features turn on or turn off Windows features > Internet Information Services > World Wide Web Services > Application Development features > ASP. NET (see if this is selected)

Such as:

So what's the version of the. NET framework for the application pool?

4.HTTP Error 500.23

As shown in the previous figure, the mapping for ASP. NET 4.0 is missing from the handler mappings and needs to be added.

How to: Open the command line as an administrator and run the following command:

C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis-i

After installing this aspnet_regiis, the application pool selected for this site is: Classic. NET AppPool

Application pools are not for Asp. NET v4.0 and DefaultAppPool;

5, if the page can not display

From the Internet to check the reason, know that it is caused by the firewall. If you "shut down" the firewall directly, you can resolve the problem, but it may be less secure, and we recommend that you add the port number of the default Web site to the "exceptions" item in the firewall. (Control Panel--Security Center--windows Firewall--exception--add port).

6, 404.8-The hidden namespace. The requested URL was rejected because the directory was hidden.

1. Click Start, type Notepad in the Start search box, right-click, and then click Run as Administrator. Note If you are prompted for an administrator password or for confirmation, type the password, or click Continue.

2. On the File menu, click Open, type%windir%\system32\inetsrv\config\applicationhost.config in the File name box, and then click Open.

Locate the <requestfiltering> element in the ApplicationHost.config file, and then find the

3. In the

4. On the File menu, click Save.

5. Quit Notepad.

7. HTTP Error 404.7-not Found

Server-side inclusion, application development features, Web Management Services, IIS configuration.

8.

How do I configure IIS for ASP? allowdefinition= ' machinetoapplication ' section is wrong

It is an error to use a section registered as allowdefinition= ' machinetoapplication ' outside the application level. This error can be caused if the virtual directory is not configured as an application in IIS.

The virtual directory is first established in IIS if it is not created as an application

Right-click on the virtual directory that corresponds to the site, select Properties, and then click Create after the application name.

If it is not resolved, right-click website in IIS,

Click Properties, in the application settings for directory,

Click "Delete" to remove "application name".

If after this, it also appears: "Using a section registered as allowdefinition= ' machinetoapplication ' outside the application level is an error."

If the virtual directory is not configured as an application in IIS,

This error may be caused. "Such an error, remove the <authentication mode=" Windows "/> node in the Web. config file.

If there is no application name in IIS, create it first, and if not, all allowdefinition= in C:\WINDOWS\Microsoft.NET\work\v2.0.50727\CONFIG\machine.config " MachineToApplication "Change to allowdefinition=" Everywhere "

9, the Client Access server in the LAN, Access not?

1. Control Panel->windows Firewall, advanced settings,

Inbound rules, new rule--port--input port

2. Outbound rules, new rule--port--input port

This error is due to insufficient access to the file. The workaround is to click Edit Permissions.

Then select the Security bar and click Edit.

Then click Add a user and set the permission to allow. Or use the following method:

Select the website, then check authentication and click Basic Settings.

Select Connect As.

Then select a specific user, click Settings, enter the user name and password of the computer, click OK. You can then click on the test settings to see the effect.

The reason for this error is that after the framework v4.0 is installed, IIS is enabled, causing the framework to not be fully installed.

The workaround is: Start menu > Command Prompt (Administrator), and then enter and execute the%windir%\microsoft.net\framework\v4.0.30319\aspnet_regiis.exe-i command line.

The problem is that because of the application pool settings, the application pool is not selected when the new site is started, the default is v2.0 version, and the Framework 4.5 is not supported.

The workaround is to select the application pool and then change to the v4.0 version, and the pipeline mode is set to integrated.

The reason for this error is because the TEMP directory under the system directory does not have the appropriate permissions.

The workaround is to go to the Temp directory under the C-drive Windows directory, right-click Properties > Security Bar > Edit > Iis_iusrs permissions to Full control.

The reason for this error is that the default document for the Web site is not configured.

The workaround is to select the site, click the default document, and then add a default page, the application's start page.

Then, after dealing with a number of problems, the deployment was finally successful.

IIS Deployment WebService Issues Collection