Usually then the viewstate can't be authenticated, it's just IIS thinking it's been given a "different" viewstate" for the same page. I "think" this is a security measure and can be disabled in the web.config. I had some problems with it in the past (when getting pages with Server.Execute).
My biggest gripe with ASP.NET is the seemingly chaotic pattern that event handlers execute. Probably because I haven't learned enough about it, yet. :P E G wrote: >Random errors when Viewstate is enabled on a page. Page loads, user remains >idle for a long enough time that their worker process is terminated. Then >the user fires off an event on the page that calls a postback. The engine is >then unable to authenticate the viewstate because it's using the wrong key >phrase.......or something to that affect. > >Read some more about it here if you are interested: > >http://tinyurl.com/cgfsh > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Save $10 Download ZoneAlarm Security Suite http://www.houseoffusion.com/banners/view.cfm?bannerid=66 Message: http://www.houseoffusion.com/lists.cfm/link=i:5:158838 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/5 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:5 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.5 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
