61
votes

Possible Duplicate:
ASP MVC in IIS 7 results in: HTTP Error 403.14 - Forbidden

I published my application on server. When I enter my domain i got this error:

403 - Forbidden: Access is denied. You do not have permission to view this directory or page using the credentials that you supplied.

What's happend?

4
is your iis pointing to the correct place? i once got this error when i (mistakenly) pointed to an empty folder.robasta
our problem was missing global.asax file in published deploy foldersasjaq
Could you please have a look at my answer on ASP MVC in IIS 7 results in: HTTP Error 403.14 - Forbidden.Murat Yıldız
I had the same problem accessing http while issue was "Require SSL Enabled".wast

4 Answers

14
votes

Are you hosting the site on iis? if so make sure the account your website runs under has access to local file system?

Straight from msdn .....

The Network Service account has Read and Execute permissions on the IIS server root folder by default. The IIS server root folder is named Wwwroot. This means that an ASP.NET application deployed inside the root folder already has Read and Execute permissions to its application folders. However, if your ASP.NET application needs to use files or folders in other locations, you must specifically enable access.

To provide access to an ASP.NET application running as Network Service, you must grant access to the Network Service account.

To grant read, write, and modify permissions to a specific file

  • In Windows Explorer, locate and select the required file.
  • Right-click the file, and then click Properties.
  • In the Properties dialog box, click the Security tab.
  • On the Security tab, examine the list of users. If the Network Service
  • account is not listed, add it.
  • In the Properties dialog box, click the Network Service user name, and in the Permissions for NETWORK SERVICE section, select the Read, Write, and Modify permissions.
  • Click Apply, and then click OK.

Click here for more

13
votes

In addition to the answers above, you may also get that error when you have Windows Authenticaton set and :

  • IIS is pointing to an empty folder.
  • You do not have a default document set.
9
votes

I just had this issue, it was because the IIS site was pointing at the wrong Application Pool.

4
votes

I had the same issue (on windows server 2003), check in the IIS console if you have allowed ASP.NET v4 service extension (under IIS / ComputerName / Web Service extensions)