cancel
Showing results for 
Search instead for 
Did you mean: 

License Reconcile Import TimeOut at writer 'ApplicationAlerts'

License Reconcile Import TimeOut at writer 'ApplicationAlerts'

Summary

This Knowledge Base article will provide with a SQL patch for a product defect Cause License Reconcile Import time out at Writer 'ApplicationAlerts' checking.

Symptoms

There is a SQL performance defect may hit your system which cause the License Reconcile Import failure due to timeout. The error message looks like below:

2016-07-01 02:03:50,621 [INFO ] ApplicationAlerts
2016-07-01 04:03:50,939 [INFO ] Failed to execute Writer 'ApplicationAlerts' from file C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Writer\InstalledSoftware.xml
Error: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
2016-07-01 04:03:50,941 [INFO ] All retries have been attempted for Writer 'ApplicationAlerts'
2016-07-01 04:03:50,989 [ERROR] System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out
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.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at ManageSoft.Compliance.Importer.Logic.XML.Writer.Execute(IExecutionContext context)
at ManageSoft.Compliance.Importer.Logic.ComplianceImporter.ExecuteWriters(ComplianceReader p_ComplianceReader, IExecutionContext context, String singleConnectionIdentifier)
ClientConnectionId:236b273c-8d95-4abb-a0b7-7350b95345b3
Error Number:-2,State:0,Class:11
2016-07-01 04:03:51,642 [INFO ] Completed with error in 2 hours, 0 minutes, 1 second

Cause

In Writer (InstalledSoftware.xml) the function 'List_OverlappingEvidenceAndApplications' has poor SQL performance.

** It doesn't necessary happens in all the system but only certain SQL environment. Most reported customer are using 2015 R2 or later service pack installed.


Resolution

The fixes has been added in 2016 release.

Workaround

For any previous version which affected by this timeout issue. Please apply the SQL hotfix by following steps:

1. Backup your SQL database.
2. Download the SQL attachment and run once in FNMSCompliance database
3. Redo the License reconcile import.
Attachments
Was this article helpful? Yes No
No ratings
Comments

Hi,

We are using FNMS 2019 R1 and today I found: Reconciliation failed
In the log file I found:

2019-07-03 23:12:56,253 [INFO ] ApplicationAlerts
2019-07-04 11:13:01,936 [INFO ] Failed to execute Writer 'ApplicationAlerts' from file C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Writer\InstalledSoftware.xml, at step line 1
Error: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
2019-07-04 11:13:01,936 [INFO ] All retries have been attempted for Writer 'ApplicationAlerts'
2019-07-04 11:13:02,061 [ERROR] System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
at System.Data.SqlClient.TdsParserStateObject.ReadSniSyncOverAsync()
at System.Data.SqlClient.TdsParserStateObject.TryReadNetworkPacket()
at System.Data.SqlClient.TdsParserStateObject.TryPrepareBuffer()
at System.Data.SqlClient.TdsParserStateObject.TryReadByte(Byte& value)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at ManageSoft.Compliance.Importer.Logic.XML.Writer.Execute(IExecutionContext context)
at ManageSoft.Compliance.Importer.Logic.ComplianceImporter.ExecuteWriters(ComplianceReader p_ComplianceReader, IExecutionContext context, String singleConnectionIdentifier)
ClientConnectionId:a21d8354-0d95-4951-91a9-c72e6e32efd0
Error Number:-2,State:0,Class:11

Is the behavior back again? Or is that other issue?

Kind regards

 

@Tooling42 - while the timeout you're experiencing is in the same place as what this article is talking about, the database queries used in your release (FlexNet 2019 R1) have evolved and changed somewhat from the queries behind this article (FlexNet prior to 2016). So the details behind the scenes of what is affecting you will be different - the workaround described in this article will not apply to you. If your problem is occurring repeatedly, you may wish to raise a case with Flexera Support to investigate further.

@ChrisG
Thanks a lot for the quick answer, I will raise a ticket for that.