Session Time out Problem in Asp.net......Please help

Question

1.00/5 (1 vote)

See more:

Hello FRIENDS,

Have a good day all of you.

Facing trouble with session timeout.
----------------------------------

I have created a web application in Asp.net c#, Sql Server 2005.

but am facing a problem with session timeout.

my first page is login.aspx, this page is used to access/open the application.

after user login, if his/her username and password is correct. it will redirect to the main pages, here he will see/access all the webpages.

Suppose, if i stay idle for some time on this application....it shows an error.

THIS IS THE ERROR...

=================================================================

Object reference not set to an instance of an object.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error:

Line 18: lblDate.Text = System.DateTime.Now.ToLongDateString();
Line 19: lblTime.Text = System.DateTime.Now.ToShortTimeString();
Line 20: lblWelcomeMSG.Text = Session["UserName"].ToString();
Line 21: }
Line 22: }

====================================================================

Please help me and SUGGEST me, how to solve me this problem.

Thanks in Advance.

Posted 10-Jan-13 5:04am

Software Engineer 892

Add a Solution

Comments

Richard C Bishop 10-Jan-13 11:12am

Do you have the timeout attribute set to anything in the session tag of the web.config file?

Software Engineer 892 10-Jan-13 11:17am

No Sir, Please help me how to add this.

Richard C Bishop 10-Jan-13 11:51am

Here is the code to add to your web.config file. It belongs between the SEYSTEM.WEB tags. SESSIONSTATE timeout="20". However, the solution below is probably a better way to handle this.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2013-01-10T05:27:00

You can increase the timeout, but you shouldn't have to.
To increase it, see here: http://msdn.microsoft.com/en-us/library/h6bb9cz9(vs.80).aspx[^]
But you should cope with the session timing out gracefully, by checking, or by using a try...catch block.
Oh, and by the way, never read the date and time twice - read it once, store it in a variable, and use it twice instead:

C#

try
   {
   DateTime now = System.DateTime.Now;
   lblDate.Text = now.ToLongDateString();
   lblTime.Text = now.ToShortTimeString();
   lblWelcomeMSG.Text = Session["UserName"].ToString();
   ...
   }
catch (Exception ex)
   {
   // Log it, or report to the user that he needs to log in again.
   }

If you read twice, you can get different days, months, or even years and this can cause subtle bugs which are hard to track down. In this case, it just presents a bad date and time combo to the user, but if you use similar code for databases you can truly mess up your data!