none
MIM 2016 transaction deadlock error on export to FIM MA RRS feed

  • Question

  • I'm getting a deadlock error for groups when running an export on the FIM MA.  Or MIM MA or whatever it's called now.  I set up the required attribute flows and sync rules (after having some failures around not having group type and scope flowed).  And enabled the group sync MPRs.  I haven't had group provisioning working in this instance yet. It is provisioning projected AD users to an LDAP server though, so I've got that going for me.

    This is on version 4.5.286.0.  Can anyone offer suggestions?

    Fault Reason: The endpoint could not dispatch the request.\r\n\r\nFault Details: <DispatchRequestFailures xmlns="http://schemas.microsoft.com/2006/11/ResourceManagement" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><DispatchRequestAdministratorDetails><FailureMessage>Exception: Other
    Stack Trace: Microsoft.ResourceManagement.WebServices.Exceptions.UnwillingToPerformException: Other ---> System.Data.SqlClient.SqlException: Reraised Error 50000, Level 13, State 1, Procedure ReRaiseException, Line 37, Message: Reraised Error 50000, Level 13, State 1, Procedure ReRaiseException, Line 37, Message: Reraised Error 1205, Level 13, State 51, Procedure GenerateRequestOutput, Line 2147, Message: Transaction (Process ID 325) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.


    Thursday, May 9, 2019 3:07 AM

Answers

All replies

  • I'm experiencing the same error on the same build.  Using SQL tracing I've been able to isolate the issue to a stored procedure named GenerateRequestOutput that is causing the deadlock.

    One of the replies to this post describes getting an updated stored procedure from Microsoft to fix the issue.

    https://social.technet.microsoft.com/Forums/en-US/102e8b67-2e4f-4817-8624-138f08331b69/sql-deadlocks-after-upgrading-to-mim-2016?forum=ilm2

    I think the error is related to the stored procedure, and likely need to get a fix from Microsoft.

    Wednesday, May 15, 2019 6:54 PM
    • Marked as answer by Jordan Mills Thursday, May 16, 2019 2:44 AM
    Wednesday, May 15, 2019 7:04 PM
  • Hotfix released on 5/10 should fix this:

    https://support.microsoft.com/en-us/help/4489646/hotfix-rollup-4-5-412-0-available-for-mim-2016-sp1


    Well I guess I have some bad timing.  Thanks for the quick follow up.  I'm trying this tonight.
    Thursday, May 16, 2019 1:53 AM
  • Hotfix released on 5/10 should fix this:

    https://support.microsoft.com/en-us/help/4489646/hotfix-rollup-4-5-412-0-available-for-mim-2016-sp1


    Looks like that fixed it.  Thanks!
    Thursday, May 16, 2019 2:44 AM
  • Hi, we started to get this error when our MIM wanted to delete 1730 groups in the portal
    Today we applied this patch to our MIM
    https://support.microsoft.com/en-us/help/4489646/hotfix-rollup-4-5-412-0-available-for-mim-2016-sp1

    But the error still remains:
    Requestor: urn:uuid:fb89aefa-5ea1-47f1-8890-abe7797d6497
    Correlation Identifier: 71c9d030-8127-48cd-92a2-ecc788bb6128
    Microsoft.ResourceManagement.Service: Microsoft.ResourceManagement.WebServices.Exceptions.UnwillingToPerformException: Other ---> System.Data.SqlClient.SqlException: Reraised Error 50000, 
    Level 13, State 1, Procedure ReRaiseException, Line 37, Message: Reraised Error 50000, Level 13, State 1, Procedure ReRaiseException, Line 37, 
    Message: Reraised Error 1205, Level 13, State 51, Procedure GenerateRequestOutput, Line 914, Message: Transaction (Process ID 123) 
    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)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
       at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
       at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
       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)
       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
       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.ExecuteReader()
       at Microsoft.ResourceManagement.Data.DataAccess.DoRequestCreation(RequestType request, Guid cause, Guid requestMarker, Boolean doEvaluation, Int16 serviceId, Int16 servicePartitionId)
       --- End of inner exception stack trace ---
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.CreateRequest(UniqueIdentifier requestor, UniqueIdentifier targetIdentifier, OperationType operation, String businessJustification, List`1 requestParameters, CultureInfo locale, Boolean isChildRequest, Guid cause, Boolean doEvaluation, Nullable`1 serviceId, Nullable`1 servicePartitionId, UniqueId messageIdentifier, UniqueIdentifier requestContextIdentifier, Boolean maintenanceMode)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.CreateRequest(UniqueIdentifier requestor, UniqueIdentifier targetIdentifier, OperationType operation, String businessJustification, List`1 requestParameters, CultureInfo locale, Boolean isChildRequest, Guid cause, Boolean doEvaluation, Nullable`1 serviceId, Nullable`1 servicePartitionId, UniqueId messageIdentifier)
       at Microsoft.ResourceManagement.WebServices.ResourceManagementService.Delete(Message request)
       
       
       
       


    Wednesday, June 12, 2019 11:07 AM
  • I ran into this issue again yesterday (after that recent patch). In my case, I was getting it when the sync account did not have an MPR allowing it to alter a custom attribute when creating a user.  
    Wednesday, June 12, 2019 12:14 PM
  • I have to add that we only get these errors when it occurs a delete on a group in the Portal

    and when we set the synchronization engine to only run synchronous requests, it worked for us.

    <resourceSynchronizationClient
    asynchronous=“false” aggregate=“false”/>

    Anders

    Wednesday, June 12, 2019 1:01 PM