May 21, 2008 at 8:15 am
This is certainly one that has stumped me.
The only thing I can say is that if I change AsyncRendering to true, or omit it, then I get the problem.
Luckily for me this is only for my personal use. I am planning to publish lots of statistics on my local football (soccer) team - a good way of self teaching, hence the third party hosting.
My employers host internally via the local domain - which seems to work without the "ASP.NET has expired" message.
Cheers,
Lee.
September 26, 2009 at 12:22 am
Hi All,
I hope this article will help to fix this issue.
http://balanagaraj.wordpress.com/2009/09/25/session-has-expired-in-asp-net/
September 26, 2009 at 7:10 am
Sorry about now posting an update on this thread but i did solve the problem... it turned out to be a picture that i was referencing...I saved the link to the pictures in the database and then the picture was saved onthe webserver where the application used to run.. but since we changed the servers and domain names and since the application was looking at the link that didnt exists in the domain.. Asp.net gave up and threw this error..
So once i change the link of those picture everything worked as normal...
I also tried inproc thing that was mentioned by Previous poster but it didnt help at all..
So anyways thanks everyone for looking into this thread and replying to it..
Thanks,
Karen
September 28, 2009 at 8:07 am
Hi, Karen Roslund.
If your webserver name contains "_" you will see this weird error. Try http://IPAddress/AppName.
I had the similar error and this fixed it.
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply