Hi there, according to the documentation, it states

"Workflow Manager 1.0 does not currently support direct SOAP messaging, including two-way (request-response) communication."

We need to provide some WCF services (on premises) which are required to be request response, do you guys think it is convenient to still consider Workflow Manager as an option (exploring workarounds to make this possible) or should we stick with Windows Server AppFabric?

Thanks in advance

Hello,

in order to install the 26/02/2013 version of the Microsoft Office Developer Tools for Visual Studio 2012, you need to install first the Service Bus 1.0 Cumulative Update 1.

The thing is that I can not install this update, I always get an error:

DownloadManager Information: 0 : Using cached file at C:\Users\Gilles\AppData\Local\Microsoft\Web Platform Installer\installers\ServiceBusCU1\5024FF633CA537CDB1C2903F97E1244457BAEE18\ServiceBus-KB2799752-x64-EN.exe instead of downloading from http://go.microsoft.com/fwlink/?LinkId=285191&CLCID=0x409
DownloadManager Information: 0 : Starting EXE command for product 'Service Bus 1.0 Cumulative Update 1'. Commandline is: 'C:\Users\Gilles\AppData\Local\Microsoft\Web Platform Installer\installers\ServiceBusCU1\5024FF633CA537CDB1C2903F97E1244457BAEE18\ServiceBus-KB2799752-x64-EN.exe /quiet'. Process Id: 6308
DownloadManager Information: 0 : Install exit code for product 'Service Bus 1.0 Cumulative Update 1' is '-1'
DownloadManager Error: 0 : Install return code for product 'Service Bus 1.0 Cumulative Update 1' is Failure
DownloadManager Information: 0 : Product Service Bus 1.0 Cumulative Update 1 done install completed
DownloadManager Information: 0 : Increasing current install to 2

if I run C:\Users\Gilles\AppData\Local\Microsoft\Web Platform Installer\installers\ServiceBusCU1\5024FF633CA537CDB1C2903F97E1244457BAEE18\ServiceBus-KB2799752-x64-EN.exe

I get : "an unexpected internal error has occured."

I am running Windows 8.

Somebody having the same issue?

Thx

Gilles

http://gilleslauwers.wordpress.com

I want to install workflow service for sharepoint 2013. All documents say I need to install workflow with web PI program.

But the problem is my sharepoint server can't access the internet. I tried running the web PI program on a Win7 PC in order to get the cached package, but it can't find the needed packages.

Could I get the packages by this way? If so, do I have to run web PI program on Win Server 2008?  If not, could I download these packages directly somewhere?

thanks.

Hello:

Workflow manager sounds every exciting to me, I am trying it out to see if it will work for me.

I downloaded "CustomCodeActivitySample" of workflow manager 1.0, and when I ran, I got following exception:

Workflow XAML failed validation due to the following errors:
Cannot create unknown type '{clr-namespace:HashActivity;assembly=HashActivity}ComputeHash'. HTTP headers received from the server - ActivityId: 2a1e4d9d-90bd-4f59-a1fc-d3673194dd54. NodeId: NDL0714. Scope: /CustomCodeActivitiesSample. Client ActivityId : 235d66c1-bbe6-4982-8242-833a6bc1f6b1.

more details:

Microsoft.Workflow.Client.ActivityValidationException was unhandled
  HResult=-2146233088
  Message=Workflow XAML failed validation due to the following errors:
Cannot create unknown type '{clr-namespace:HashActivity;assembly=HashActivity}ComputeHash'. HTTP headers received from the server - ActivityId: efe2c3cb-e6fd-4124-88a1-6c8e72aecb06. NodeId: NDL0714. Scope: /CustomCodeActivitiesSample. Client ActivityId : 73d7b773-be53-4a7b-b2d8-ba687e60a4f4.
  Source=Microsoft.Workflow.Client
  ActivityName=ProcessMovies
  ScopePath=/CustomCodeActivitiesSample
  StackTrace:
       at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest request, T content)
       at Microsoft.Workflow.Client.WorkflowManagementClient.SendRequest[T](HttpWebRequest request, T content)
       at Microsoft.Workflow.Client.ActivityManager.Publish(ActivityDescription description, Boolean overwriteXClassName, Boolean terminateDependentInstances)
       at Microsoft.Workflow.Client.ActivityManager.Publish(ActivityDescription description)
       at Microsoft.Workflow.Samples.Common.WorkflowManagementClientExtensions.PublishWorkflow(WorkflowManagementClient client, String workflowName, String xamlFilePath, Collection`1 externalVariables, IDictionary`2 configValues, SubscriptionFilter activationFilter) in c:\WFM_C\C\Microsoft.Workflow.Samples.Common\WorkflowManagementClientExtensions.cs:line 45
       at Microsoft.Workflow.Samples.Common.WorkflowManagementClientExtensions.PublishWorkflow(WorkflowManagementClient client, String workflowName, String xamlFilePath, SubscriptionFilter activationFilter) in c:\WFM_C\C\Microsoft.Workflow.Samples.Common\WorkflowManagementClientExtensions.cs:line 29
       at CustomCodeActivitySample.Program.Main(String[] args) in c:\WFM_C\C\CustomCodeActivitySample\Program.cs:line 39
       at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] args)
       at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
       at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
       at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
  InnerException: System.Net.WebException
       HResult=-2146233079
       Message=The remote server returned an error: (400) Bad Request.
       Source=Microsoft.Workflow.Common
       StackTrace:
            at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
            at Microsoft.Workflow.Client.HttpGetResponseAsyncResult`1.End(IAsyncResult result)
            at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest request, T content)
       InnerException:

Thanks

ahorse

When designing workflows in Visual Studio 2012, we are consistently running into a situation whereby clicking on the property value input box of an activity property, results in any existing value being cleared out and a message appearing which says "C:\ ..... \obj\x86\Debug\TemporaryGeneratedFile_E7 .... D3.cs  This file has been modified outside of the source editor. Do you want to reload it?".

Regardless of whether we choose Yes or No at this point, the property value has been erased and we cannot recover it. It happens more often than not. 

We've also noticed that selecting the ellipses button within the activity property value input box results in a blank input box - even if a c# expression is clearly visible within the property window.

We have installed the cumulative update for workflow manager 1.0 and are using Visual Studio 2012 with TFS 2012. 

Thanks,
Sohel Rana
http://ranaictiu-technicalblog.blogspot.com

Hi there,

Is there any way to implement request response workflows using Workflow Manager?

"Workflow Manager 1.0 does not currently support direct SOAP messaging, including two-way (request-response) communication." however wondering if that means it is not possible, I couldn't find any sample though

Thanks

• Windows Server 2008 R2 + SP1 (latest updates/patches), configured as Active Directory/Domain Controller in Windows Server 2003 forest/domain functional level.  
• Made Group Policy changes outlined here: http://blakeblackshear.wordpress.com/2010/11/23/sharepoint-2010-development-vm-part-6-setup-ad-and-configure-group-policy/ (essentially just stuff that makes a dev/eval environment easier such as disabling UAC, etc)
• Then installed SQL Server 2012 Developer.  
• Then installed SP2013 RTM bits (downloaded today).  Configured following Service Applications in SP: State Service, Secure Store, Managed Metadata, and Workflow Service.
  
• Downloaded WebPI for Workflow Manager: http://www.microsoft.com/en-my/download/details.aspx?id=35375.  Ran WebPI, and failed during installation of "Microsoft Windows Fabric", which is a dependency of Service Bus I believe.

Here is a link to the Windows Fabric installer log: https://skydrive.live.com/redir?resid=1154E613152247C2!1016&authkey=!ABCaCabHblUuQOE

* I know some folks are saying that installing on a Domain Controller is not possible, however, for as many as I find saying it's not possible, I find just as many saying it IS possible.

Update: I also tried running the Service Bus installer by itself, and same result.  Here is the link I used to download the installer: http://msdn.microsoft.com/en-us/library/jj193004(v=azure.10).aspx

Update 2:  Tried just the Windows Fabric installer.  Here are the two logs that got generated:

FabricSetup trace: https://skydrive.live.com/redir?resid=1154E613152247C2!1017&authkey=!AOfP8yEymG32DwY

FabricDeployer trace: https://skydrive.live.com/redir?resid=1154E613152247C2!1018&authkey=!AKwER4bwr2RM97M

Update 3: from the FabricSetup logs:

-brian

Brian McCullough

Hi,

PublishNotification is pushing a brokered message on the Service Bus. The SB client libraries have highly efficient async methods to push and pull messages (3000 msg/sec on a dual-core i7 laptop).

PublishNotification, on the other hand, is struggling to reach 40 msg/sec on the same machine. There are no workflows published, so the Workflow Manager is just dequeuing the messages.

I can't find an async version of PublishNotification. Any tips on how to improve performance?

The code is straightforward:

for (i = 0; i < 1000; i++)
{
   client.PublishNotification (new WorkflowNotification()
   {
      Properties = { { "EventName", "New Msg" } }
    });
}

Thanks

I have just posted a new Workflow Manager getting started tutorial:

Workflow Manager 1.0 Getting Started Tutorial

This is a 3 step tutorial which covers creating a custom activity, using it in a workflow, and publishing and invoking the workflow. It covers the use of the HttpSend activity, and several of the DynamicValue activities, as well as other control flow, primitives, and runtime activities.

There is a video walkthrough and a download of the completed tutorial here:

Workflow Manager 1.0 Getting Started Tutorial Download and Video Walkthrough

This download also includes the starter files for the tutorial.

Please check it out and let me know what you think, and what you would like to see for future tutorials.

Thanks,

Steve Danielson [Microsoft]
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm

Hi,

I'm trying to configure Workflow Manager 1.0 with the wizard but I have faced the bad request error. Here is the log:

[Verbose] [16/05/2013 13:58:50]: Created and configured Service Bus farm management database.
[Progress] [16/05/2013 13:58:50]: Created and configured Service Bus farm management database.
[Verbose] [16/05/2013 13:58:53]: Created and configured Service Bus gateway database.
[Progress] [16/05/2013 13:58:53]: Created and configured Service Bus gateway database.
[Verbose] [16/05/2013 13:58:53]: Configuration added to farm management database.
[Verbose] [16/05/2013 13:58:53]: Generating Certificate.
[Verbose] [16/05/2013 13:58:57]: Service Bus configuration added to the farm management database.
[Verbose] [16/05/2013 13:58:57]: Creating default container.
[Progress] [16/05/2013 13:58:57]: Creating default container.
[Verbose] [16/05/2013 13:59:02]: New-SBFarm successfully completed.
[Info] [16/05/2013 13:59:02]: Microsoft.ServiceBus.Commands.SBFarmInfo

[Info] [16/05/2013 13:59:02]: Processing completed
[Verbose] [16/05/2013 13:59:04]: Created and configured farm management database.
[Progress] [16/05/2013 13:59:04]: Created and configured farm management database.
[Verbose] [16/05/2013 13:59:07]: Created and configured Workflow Manager resource management database.
[Progress] [16/05/2013 13:59:07]: Created and configured Workflow Manager resource management database.
[Verbose] [16/05/2013 13:59:09]: Created and configured Workflow Manager instance management database.
[Progress] [16/05/2013 13:59:09]: Created and configured Workflow Manager instance management database.
[Verbose] [16/05/2013 13:59:09]: Configuration added to farm management database.
[Verbose] [16/05/2013 13:59:09]: Generating certificate.
[Verbose] [16/05/2013 13:59:10]: Workflow Manager configuration added to the Workflow Manager farm management database.
[Verbose] [16/05/2013 13:59:10]: New-WFFarm successfully completed.
[Info] [16/05/2013 13:59:10]: Microsoft.Workflow.Deployment.Commands.WFFarmInfo

[Info] [16/05/2013 13:59:10]: Processing completed
[Verbose] [16/05/2013 13:59:11]: Validating input and configuration parameters.
[Progress] [16/05/2013 13:59:11]: Validating input and configuration parameters.
[Verbose] [16/05/2013 13:59:11]: Installing auto-generated certificate.
[Progress] [16/05/2013 13:59:11]: Installing auto-generated certificate.
[Verbose] [16/05/2013 13:59:11]: Granting 'Log on as Service' privilege to the run as account.
[Progress] [16/05/2013 13:59:11]: Granting 'Log on as Service' privilege to the run as account.
[Verbose] [16/05/2013 13:59:12]: Windows Fabric configuration started.
[Progress] [16/05/2013 13:59:12]: Windows Fabric configuration started.
[Verbose] [16/05/2013 13:59:12]: Windows Fabric cluster manifest generated.
[Verbose] [16/05/2013 13:59:12]: Running Windows Fabric deployment.
[Progress] [16/05/2013 13:59:12]: Running Windows Fabric deployment.
[Verbose] [16/05/2013 13:59:14]: Windows Fabric starting.
[Progress] [16/05/2013 13:59:14]: Windows Fabric starting.
[Verbose] [16/05/2013 13:59:15]: Service Bus configuration started.
[Progress] [16/05/2013 13:59:15]: Service Bus configuration started.
[Verbose] [16/05/2013 13:59:23]: Updating database.
[Progress] [16/05/2013 13:59:23]: Updating database.
[Verbose] [16/05/2013 13:59:23]: Service Bus services starting.
[Progress] [16/05/2013 13:59:23]: Service Bus services starting.
[Verbose] [16/05/2013 13:59:37]: Restarting Service Bus Farm.
[Verbose] [16/05/2013 13:59:37]: Updating local registry.
[Progress] [16/05/2013 13:59:37]: Updating local registry.
[Verbose] [16/05/2013 13:59:39]: Successfully added this host to the farm.
[Progress] [16/05/2013 13:59:39]: Successfully added this host to the farm.
[Info] [16/05/2013 13:59:39]: Microsoft.ServiceBus.Commands.SBFarmInfo

[Info] [16/05/2013 13:59:39]: Processing completed
[Info] [16/05/2013 13:59:40]: Name: WorkflowDefaultNamespace
AddressingScheme: Path
CreatedTime: 16/05/2013 16:59:40
IssuerName: WorkflowDefaultNamespace
IssuerUri: WorkflowDefaultNamespace
ManageUsers: abc@xyz.com.br
DnsEntry:
PrimarySymmetricKey:
SecondarySymmetricKey:

[Info] [16/05/2013 13:59:40]: Processing completed
[Info] [16/05/2013 14:01:10]: Endpoint=sb://xyz.com.br/WorkflowDefaultNamespace;StsEndpoint=https://xyz.com.br:9355/WorkflowDefaultNamespace;RuntimePort=9354;ManagementPort=9355

[Info] [16/05/2013 14:01:10]: Processing completed
[Verbose] [16/05/2013 14:01:11]: Validating input and configuration parameters.
[Verbose] [16/05/2013 14:01:11]: Installing auto-generated certificate.
[Progress] [16/05/2013 14:01:11]: Installing auto-generated certificate.
[Verbose] [16/05/2013 14:01:11]: Granting 'Log on as Service' privilege to the RunAs account.
[Progress] [16/05/2013 14:01:11]: Granting 'Log on as Service' privilege to the RunAs account.
[Verbose] [16/05/2013 14:01:11]: Workflow Manager configuration starting.
[Progress] [16/05/2013 14:01:11]: Workflow Manager configuration starting.
[Verbose] [16/05/2013 14:01:15]: Configuring Workflow Manager runtime settings.
[Progress] [16/05/2013 14:01:15]: Configuring Workflow Manager runtime settings.
[Error] [16/05/2013 14:01:20]: System.Management.Automation.CmdletInvocationException: O servidor remoto retornou um erro: (400) Solicitação Incorreta. Incorrect request Uri format..TrackingId:188e90f3-6546-4459-b3e7-399867b00591_GMS-PRO143,TimeStamp:16/05/2013 17:01:19 ---> System.ArgumentException: O servidor remoto retornou um erro: (400) Solicitação Incorreta. Incorrect request Uri format..TrackingId:188e90f3-6546-4459-b3e7-399867b00591_GMS-PRO143,TimeStamp:16/05/2013 17:01:19 ---> System.Net.WebException: O servidor remoto retornou um erro: (400) Solicitação Incorreta.
   em System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   em Microsoft.ServiceBus.Messaging.ServiceBusResourceOperations.GetAsyncResult`1.EndGetResponse(GetAsyncResult`1 thisPtr, IAsyncResult ar)
   em Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StepCallback(IAsyncResult result)
   --- Fim do rastreamento de pilha de exceções internas ---

Server stack trace:


Exception rethrown at [0]:
   em Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
   em Microsoft.ServiceBus.NamespaceManager.OnEndTopicExists(IAsyncResult result)
   em Microsoft.ServiceBus.NamespaceManager.TopicExists(String path)
   em Microsoft.Workflow.Deployment.Commands.WorkflowServiceConfigHelper.SetWFRuntimeSettings(String resourceDBConnectionString, String config)
   em Microsoft.Workflow.Deployment.Commands.AddWFHost.CallWFRuntimeSettings(Service wfserviceInfo, String unencryptedResourceConnectionString)
   --- Fim do rastreamento de pilha de exceções internas ---
   em System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
   em Microsoft.Workflow.Deployment.ConfigWizard.CommandletHelper.InvokePowershell(Command command, Action`3 updateProgress)
   em Microsoft.Workflow.Deployment.ConfigWizard.ProgressPageViewModel.AddWFNode(FarmCreationModel model, Boolean isFirstCommand)

I've reinstalled the workflow manager and nothing change.

Thanks.

Vinicius

I've recently built a new SharePoint 2013 farm and have deployed workflow to a mail enabled document library. 

If the workflow is 2013 mode it will not be triggered by a new item added to a library via email. The same thing works fine for a 2010 mode workflow. 

Is there any known reason why this won't work with the new workflow manager in SP2013?

Hello,

I'm having trouble configuring WM on my machine. In a nutshell, it complains about the Fabric Data Collection Agent being disabled. Here's the full error message:

Starting

And here's the log file:

I must say that all AppFabric services are running, even AppFabric Event Collection Service (don't know if it is the same, though).

Any ideas? Has anyone experienced this problem?

Cheers,

RP

Hi All,

I am trying to apply Cumulative Update for Workflow Manager 1.0 (KB2799754) to the workflow servers in our farm. 5 out of 6 servers have been updated successfully, but the last server kept erroring out. From the log file I got this information:

[05/16/13 16:17:15] Process exit code is -1.
Complete-WFHostUpgrade : CompleteUpgrade is not allowed because the upgrade step has not entered Started state yet. Either wait for that state, or call InitiateUpgrade again.
At C:\ProgramData\Microsoft\E-Business Servers Updates\Updates\Uninstall2799754\UnifiedWFHotfixUpgrade.PS1:584 char:5
+           Complete-WFHostUpgrade -TargetWFVersion $TargetWFVersion
+           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : WriteError: (:) [Complete-WFHostUpgrade], InvalidOperationException
    + FullyQualifiedErrorId : WFServiceUpgradeFailed,Microsoft.Workflow.Deployment.Commands.CompleteWFHostUpgrade

What does Complete-WFHostUpgrade do anyway? How do I get around this problem? I'm already considering removing this server from the farm, renstall the original WM binary, appy the update then add it back to the farm. But just wondering if any has come across this issue and had it fixed.

Any idea is very much appreciated.

Hi,

I've developed few workflows (2013) and deployed. All of sudden I can't associate the workflows. As I try to associate the workflows, the page just refreshes. Investigating log file I've found the workflow ID is empty guid. So, though the workflows are showing in the workflow association form, the workflow id is empty guid as a result the association is failing. I was wondering if it's possible to delete the workflow definition?

Thanks,
Sohel Rana
http://ranaictiu-technicalblog.blogspot.com

Can anyone from the product team comment on whether Service Bus and Workflow Manager have been tested on Hyper-V within VMs that had Dynamic Memory enabled?

Anybody know how  integrate Service bus and Workflow manager 1.0 for a .NET Multi-Tier Application (see: http://www.windowsazure.com/en-us/develop/net/tutorials/multi-tier-application/)

using Service Bus Server 1.0 instead of Azure Service bus

using Work Flow Manager 1.0 instead of Worker Role

Thanks in advance

Samuele

Hello everyone,

     I have successfully installed Workflow Manager 1.0 (and its prerequisites) on my Server 2008 R2 SP1 machine that is hosting Sharepoint 2013.  I attempt to go into the Workflow Manager Configuration.  That comes up and asks me if I want to Create new farm with Default Settings, New Farm with custom settings, or existing farm.  I've tried both Default settings AND Custom settings.

•            When the configuration wizard comes up, I attempt to fill out the necessary information.  It seems to connect to the SQL server without a problem.  I only run into an issue when setting the USER ID.  The program totally freezes up and force closes. 
•            I have verified that the USERID is in the correct format and tried multiple different formats.  The problem is that the moment I move the cursor from the USERID field to ANY other field, the program force closes.  I'm not able to hit submit, I'm not able to change any other options.  The moment USERID is manipulated or the cursor LEAVES the USERID field, the program force closes.  It won't even allow me to put in a password before it force closes.
•             Customer domain is running in Windows Server 2003 Enterprise Edittion SP2.

Any ideas?

Thank you very much!

•        I have copied the errors from event viewer below:

APPLICATION ERROR

Faulting application name: Microsoft.Workflow.Deployment.ConfigWizard.exe, version: 1.0.20922.0, time stamp: 0x505e1b30
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17965, time stamp: 0x506dcae6
Exception code: 0xe0434352
Fault offset: 0x000000000000bccd
Faulting process id: 0x17f8
Faulting application start time: 0x01cddee198ece72e
Faulting application path: C:\Program Files\Workflow Manager\1.0\Microsoft.Workflow.Deployment.ConfigWizard.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 22ab8b69-4ad5-11e2-af8f-005056965915

.NET Runtime Error

Application: Microsoft.Workflow.Deployment.ConfigWizard.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.COMException
Stack:
   at System.DirectoryServices.AccountManagement.PrincipalContext.DoLDAPDirectoryInitNoContainer()
   at System.DirectoryServices.AccountManagement.PrincipalContext.DoDomainInit()
   at System.DirectoryServices.AccountManagement.PrincipalContext.Initialize()
   at System.DirectoryServices.AccountManagement.PrincipalContext.get_QueryCtx()
   at System.DirectoryServices.AccountManagement.Principal.FindByIdentityWithTypeHelper(System.DirectoryServices.AccountManagement.PrincipalContext, System.Type, System.Nullable`1<System.DirectoryServices.AccountManagement.IdentityType>, System.String, System.DateTime)
   at System.DirectoryServices.AccountManagement.UserPrincipal.FindByIdentity(System.DirectoryServices.AccountManagement.PrincipalContext, System.String)
   at Microsoft.ServiceBus.Commands.Common.SecurityHelper.IsUserValid(System.DirectoryServices.AccountManagement.PrincipalContext, System.String)
   at Microsoft.ServiceBus.Commands.Common.SecurityHelper.IsDomainUserValid(System.String, System.String)
   at Microsoft.ServiceBus.Commands.Common.ValidateUserAttribute.Validate(System.String)
   at Microsoft.Deployment.ConfigWizard.UICommon.AccountDetailsViewModel.ValidateDomainUser()
   at Microsoft.Deployment.ConfigWizard.UICommon.AccountDetailsControl.UserIdTextBox_LostFocus(System.Object, System.Windows.RoutedEventArgs)
   at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
   at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs)
   at System.Windows.Controls.Primitives.TextBoxBase.OnLostFocus(System.Windows.RoutedEventArgs)
   at System.Windows.UIElement.IsFocused_Changed(System.Windows.DependencyObject, System.Windows.DependencyPropertyChangedEventArgs)
   at System.Windows.DependencyObject.OnPropertyChanged(System.Windows.DependencyPropertyChangedEventArgs)
   at System.Windows.FrameworkElement.OnPropertyChanged(System.Windows.DependencyPropertyChangedEventArgs)
   at System.Windows.Controls.TextBox.OnPropertyChanged(System.Windows.DependencyPropertyChangedEventArgs)
   at System.Windows.DependencyObject.NotifyPropertyChange(System.Windows.DependencyPropertyChangedEventArgs)
   at System.Windows.DependencyObject.UpdateEffectiveValue(System.Windows.EntryIndex, System.Windows.DependencyProperty, System.Windows.PropertyMetadata, System.Windows.EffectiveValueEntry, System.Windows.EffectiveValueEntry ByRef, Boolean, Boolean, System.Windows.OperationType)
   at System.Windows.DependencyObject.ClearValueCommon(System.Windows.EntryIndex, System.Windows.DependencyProperty, System.Windows.PropertyMetadata)
   at System.Windows.DependencyObject.ClearValue(System.Windows.DependencyPropertyKey)
   at System.Windows.Input.FocusManager.OnFocusedElementChanged(System.Windows.DependencyObject, System.Windows.DependencyPropertyChangedEventArgs)
   at System.Windows.DependencyObject.OnPropertyChanged(System.Windows.DependencyPropertyChangedEventArgs)
   at System.Windows.FrameworkElement.OnPropertyChanged(System.Windows.DependencyPropertyChangedEventArgs)
   at System.Windows.DependencyObject.NotifyPropertyChange(System.Windows.DependencyPropertyChangedEventArgs)
   at System.Windows.DependencyObject.UpdateEffectiveValue(System.Windows.EntryIndex, System.Windows.DependencyProperty, System.Windows.PropertyMetadata, System.Windows.EffectiveValueEntry, System.Windows.EffectiveValueEntry ByRef, Boolean, Boolean, System.Windows.OperationType)
   at System.Windows.DependencyObject.SetValueCommon(System.Windows.DependencyProperty, System.Object, System.Windows.PropertyMetadata, Boolean, Boolean, System.Windows.OperationType, Boolean)
   at System.Windows.DependencyObject.SetValue(System.Windows.DependencyProperty, System.Object)
   at System.Windows.FrameworkElement.OnGotKeyboardFocus(System.Object, System.Windows.Input.KeyboardFocusChangedEventArgs)
   at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object)
   at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
   at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs)
   at System.Windows.UIElement.RaiseTrustedEvent(System.Windows.RoutedEventArgs)
   at System.Windows.Input.InputManager.ProcessStagingArea()
   at System.Windows.Input.KeyboardDevice.ChangeFocus(System.Windows.DependencyObject, Int32)
   at System.Windows.Input.KeyboardDevice.Focus(System.Windows.DependencyObject, Boolean, Boolean, Boolean)
   at System.Windows.Input.KeyboardDevice.Focus(System.Windows.IInputElement)
   at System.Windows.UIElement.Focus()
   at System.Windows.Input.KeyboardNavigation.Navigate(System.Windows.DependencyObject, System.Windows.Input.TraversalRequest, System.Windows.Input.ModifierKeys, System.Windows.DependencyObject)
   at System.Windows.Input.KeyboardNavigation.Navigate(System.Windows.DependencyObject, System.Windows.Input.Key, System.Windows.Input.ModifierKeys)
   at System.Windows.Input.KeyboardNavigation.ProcessInput(System.Windows.Input.InputEventArgs)
   at System.Windows.Input.InputManager.RaiseProcessInputEventHandlers(System.Windows.Input.ProcessInputEventHandler, System.Windows.Input.ProcessInputEventArgs)
   at System.Windows.Input.InputManager.ProcessStagingArea()
   at System.Windows.Input.InputManager.ProcessInput(System.Windows.Input.InputEventArgs)
   at System.Windows.Interop.HwndKeyboardInputProvider.ReportInput(IntPtr, System.Windows.Input.InputMode, Int32, System.Windows.Input.RawKeyboardActions, Int32, Boolean, Boolean, Int32)
   at System.Windows.Interop.HwndKeyboardInputProvider.ProcessKeyAction(System.Windows.Interop.MSG ByRef, Boolean ByRef)
   at System.Windows.Interop.HwndSource.CriticalTranslateAccelerator(System.Windows.Interop.MSG ByRef, System.Windows.Input.ModifierKeys)
   at System.Windows.Interop.HwndSource.OnPreprocessMessage(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   at System.Windows.Threading.Dispatcher.Invoke(System.Windows.Threading.DispatcherPriority, System.Delegate, System.Object)
   at System.Windows.Interop.HwndSource.OnPreprocessMessageThunk(System.Windows.Interop.MSG ByRef, Boolean ByRef)
   at System.Windows.Interop.ComponentDispatcherThread.RaiseThreadMessage(System.Windows.Interop.MSG ByRef)
   at System.Windows.Threading.Dispatcher.TranslateAndDispatchMessage(System.Windows.Interop.MSG ByRef)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Application.RunInternal(System.Windows.Window)
   at System.Windows.Application.Run()
   at Microsoft.Workflow.Deployment.ConfigWizard.App.Main()

We have an issue with user logins and their use in Workflow Manager workflows, these workflows have been created in SharePoint designer.

Background:

* Environment

SharePoint 2013 with WFM 1.0 Feb Update, SharePoint Mar and Apr updates.

* Create two users in AD with the following details

First Name: Jack

Surname: Smi

Login: jsmi@domain

First Name: John

Surname: Smith

Login: jsmith@domain

* Create a Custom List and add a People column.

* Create a list 2013 workflow in SharePoint designer.

* First Action: Set your new people column to = item created by user, using Login value

* Second Action: Write a history record displaying the Display Name of your People column value.

Result:

* Create a list item and start workflow as jsmi@domain (Jack Smi)

* People column displays John Smith (Should be Jack Smi)

* Name displayed in history is John Smith (Should be Jack Smi)

Observation:

* We can reproduce this in at least two separate SharePoint 2013 environments.

* We can make sure the right user is assigned by "Set" action in workflow by using the User ID when copying from the source.

* We can not display the correct users name in any history or emails as choosing to show the Display Name of a people variable forjsmi@domain always show the display name for jsmith@domain.

Help:

* Anyone else come across this issue?

* Know of any work arounds?

Thanks.