Updates that are included in this cumulative update package
- Workflow Manager Client 1.0 with Cumulative Update 3 (Full install)
This update makes some changes in core assemblies and client API for Workflow Manager and associated Visual Studio Tools. Workflow Manager is a multi-tenant and high-scale host for running and managing Windows Workflow Foundation workflows. It's a full MSI that can be installed on a fresh computer or in addition to Workflow Manager Client 1.0. It's compatible with Workflow Manager Client 1.0 Updates and also Workflow Manager 1.0 CU3. - Workflow Manager Tools 1.0 with Cumulative Update 3 (Full install) for Visual Studio 2012
This installation includes activity designers, debugging and expression translation for authoring workflows for Workflow Manager 1.0 CU3. It's compatible with Workflow Manager 1.0 CU3. - Workflow Manager 1.0 CU3 (Update)
This cumulative update contains several software updates. It should be used by customers who have Workflow Manager 1.0, Workflow Manager 1.0 Cumulative Update 1, or Workflow Manager 1.0 Cumulative Update 2 deployed. You have to install Workflow Manager Client 1.0 with Cumulative Update 3 (Full install) to update the client before you install this update that will update the server only.
Prerequisites
- Software requirements for Workflow Manager Tools 1.0 CU3:
- Workflow Manager Client 1.0 CU3 must be installed on the computer.
- Software requirements for Workflow Manager 1.0 CU3:
- PowerShell 3.0 must be installed on the computer to be updated. PowerShell 3.0 is included in the Windows Management Framework 3.0 installation. Go to Windows Management Framework 3.0 to install this update.
- Workflow Manager Client 1.0 CU3 must be installed first on the computer.
- For computers that have Workflow Manager 1.0 installed, one of the following additional requirements applies:
- The Service Bus for Windows Server cumulative update must be installed on the whole computer farm before you install the cumulative update for Workflow Manager 1.0.
2799752 Description of the Service Bus for Windows Server Cumulative Update: February 22, 2013
- Service Bus 1.1 for Windows Server must be installed on the computer.
- Supported operating systems: Windows Server 2008 R2 SP1, Windows Server 2012, and Windows Server 2012 R2
- Workflow Manager Client 1.0 can also be independently installed on the x86 and x64 versions of Windows 7, Windows 8, and Windows Server 2008.
- Credential requirements: Before you run the executable, you must have administrative credentials on the computer where you're installing the software. In addition you must log in as a user in the ManageUsers list of the Get-SBNamespace PowerShell command output.
- Do not manually stop any Service Bus service before the installation.
Deployment
For each computer that uses a Workflow Manager host in a computer farm, this update must be installed on that computer.
Database changes
There are some minimal database changes that will occur when this cumulative update is installed. If you decide to uninstall this update, these database changes are backward-compatible, and won't be rolled back.
Restart requirement
You may have to restart the computer after you apply this cumulative update.
Issues that are fixed in this cumulative update
Issue 1:
The workflow manager back-end service crashes intermittently, and you may experience the following exception:
System.AggregateException: One or more errors occurred. ---> System.Net.ProtocolViolationException: Cannot send a content-body with this verb-type.
at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Activities.Hosting.HostedHttpExtension.HttpRequestWorkItem.HttpRequestWorkItemAsyncResult.End(IAsyncResult result, Int32& responseCode)
at Microsoft.Activities.Hosting.HostedHttpExtension.HttpRequestWorkItem.OnEndComplete(ScheduledWorkItemContext context, IAsyncResult result)
at Microsoft.Activities.Hosting.ScheduledWorkItem.EndComplete(ScheduledWorkItemContext context, IAsyncResult result)
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.SingleNonTransactionalWorkItemComplete(IAsyncResult result)
---End of inner exception stack trace ---
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.UpdateNonTransactionalWork()
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.Isolate(AsyncCompletion callback, IAsyncResult result)
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.SingleNonTransactionalWorkItemComplete(IAsyncResult result)
--- End of inner exception stack trace ---
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.UpdateNonTransactionalWork()
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.Isolate(AsyncCompletion callback, IAsyncResult result)
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.SingleNonTransactionalWorkItemComplete(IAsyncResult result)
Issue 2:
The workflow manager back-end service crashes intermittently with the following exception:
System.ArgumentException: An item with the same key has already been added.
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value)
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.ProcessWaiter()
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.ProcessMatch(Boolean consumeInput)
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.StartEpisode()
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.ReceiveNextMessage()
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.UpdateNonTransactionalWork()
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.ProcessNonTransactionalWork()
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.ProcessWaiter()
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.ProcessMatch(Boolean consumeInput)
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.StartEpisode()
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.ReceiveNextMessage()
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.UpdateNonTransactionalWork()
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.Isolate(AsyncCompletion callback, IAsyncResult result) at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.ExceptionHandlingFrame(IAsyncResult result)
Issue 3:
The workflow manager back-end service crashes intermittently with the following exception:
System.ArgumentNullException: Value cannot be null.
Parameter name: key
at System.Collections.Generic.Dictionary`2.FindEntry(TKey key)
at System.Collections.Generic.Dictionary`2.TryGetValue(TKey key, TValue& value)
at Microsoft.Activities.Hosting.InputWaiterTable.InternalMatch(EventTraceActivity traceActivity, DateTime now, MessageDispatchProperties input, Guid currentInstanceId, Boolean removeWaiter, Guid currentSuspensionId, Boolean& consumeInput)
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.StartEpisode() at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.ReceiveNextMessage()
Issue 4:
The workflow manager back-end service crashes intermittently with the following exception:
System.ArgumentException: An item with the same key has already been added.
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value)
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.ProcessWaiter()
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.Isolate(AsyncCompletion callback, IAsyncResult result)
at Microsoft.Activities.Dispatcher.DispatchLoopInstanceAsyncResult.ExceptionHandlingFrame(IAsyncResult result)
Issue 5:
The restore scope operation fails, and you experience a unique key violation error as follows:
Restore-WFScope : Cannot insert duplicate key row in object 'dbo.Activities'
with unique index 'IX_Activities_Name_Version'. The duplicate key value is
(fef3537a-eefe-1340-5d86-335e62409f9c, IsEqualUser, 1).
The statement has been terminated.At C:\restoreScope.ps1:12 char:1
Issue 6:
Workflow manager front end can't report notification errors if a workflow notification message contains properties differ only in case. Instead, it emits the following exception in the event log:
System.ArgumentException: An item with the same key has already been added.
at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Gateway.HttpAsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Gateway.PublishWorkflowEventAsyncResult.End(IAsyncResult result)
at Microsoft.Workflow.Gateway.WorkflowServiceGateway.ExceptionFilter[T](Func`1 body) at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
Issue 7:
Instance is suspended instead of terminated if a non-transaction (Http) work item throws an exception.
Issue 8:
Enables WFM client to let you control retry behavior on http requests. You can add retry logic in the error handler on publish notification failures in WFM client.
Issue 9:
Fixes the
Set-WFCertificate command to enable users to update outgoing signing certificate thumbprint in WFM farm configuration.
Issue 10:
Fixes transaction leaks that are caused by stored procedure execution failures on workflow manager front end when you publish a workflow.
Issue 11:Prevents excessive growth of the Message Container databases which may result in the maximum Topic quota is exceeded and no workflow can be started.
