This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Top 40 most vulnerable widget - No data to display

Recently I have found that the Top 40 Most Vulnerable Machines widget in the Orion web browser shows an information box that says no data to display.

Anyone seen this before or have any pointers? Everything else seems to be displayed correctly and syncing with the patch manager server.

  • There could be a timeout occurring due to the widget being based on 40 nodes, I'd recommend raising a Tech Support ticket so they can analyze debug logs and determine the root cause. As a first port of call, you could edit the widget and change the 'max number of items to display' to 10 and see if that results in the same error:

    Screenshot 2019-08-23 at 10.53.27.png 

  • Good shout but unfortunately the same error as before.

    OrionWeb log is showing the following:

    2019-08-27 09:47:36,139 [3745] (263) ERROR SolarWinds.Orion.Web.InformationService.InformationServiceProxy - (null)  Invalid column name 'C15'.

    System.ServiceModel.FaultException`1[SolarWinds.InformationService.Contract2.InfoServiceFaultContract]: RunQuery failed, check fault information.

    Invalid column name 'C15'. (Fault Detail is equal to InfoServiceFaultContract [ System.Data.SqlClient.SqlException (0x80131904): Invalid column name 'C15'.

       at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)

       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)

       at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)

       at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()

       at System.Data.SqlClient.SqlDataReader.get_MetaData()

       at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted)

       at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmd...).

    Anyone have any ideas?

  • Something on the last patch caused the issue but after applying the 2019.4 updates the issue was resolved.