7 Replies Latest reply on Feb 4, 2010 12:44 PM by aLTeReGo

Syslog messages set too high...

whitejcdc Jan 2, 2009 12:02 PM

This seems to not be able to be set back to 250, and if you do it generates an error. One of my network team was logged in as admin on the web console and inadvertently set the messages to display to 25000. This seems to have stuck and causes an error when you try to run any syslog display for the page. Help.

The page takes a very long time to load of course, and when you try to modify anything and refresh you get this error:

System.Web.HttpException: Maximum request length exceeded.
at System.Web.HttpRequest.GetEntireRawContent()
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)

Thanks, Jeff

Re: Syslog messages set too high...

denny.lecompte Jan 3, 2009 3:10 PM (in response to whitejcdc)

This is a bug on our part. We're going to get it fixed, but in the meantime, you can edit the value in the database. It's in the WebUserSettings table. The value you need to change back to 250 is Web-SyslogMaxMsgPerPage.
Like Show 0 Likes(0)

Actions
- Re: Syslog messages set too high...
  
  TRueb Jul 22, 2009 2:16 PM (in response to denny.lecompte)
  
  Hi Denny,
  I'm having the same problem as stated originally, and I tried to follow your advise - unsuccessful, unfortunately. I made it to the "WebUserSettings" table, but couldn't find the mentioned "Web-SyslogMaxMsgPerPage" value. Could you please advise in more detail how to get there?
  Thanks & regards,
  Thomas
  
  Like Show 0 Likes(0)
  
  Actions
  - Re: Syslog messages set too high...
    
    bshopp Jul 22, 2009 3:43 PM (in response to TRueb)
    
    What version are you on and are you using SQL Server or Express?
    
    Like Show 0 Likes(0)
    
    Actions
    - Re: Syslog messages set too high...
      
      TRueb Jul 23, 2009 2:26 AM (in response to bshopp)
      
      Sorted - Thanks to Ciaran Luttrell!
      
      Like Show 0 Likes(0)
      
      Actions
- Re: Syslog messages set too high...
  
  aLTeReGo Feb 4, 2010 12:44 PM (in response to denny.lecompte)
  
  This is a bug on our part. We're going to get it fixed, but in the meantime, you can edit the value in the database. It's in the WebUserSettings table. The value you need to change back to 250 is Web-SyslogMaxMsgPerPage.
  
  I'm still seeing this issue in 8.5.1 (A little more than a year after your post) Any update on a possible resolution to this issue?
  
  Like Show 0 Likes(0)
  
  Actions
Re: Syslog messages set too high...

jkennedy Sep 29, 2009 6:27 PM (in response to whitejcdc)

Has anyone found a way to limit the max number of messages a user can try to view? I have users trying to pull 10000+ messages any complaining about response time.
Like Show 0 Likes(0)

Actions
Re: Syslog messages set too high...

jkennedy Sep 30, 2009 11:41 AM (in response to whitejcdc)

I have found a workaround to my issues regarding users setting this threshold too high.

I replaced the built in menu bar link to SysLog with a link which point to this URL.

/Orion/NetPerfMon/SysLog.aspx?MaxMessages=100

Whenever you use the SysLog link in the menu bar, it will only load the past 100 messages. Most likely your users will then be using search criteria to refine their search and include a larger number of messages.
Like Show 0 Likes(0)

Actions

Go to original post