Welcome Guest! You need to login or register to make posts.

Notification

Icon
Error

Options
Go to last post Go to first unread
Ericallenpaul  
#1 Posted : Wednesday, January 4, 2012 6:53:39 AM(UTC)
Ericallenpaul

Rank: Newbie

Groups: Member
Joined: 2/26/2010(UTC)
Posts: 3

i have a problem. uploader has been working fine for a long time, all of a sudden it won't upload more than 45 photos. MaxFileCount="60", if i upload 45 it works fine, regardless of file size, if i upload 46 it bombs and gives the following(using ShowDebugWindow=true):

Server Error in '/' Application.
________________________________________
Operation is not valid due to the current state of the object.
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.InvalidOperationException: Operation is not valid due to the current state of the object.

Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[InvalidOperationException: Operation is not valid due to the current state of the object.]
System.Web.HttpRequest.FillInFormCollection() +11091695
System.Web.HttpRequest.get_Form() +119
System.Web.HttpRequest.get_HasForm() +11085399
System.Web.UI.Page.GetCollectionBasedOnMethod(Boolean dontReturnNull) +124
System.Web.UI.Page.DeterminePostBackMode() +83
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +270

________________________________________
Version Information: Microsoft .NET Framework Version:2.0.50727.3625; ASP.NET Version:2.0.50727.3634

anybody got any ideas? we have had the uploader in production on these two servers for almost a year and not had any problems, just randomly crept up on us??

thanks,
matt
Ericallenpaul  
#2 Posted : Wednesday, January 4, 2012 8:22:35 AM(UTC)
Ericallenpaul

Rank: Newbie

Groups: Member
Joined: 2/26/2010(UTC)
Posts: 3

a quick update, this is being caused by a "critical" patch to the asp.net service packs..... i had a qa server that didn't have the patch installed yet, it worked fine, installed the patch, stopped working, uninstalled the patch and it started working again.

http://technet.microsoft...curity/bulletin/ms11-100

here is the security bulletin from microsoft i was referring to.

thanks,
matt
Ericallenpaul  
#3 Posted : Friday, January 6, 2012 10:43:07 AM(UTC)
Ericallenpaul

Rank: Newbie

Groups: Member
Joined: 2/26/2010(UTC)
Posts: 3

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


added this key to the <appsettings> and it fixed the problem.

http://stackoverflow.com...mum-number-of-posted-for
Dmitry  
#4 Posted : Monday, January 9, 2012 10:29:41 AM(UTC)
Dmitry

Rank: Advanced Member

Groups: Member, Administration, Moderator
Joined: 8/3/2003(UTC)
Posts: 1,070

Thanks: 1 times
Was thanked: 12 time(s) in 12 post(s)
Sincerely yours,
Dmitry Sevostyanov

UserPostedImage Follow Aurigma on Twitter!
Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.