Skip to main content

ASP.NET formsauthentication - Images not displaying

Few days back I was working on an ASP.NET website. The website uses custom formsauthentication. I had the login page under the root directory and other pages and images etc in separate folders. So the structure was something like this:-

Folder_Application Root
      Folder_Pages
      Folder_MasterPages
      Folder_Images
      Folder_Scripts
      Folder_Controls
File_Login.aspx                         //Files
File_Web.config

Problem statement:- 
After publishing the website on the server I was not able to see the Images which were present on the login page. 

Solution One:-
I realized that I am using formsauthentication so I must allow anonymous access to the Images folder in order for the images to show up on login page. So I did that.
  
I was assuming that everything will be cool now. But it was not. As usual :) for we developers :).

But surprisingly things were working fine on ASP.NET internal server. This shows there is something wrong with the server and not the method. So I started looking into the IIS, but it was of no help. Then I thought of checking the IIS roles and services which were installed. I came across a service - Static Content. This service was not installed. It seems like the culprit. So I installed it and bingo. Everything started working as i wanted.

Summary:-

When using formsauthentication and if you have images on your login page, give anonymous access to your images folder.

While publishing website on the IIS web server do check whether static content service is installed or not. It will be needed.

To check the services installed. On windows 7 go to control panel -> add remove programs -> turn windows features on or off -> iis and on windows server 2008 you can check this using server explorer.

Happy Coding!!! Hope this will be of some help.

Comments

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'  => '', '

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.

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