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

Full Recon failed after Upgrade to 2019 R1

Full Recon was failed after upgrade to 2019 R1. It timeout after 8 hrs. I have gone through below KB and increased timout value from 4 hrs to 8 hrs.

Full Recon successfully completed before upgrade to 2019 R1. refer attached import error log file and user.xml file.


2019-09-09 20:35:13,893 [INFO ] CreateLicenseUserStringMappings (Execute on FNMP)
2019-09-10 04:35:13,581 [INFO ] Failed to execute Reader 'CreateLicenseUserStringMappings' from file C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Reader\managesoft\User.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-09-10 04:35:13,581 [INFO ] All retries have been attempted for Reader 'CreateLicenseUserStringMappings'
2019-09-10 04:35:13,597 [INFO ] Completed with error in 8 hours, 0 minutes, 0 seconds.
2019-09-10 04:35:13,597 [INFO ] Released application lock Reader_9b412189-6ce9-4fbf-8eb4-38bfee10b7e1_Computer_ALL
2019-09-10 04:35:13,613 [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.ExecuteOnTarget.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)
Error Number:-2,State:0,Class:11
2019-09-10 04:35:14,894 [INFO ] Released application lock ManageSoftComplianceImporter_Exclusive
2019-09-10 04:35:14,910 [INFO ] Time: 10 September 2019 04:35:14
2019-09-10 04:35:14,910 [INFO ] Total import time: 8 hours, 1 minute, 27 seconds
2019-09-10 04:35:14,910 [INFO ] 0 source data warnings
2019-09-10 04:35:14,910 [INFO ] 1 errors, 0 warnings

(2) Replies
By Community Manager Community Manager
Community Manager

I have heard of this problem affecting a range of FlexNet releases, at least back to the 2017 R3 release.

One thing to try here would be to edit the User.xml file to add a line like the following at the start of the CreateLicenseUserStringMappings reader:

CREATE NONCLUSTERED INDEX NC_LicenseUser_ExternalUserIDForMapping ON #LicenseUser ([ExternalUserIDForMapping])


(On a more personal note - I see that Flexera Support sent you some guidance in May this year on how to resolve this problem on your 2018 R2 system; I'm not sure if they sent the same guidance as what I've suggested here, but you may want to check those details again in case they help with the current timeout.)

(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.)
Thanks Chris, this helped me to solve the reconciliation error after upgrade FNMS 2018R2 to 2019R.