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

The timeout period elapsed prior to completion of the operation or the server is not responding

Jump to solution

Hi All,

unable to upload the data to Import Inventory devices getting below error.

Failed to execute Writer 'ApplicationInstances' from file C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Writer\InstalledSoftware.xml, at step line 1
Error: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Added 0 new Installed Application Instances from the source database connections.
Installed Application Instance: Added 0 new Installed Application Instances from the source database connections.
The statement has been terminated.
2022-09-08 11:15:35,197 [INFO ] All retries have been attempted for Writer 'ApplicationInstances'
2022-09-08 11:15:35,432 [ERROR] System.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Added 0 new Installed Application Instances from the source database connections.
Installed Application Instance: Added 0 new Installed Application Instances from the source database connections.
The statement has been terminated. ---> 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& usedCache, Boolean asyncWrite, Boolean inRetry)
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)

 

Thanks,

Sreerama Yenuga.

0 Kudos
1 Solution
ChrisG
Community Manager Community Manager
Community Manager

If you are using a very old version of FlexNet Manager Suite (2017 Rx or earlier) then there are potentially some database queries involved in the "ApplicationInstances" step that are known to perform poorly. However it is not common to see timeout problems at this step with more current releases of FlexNet Manager Suite.

If this issue continues to reoccur each time you run an import, setting the HKLM\Software\Wow6432Node\ManageSoft Corp\ManageSoft\Compliance\CurrentVersion\CommandTimeout registry entry on your batch server to a value such as 28800 (corresponding to 8 hours) will give the import process a longer time before it times out, and may allow this step to get through its work.

See the following page for some info on this configuration setting: Inventory import and license reconcile timeouts.

(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.)

View solution in original post

0 Kudos
1 Reply
ChrisG
Community Manager Community Manager
Community Manager

If you are using a very old version of FlexNet Manager Suite (2017 Rx or earlier) then there are potentially some database queries involved in the "ApplicationInstances" step that are known to perform poorly. However it is not common to see timeout problems at this step with more current releases of FlexNet Manager Suite.

If this issue continues to reoccur each time you run an import, setting the HKLM\Software\Wow6432Node\ManageSoft Corp\ManageSoft\Compliance\CurrentVersion\CommandTimeout registry entry on your batch server to a value such as 28800 (corresponding to 8 hours) will give the import process a longer time before it times out, and may allow this step to get through its work.

See the following page for some info on this configuration setting: Inventory import and license reconcile timeouts.

(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.)
0 Kudos