Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Network Performance Monitor (NPM) > Clearing syslog messages error: Unexpected Website Error. Value was either too large or too small for an Int32

Clearing syslog messages error: Unexpected Website Error. Value was either too large or too small for an Int32

Overview:

The following error appears when trying to clear the syslog messages thru the Website:

Unexpected Website Error. Value was either too large or too small for an Int32.

Environment

All NPM versions

Resolution:

Truncate syslog messages via Database Manager.

Execute the following query using the Database Manager:

UPDATE [dbo].[WebUserSettings]
SET SettingValue = '250'
WHERE SettingName = 'Web-OrionMessagesMaxMsgPerPage'

 

Truncate syslog messages:

You can remove all the historical Syslog messages from your database using a TRUNCATE query.

  1. Stop all Orion services using the Orion Service Manager.
  2. Open the Database Manager and connect to your Orion database.
  3. Right click on any table and select 'Query Table...'
  4. Set the radio button to Read/Write and clear out the default query.
  5. Enter the following query and click Refresh:
    *****************************************************************************
    TRUNCATE TABLE Syslog
    *****************************************************************************
    UPDATE [dbo].[WebUserSettings]
    SET SettingValue = '250'
    WHERE SettingName = 'Web-OrionMessagesMaxMsgPerPage'
    *****************************************************************************
    
     
  6. Restart the Orion services using the Orion Service Manager.

Notes:

  • Consult your database administrator before performing any of the following steps. 
  • Create a backup of the database in your local drive, in case you need to roll back later.

 

Last modified
19:41, 1 Mar 2017

Tags

Classifications

Public