Transaction was deadlocked in the Dispatcher log

[#1]

Summary

System.Data.SqlClient.SqlException (0x80131904): Transaction (Process ID xxx) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. In the dispatcher log

Symptoms

You may experience the following error in the dispatcher log file when importing inventory or AD data:

[ERROR 2015-12-04 05:06:37,607 7711964ms Dispatcher ] Failed to run importer
System.Data.SqlClient.SqlException (0x80131904): Transaction (Process ID 120) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
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.SqlDataReader.TryConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior)
at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader()
at ManageSoft.Database.DatabaseCommand.ExecuteReader(IDatabaseLayer m_DataLayer)
at ManageSoft.Database.Impl.DatabaseLayerBaseSql.GetResult(IDatabaseObjectFactory p_ObjectFactory, CommandType p_CommandType, String p_CommandText, DatabaseParameter[] p_Parameters)
at ManageSoft.Database.Impl.DatabaseLayerBase.GetResult(String p_StoredProcedure, DatabaseParameter[] p_Parameters)
at ManageSoft.Directory.Impl.DirectoryBinder.BindToComputerAndUser(IManageSoftDatabaseLayer databaseLayer, String computerName, String computerDomain, String computerFlatDomain, String computerUID, DirectoryEntry computerObject, String userName, String userDomain, String userUID, Boolean useUniqueNames, Int32& computerID, Int32& computerOUID, Int32& userID, Int32& userOUID)
at ManageSoft.Inventory.Importer.DatabaseImport.Begin(InventoryImportSession session)
at ManageSoft.Inventory.Importer.Implementation.RootNodeProcessor.HandleElement()
at ManageSoft.Inventory.Importer.Implementation.BaseElementNodeProcessor.Process(InventoryImportSession session)
at ManageSoft.Inventory.Importer.InventoryImporter.Import(String importType, Stream inputStream, Boolean isGzipped, String sourceIdentifier, String targetFilename, MGSLicenseTermCheckResult licenseCheckResult, ImportProcessingStats& stats)
at ManageSoft.Import.Dispatcher.runImporter_ActualExecution_invokeImporter(ItemProcessingTask processingTask)
ClientConnectionId:34ab8019-87f5-40a3-8fb0-f9680b49dc17
Error Number:1205,State:48,Class:13

Workaround

Currently the only workaround is to try and resolve the file again until it succeeds. This can be done by either:

- Waiting for the next active directory file to be created and uploaded.
- Moving the latest .actdir file from bad logs back into the Incoming\ActiveDirectory folder on the FNMS server and letting the resolvers try again. Note that it is not necessary to try and process all bad logs, just the latest.

Additional Information

Currently being tracked under FNMS-14623

Related KB Articles

Article #000019009 Known issues for FlexNet Manager Suite 2015 R2 SP1