Video Screencast Help

Resource History - Can't activate -> Error

Created: 10 May 2012 • Updated: 14 Aug 2012 | 5 comments
This issue has been solved. See solution.


I created a Custom Data class where I need a Resoure History.

I go to Settings -> Notification Server -> Resource and Data Class Settings -> Resource History

Check my Data Class and activate it. If I try this I get following error in the Log files:


Log File Name: C:\ProgramData\Symantec\SMP\Logs\a.log

Priority: 2

Date: 10.05.2012 14:20:30

Tick Count: 1788354683

Host Name: HGRS-HBK-S1150

Process: w3wp (9972)

Thread ID: 46

Module: w3wp.exe

Source: Altiris.NS.UI.AltirisWebApplication.Application_PreRequestHandlerExecute

Description: provided fallback culture(en-US) for non supported languages. The URL-encoded form data is not valid.


"10.05.2012 14:20:30","Unhandled exception.  Type=System.InvalidOperationException Msg=Operation is not valid due to the current state of the object.
   at System.Web.HttpValueCollection.ThrowIfMaxHttpCollectionKeysExceeded()
   at System.Web.HttpValueCollection.Add(HttpCookieCollection c)
   at System.Web.HttpRequest.FillInParamsCollection()
   at System.Web.HttpRequest.GetParams()
   at ComponentArt.Web.UI.BaseNavigator.UpdateSelectedNode()
   at ComponentArt.Web.UI.Menu.OnLoad(EventArgs e)
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
**CEDUrlStart** :**CEDUrlEnd**

 Screenshot in Attachement:

Anybody else encountered thsi?



Comments 5 CommentsJump to latest comment

Greer_IT's picture

I have a support ticket open for this issue. They said it was fixed at one point, but it seems to have been reintroduced in 7.1 SP2. I'll let you know how it goes.


Don Rowland's picture

I am getting a similar error description in my 7.1 SP2 as well as my archived 6.5 instance.  Makes we wonder if this is tied to a Windows update?  Any news from support?

After all the talking stops 1 simple fact remains.

It is what we, collectively, have allowed it to become.
HighTower's picture

I just applied this and it fixed my inability to set one of the data classes to a shorter retention period.