I've been asking this question on different developers list that I am on, but I am beginning to think that the real problem is at the system level, rather than a programming level. We've got an ASP.NET 1.1 application on a Windows 2000 Server. (It has the latest service pack for .NET 1.1.) I've got a user who, when running the ASP.NET application gets the following error message: "Unable to validate data. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Web.HttpException: Unable to validate data. Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [HttpException (0x80004005): Unable to validate data.] System.Web.Configuration.MachineKey.GetDecodedData(Byte[] buf, Byte[] modifier, Int32 start, Int32 length, Int32& dataLength) +195 System.Web.UI.LosFormatter.Deserialize(String input) +60 [HttpException (0x80004005): Authentication of viewstate failed. 1) If this is a cluster, edit <machineKey> configuration so all servers use the same validationKey and validation algorithm. AutoGenerate cannot be used in a cluster. 2) Viewstate can only be posted back to the same page. 3) The viewstate for this page might be corrupted.] System.Web.UI.LosFormatter.Deserialize(String input) +118 System.Web.UI.Page.LoadPageStateFromPersistenceMedium() +101 [HttpException (0x80004005): Invalid_Viewstate Client IP: 192.9.200.185 Port: 2192 User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) ViewState: dDwyMDA2NjA4NTcwO3Q8O2w8aTwxPjs+O2w8dDw7bDxpPDE+O2k8OT47aTwyND47aTwyNj47aTwyOT47aTwzMT47PjtsPHQ8O2w8aTwwPjs+O2w8dDw7bDxpPDE+Oz47bDx0PDtsPGk8NT47PjtsPHQ8cDxwPGw8VGV4dDs+O2w8Q2FybWVsYSBTdXRoZXJsYW5kIGlzIGxvZ2dlZCBvbjs+Pjs+Ozs+Oz4+Oz4+Oz4+O3Q8dDxwPHA8bDxEYXRhVGV4dEZpZWxkO0RhdGFWYWx1ZUZpZWxkOz47bDxBcHBvaW50bWVudFR5cGVEZXNjO0FwcG9pbnRtZW50VHlwZTs+Pjs+O3Q8aTwyPjtAPEFnZW5jeTtBTUNJIFJlZ3VsYXI7PjtAPDI7MTs+PjtsPGk8MD47Pj47Oz47dDxwPHA8bDxWaXNpYmxlOz47bDxvPGY+Oz4+Oz47Oz47dDxAMDw7Ozs7Ozs7Ozs7Pjs7Pjt0PHA8cDxsPFRleHQ7PjtsPDUvMjUvMjAwNTs+Pjs+Ozs+O3Q8cDxwPGw8VGV4dDs+O2w8NS8yNS8yMDA1Oz4+Oz47Oz47Pj47Pj47bDxjaGtTcGFuaXNoT25seTtjaGtGaXJzdEF2YWlsO2liR2V0QXBwdHM7Pj6sdXeWWc1xX2wHlzI8a/3bALveSQ== Http-Referer: http://amcis-00/appointments/appointmentshome.aspx/appointmentshome.aspx Path: /appointments/appointmentshome.aspx/SelectOpenAppointment.aspx.] System.Web.UI.Page.LoadPageStateFromPersistenceMedium() +442 System.Web.UI.Page.LoadPageViewState() +18 System.Web.UI.Page.ProcessRequestMain() +447 -------------------------------------------------------------------------------- Version Information: Microsoft .NET Framework Version:1.1.4322.2032; ASP.NET Version:1.1.4322.2032" We do not have a cluster here, so I do not believe that has any bearing on our problem. The strangest thing about all of this is that the problem is localized to just one PC. If the same user goes to any other PC in-house, and logs on as herself, she can run the application just fine. And, if anyone goes to her PC and logs into the ASP.NET application, it does NOT work for them, either. What could the problem be? The IIS server is: Windows 2000 Server, with SP4 for 2000 and the latest service pack for .NET Framework 1.1. The user's PC is a Windows XP Professional machine with SP2. Rod ******************************************************** This Weeks Sponsor: Straymonkey.com Excellent web templates, fonts, and downloads on this new site brought to you by The Kenzig Group http://www.straymonkey.com ********************************************************** To Unsubscribe, set digest or vacation mode or view archives use the below link. http://thethin.net/win2000list.cfm