There are possible work-a-round and solution to work upon "session auto expire earlier" issue. Setting SessionTimeOut in web.config would no be enough to have your session persist for the said time or you want it to be.
Here I have found some solution which worked in my case:
[1] go to IIS/inetmgr > right click the website > properties
> Virtual Directory/Home Directory Tab > Click Configufation
button > Select Option Tab > Check "Enable Session State"
CheckBox and Set the Sesion Timeout Minutes you want it tobe > Apply
the changes made by clicking OK.
[2] next is, just check the
application pool under which the site is running. > goto that
application pool > right click > properties > performance tab
> check the CheckBox which is under "Idle TimeOut" Panel (first
checkbox) and set the TimeOut you want it tobe.
Hope it would help some one!!
Generally, I would like to blog post any errors that I face duing development. So that it would be helpful to me for my future reference in case I face it again as well as for the sake of any blog readers who may face same error.
Talking about the error "Invalid URI: The hostname could not be parsed error": This the same and common error I faced previously some times back and which I also stated in my blog entry DotNetNuke - Invalid URI: The hostname could not be parsed
This time I was about to run a DNN application which is configured from my local server to live application server when I faced the same error. I tried the same work-a-round which I stated in my previous blog entry. But, this time that didn't work even after investing some hrs investigation. I noticed that portal alias was not getting changed in the url when running the application. So, I tried to change the database name (in web.config connectionstring) to some arbitrary (i dont know why!!) names and ran the applicaiton again. Obviously, this will give sql server related error, as it would not found that catalog in sql server. After running the application once with wrong database name, I again changed the database name in connection string to correct name and recycled the application pool. Great!! This time it worked any anyhow. (again, I dont know, Why!!)