VWD 2008 Express. IIS 6.0. Forms Authentication.My web site uses forms authentication (in case that makes a difference). Folks who are using the site indicate that it is timing out on them (logging them out) before they can finish some entries. How can I increase the timeout period? The following is my web.config file in my root directory:
[Code]....
Here is the web.config in the subdirectory to which all users are directed at login:
I'm working with ASP.Net web services and am having a problem with a long-running process that takes about 5 minutes to complete, and it's timing out. To fix this, I was able to set the executionTimeout on the server's web.config to 10 minutes, and then set the .Timeout property on the Web Service object to approximately 9 minutes. Now, I'm worried that this may possibly cause some other web service calls to sit there for 10 minutes before they time out rather than the previous 90-100 seconds. I know the default on the client side is 100 seconds, but wasn't sure if updating the server's timeout setting would affect this.
Bottom line is - Is it safe to update the server's timeout setting to a long amount like 10 minutes, and rely on the default timeout on the client, or could this end up causing some problems?
If I have not activity in browser for about 10 mins, shouldn't the Session object be removed. But after 10 mins I can still access the Session variable. Am I missing something here?
EDIT:
If I access a session variable after 10 mins as shown below shouldn't I get NULL
var myObj = Session["MyKey"] as MyClass; mObj is not NULL after 10 mins.
I'm using ASP.NET 3.5 (c#) with SQL Server 2008 server. Recently, I started getting error "Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.".
After looking at forums for solutions, I added the below common code to my application.
[Code]....
However, intermittently, I'm still getting the timeout error. I added the logging to see where error is occuring. And found that before executing one of the query, it is giving this error. Now, my assumption is that I should have received this error after runnign query for 600 seconds (10 minutes) since I set it in the above function. But the timeout error is occuring instantaneously within 1 second itself. In the log, I printed one line above & after the query to identify how much time it would take. Surprisingly, the log says that 9:00 AM "Before query execution" & at 9:01 AM "timeout expired...."
I have creetaed OSDesign using VS 2005.Later,I have created device application and I am using emulator created from OSDesign as device for connection.When I debug it gives error as, This operation returned because the timeout period expired
I have the problem of Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
I'm getting the following error after uploading my site on live server:Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.i'm using the following code:
public static IQueryable<Property> Properties(string name, string city, string state, int pageIndex, int pageSize, ref int total) { ServerDataContext server = new ServerDataContext(); total = server.Properties.Count(x => x.Name.StartsWith(name) && x.City.StartsWith(city) && x.State.Contains(state)); return server.Properties.Where(x => x.Name.StartsWith(name) && x.City.StartsWith(city) && x.State.Contains(state)).Skip(pageIndex * pageSize - pageSize).Take(pageSize); }
Error occured: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
I have stored procedure, execution time is just 1 sec, returns 20 rows.I droped it on my LINQ2SQL diagram (.dbml).But when calling it from LINQ2SQL it hangs and after some time throws an exception: "Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding."
am getting "Time Out Expired,The Timeout period elapsed prior to obtaining a connecttion from pool".Please suggest suddenly i am getting this error in 10% of the pages.
Is there any way to stablish a global timeot when calling webservices from Javascript in an ASP.NET application?Now the only way I know is setting the timeout manually for each service: service1.set_timeout=100000;
have a website which as far as I know has the following timeout settings:1) In Web.config, FORM's authentication timeout="10"2) In Web.config, MEMBERSHIP's userIsOnlineTimeWindow="10"3) Assigned in Global.asax on Session_Start(): Session.Timeout =10;In the past I had problems because at least 1) and 3) weren't in sync, not sure about 2).
Do these 3 have to be in sync and if so, is there a way to set the timeout once and to have it applied to all 3? I deploy my website to many clients and each may want a different timeout, so I'm looking for a dynamic method to set this, perhaps after loading the timeout period from the db or settings file.
I am using Asp.net 2.0 and C#.I have 2 webpages, which contain lot of questionnaires. I have a submit button in my 2nd web page. I want to set a timer in the page, so that after 2 minutes, if the user has not completed the questionaire, i want to click on the submit button automiatically.
I have a site that when a user logs in it sets their initials into a session variable and sets the timeout value like so:
[Code]....
I want the user to be logged in for 3 hours. This does not work, the session expires after a short period of time, maybe 20 minutes. What do I need to change to make this page level validation work?I have tried setting in web.config also, but this doesn't work either.
The constructors for manually creating FormsAuthenticationTicket objects force us to set an "expiration" value, and this value overrides the "timeout" setting in web.config in my tags, which is not what I want, because now the user doesn't timeout. The "session" just expires at the given time.I need to manually create my ticket for UserData reasons, and it is just the way I decided to build my app. I guess I could spend a whole lot of time and redo the way my app. authorizes, and store the "userdata" elsewhere... but this seems extremely tedious for something so small..Is there anyway to manually create an Auth Ticket and still maintain timeout settings?! And by timeout, I mean resetting the timer on user activity. Not a fixed timeout!
I want to allow admins to be logged in for longer than normal users. I don't see a hook for setting the cookie timeout programmatically or in a role-based way. Is this possible in ASP using Forms Authentication?
i am working on an application ,i have hosted on server. everything going fine . i have added a code to set session timeout in webconfig . but its expire default time .
I'm used to public facing websites that use ASP.net membership - and when the SESSION vbl's timeout we re-direct to the login page like this
Code:
If Session("Yr") Is Nothing Then Page.Response.Redirect("~Login.aspx?reason=timeout") End If
And on the login page we check for that reason and put up a label on the screen saying that things timed out to protect sensitive data. This works fine. Now I'm doing a web site that's in house - and when the users connect they get a BROWSER POP-UP to login with the DOMAIN UN/PW - and once they get past that my default page redirects them to a home portal page. What do I do when my session vbl's expire now? I can't redirect to a login page - there is not one. How do I cause the re-authentication to happen more naturally?
is it possible to set a user defined timeout value on an asp.net website...i have a table that stores the time out value for each user of my website...i need to set the time out based on who logged in...i know that the default aspnet timeout setting is 20 mins of inactivity...is there any way i can circumvent this...and yes i do need to show a modal when the timeout expires and need to reset the timeout value if the user wants to continue the session or log them out if they choose not to continue...
We have the timeout value set to 120 in our <form> tag within the web.config. We do not have a session timeout set.. and we have various connection strings.
We are having a problem where a session variable will disappear (become NULL) .. but, the form evidently remains 'open'.. or no re-login is required..... so, my question(s):
1. what is the relationship between form timeout and session timeout
I have a site that is using Forms Auth. The client does not want the site session to expire at all for users. In the login page codebehind, the following code is used:
// user passed validation FormsAuthentication.Initialize(); // grab the user's roles out of the database String strRole = AssignRoles(UserName.Text); // creates forms auth ticket with expiration date of 100 years from now and make it persistent FormsAuthenticationTicket fat = new FormsAuthenticationTicket(1, UserName.Text, DateTime.Now, DateTime.Now.AddYears(100), true, strRole, FormsAuthentication.FormsCookiePath); // create a cookie and throw the ticket in there, set expiration date to 100 years from now HttpCookie cookie = new HttpCookie(FormsAuthentication.FormsCookieName, FormsAuthentication.Encrypt(fat)) { Expires = DateTime.Now.AddYears(100) }; // add the cookie to the response queue Response.Cookies.Add(cookie); Response.Redirect(FormsAuthentication.GetRedirectUrl(UserName.Text, false));
When I log into the site I do see the cookie correctly being sent to the browser and passed back up: However, when I walk away for 20 minutes or so, come back and try to do anything on the site, the login window reappears. This solution was working for a while on our servers - now it's back. The problem doesn't occur on my local dev box running Cassini in VS2008.
steps for using IIS to host a website I created in visual studio? I have the files in a folder called HelpDesk under inetpub and have the path correctly specified in IIS, but IE is stating it cannot display this webpage.
