Skip to main content

HTTP Error 403.14 - Forbidden


You might see the error “HTTP Error 403.14 – Forbidden” when you have a Web site that is hosted on Internet Information Services (IIS) 7.0 and when you visit the Web site in a Web browser.

Error

Server Error in Application "application name"
HTTP Error 403.14 - Forbidden
HRESULT: 0x00000000
Description of HRESULT : The Web server is configured to not list the contents of this directory.
 

Discussion

This problem occurs because the Web site does not have the Directory Browsing feature enabled, and the default document is not configured.
Now what is this “Default Document”? A default document is the document to which the request will be redirected by the server when the user hits you website domain. That is, the user is typing “http://www.<domain name>” e.g. http://www.anujyadavcse.blogspot.com. Here the user is not typing which page he want the server to serve as part of the request. e.g. http://localhost/Admin.aspx. This generally is the home/login page or the page redirects the  user to some other page but is the target for all such requests.

 

Solution

Though the error message says that the “Directory Browsing” is not configured I reckon that will be the last thing you will do to resolve this issue. As it opens the gate for all to browse your directory.
Thus to solve it you will have to configure a default page.
  1. Start IIS Manager. To do this, click Start, click Run, type inetmgr.exe, and then clickOK.
  2. In IIS Manager, expand server name, expand Web sites, and then click the Web site that you want to modify.
  3. In Features view, double-click Default Document.
  4. In the Actions pane, click Enable.
  5. In the File Name box, type the name of the default document, and then click OK.
dd1
dd2
Hope this will help.

Here is a book which I will refer. This book covers almost all the aspects of IIS 7 and ASP.NET. It is worth reading this one.

Labels:

Comments

Post a Comment

Popular posts from this blog

Laravel XAMPP MySQL artisan migrate install error mysql.sock

In my previous post I wrote about setting up Laravel 4 on Mac with XAMPP . When I tried to use migrations (using artisan) I faced some issue. I will also post about Laravel migrations soon.    php artisan migrate:install Error :                                                     [PDOException]                                       SQLSTATE[HY000] [2002] No such file or directory                                              Solution : We need to tell artisan which mysql we want it to use. For this to work we need to porivde it with mysql.sock which we want it to use. So change your database settings like this: 'mysql' => array( 'driver'    => 'mysql', 'host'      => 'localhost',     'unix_socket' => '/Applications/xampp/xamppfiles/var/mysql/mysql.sock', 'database'  => 'wedding', 'username'  => 'root', 'password'  => '', '
6 comments
Read more

Add (Drop) a new article (table) at publisher in merge replication

Let us add the article using the GUI first. First of all create the table on publisher database. Now right click on the publisher and select properties from the menu. Click on articles. Uncheck the - "Show only checked articles in the list" checkbox, in order to see the newly added table. Select the table as shown in the figure below. Press ok The article has now been added to the publisher We now need to recreate the snapshot Right click the publication and select – “View snapshot agent status”. Click start to regenerate snapshot. Now right click on the subscription (I have both on same server you may have on different servers) and select “View synchronization status” Click on start on the agent. The schema changes will propagate to the client if you have "Replicate schema changes" property set to true in the publisher.
Post a Comment
Read more

Check SQL Server Job status (State) using sp_help_job and xp_sqlagent_enum_jobs

This article is about checking the status of a SQL job. In our work place we have lot of SQL jobs. These jobs will run whole day and are business critical. They will load the data and generate extracts which will be used by business people. Thus, it becomes quite essential to support the system efficiently so that the job finishes in time and as desired. Also, while designing a new system sometimes we need to check the dependency of one job over another. In such scenario we need to check whether a particular job has finished or not. All this can be achieved in SQL Server by using the procedures:- sp_help_job xp_sqlagent_enum_jobs Note: xp_sqlagent_enum_jobs is an undocumented proc inside of sp_help_job and is used extensively to get SQL agent job information. sp_help_job: This procedure gives some insight into the status, and information, about a job. This stored procedure provides information such as last start time, job status etc. Syntax sp_help_job { [ @job_id= ] jo
2 comments
Read more