Microsoft.ResourceManagement.Workflow.Hosting.WorkflowManagerException
After applying the August 2010 Cumulative Update to a few SharePoint 2010 farms (better late than never), a number of errors were occurring in the event log on the server running the Forefront Identity Manager Service (FIMService) and the Forefront Identity Manager Synchronization Service (FIMSynchronizationService).
First up, the User Profile Synchronization Service could not be started. The following errors where appearing in the event log on the service hosting the FIMSynchronizationService:
The Forefront Identity Manager Service cannot connect to the SQL Database Server.
The SQL Server could not be contacted. The connection failure may be due to a network failure, firewall configuration error, or other connection issue. Additionally, the SQL Server connection information could be configured incorrectly.
Verify that the SQL Server is reachable from the Forefront Identity Manager Service computer. Ensure that SQL Server is running, that the network connection is active, and that the firewall is configured properly. Last, verify the connection information has been configured properly. This configuration is stored in the Windows Registry.
and
Detection of product ‘{90140000-104C-0000-1000-0000000FF1CE}’, feature ‘PeopleILM’, component ‘{CF90B971-D78A-4794-8F90-EB5FB5028DDA}’ failed. The resource ‘C:\Program Files\Microsoft Office Servers\14.0\SQL\DatabaseSettings.sql’ does not exist.
The NETWORK SERVICE account needs to be granted “Read & Execute” rights to the folder C:\Program Files\Microsoft Office Servers\14.0 on the server hosting the FIMSynchronizationService.
After the service has been started, the next set of errors will begin appearing the in event log with a regular frequency:
Microsoft.ResourceManagement.Workflow.Hosting.WorkflowManagerException: Forefront Identity Management Service does not support workflows of type ‘Microsoft.ResourceManagement.Workflow.Activities.SequentialWorkflow, Microsoft.ResourceManagement, Version=4.0.2450.5, Culture=neutral, PublicKeyToken=31bf3856ad364e35′.
and
Microsoft.ResourceManagement.Service: Microsoft.ResourceManagement.Workflow.Hosting.WorkflowManagerException: Forefront Identity Management Service does not support workflows of type ‘Microsoft.ResourceManagement.Workflow.Activities.SequentialWorkflow, Microsoft.ResourceManagement, Version=4.0.2450.5, Culture=neutral, PublicKeyToken=31bf3856ad364e35′.
at Microsoft.ResourceManagement.Workflow.Hosting.HostActivator.ActivateHost(ResourceManagementWorkflowDefinition workflowDefinition)
at Microsoft.ResourceManagement.Workflow.Hosting.WorkflowManager.StartWorkflowInstance(Guid workflowInstanceIdentifier, KeyValuePair`2[] additionalParameters)
A quick trip to the MS Support portal leads to the wonderfully titled KB article “Event ID 3 is logged in the Application log if you run the User Profile Synchronization service after you install hotfix package 2281364 or 2352342 in SharePoint Server 2010“. Due to a mismatch in the WorkflowDefinition table in the FIM sync database and what has been deployed to the file system, your servers will now throw the errors shown above once a minute. You’ll have to weigh whether it is worth it to rebuild your User Profile Service Application or live with the errors.
Reference
- Event ID 3 is logged in the Application log if you run the User Profile Synchronization service after you install hotfix package 2281364 or 2352342 in SharePoint Server 2010
- SharePoint Foundation 2010 Cumulative Update Server Hotfix Package: August 31, 2010
- SharePoint Server 2010 Cumulative Update Server Hotfix Package: August 31, 2010
- Office 2010 Cumulative Update for August 2010