Solved

Web Site Wont work (HTTP 403)

Posted on 2014-01-09
8
694 Views
Last Modified: 2014-01-15
"This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage."

Asp.net 4.0.

I created a new web site and it if giving error above.  It is exactly like another site that works.  I even tried pointing it at the same directory (web.config, files, etc).  Still doesn't work.

The site will serve htm files, but not aspx files.

The only thing I see different is the handler mappings (in the IIS console).  On the site that works, most are enabled.  On the one that doesn't, most are disabled, including *.aspx.  I don't see how to enable them.  Not sure if this is problem or not.

All permissions are the same.  IIS_USER has full read/write access.

Help!  Urgent!
0
Comment
Question by:No1Coder
  • 5
8 Comments
 
LVL 29

Expert Comment

by:Paul Jackson
ID: 39770383
If you are using Internet Information Services 7.0, after installing ASP.NET you might need to enable ASP.NET in the Internet Information Services (IIS) management console. IIS 7.0 introduces a new security lockdown console, which allows an administrator to selectively enable and disable functionality in IIS. When ASP.NET 4.0 is installed on a computer that uses IIS 7.0, the installation script creates a metabase key for that version of ASP.NET. This metabase key allows ASP.NET to appear in the console as a configurable component. A separate key is created for each installed version of ASP.NET, allowing each version to be separately configurable in the console.

To enable the Web service extension for ASP.NET 4.0


1.Click Start, click Control Panel, click System Security, click Administrative Tools, and then click Internet Information Services (IIS) Manager.


2.If you need to connect to a remote IIS Server, right click the Internet Information Services node and click the Connect... option.


3.Type in the computer name for the remote IIS Server and credentials if necessary.


4.Click the Web Service Extensions folder. The security lockdown console appears in the frame on the right.


5.In the Web Service Extensions window, right-click the ASP.NET v4.X.XXXX, and then click Allow.

http://msdn.microsoft.com/en-us/library/aa560277.aspx
0
 

Author Comment

by:No1Coder
ID: 39770747
I am using IIS7 on W2008.  These instruction to not match my system.

I can get into IIS console.  When I expand the sites, there is no Web Service Extension folder.  Also, my sites do not have virtual directories or applications.  

I was able to take an existing site that works (which has handler mappings enabled), and point at my new web site directory.  If I change the bindings, I can make it work.  There is nothing wrong with my site or web.config, it is the site config is IIS that is bad.

I still don't see how to update the handler mappings.  Also don't understand how to enable the web service extensions, and mentioned in this article.  The instructions don't seem to apply to W2008, IIS7.

I tried connecting to the server from a w2012R2 box.  When I connect, I get a strange dialog (attached).  I installed these.  I still don't see the Web Service Extensions folder on w2012R2 console either.  Still doesn't work.
Capture.JPG
0
 
LVL 3

Expert Comment

by:DaveKeyes
ID: 39771024
Check your app pool for your new site.  You need to set the framework to 4.0, normally it defaults to 2.0
0
How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

 

Author Comment

by:No1Coder
ID: 39771027
The app pool is set to 4.0 (classic)
0
 

Author Comment

by:No1Coder
ID: 39771030
I am pretty sure it is the handler mapping thing.  How to I enable it?
0
 

Accepted Solution

by:
No1Coder earned 0 total points
ID: 39771378
Was able to fix by enabling  read and script permissions on the isappy-dll.  I don't know what turned this off on my server, but enabling fixed.
0
 

Author Closing Comment

by:No1Coder
ID: 39781794
fixed problem
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Join & Write a Comment

A long time ago (May 2011), I have written an article showing you how to create a DLL using Visual Studio 2005 to be hosted in SQL Server 2005. That was valid at that time and it is still valid if you are still using these versions. You can still re…
A safe way to clean winsxs folder from your windows server 2008 R2 editions
This tutorial will walk an individual through configuring a drive on a Windows Server 2008 to perform shadow copies in order to quickly recover deleted files and folders. Click on Start and then select Computer to view the available drives on the se…
This tutorial will walk an individual through the steps necessary to install and configure the Windows Server Backup Utility. Directly connect an external storage device such as a USB drive, or CD\DVD burner: If the device is a USB drive, ensure i…

708 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now