Are there any updates on web132, the last update was from this morning at 7:00 AM. I do see that my sites are available but my web applications are no longer maintaining view states and my support line has been ringing off the hook all day long not to mention the emails. Thanks, John,
Hello John, I believe that the issue with WEB132 was resolved this morning, we are migrating some servers off the shared host that WEB132 was on, which should reduce total load on the host and increase performance for your web server specifically.
Hi Andcon, Thank you for the update. I do see though that there may still be come configuration errors. For example I logged in and let the system sit for a minute or two and then tried moving on and received the following. We have never had an issue until today, including right now. I have no problem updating my application but I would need the keys to add to the configuration. Validation of viewstate MAC failed. If this application is hosted by a Web Farm or cluster, ensure that <machineKey> configuration specifies the same validationKey and validation algorithm. AutoGenerate cannot be used in a cluster. 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: Validation of viewstate MAC failed. If this application is hosted by a Web Farm or cluster, ensure that <machineKey> configuration specifies the same validationKey and validation algorithm. AutoGenerate cannot be used in a cluster. Source Error: The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL: 1. Add a "Debug=true" directive at the top of the file that generated the error. Example: <%@ Page Language="C#" Debug="true" %> or: 2) Add the following section to the configuration file of your application: <configuration> <system.web> <compilation debug="true"/> </system.web> </configuration> Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode. Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario. Stack Trace: [ViewStateException: Invalid viewstate. Client IP: 142.129.97.170 Port: 54319 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/30.0.1599.69 Safari/537.36 ViewState: 5qTxwY/olw4WDbMeJ0tRbyNomSNVT5yIlpH04BCmGLo55fGyOzmCaO9ZsoMi/gh/v1NEpHRU0hxFccA4ls8UaSQC8QZWex6V5yvGHukfidC2yEfj/XZtbnMNrh9hm018p7XG8rCpiH0DeZqFtMZiTcodthNKc0+x3jx9Mrvx0vBC2dftY8YuOJON8ZUznObnGDfl3FXoBzlZgQbG8xcrCtiW8W1CajL/nSFl1WoKPfVN3c9DrzNFurTglF6SsYKGK1ZZlwgvz3un1fvSEuiCZ/lTCuZit51pixtgQR8qJKp8YvIueD79voZwpVuv/FVmiViS92A4SUxGl2SiJvnIoCQyLPLWPR59byIkqJQZTvB8mAsgAUhGMWHAepqXI60mh+4vgaUJDGCV+fXBmkTRIb+KBQwHmA80Gg4lLaC6ovtSwJIU7vsd4Zb61VCywtBjg99fjL2N90GIMhuple1/K/NNwDM19eWbilaUSCa9X9NKE7SRWeq6qSu93EhNxNyCmHcBaneVYBmpO9wLcpJQu/KXE9/GEJCbAK+SFDcEkqZzLJeA41wDjDUqfcEGfwSxnpktx/e3limD6veqHHeQ4BS4HXo4RGIu6eFxpuWkIzYgsJXDpLrUuGlav3yh5ZG5bruV9jf3+ZZqopj5r05M18OPVHpr0+ZiENY5oIS8JJifsJjed25ML2sO+5PqUR3GlmW7zBrrGTUaeLqbBwNzZTAZ6G4XwU7qeEctuCzUY6Jutz3lcZtlrxKyYYZuwlPID1sJ8UwbF4tr3j8yEnU2rn+QXJxLg3YDnqQwZXmi+f4CqgMbMsoBM/9io1YfJ5XQzpkGz5jH8P...] [HttpException (0x80004005): Validation of viewstate MAC failed. If this application is hosted by a Web Farm or cluster, ensure that <machineKey> configuration specifies the same validationKey and validation algorithm. AutoGenerate cannot be used in a cluster.] System.Web.UI.ViewStateException.ThrowError(Exception inner, String persistedState, String errorPageMessage, Boolean macValidationError) +106 System.Web.UI.ViewStateException.ThrowMacValidationError(Exception inner, String persistedState) +14 System.Web.UI.ObjectStateFormatter.Deserialize(String inputString) +237 System.Web.UI.ObjectStateFormatter.System.Web.UI.IStateFormatter.Deserialize(String serializedState) +4 System.Web.UI.Util.DeserializeWithAssert(IStateFormatter formatter, String serializedState) +37 System.Web.UI.HiddenFieldPageStatePersister.Load() +207 System.Web.UI.Page.LoadPageStateFromPersistenceMedium() +105 System.Web.UI.Page.LoadAllState() +43 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +6785 System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +242 System.Web.UI.Page.ProcessRequest() +80 System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +21 System.Web.UI.Page.ProcessRequest(HttpContext context) +49 ASP.index_aspx.ProcessRequest(HttpContext context) +37 System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +181 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75
Try using the following page to create a set a static machine key for your site. http://aspnetresources.com/tools/keycreator.aspx