Hello, I am experiencing the following problem with the Forefront Identity Manager and the User Profile Service. Forefront appears to be attempting to start a Transaction but errors due to the transaction numbers being out of sync. Errors listed below. I have 3 servers: Server 1 - Designed to just be the webserver Server 2 - Central Admin and all extra services running on this server All services are currently running under the same account, which is a local administrator on each machine and is the account used to install SharePoint. Server 3 - Database Server I originally followed the Technet article, http://technet.microsoft.com/en-us/library/ee721050.aspx , to create and configure the user profile service and followed the Technet articles for all parts of the initial setup. Assistance appreciated! Thanks! ERROR #1: .Net SqlClient Data Provider: 266 : UpdateRequestStatusForCompletedActionWorkflows : System.Data.SqlClient.SqlException: Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1. Uncommittable transaction is detected at the end of the batch. The transaction is rolled back. at Microsoft.ResourceManagement.Data.Exception.DataAccessExceptionManager.ThrowException(SqlException innerException) at Microsoft.ResourceManagement.Data.DataAccess.UpdateRequestStatusForCompletedActionWorkflows(Int16 maxRequestsToProcess) at Microsoft.ResourceManagement.Workflow.PostProcessingManager.Execute() ERROR #2: .Net SqlClient Data Provider: System.Data.SqlClient.SqlException: Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1. Uncommittable transaction is detected at the end of the batch. The transaction is rolled back. 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.UpdateRequestStatusForCompletedActionWorkflows(Int16 maxRequestsToProcess) -Bagles1

Hello, Does anyone have any ideas on what might be causing the above problem? Everytime I start the FIM services, it starts throwing these errors. Any assistance, ideas or suggestions would be greatly appreciated! Many thanks in advance!-Bagles1

I have an identical issue. User Profile appears to work, but the event log is going insane with the above errors.

We are seeing the same error in our logs, any help as to what is causing it and any solution that you find would be great. (looking at you Microsoft)

I know it doesn't help much but I am having the same trouble...it's filling the event logs! The repeating two errors as reported by Bagles1 seem to be precluded by the following errors: Source: Forefront Identity Manager Event ID: 3 Level: Error System.Data.ConstraintException: Schema validation failed. Source: Forefront Identity Manager Event ID: 3 Level: Error Microsoft.ResourceManagement.Service: System.Data.ConstraintException: Schema validation failed. at Microsoft.ResourceManagement.ActionProcessor.ActionDispatcher.ProcessInputRequest(RequestType request) at Microsoft.ResourceManagement.WebServices.RequestDispatcher.ExecuteAction(RequestType request) at Microsoft.ResourceManagement.WebServices.RequestDispatcher.ExecuteAction[ResponseBodyType](RequestType request) at Microsoft.ResourceManagement.WebServices.RequestDispatcher.DispatchRequest[ResponseBodyType](RequestType request, Guid requestIdentifier, Object redispatchSingleInstanceKey) at Microsoft.ResourceManagement.WebServices.RequestDispatcher.DispatchRequest[ResponseBodyType](RequestType request) at Microsoft.ResourceManagement.WebServices.ResourceManagementService.Create(Message request)

Not that it helps, but we're experiencing the same; will update if I find a cause.

Also experiencing the same errors. Event ID's: 1004, 1001, 6398, 22, 3 etc... All associated with Profile Sync.

With the number of people that have reported this I'm beginning to believe it's a pretty major bug. I have a case open with PSS, hopefully I'll have some promising news...

Corbett, any update on this issue as a result of your PSS call with MSoft? Seeing the same thing..... Both of my Forefront identity manager services (service and synchronization) are started ok, but in CAdmin it sits on starting for the User Profile Synchronization Service. Thanks E.R.

It appears that recreating the Profile Service Application fixed the problem. At a high level: -Delete the Profile Service Application (do not delete the data) -Delete the Profile Sync Database -Create the Profile Service Application again (map to the existing Profile and Social databases) -Start the Profile Service -Recreate the Synchronization Connection(s)

We had the same conversation with Microsoft and ran the fix on our Beta and Production machines. In Beta the Forefront Identity Manager error went away. In Production the errors are still there, though the problem that we were having with not being able to create and new sync setup went away. So we did get a partial fix out of this, I would still like to find a way to get this error to stop flooding my SP logs.

That dose not seem to work for me. Even with a fresh created SyncDB, there still is a SQL problem. Maybe a MS enginner for the SharePoint Group can look over their stored procedure thats causing the problem and provide a hot fix? It's UpdateRequestStatusForCompletedActionWorkflows Stored procedure in teh SyncDB.

I have the same problem. Fresh SyncDB, but error appears as before.

I also have the same problem. Recently refreshed profile sync service... I noticed that my install of ForeFront Identify Manager (FIM) is still RC1. There appears to be a full release out there, but there hasn't been a SharePoint 2010 update to update FIM. I haven't tried installing FIM seperately, has anyone tried?kam

I had exactly this issue. After some search in the database and debug of the stored procedure "UpdateRequestStatusForCompletedActionWorkflows", i have found some "requests" that didnt success. /****** Script for SelectTopNRows command from SSMS ******/ SELECT * FROM [Userprofile_Sync].[dbo].[Request] the last entry: Identifier TargetIdentifier TargetObjectTypeKey TargetObjectTypeName Creator Anonymous Operation Status Cause Time Locale LocaleKey CommittedTime ReEvaluated D302D9E0-088C-4E55-BE11-D1D4BCE4786A 00000000-0000-0000-0000-000000000000 24 Person FB89AEFA-5EA1-47F1-8890-ABE7797D6497 0 Create 0 FB89AEFA-5EA1-47F1-8890-ABE7797D6497 2011-06-16 09:17:59.727 NULL NULL NULL NULL SELECT * FROM [Userprofile_Sync].[dbo].[RequestOutput] and /****** Script for SelectTopNRows command from SSMS ******/ SELECT TOP * FROM [Userprofile_Sync].[dbo].[RequestParameter] showed entries about which person would be created. here it was a domain group! While debugging the procedure I've got a @currentRequestStatus Denied nvarchar Don't know why there is no log somewhere about this. The MIISClient on the server didnt show any errors. The problem was: A day before I granted this group full rights on the user profile service application via "Central Administration > Manage Service Applications > User Profile Service Application > Administrators. Solution: Right after I removed this group the errors were gone.

Thanks Brotbuexe! Removing the group from the User Profile Application Administrators fixed it for me. No need to recreate the UPA. I suspect that the reason that worked for folks is you are deleting the Service Application and not recreating it with the same permissions. For those that it reappeared, look at your administrators and see if you have groups in there. HTH, MattMatthew McDermott, MVP SharePoint

To revive this post - i can also verify Brotbuexe's approach as a fix

The problem was: A day before I granted this group full rights on the user profile service application via "Central Administration > Manage Service Applications > User Profile Service Application > Administrators. Solution: Right after I removed this group the errors were gone. This worked a treat for me. I found that if you use an AD group it gives the error but single users dont. I just removed my group and replaced it with individual accounts. Cheers, Euan

Hi, well recreating the upa worked for me. Only thing is that when you delete the old upa, the FIM certificates are not removed. So when you recreate the upa, the eventlog will warn ILM Certificate could not be created: netsh http error:netsh http add urlacl url=http://+:5726/ user=D026001\svc-sps-farm sddl=D:(A;;GA;;;S-1-5-21-9395636-250898263-1546849883-4932) This is because the root certificate allready exists. So completing the overall picture 1 Delete the Profile Service Application (do not delete the data) 2 Delete the Profile Sync Database 2a delete any FIm certificates (please look here for full instructions http://www.cleverworkarounds.com/2010/08/15/more-user-profile-sync-in-sp2010-certificate-provisioning-issues/ 3 Create the Profile Service Application again (map to the existing Profile and Social databases) 4 Start the Profile Service 5 Recreate the Synchronization Connection(s) Thanx Sander

Thanks Brotbuexe! Removing the group from the User Profile Application Administrators fixed it for me. No need to recreate the UPA. I suspect that the reason that worked for folks is you are deleting the Service Application and not recreating it with the same permissions. For those that it reappeared, look at your administrators and see if you have groups in there. HTH, Matt Matthew McDermott, MVP SharePoint Worked - those tons of errors disappeared right after the group-removal. Thx!