Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. "Failed to load viewstate" error message when you trigger an AxGridView control that has the "MainGrid.ShowFilter" flag set to false in Enterprise Portal in Microsoft Dynamics AX 2009 Service Pack 1

"Failed to load viewstate" error message when you trigger an AxGridView control that has the "MainGrid.ShowFilter" flag set to false in Enterprise Portal in Microsoft Dynamics AX 2009 Service Pack 1

View products that this article applies to.

This article applies to Microsoft Dynamics AX for all regions.

↑ Back to the top

Symptoms

You set the "MainGrid.ShowFilter" flag to false in an AxGridView control project in Microsoft Visual Studio for Enterprise Portal in Microsoft Dynamics AX 2009 Service Pack 1 (SP1). You apply the AxGridView control project in Enterprise Portal. In this situation, when you trigger the control, you receive the following error message:
System.Web.HttpException: Failed to load viewstate. The control tree into which viewstate is being loaded must match the control tree that was used to save viewstate during the previous request.

↑ Back to the top

Resolution

Hotfix information

A supported hotfix is available from Microsoft. There is a "Hotfix download available" section at the top of this Knowledge Base article. If you are encountering an issue downloading, installing this hotfix, or have other technical support questions, contact your partner or, if enrolled in a support plan directly with Microsoft, you can contact technical support for Microsoft Dynamics and create a new support request. To do this, visit the following Microsoft website:
https://mbs.microsoft.com/support/newstart.aspx
You can also contact technical support for Microsoft Dynamics by phone using these links for country specific phone numbers. To do this, visit one of the following Microsoft websites:

Partners
https://mbs.microsoft.com/partnersource/support/
Customers
https://mbs.microsoft.com/customersource/support/information/SupportInformation/global_support_contacts_eng.htm
In special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to any additional support questions and issues that do not qualify for the specific update in question.

↑ Back to the top

Installation information

If you have customizations for one or more of the methods or the tables that are affected by this hotfix, you must follow these steps:
  1. Review the changes that are documented in the .xpo file.
  2. Apply these changes in a test environment before you apply the hotfix in a production environment.


For more information about how to install this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:
893082 How to install a Microsoft Dynamics AX hotfix

Prerequisites

You must have Microsoft Dynamics AX 2009 Service Pack 1 installed to apply this hotfix.

Restart requirement

You must restart the Application Object Server (AOS) service after you apply this hotfix.

File information

The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
File nameFile versionFile sizeDateTimePlatform
Axupdate.exeNot applicable61,67226-Jun-1222:24x86
Kb2724141.xpoNot applicable12,202,69226-Jun-1222:14Not applicable
Metadata.xmlNot applicable7226-Jun-1222:14Not applicable
Kb2724141.xpoNot applicable12,202,69426-Jun-1222:14Not applicable
Metadata.xmlNot applicable7226-Jun-1222:14Not applicable
Kb2724141.xpoNot applicable12,202,68626-Jun-1222:14Not applicable
Metadata.xmlNot applicable7226-Jun-1222:14Not applicable
Kb2724141.xpoNot applicable12,202,64026-Jun-1222:14Not applicable
Metadata.xmlNot applicable7226-Jun-1222:14Not applicable
Kb2724141.xpoNot applicable12,202,68626-Jun-1222:14Not applicable
Metadata.xmlNot applicable7226-Jun-1222:14Not applicable
Axsetupsp.exe5.0.1100.451,636,58426-Jun-1222:24x86
Cabextractor.dllNot applicable19,18426-Jun-1222:24x86
Microsoft.dynamics.setup.reportingservices.dll5.0.1100.9150,44027-May-116:19x86
Axsetupsp.resources.dll5.0.1100.40538,88026-Jun-1222:24x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4517,33627-May-116:19x86
Axsetupsp.resources.dll5.0.1100.40534,78426-Jun-1222:24x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31227-May-116:19x86
Axsetupsp.resources.dll5.0.1100.40530,68826-Jun-1222:24x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31227-May-116:19x86
Axsetupsp.resources.dll5.0.1100.40534,78426-Jun-1222:24x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,82427-May-116:19x86
Axsetupsp.resources.dll5.0.1100.40534,78426-Jun-1222:24x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,82427-May-116:19x86
Axsetupsp.resources.dll5.0.1100.40530,67226-Jun-1222:24x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31227-May-116:19x86
Axsetupsp.resources.dll5.0.1100.40530,68826-Jun-1222:24x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31227-May-116:19x86
Axsetupsp.resources.dll5.0.1100.40538,88026-Jun-1222:24x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,82427-May-116:19x86
Axsetupsp.resources.dll5.0.1100.40538,86426-Jun-1222:24x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1500.121216,32027-May-116:19x86
Axsetupsp.resources.dll5.0.1100.40534,78426-Jun-1222:24x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,82427-May-116:19x86
Axsetupsp.resources.dll5.0.1100.40530,68826-Jun-1222:24x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31227-May-116:19x86
Axsetupsp.resources.dll5.0.1100.40530,67226-Jun-1222:24x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31227-May-116:19x86
Axsetupsp.resources.dll5.0.1100.40542,97626-Jun-1222:24x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4517,84827-May-116:19x86
Axsetupsp.resources.dll5.0.1100.40530,67226-Jun-1222:24x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31227-May-116:19x86
Axsetupsp.resources.dll5.0.1100.40534,76826-Jun-1222:24x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31227-May-116:19x86
Axsetupsp.resources.dll5.0.1100.40530,68826-Jun-1222:24x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31227-May-116:19x86
Axsetupsp.resources.dll5.0.1100.40530,68826-Jun-1222:24x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31227-May-116:19x86
Axsetupsp.resources.dll5.0.1100.40534,78426-Jun-1222:24x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,82427-May-116:19x86
Axsetupsp.resources.dll5.0.1100.40534,78426-Jun-1222:24x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31227-May-116:19x86
Axsetupsp.resources.dll5.0.1100.40547,07226-Jun-1222:24x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4518,87227-May-116:19x86
Axsetupsp.resources.dll5.0.1100.40530,67226-Jun-1222:24x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31227-May-116:19x86
Axsetupsp.resources.dll5.0.1100.40559,36026-Jun-1222:24x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4520,40827-May-116:19x86
Axsetupsp.resources.dll5.0.1100.40530,68826-Jun-1222:24x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4516,31227-May-116:19x86
Axsetupsp.resources.dll5.0.1100.40526,59226-Jun-1222:24x86
Microsoft.dynamics.setup.reportingservices.resources.dll5.0.1000.4515,80027-May-116:19x86
Cabextractor.dllNot applicable22,75226-Jun-1222:24x64

Validation of the application hotfix installation

To validate the installation of the application hotfix, open the SysHotfixManifest class in the Application Object Tree (AOT). Then, verify that there is a method whose name includes the Knowledge Base (KB) article number of the installed hotfix. Additionally, you can cross-check the affected objects by comparing the KBXXXXXX.txt file against the objects in the AOT. By doing this, you can make sure that the objects are changed correctly in the SYP layer or in the GLP layer.

Note The XXXXXX placeholder represents the KB article number of the installed hotfix.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
974255 Impact Analysis feature for Dynamics AX 2009

↑ Back to the top

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

↑ Back to the top

Keywords: kberrmsg, kbsurveynew, kbnoloc, kbmbsmigrate, kbmbspartner, kbmbsquickpub, kbhotfixserver, kbexpertisebeginner, kbexpertiseadvanced, kb, kbautohotfix, kbqfe, kbexpertiseinter

↑ Back to the top

Article Info
Article ID : 2724141
Revision : 2
Created on : 2/13/2017
Published on : 2/17/2017
Exists online : False
Views : 302