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

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

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

Symptoms

The inventory reading process reading data from an ILMT database running on SQL Server  fails with an error similar to the following:

SendInstallerEvidence (Transfer data from source 'ILMT' to FNMP) (VersionFrom: 9.2.3)
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'.

Alternatively, if the ILMT database is running on DB2 then the error would be similar to the following:

SendInstallerEvidence (Transfer data from source 'ILMT' to FNMP) (VersionFrom: 9.2.3)
  Failed to execute Reader 'SendInstallerEvidence' from file C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Reader\ilmt\InstallerEvidence.xml, at step line 1
Error: [DB2/LINUXX8664] SQL0204N  "SAM.SOFTWARE_FACTS" is an undefined name.  SQLSTATE=42704

Cause

The ILMT database schema (in both SQL Server and DB2 databases) changed in version 9.2.20, necessitating a change to the queries used by FlexNet Manager Suite to retrieve installer evidence data.

Resolution

FlexNet Manager Suite 2021 R1 and later provide out-of-the-box support for the ILMT 9.2.20 database schema changes, so one option to resolve this issue is to upgrade your FlexNet Manager Suite installation.

Alternatively, perform the following steps to apply an update to the reader queries.

If you are using ILMT with a SQL Server database:

  1. Make a backup copy of the following files in the C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Reader\ILMT SQL directory on your batch server (so that the original versions of these files can be restored in the case of a problem):
    • InstallerEvidence.xml
    • reader.config
  2. Download the ILMT SQL.zip file attached to this article and extract its contents into the above directory.

If you are using ILMT with a DB2 database:

  1. Make a backup copy of the following files in the C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Reader\ILMT directory on your batch server (so that the original versions of these files can be restored in the case of a problem):
    • InstallerEvidence.xml
    • reader.config
  2. Download the ILMT.zip file attached to this article and extract its contents into the above directory.

Other notes

The change to add support for ILMT 9.2.20 is tracked with reference number IOJ-2182680.

Was this article helpful? Yes No
No ratings
Comments

I am facing the same error in my environment but we are using the ILMT DB2 database (temadb) not SQL. Can you please provide the installerevidence for ILMT DB 

 

Failed to execute Reader 'SendInstallerEvidence' from file C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Reader\ilmt\InstallerEvidence.xml, at step line 1
Error: [DB2/LINUXX8664] SQL0204N "SAM.SOFTWARE_FACTS" is an undefined name.

 

System.Data.OleDb.OleDbException (0x80040E37): [DB2/LINUXX8664] SQL0204N "SAM.SOFTWARE_FACTS" is an undefined name. SQLSTATE=42704
at System.Data.OleDb.OleDbCommand.ExecuteCommandTextErrorHandling(OleDbHResult hr)
at System.Data.OleDb.OleDbCommand.ExecuteCommandTextForMultpleResults(tagDBPARAMS dbParams, Object& executeResult)
at System.Data.OleDb.OleDbCommand.ExecuteCommandText(Object& executeResult)
at System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior behavior, String method)
at System.Data.OleDb.OleDbCommand.ExecuteReader(CommandBehavior behavior)
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)

 

Best Regards

Venu Gopal

@venujuturi - an update to work with ILMT 9.2.20 running on a DB2 database has now been attached to this article.

Version history
Last update:
‎Mar 16, 2022 06:13 PM
Updated by:
Contributors