I'm about to raise this with PSS, but as it takes about eight hours to get a conference setup, I thought I'd ask here. We've just started experiencing a reoccuring problem, where requests fail and error out. The error is due to a SQL Server deadlocking issue. Here's the two distinct error types I can see in the FIM Service event log. This issue happens on data-load, and also when creating a new user. We're not aware of any changes to the SQL Server instance. The configuration is one SQL instance with both FIMService, and FIMSynchronizationService databases on. We're running RTM version (we'll be upgrading soon). Has anyone seen anything like this? Microsoft.ResourceManagement.WebServices.Exceptions.UnwillingToPerformException: Other ---> System.Data.SqlClient.SqlException: Reraised Error 50000, Level 13, State 1, Procedure ReRaiseException, Line 37, Message: Reraised Error 1205, Level 13, State 51, Procedure UpdateRequestStatus, Line 43, Message: Transaction (Process ID 82) 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 --- 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 UpdateRequestStatus, Line 43, Message: Transaction (Process ID 67) 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.HasMoreRows() at System.Data.SqlClient.SqlDataReader.ReadInternal(Boolean setTimeout) at System.Data.SqlClient.SqlDataReader.NextResult() at Microsoft.ResourceManagement.Data.DataAccess.ProcessRequest(RequestType request) --- End of inner exception stack trace ---

are you running multiple "Synchronization" run profiles at the same time?http://setspn.blogspot.com

No. This happens when we do a data-load into FIM, using the FIMService API. It also happens when we create a user (this is one operation I've tried, it could be happening to all operations).

Your best bet is to move to the latest build of the product. There may have been fixes for deadlocks in the FIM Service DB since RTM.CraigMartin Edgile, Inc. http://identitytrench.com

I agree, that'd be the right thing to do, though, unfortunately, the process to this is involved, and there's no time in the project plan for that, at this time. It's a high priority task though, and will be done soon, but of course, it involves an isolated test, full regression testing, then synchronisation with the data-centre teams, etc... Not so easy to do :) I have a call with PSS later today about it. Fingers crossed.