Summary

This article provides a hot-fix for when an error is experienced during the execution of the 'SnapshotConsumptionData' exporter.

Symptoms

The Data warehouse export task is showing as failed in your FNMS environment, and the failure is observed in the System Tasks page and the specific error is present in the importer.log:

2017-03-26 06:00:57,212 [INFO ]         Failed to execute Exporter 'SnapshotConsumptionData' from file C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Exporter\fnmpdatawarehouse\BusinessIntelligenceData.xml
Error: Violation of UNIQUE KEY constraint 'UQ_ConsumptionData'. Cannot insert duplicate key in object 'dbo.ConsumptionData_MT'. The duplicate key value is (67, 66, 1, 2, 3, 4).
The statement has been terminated.
2017-03-26 06:00:57,212 [INFO ]         All retries have been attempted for Exporter 'SnapshotConsumptionData'
2017-03-26 06:00:57,212 [INFO ]         Completed in 5 seconds
2017-03-26 06:00:57,227 [INFO ]       Released application lock Exporter_26ab3873-fe65-4f8b-b718-3a6057f74c30_BusinessIntelligenceData_ALL
2017-03-26 06:00:57,462 [ERROR]     System.Data.SqlClient.SqlException (0x80131904): Violation of UNIQUE KEY constraint 'UQ_ConsumptionData'. Cannot insert duplicate key in object 'dbo.ConsumptionData_MT'. The duplicate key value is (67, 66, 1, 2, 3, 4).
The statement has been terminated.
   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.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlBulkCopy.RunParser(BulkCopySimpleResultSet bulkCopyHandler)
   at System.Data.SqlClient.SqlBulkCopy.CopyBatchesAsyncContinuedOnSuccess(BulkCopySimpleResultSet internalResults, String updateBulkCommandText, CancellationToken cts, TaskCompletionSource`1 source)
   at System.Data.SqlClient.SqlBulkCopy.CopyBatchesAsyncContinued(BulkCopySimpleResultSet internalResults, String updateBulkCommandText, CancellationToken cts, TaskCompletionSource`1 source)
   at System.Data.SqlClient.SqlBulkCopy.CopyBatchesAsync(BulkCopySimpleResultSet internalResults, String updateBulkCommandText, CancellationToken cts, TaskCompletionSource`1 source)
   at System.Data.SqlClient.SqlBulkCopy.WriteToServerInternalRestContinuedAsync(BulkCopySimpleResultSet internalResults, CancellationToken cts, TaskCompletionSource`1 source)
   at System.Data.SqlClient.SqlBulkCopy.WriteToServerInternalRestAsync(CancellationToken cts, TaskCompletionSource`1 source)
   at System.Data.SqlClient.SqlBulkCopy.WriteToServerInternalAsync(CancellationToken ctoken)
   at System.Data.SqlClient.SqlBulkCopy.WriteRowSourceToServerAsync(Int32 columnCount, CancellationToken ctoken)
   at System.Data.SqlClient.SqlBulkCopy.WriteToServer(IDataReader reader)
   at ManageSoft.Compliance.Importer.Logic.DatabaseConnection.LoadData(IDataReader p_DataReader, String p_TableName, Int32 p_BatchSize, Boolean p_ExplicitColumns)
   at ManageSoft.Compliance.Importer.Logic.XML.TargetToDestination.ExecuteSQL(IExecutionContext context)
   at ManageSoft.Compliance.Importer.Logic.XML.Exporter.Execute(IExecutionContext context)
   at ManageSoft.Compliance.Importer.Logic.ActionExecuter.ExporterExecuter.Execute()
   at ManageSoft.Compliance.Importer.Logic.ComplianceImporter.ExecuteExporters(ComplianceReader p_ComplianceReader, IExecutionContext context)
   at ManageSoft.Compliance.Importer.Logic.ComplianceImporter.ProcessExecution(ComplianceReader p_ComplianceReader, Tenant p_Tenant, IExecutionContext p_Context)
ClientConnectionId:5ccf700d-c094-46f1-be6f-dbcb300c0a8e
Error Number:2627,State:1,Class:14

Log files from export operations can commonly be accessed when drilling down to see the status of a task on the System Tasks page in the UI:

There are a few failure modes where the "Download log" link doesn't appear in the UI, in which case you can find log files on the batch server under the C:\ProgramData\Flexera Software\Compliance\Logging\ComplianceReader\ directory.

Resolution

This is a known issue (FNMS-41120) fixed in FlexNet Manager Suite 2017 R1.

Workaround

There is a hotfix attached to this article. N.B. this should only be used on FNMS 2016 R1 SP1.