Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Error: The URL-encoded form data is not valid

Error: The URL-encoded form data is not valid

Created by Karen Valdellon_ret, last modified by MindTouch on Jun 23, 2016

Views: 1,981 Votes: 0 Revisions: 3

Overview

Some Orion Web Console views fail to load if they contain too much information. Views that require large numbers of HTTP collection keys generate errors in the OrionWeb.log file that are similar to the following:

2012-01-02 11:12:07,053 [6] ERROR ASP.global_asax - Application_Error(27bf48a5c1cd4932bddd18910b1de04b) System.Web.HttpException: The URL-encoded form data is not valid. ---> System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at System.Web.HttpValueCollection.ThrowIfMaxHttpCollectionKeysExceeded()
   at System.Web.HttpValueCollection.FillFromEncodedBytes(Byte[] bytes, Encoding encoding)
   at System.Web.HttpRequest.FillInFormCollection()
   --- End of inner exception 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(Boolean dontReturnNull)
   at System.Web.UI.Page.DeterminePostBackMode()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Environment

All Orion products running on servers to which the Microsoft Security Bulletin MS11-100 has been applied.

Cause 

This is caused by a Microsoft Security update intended to address an ASP.NET Security Vulnerability.

Resolution

Warning: 

SolarWinds strongly recommends that you only edit the web.config file as instructed. Any additional modifications may result in system performance issues or may create an error state.

Save a copy of the original web.configl file to your local drive as a backup file, in case you need to rollback later.

All edits made in this procedure are overwritten if and when the SolarWinds Configuration Wizard runs. If you run the SolarWinds Configuration Wizard, you will need to make this edit again.

NPM

  1. Log on to your SolarWinds server as an administrator.
  2. In a text editor, open the Orion Web Console configuration file, web.config
    Note: The default location of web.config is C:\Inetpub\SolarWinds\
  3. Locate the following line: 
    <add key="aspnet:MaxHttpCollectionKeys" value="XXX" />
    <add key="aspnet:MaxHttpCollectionKeys" value="&lt;em&gt;number&lt;/em&gt;"/>
  4. Increase the value for the aspnet:MaxHttpCollectionKeys key.
    Note: Internal testing has shown that 2000 may be an acceptable value for NPM.
  5. Save web.config

APM

  1. Log on to your SolarWinds server as an administrator.
  2. In a text editor, open the Orion Web Console configuration file, web.config
    Note: The default location of web.config is C:\Inetpub\SolarWinds\
  3. Add the following line in the <AppSettings><appsettings/> section: 
    <add key="aspnet:MaxHttpCollectionKeys" value="XXX" />
  4. Increase the value for the aspnet:MaxHttpCollectionKeys key.
    Note: Internal testing has shown that 4000 may be an acceptable value for APM.
  5. Save web.config

 

Last modified

Tags

Classifications

Public