Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

Home > Success Center > Network Performance Monitor (NPM) > HTTP 500 Error

HTTP 500 Error

Updated October 12th, 2016

Overview

Web site timing out with HTTP 500

Error in the Orion Web Log

ERROR ASP.global_asax - Application_Error(a2616d17b7c341378d4d1da0a94b06df)
System.Web.HttpException (0x80004005): Request timed out.

Error in the Information log V3

ERROR SolarWinds.InformationService.Core.InformationService - SolarWinds.Orion.Core.Alerting.Plugins.Conditions.Swql.ConditionEvaluatorSwql.ExecuteQuery()  
Exception caught in method RunQuery
SolarWinds.Data.Query.ParserException: Conversion failed when parsing the value %10  to data type int.

Error in the Alert  Services V2 log

ERROR SolarWinds.Orion.Core.Alerting.Service.ConditionsStateEvaluator - Condition 'AlertId: 10, AlertLastEdit: 10/23/2015 7:06:43 AM, ConditionIndex: 0, Type: Trigger' Evaluator failed - Condition evaluation failed for query = (SELECT E0.[Uri], E0.[DisplayName]
FROM Orion.Nodes AS E0
WHERE ( ( ( ( E0.[Engine].[Uri] = @p0 ) ) ) AND ( ( E0.[CPULoad] > @p1 ) ) )), condition = (AlertConditionDynamic: scope=(AND ([<this>.Orion.Engines|instance|Engine] IS '')): (AND ([Orion.Nodes|CPULoad] > '%10 '))) - System.ServiceModel.FaultException`1[SolarWinds.InformationService.Contract2.InfoServiceFaultContract]: RunQuery failed, check fault information. (Fault Detail is equal to InfoServiceFaultContract [ SolarWinds.Data.Query.ParserException: Conversion failed when parsing the value %10  to data type int.
   at SolarWinds.Data.Query.Processor.TypeValidator.ValidateLiteral(TypeInformation commonType, ValueType expressionType,

Environment

  • NPM11.5

Cause 

HTTP errors are usually troubleshooted using this article

These steps did not help. Issue was SWIS was being heavily utilized in evulatiing the query WHERE ( ( ( ( E0.[Engine].[Uri] = @p0 ) ) ) AND ( ( E0.[CPULoad] > @p1 ) ) )), condition = (AlertConditionDynamic: scope=(AND ([<this>.Orion.Engines|instance|Engine] IS '')): (AND ([Orion.Nodes|CPULoad] > '%10 '))) -

Resolution

  1. Trace the error through the logs.
  2. Checked the Orion Web Log
  3. Checked the Information V3 log
  4. Checked the Alert Service V2 log
  5. The Alert Service V2 log identified AlertId: 10
  6. Go to the database manager and check the alert configuration table
  7. Use the alert id to get the name of the alert.
  8. Go to the Orion console and using the name of the alert to find and edit the alert
  9. In the Alert trigger I could see that the condition was CPU load > %10
  10. Removed the % and saved the alert.

 

Last modified

Tags

Classifications

Public