Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > VoIP & Network Quality Manager (VNQM) > VNQM - Knowledgebase Articles > SWIS logs - ERROR SolarWinds.InformationService.Core.InformationService - (null)

SWIS logs - ERROR SolarWinds.InformationService.Core.InformationService - (null)

Created by Harry Griffiths, last modified by Eric Bryant on Dec 20, 2016

Views: 1,403 Votes: 2 Revisions: 6


In certain versions of VNQM, you may experience unusual slowness. You can investigate this by looking at the SolarWinds Information Service (SWIS) log files. When reviewing the SWIS logs, you may find an exception running a specific query:


ERROR SolarWinds.InformationService.Core.InformationService - (null) 
Exception running query:
SELECT InfrastructureNodes.InfrastructureNodeID, InfrastructureNodes.NodeID, InfrastructureNodes.DisplayName, InfrastructureNodes.Status, InfrastructureNodes.DetailsUrl, InfrastructureNodes.StatusDescription, InfrastructureNodes.StatusLED, InfrastructureNodes.Image, InfrastructureNodes.AncestorDisplayNames, InfrastructureNodes.AncestorDetailsUrls, InfrastructureNodes.StatusIconHint, InfrastructureNodes.Description, InfrastructureNodes.Uri
 FROM Orion.IpSla.InfrastructureNodes   WHERE   ORDER BY InfrastructureNodes.DisplayName RETURN XML AUTO
ERROR SolarWinds.InformationService.Core.InformationService - (null) 
Exception caught in method RunQuery
SolarWinds.Data.SWQL.SWQLSyntaxException: no viable alternative at input 'ORDER' in Where clause ---> Antlr.Runtime.NoViableAltException: A recognition error occurred.
   at SolarWinds.Data.SWQL.Parser.SWQLParser.negatedExpression()
   --- End of inner exception stack trace ---
   at SolarWinds.Data.SWQL.Parser.SWQLParser.negatedExpression()
   at SolarWinds.Data.SWQL.Parser.SWQLParser.logicalAndExpression()
   at SolarWinds.Data.SWQL.Parser.SWQLParser.logicalOrExpression()
   at SolarWinds.Data.SWQL.Parser.SWQLParser.expression()
   at SolarWinds.Data.SWQL.Parser.SWQLParser.logicalExpression()
   at SolarWinds.Data.SWQL.Parser.SWQLParser.whereClause()
   at SolarWinds.Data.SWQL.Parser.SWQLParser.queryRule()
   at SolarWinds.Data.SWQL.Parser.SWQLParser.selectStatement()
   at SolarWinds.Data.SWQL.Parser.SWQLParser.statement()
   at SolarWinds.Data.SWQL.SWQLParser.Parse(String query)
   at SolarWinds.Data.Query.Engine.QueryProcessor.ProcessInternal(String query, IQueryExecutionContext context)
   at SolarWinds.InformationService.Core.QueryPlanCache.GetQueryPlan(String query, String username, Func`1 buildQueryPlan)
   at SolarWinds.InformationService.Core.InformationService.RunQuery(String query, IDictionary`2 parameters, IDataSerializer serializer)



VNQM Versions earlier than 4.2.2 (SR1)



This issue is fixed in VNQM 4.2.2 (SR1). To resolve this issue, SolarWinds recommends upgrading to VNQM 4.2.2 (SR1), because there are other issues solved in this release.


If you cannot upgrade, perform the following steps to as a workaround:

  1. Stop the Orion services using the Orion Service Manage.
  2. Go to the following folder: C:\Program Files (x86)\SolarWinds\Orion\Information Service\3.0\Schemas.
  3. Search for the file IpSlaSchema.xml.
  4. Make a backup of IpSlaSchema.xml and the IpSlaSchema.resx files. (Do not leave the backup in the installation directory) 
  5. Edit IpSlaSchema.xml file with following changes:


 Search for entity




Replace the following property element:


<property name="NodeID" type="System.Int32" displayName="$Orion.IpSla.VoipGateways.NodeID.displayName" groupBy="true" filterBy="true" />


with the following property element.


<property name="NodeID" type="System.Int32" key="True" displayName="$Orion.IpSla.VoipGateways.NodeID.displayName" groupBy="true" filterBy="true" />


Search for  entity name="Orion.IpSla.InfrastructureNodes". Replace the following property element


<property name="NodeID" type="System.Int32" displayName="$Orion.IpSla.InfrastructureNodes.NodeID.displayName" groupBy="true" filterBy="true" />


with the following property element.

<property name="NodeID" type="System.Int32" key="True" displayName="$Orion.IpSla.InfrastructureNodes.NodeID.displayName" groupBy="true" filterBy="true" />


 6. Start The Orion services using the Orion Service Manager.

Last modified