Hi,
We have deployed FIM 2010 R2 in our client environment.
We are facing issues in FIM Portal. For all the authorization workflows, we have created custom approval activities.Whenever the approver approves requests in bulk (20 requests or more), the following behaviour is observed:
- the approval response is generated and the approval status is updated in the request window as "Approved" but the request status is set to "Failed" or "PostProcessing" or "PostProcessingError".
- The transaction running to set the value of an attribute is not completed.
- Action workflows not running after completion of Authorization workflows.
We are not running any parallel workflows. When we have analyzed the event viewer logs on FIM Portal machine, we have got the below Warning / errors:
Administrative / Application Logs
The Forefront Identity Manager Service was not able to perform the following operation 'Resume Request 5xxxxxd9-xxxx-4c04-b18c-xxd77ccba2f8' successfully.
The Forefront Identity Manager Service will attempt execution of this operation in the future if the operation is recoverable, or will cancel the operation. If this warning is repeated for the same operation, it is likely the Forefront Identity Manager Service will not be able to complete or cancel the operation automatically. There may be no automated recovery for this issue.
Restart the Forefront Identity Manager Service.
Forefront Identity Manager Logs:
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 50000, Level 13, State 1, Procedure ReRaiseException, Line 37, Message: Reraised Error 1205, Level 13, State 56, Procedure DoDeleteCachedRequest, Line 47, Message: Transaction (Process
ID 53) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 1, current count = 0.
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.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.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.ResourceManagement.Data.DataAccess.UpdateRequest(RequestType request, IEnumerable`1 updates)
--- End of inner exception stack trace ---
Is this a bug or limitation for FIM Portal?
Can somebody help me to identify the issue? has anyone seen this issue earlier?
Quick response will be really helpful.
Thanks,
Sanjog