Changing the month selector or clicking the New Event link in an Event Calendar Group part generates a run-time error.

When any of certain sub-set of Team Calendars are added to an Event Calendar Group part as feeder calendars, using the drop-down control [in Calendar View] to change the display month or clicking the "New Event" hyperlink produces a runtime error with the following details:

Operation is not valid due to the current state of the object. 
at System.Web.HttpValueCollection.FillFromEncodedBytes(Byte[] bytes, Encoding encoding) at System.Web.HttpRequest.FillInFormCollection() 

The URL-encoded form data is not valid. 
at System.Web.HttpRequest.FillInFormCollection() at System.Web.HttpRequest.get_Form() at Blackbaud.Web.Content.Core.PortalSettings.getParam(EQueryStringParams eParam, Object DefaultValue, String NameModifier) at Blackbaud.Web.Content.Core.PortalSettings.SetEmailProjectState() at Blackbaud.Web.Content.Core.PortalSettings..ctor()

Bad request. The URL-encoded form data is not valid. 
at Blackbaud.Web.Content.Core.PortalSettings..ctor() at Blackbaud.Web.Content.Core.PortalSettings.Current() at Blackbaud.Web.Content.Portal.AuthenticationModule.CheckForSSLRedirect() at Blackbaud.Web.Content.Portal.AuthenticationModule.BeginRequest(Object sender, EventArgs e) at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) 

The calendar will time out if there are a large number of feeder calendars and/or a large number of events in the feeder calendars.  We are able to increase the timeout settings to allow for the calendar to function properly.
Add the following entry to the NetCommunity web.config file:

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

If there is not <appSettings> section, one needs to be added under <configuration>:

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

The value can be adjusted to a larger number if the error persists. 

Fully-Hosted and Split Hosted Clients:
Click Chat with Support and reference this article


 6.53.516 patch 5

Was this article helpful?