This article mainly for you in detail the vs2012/vs2013 Local publishing site encountered problems, HTTP error code solution, with a certain reference value, interested in small partners can refer to
HTTP Error 500.19 Internal Server error, HTTP error 403.14 Forbidden, HTTP error 404.17 not found,3 problem resolution, the details are as follows
1. Unable to read configuration file due to insufficient permissions
Workaround: Right-click the site and select Edit Permissions. Security--edit--add--advanced--Find--everyone now.
2. Missing site Default page
Workaround: This is because the default start page for the site is not set. You need to add the default start page in the default document. Right-click Default document--Open function--Add, enter the default start page name of the publishing site.
3. NET version inconsistency
Workaround:
Enter the application pool interface
In the application pool, right-click the Web site you want to publish--Advanced Settings ——. NET Framework version set to v4.0
Of course, such published sites, but also limited to mutual access within the local area network, if you want to be able to access the network, can be routed through the server and related settings, there is no redundancy here.