cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Failed to execute Reader 'SendInstallerEvidence' Error: Invalid object name 'sam.software_facts'

Hi Forum,

Import from ILMT sql connection is getting failed with  summary Inventory gathering failed. Error: Invalid object name 'sam.software_facts'  in inventory data import task and importer log is throwing the below error.

 

Failed to execute Reader 'SendInstallerEvidence' from file C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Reader\ilmt sql\InstallerEvidence.xml, at step line 3
Error: Invalid object name 'sam.software_facts'.

2021-02-15 22:05:34,502 [INFO ] All retries have been attempted for Reader 'SendInstallerEvidence'
2021-02-15 22:05:34,502 [INFO ] Completed with error in 0 seconds.
2021-02-15 22:05:34,505 [ERROR] System.Data.SqlClient.SqlException (0x80131904): Invalid object name 'sam.software_facts'.
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 cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at ManageSoft.Compliance.Importer.Logic.DatabaseSourceConnection.CreateDataReader(Reader readerStep, IExecutionContext context)
at ManageSoft.Compliance.Importer.Logic.XML.SourceToTarget.GetReader(IExecutionContext context, ISourceConnection sourceConn)
at ManageSoft.Compliance.Importer.Logic.XML.SourceToTarget.ProcessStep(IExecutionContext context)
at ManageSoft.Compliance.Importer.Logic.XML.Reader.Execute(IExecutionContext context)
at ManageSoft.Compliance.Importer.Logic.ActionExecuter.ReaderExecuter.ExecuteSingleReader(Reader reader, Int32 procedureOrder, Version sourceDatabaseVersion)
at ManageSoft.Compliance.Importer.Logic.ActionExecuter.ReaderExecuter.Execute()
at ManageSoft.Compliance.Importer.Logic.ComplianceImporter.ProcessExecution(ComplianceReader p_ComplianceReader, Tenant p_Tenant, IExecutionContext p_Context)
ClientConnectionId:49ca3e86-458e-446c-91e2-3f496b9ca5b2
Error Number:208,State:1,Class:16

Is this issue with the installerevidence.xml file? Appreciate your thoughts on this.

(5) Replies
ChrisG
By Community Manager Community Manager
Community Manager

This error suggests that the table/view named "sam.software_facts" does not exist in the SQL Server database that you have configured as your source. Maybe take a look in the database you have and see if you can find any table or view with a similar name to get a sense of what is going on. Some examples of other tables/views that are expected to exist in the ILMT database which could you also look for are:

  • sam.catalog_dimension
  • sam.software_titles
  • sam.publishers
  • adm.node
  • adm.vm
  • adm.prod_inv
  • adm.branch

Also, what specific version of ILMT are you using? Versions formally supported by latest FlexNet Manager Suite releases are 9.2.5–9.2.18 and 10.0.0.

(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)

Hi Chris,

thanks for the insights will check as suggested, we are having ILMT 9.2.21 and FNMS 2020R1 on prem. 

 

Regards,

According to the FNMS 2020 R2 release notes, for 'BM License Metric Tool (ILMT) or IBM BigFix Inventory on Microsoft SQL Server', FNMS is compatible with:

  • IBM BigFix Inventory on Microsoft SQL Server: 9.2.5–9.2.18, 10.0.0
  • IBM License Metric Tool (ILMT) on Microsoft SQL Server: 9.2.5–9.2.18, 10.0.0

The ILMT SQL reader did not change between the FNMS 2020 R1 and R2 releases. It looks as if some tables and views including [sam.software_facts] that the FNMS 'ILMT SQL' READER expects in the ILMT database have been deprecated with ILMT 9.2.22.0 and possibly are not available in the ILMT 9.2.21 release that you use. According to the release notes, the ILMT SQL 9.2.21 release is outside of the supported ILMT releases.

As Chris G suggested, I would check the ILMT database if an object (table or view) named 'sam.software_facts' exists before contacting Flexera support and ask for an updated version of the ILMT SQL Reader files.

@winvarma - Can you verify that you are connecting to the correct database?  For BigFix/ILMT, the name of the database you should connect to is normally named TEMADB.  If you are not connecting to a different database, it would explain why it cannot find some of the Table and Views in the database schema that it is expecting.

hi @kclausen ,

thanks for the suggestion and i'm connecting to temadb in the connection only. this integration is running without any issues for 3 quarters and facing this issue from yesterday night.

No changes were made at FNMS end and checking with the ILMT team what is the exact version if there is any upgrade/changes done at their end to find the cause.

Regards,