My website never logs time out even after I set time out both in Autentication and in session state. What I did wrong? Here is my settings in web.config file
<authentication mode="Forms">
<forms loginUrl ="/default.aspx" name=".ASPXFORMSAUTH" timeout ="1">
</forms>
</authentication >
<sessionState mode="InProc" cookieless="AutoDetect" timeout="1" />
I've been running a customer's webapplication using automatically generated email for some time, being hosted on our company's web server. Send mail was done using the System.Net.Mail API using a 3rd party SMTP server. The configuration has been done in the web.config in the system.net section, something like this:
<system.net>
<mailSettings>
<smtp>
<network host="mail.jazzforum.at" userName="myUsername" password="myPassword" port="25"/>
</smtp>
</mailSettings>
</system.net>
Everything worked fine until we had to migrate to another hosting service; since then, send mail didn't work any longer with symtomatic "timeout" exceptions. We also tried using gmail and changing/omitting explicit port number specification, without any success. The server is running IIS 6 (Windows Server 2003 R2).
I just published my website to my webhost, and for some reason it's giving me errors. So I copied the solution and it works correctly.
What could the problem be? I think a possible problem may be that there's a process that creates a directory so it can copy files. By copying everything from the solution to the ftp, everything works correctly. If I publish the site, it somehow does not create the directories.
Is there something I'm not doing correctly? I've published in a local folder, and then copied to the FTP. I've also published directly to the FTP. Neither of them work.
[Code]....
I have an issue to where my users are logged into my system but thier session is null so when they try to do something in the system after 20 minutes, i get null reference expceptions because my session is gon
What is the best practice for handleing the session, should i kick the users out before thier session ends and when they log back in thier session will return or atleast a new one will be created right? How should I handle this?
In my site on every load some session is made through url and single page(say xyz.aspx) is call every time and on the basis of url we create session. When i click on a href tag , page start reloading ,url we created is accurate but data doesn't change every time, means some time it show data on first click, but some time after 3 or 4 click.
I say problem is weird because when i run this on my local server there is no problem, when i run this on my project (visual studio) there is no problem , but when i up this project on my online server it show this kind of error but not every time .
I use data caching to fill dataset. There is no problem in this website since we created this (more than 1 year) and we don't made any change on this page but suddenly it starts showing this kind of error so what kind of error this is.
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
2. how do I set session timeout
I have created a crystal following your article which url is
[URL]
It is working fine on local machine but when i upload it on the server it is not working. Crystal Report is showing but data is not showing in the crystal report.
We have an ASP.NET 2.0 site in which we use ASP.NET login / authentication controls.
Our users currently timeout after approx 20 minutes, forcing them to log back in, and this appears to be causing downstream errors in our application.
I have tried increasing the SessionTimeout value to 120 mins (<sessionState timeout="120" />) in the site's web.config file, and the "<membership userIsOnlineTimeWindow="5000" >" value in the web.config is set to 5000 minutes.
These are the only values / settings I can think of to affect this behaviour.
how to set the application timeout in web.config or iis?
View 9 RepliesIn my website, the session is expired after 5 minutes. I need to extend the seesion state to minimum 4 hours. Currently, in web.config file I used the following code.
<sessionstate cookieless="false" timeout="1440"></sessionstate>
But its expired after just 5 minutes.
We have a asp.net application where users will apply for jobs online. When users fill out the form the page isn't timing out the session. If a user goes back to the main page the last user's information is still available.
I have setup many websites and have never had to make any changes on IIS, under the configuration within the website. The default is 20 minutes we can change it to 8 or 10, but I think this issue should be taken care of in the code. The setting will affect the entire site instead of the pages that need to timeout.
What is the best way to do this within the code?
I recently inherited an asp.net website made up of multiple .aspx and .ascx pages and being rather new to web development and especailly asp.net. I have the site create a cookie upon login to automatically log users back in if the page times out on them while they're entering information.
I need the site to automatically log users out when the site is closed. Obviously using the me.close event on each page won't work because we don't want it to log people out every time they navigate to a new page in the site.
I've tried setting the timeouts in both IIS and in the files of the website to longer but it doesn't seem to have an effect.
Is there an easy way to automatically log users out when they leave the site but not when they navigate from page to page.
The error: "DCOM {guid} didn't register within the requied timeout" seems to be a common problem when I search on the internet.I have searched through forums and google and I believe my error is being caused by something else rather than the solution provided for this type of error.To give a brief backgorund, I have developed an ASP.NET application that uses a thrid-party API COM Interop assemblies (.tlb files which already existed when the 3rd party application was installed). The web application was initially hosted on IIS 5.0 in
WInXP and the .exe file gets launched when I run the ASP.NET website through the IIS server.
I have a testproject and the forms timeout specified in web.config overrules the timeout which I set in FormsAuthenticationTicket. According the documentation, the timeout (expire date) in FormsAuthenticationTicket must override the timeout in web.config.
Documentation found on:
[URL]
[Code]....
Here is my code:
Web.config:
[Code]....
Login.aspc.cs:
[Code]....
Now, when I login, i get redirected after 1 minute of inactivity. This isn't supposed to happen, right? I have to be redirected after 2 minutes.
I tried to insert 3 xml files into database.But while i am trying to insert half of the value gets inserted after that i am getting error like
"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."
How to resolve this error....
I am trying to build an ASP.NET site that allows each user to set their own session timeout value. Basically from the user's perspective if they set their timeout value to 30 then that means that after 30 minutes of inactivity they are required to re-authenticate. If they set their timeout value to 0 then that means that they can leave the browser open as long as they want and their session never expires - they never have to re-authenticate. This is different than "remember me" functionality. If they close their browser they will have to re-authenticate.
Currently I am using Forms Authentication in my application and I have one object that I am storing in ASP.NET session. This object is a custom User object that has a number of different pieces of information about the current user.
What code would I need to write so that after successful login, the system has the proper authentication ticket and the proper session expiration value? I keep thinking I have this working and then I notice weird time outs where the system seems to think I am authenticated but my session has expired.
Currently on my login page I am using an ASP.NET login control. i have custom code in the Login_Authenticate event to authorize the user. Then I have the following code in the Login_LoggedIn event to set the auth ticket.
[code]....
I'm currently developing a web application where everything works fine in the visual studio web server. It authenticates the user, access the database, writes to it, etc.
After I wrestled yesterday to publish it to my local iis, a subject I admit I have little to no experience of doing, suddenly the membership of the website started to not authenticate the users.
At first I suspected maybe the app wasn't accessing SQLServer, or that the data with the users I had in the asp.net membership database was erased when I uploaded the website.
So I stopped iis, i attached the db file to my local sql server, and I can see that all the users are there just like I uploaded them. I also can see the website can access another database with micellaneous contents just fine.
The loging controls don't tell me there's any problem either, they just show a message telling the user that the login attempt wasn't successful.
So, here's what I remember I did to make the app work as it wasn't even doing that when I first uploaded it.
I used the asp.net_regiis tool to copy website scripts to the website.
aspnet_regiis -sn <path>
then I deleted the website, uploaded again from VS. this time it shows in the browser but it doesn't authenticate the users.
The application isn't precompiled, I just uploaded it.
I move a file from server to another server .in local it is woking fine .but in production it is getting error
The remote server returned an error: (408) Request Timeout.
i used like this ..
objWebClient.UploadFile(ClientLocation,
"POST", fileName.ToString());
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 .
<sessionState mode="InProc" timeout="524601"/>
since a have an app, that makes heavy use of AJAX (jQuery), I faced a problem of session timeout.
After a little bit of googling I found something like :
[Code]....
In the refresh page I have just this code :
[code]....
jQuery indeed calls refresh page, writes "success", however- session times out.
Am I doing wrong something? Is there a better way to prevent session time out?
I am getting this error:
"timeout expired. the timeout period elapsed prior to obtaining a connection from the pool"
when I am testing my webiste on production server. Its working perfectly on my local machine but not on production.
Sometimes it works and sometimes not.
My host moved my website to a new server. The DNS configuration is correct but the website is still down and I'm getting this message
"unable to open website at www.aboutmecfs.org. Internal Server error"
I want to make a 2nd website and am using a copy of the site files from my 1st site built for me, I added them via FTP to the hosting company. I realise when I edit the new site via the CMS it is editing both sites plus when I try to change anything to the CSS file I get the following error -
C:inetpubvhosts*****mysite******httpdocsapp_themessiteStyleSheet.css
So my questions are what do I need to change to be able to deploy a new site with the files I have to make a new site?I also don't understand where the password is coming from, I can see the User ID comes from the database. in the Asp.net connection strings are the following:
site Data Source=sql7.hostinguk.net;Initial Catalog=***;User ID=***;Password=*** - Where is this password coming from?
membership Data Source=sql7.hostinguk.net;User ID=***;Password=***;persist security info=False;initial catalog=***;
I am trying to force to show to the Logon popup when the session is timeout in Integrated Windows Authentication Enabled website. The session_timeout is firing during the session timeout, but the User.Identity.IsAuthenticated is true. How force to use the Windows Logon Screen when the session is timeout.
View 4 RepliesI need to have a copy of all my pages, bin fold, data folder, etc stored in a folder in the root of project called installation.
Once I have copied the contents of my web site into the installation folder how can I tell the complie/run process to ignore that folder ?