Thread: Error Message While Updating Display Order

Hey guys,

I'm new to the forum and have very little experience with aspdotnetstorefront so take it easy on me.

I have a fairly large category that I'm trying to adjust the display order for. The category has 1265 items.

When I click the "Order Update" button this is the error I receive: GeneralException | Error | Exception of type 'System.Web.HttpUnhandledException' was thrown.

I'm running version 9.2 Multistore.

Please let me know if you need additional information. Any help would be greatly appreciated!

Hello, and welcome to the forum!

Could you provide more error details, including the Error StackTrace. Check your System Log for more information regarding the error. From your admin console, go to Configuration --> Maintenance --> View System Log. Click on the arrow to the left of the error for more info.

Also, it would be of interest to know if the error presents itself when updating other categories, with a smaller number of products.

Let me know!
Robert

Thanks for taking the time to look at this for me, Robert.

Here are the error details:

Page URL:/pcadmin/entityProductBulkDisplayOrder.aspx
Source:System.Web
Message:The URL-encoded form data is not valid.
Stack Trace:
at System.Web.HttpRequest.FillInFormCollection()
at System.Web.HttpRequest.get_Form()
at System.Web.HttpRequest.get_HasForm()
at System.Web.UI.Page.GetCollectionBasedOnMethod(Bool ean dontReturnNull)
at System.Web.UI.Page.DeterminePostBackMode()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)


The error only happens with larger categories. I have no problem updated the display order of smaller categories.

Lyndsey

Hi Lyndsey,

Note: The following updates will cause your site to restart. Do pay particularly close attention when working on a production site.

I suspect your issue is related to the number of form fields being posted; exceeding the number allowed. If you are comfortable making code level changes, you may be able to resolve the issue, by modifying the following line of code in your web.config:

Code:

<add key="aspnet:MaxHttpCollectionKeys" value="2000" />

Try increasing the value to 5000.

Also important to look over, is the following Microsoft KB article http://support.microsoft.com/kb/2661403. It provides more details regarding the limits and security concerns relating to the MaxHttpCollectionKeys config key.

Let me know if that works out for you.
Robert

Robert,

I'm not finding the line of code to which you are referring in my web.config. I see several other keys such as EncryptKey, DBSQLServerLocaleSetting, and SiteDownForMaintenance to name a few. These are all between the <appSettings> tags. Is the MaxHttpCollectionKeys key something I need to add?

Thank you for the heads up on the security concerns. I'll be sure to consider it carefully before I make any changes.

Lyndsey

The alternative way to do this, if you can't resolve this with the previous suggestion, would be to export the data from the SQL table to Excel, make the changes there and then re-import the data.

Originally Posted by esedirect

The alternative way to do this, if you can't resolve this with the previous suggestion, would be to export the data from the SQL table to Excel, make the changes there and then re-import the data.

Is there some sort of plugin I need to export all of the product data? I have the option to import data as well as the option to import/export prices.

My suggestion is based on access to the database itself through your webserver using Microsoft SQL Server Management Studio. Perhaps that's not possible for you or you don't have the technical background. I don't know from your posts.

That would certainly be stretching my expertise but the owner of our company may have the capability. Thanks for the suggestion, I'll keep it in mind!

Originally Posted by lweedop

Robert,

I'm not finding the line of code to which you are referring in my web.config. I see several other keys such as EncryptKey, DBSQLServerLocaleSetting, and SiteDownForMaintenance to name a few. These are all between the <appSettings> tags. Is the MaxHttpCollectionKeys key something I need to add?

Thank you for the heads up on the security concerns. I'll be sure to consider it carefully before I make any changes.

Lyndsey

Yes, go ahead and add it before the appSettings closing tag in your web.config. For example:

Code:

	<add key="aspnet:MaxHttpCollectionKeys" value="2000" />
	</appSettings>

Try starting with 2000, and increasing the value if it doesn't work. Since you did not already have the key, it would have defaulted to 1000.

Let me know if that works out.

Worked like a charm, Robert. Thank you so much for your help!

You're welcome!