Currupted Workflow Manager Configuration, RE-Installation Guidence?

Dear All,
We have few workflows which are currently running in our SP 2013 server farm. The workflows stopped working for sometime, when we examined the errors, we could see that we are no longer able to open the workflow manager and Service Bus configuration wizards,
they say a certificate is missing in the certificate Store.
But on visiting the certificate store, I can see that there is a certificate with the Thumbprint specified in the error but it is expired.
We are not able to find any guidance on how to solve these errors. The Workflow Manager documentation doesn't have this info as on date.
We can't make our workflows run in the usual way.
We can't find any guidance on how to re-install the Workflow Manager on such server Farm with workflows deployed and with their history.
Could you please let us know any possible solution.
Best regards,
Prem
-Prem

In Test env try to remove all servers from the farm without deleting dbs or uninstalling, then rejoin them, and recreate the certs.

Similar Messages

Workflow Manager Configuration Wizard is not working with USER ID

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?
I have installed also cumulative update to avoid crash but still I am getting force to close workflow wizard. I have used users which are already added in administrator groups.
We are using 3 tier architecture for Sharepoint 2013.
Also we have made Alias of Domain controller. Eg:-Alias is "labs" for domain "xyz.ab.com".
And we are using labs\spadmin and labs\spservice for Workflow Manager Configuration 1.0
Is there any issue with Domain Alias "labs" as Workflow gives error "Specified RunAs account is invalid" or "Force close the application".
  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()
Thanks
Hansraj Rathva

Check to ensure that the user you're running the wizard as has access to the Users and Computers folders in Active Directory. I had trouble with the "specified RunAs account is invalid" message, and when I granted the AD rights, I was able to proceed.
The issue would be that the user executing the wizard isn't able to query AD to look up the specified user. The RunAs account you're specifying is probably fine.

Workflow Manager Configuration - Certificate with Thumbprint does not have a private key

After following the video series on how to install and Configure Workflow Manager into SharePoint 2013 http://technet.microsoft.com/en-us/library/dn201724(v=office.15).aspx,
I get to the 'Configure Certificates' section in the Workflow Manager Configuration: I browse to our wildcard certificate and select it.
When I try to move to the next page of the configuration wizard, I get the following red error under the certificate:
Certificate with thumbprint LONG STRING does not have a private key.
I checked the properties of the certificate, and it says: You have a private key that corresponds to this certificate.
What am I missing??
Thank you.
macrel

Hi,
According to your post, my understanding is that you got error under the certificate.
Please make sure you configure the workflow manager correctly.
More information:
Install and configure workflow for SharePoint Server 2013
Installing and Configuring Workflow Manager 1.0
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Workflow manager configuration wizard failing

On running the Workflow Manager Configuration Wizard on our new SharePoint 2013 site, it fails at the stage "Add host to Service Bus farm". I am running as domain admin and have attempted this multiple times but it keeps failing on this part.
Error log gives this: "[Error] [29/05/2013 11:34:25]: System.Management.Automation.CmdletInvocationException: Starting service Service Bus Message Broker failed: Time out has expired and the operation has not been completed. ---> Microsoft.ServiceBus.Commands.Common.Exceptions.OperationFailedException:
Starting service Service Bus Message Broker failed: Time out has expired and the operation has not been completed."
Anybody know the solution to this?
Thanks

Hi Brendan,
Is there additional information in Event Viewer?
Also, probably the following links will be helpful for you:
Troubleshooting Workflow Manager 1.0 Management and Execution
Problem starting message broker during service broker configuration
Regards Michael (http://sp2013-blog.com)
Please, don't forget to press upvote (if answer is helpful) and mark as answer (if it solves your issue)

Workflow Manager Configuration Issue Windows Server 2012 R2 / SQL 2014

Hello All,
Environment: SharePoint 2013 Enterprise with SP1
Farm consists of
2 App Server, 2 Web Server and 2 SQL Servers all the server have Windows 2012 R2
OS . The SQL backend is SQL Server 2014
Installed Workflow manager on the Web server, the configuration ran fine without any errors. Trying to browse the workflow management site via IIS Manager encountered Certificate Error clicked Continue to this website which gives a HTTP 403 Forbidden and
following detail message
This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage.
Checked the web site Workflow Management Site in the IIS manager which has only one folder bin . I was not able to submit the Screenshot
I have installed the latest patch for the Workflow manager and the Service Bus
Question I have
Should there be more folder under the Workflow Management Site.
Why is the Web site not showing the web page
Is workflow manager supported for Windows Server 2012 R2 and SQL 2014
Thanks
Dhanraj

Hi Dhanraj,
I captured the screenshot from my IIS Manager on workflow server. There is only bin folder under Workflow Management site
If I browser workflow host uri from IIS Manager
https://localhost:12290, I received certification error, and I chose the continue to this website, it returned me as follow:
From the link: http://support.microsoft.com/kb/2902007/en-us It is supported on Windows Server 2012 r2 if you have install latest update.
Here is an article which talks about error:
http://www.sp2013blog.com/Lists/Posts/Post.aspx?ID=36
In addition, here is the reference for troubleshooting workflow manager 1.0 management:
http://msdn.microsoft.com/en-us/library/jj193529(v=azure.10).aspx#AnalyzingWorkflowManagementLogs
You could also open SharePoint Designer 2013 and see if you could create a workflow on platform 2013.
Regards,
Rebecca Tu
TechNet Community Support

Workflow Manager Configuration Wizard stuck on "create a new service bus farm"

Hi!
I'm looking for help because i recently tried to install WF Manager on my VM with SP 2013 SP1. Unfortunately every time i try to set wf manager im stuck on this screen:
View Log:
It seems like its stuck "generating certificate". I dont know why and how to troubleshoot this problem. I already tried to wait several hours and nothing happened ....

Hi Brendan,
Is there additional information in Event Viewer?
Also, probably the following links will be helpful for you:
Troubleshooting Workflow Manager 1.0 Management and Execution
Problem starting message broker during service broker configuration
Regards Michael (http://sp2013-blog.com)
Please, don't forget to press upvote (if answer is helpful) and mark as answer (if it solves your issue)

What permission does the Service account requires on AD for the Workflow manager 1.0 to be configured in SharePoint Farm?

What permission does the Service account requires on AD for the Workflow manager 1.0 to be configured in SharePoint Farm?
The workflow manager configuration wizard crashes with the below error when used a domain account (setup account with full prvilige on sql and server). It requires some specific permissions on AD ? I couldnt see any documentation stating what permission
it requires.
Can anyone help ?
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: AUTRTV22OQMI5JWSVNDSSNCH0E5DQ2L1
Problem Signature 02: 1.0.20922.0
Problem Signature 03: 505e1b30
Problem Signature 04: System.DirectoryServices.AccountManagement
Problem Signature 05: 4.0.30319.17929
Problem Signature 06: 4ffa5bda
Problem Signature 07: 3ef
Problem Signature 08: 348
Problem Signature 09: KCKGYE1NBUPA2CLDHCXJ0IFBDVSEPD1F
OS Version: 6.2.9200.2.0.0.272.7
Locale ID: 1044
Additional Information 1: 8e7b
Additional Information 2: 8e7b3fcdf081688bfcdf47496694f0e4
Additional Information 3: c007
Additional Information 4: c007e99b2d5f6f723ff4e7b990b5c691
Log Name:      Application
Source:        Application Error
Date:          27.08.2014 11:47:54
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      OSS01-MAP-226.global.corp
Description:
Faulting application name: Microsoft.Workflow.Deployment.ConfigWizard.exe, version: 1.0.20922.0, time stamp: 0x505e1b30
Faulting module name: KERNELBASE.dll, version: 6.2.9200.16864, time stamp: 0x531d34d8
Exception code: 0xe0434352
Fault offset: 0x0000000000047b8c
Faulting process id: 0x23a0
Faulting application start time: 0x01cfc1dbe703a8ac
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: 36f30eb4-2dcf-11e4-9415-005056892fae
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-08-27T09:47:54.000000000Z" />
    <EventRecordID>7471545</EventRecordID>
    <Channel>Application</Channel>
    <Computer>OSS01-MAP-226.global.corp</Computer>
    <Security />
</System>
<EventData>
    <Data>Microsoft.Workflow.Deployment.ConfigWizard.exe</Data>
    <Data>1.0.20922.0</Data>
    <Data>505e1b30</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>6.2.9200.16864</Data>
    <Data>531d34d8</Data>
    <Data>e0434352</Data>
    <Data>0000000000047b8c</Data>
    <Data>23a0</Data>
    <Data>01cfc1dbe703a8ac</Data>
    <Data>C:\Program Files\Workflow Manager\1.0\Microsoft.Workflow.Deployment.ConfigWizard.exe</Data>
    <Data>C:\Windows\system32\KERNELBASE.dll</Data>
    <Data>36f30eb4-2dcf-11e4-9415-005056892fae</Data>
    <Data>
    </Data>
    <Data>
    </Data>
</EventData>
</Event>
Log Name:      Application
Source:        .NET Runtime
Date:          27.08.2014 11:47:54
Event ID:      1026
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      OSS01-MAP-226.global.corp
Description:
Application: Microsoft.Workflow.Deployment.ConfigWizard.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.DirectoryServices.AccountManagement.MultipleMatchesException
Stack:
   at System.DirectoryServices.AccountManagement.ADStoreCtx.FindPrincipalByIdentRefHelper(System.Type, System.String, System.String, System.DateTime, Boolean)
   at System.DirectoryServices.AccountManagement.ADStoreCtx.FindPrincipalByIdentRef(System.Type, System.String, System.String, System.DateTime)
   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.Documents.TextEditorMouse.MoveFocusToUiScope(System.Windows.Documents.TextEditor)
   at System.Windows.Documents.TextEditorMouse.OnMouseDown(System.Object, System.Windows.Input.MouseButtonEventArgs)
   at System.Windows.UIElement.OnMouseDownThunk(System.Object, System.Windows.Input.MouseButtonEventArgs)
   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.InputProviderSite.ReportInput(System.Windows.Input.InputReport)
   at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr, System.Windows.Input.InputMode, Int32, System.Windows.Input.RawMouseActions, Int32, Int32, Int32)
   at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr, Boolean ByRef)
   at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(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 MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(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()
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name=".NET Runtime" />
    <EventID Qualifiers="0">1026</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-08-27T09:47:54.000000000Z" />
    <EventRecordID>7471544</EventRecordID>
    <Channel>Application</Channel>
    <Computer>OSS01-MAP-226.global.corp</Computer>
    <Security />
</System>
<EventData>
    <Data>Application: Microsoft.Workflow.Deployment.ConfigWizard.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.DirectoryServices.AccountManagement.MultipleMatchesException
Stack:
   at System.DirectoryServices.AccountManagement.ADStoreCtx.FindPrincipalByIdentRefHelper(System.Type, System.String, System.String, System.DateTime, Boolean)
   at System.DirectoryServices.AccountManagement.ADStoreCtx.FindPrincipalByIdentRef(System.Type, System.String, System.String, System.DateTime)
   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.Documents.TextEditorMouse.MoveFocusToUiScope(System.Windows.Documents.TextEditor)
   at System.Windows.Documents.TextEditorMouse.OnMouseDown(System.Object, System.Windows.Input.MouseButtonEventArgs)
   at System.Windows.UIElement.OnMouseDownThunk(System.Object, System.Windows.Input.MouseButtonEventArgs)
   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.InputProviderSite.ReportInput(System.Windows.Input.InputReport)
   at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr, System.Windows.Input.InputMode, Int32, System.Windows.Input.RawMouseActions, Int32, Int32, Int32)
   at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr, Boolean ByRef)
   at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(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 MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(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()
</Data>
</EventData>
</Event>

Hi Karthik,
You could refer to the series of videos below to install and configure workflow manager in SharePoint 2013:
http://technet.microsoft.com/en-us/library/dn201724(v=office.15).aspx
The Episode 2 describes the necessary account in AD with right permission in the installation process:
http://technet.microsoft.com/en-us/library/dn201724(v=office.15).aspx#episode2
Regards,
Rebecca Tu
TechNet Community Support

Facing some problem while configuring Workflow Manager 1.0.

Hi,
I am facing some problem while configuring Workflow Manager 1.0. in my farm.
Scenario is,
I have installed and configured workflow manager in my farm, it was working well with no issue. But one of team member played with AD and deleted Farm administrator's entry from AD by mistake. So suddenly workflows get affected and stopped working.
Then I added administrator entry in AD, uninstalled the Workflow Manager and installed it again. But now while configuring workflow manager I am facing some issues that "Failure to adding user in BUILTIN\Administrative group. Please add it manually"
And after sometime it shows another error message that, "Starting service Service Bus Massage broken failed: Timed out has expired, the operation has not been completed"
If I go for services then "Service bus Message broker" service is not running properly (Its status is just showing "Starting") and don't starts.
I have also added the user in BUILTIN\Administrator, IIS_IUSER, WSS_WPG group of the machine from computer manager - user and groups.
Also given permission to databases, and assign role of sysadmin and dbcreator to user
I also tried following steps
1) Stop all services associated to workflows
2) Uninstalled workflow manager
3) Deleted all databases associated with workflows
4) Installed workflow manager and tried to configure.
But showing same error.
If I use another SharePoint server farm to configure workflows, there I am not getting first error of adding user to BUILTIN\Administrator group. but second error remains same.
We having SQL server and Active directory at another machine and FARM at another machine, if I use local admin for configuration of the workflows (as local admin can start any services) but entry of local admin is not Active directory so can not assign SQL's
sysadmin, and dbcreator role to local admin.
I am attaching snapshot of error for better understanding.
Your help will be very precious to me.
Thanks,
Rajesh
Rajesh Agravat

Rajesh
Check to see what the service accounts are being used for these Workflow Manager 1.0 services:
Service Bus Message Broker
Service Bus Gateway
Workflow Manager Backend
All of these should be running and your workflow service account should be running all of these. If any are still configured under the old service account, they'll need to be updated. Next, check to see what service accounts have access to the
Workflow Manager 1.0 databases:
SbGatewayDatabase
SbManagement
SbMessageContainer
WFInstanceManagement
WFManagement
WFResourceManagement
The Workflow Manager service account should be mapped as the DBO for all of these. if any are still configured under the old service account, they'll need to be updated.
Given the complete loss of the original workflow service account, and the resultant impact on security configuration throughout the workflow farm, I would recommend performing a re-installation. Do it thus:
Launch Workflow Manager Configuration Wizard
Select the Leave Workflow Manager Farm
Stop all workflow services (see above list)
Repeat steps 1-3 for each instance of Workflow Manager 1.0 Server installed.
Delete all Workflow Manager databases (see above list).
reboot.
Start new installation.

64bit workflow manager tools installation not working

I am configuring a development machine (Server 2008 R2) and have installed workflow manager 1. Everything seems to install just fine but the workflow manager tools only installs in the program files (x86) directory. There is an install in the Program Files
directory but it doesn't have the Visual studio configurator files. I installed from the x86 directory but when running through the Visual Studio Workflow manager tutorial I am missing some things. Most importantly is the "HTTPSend" messaging activity.
In looking at another post it looks like someone fixed that problem by going back and installing workflow manager tools. It looks like it did install on my machine although from the x86 directory. Running the Microsoft.workflow.visualstudio.configurator.exe
file returns this "date -force to overwrite if necessary."
The only other potential issue is that I am using VS 2013.
Anyone else seeing the configurator only showing up in the Program Files (x86) directory? Anyone else using VS 2013?
The Win2008R2 install is 64bit obviously.
Thanks

I am having similar experience with workflow manager and VS2013 - the HttpSend activity does not show up in the toolbox and the "Choose items" dialog sees it be refuses to add it to the designer's toolbox.
Did you ever find a solution for this issue?
Thanks

Workflow Manager 1.0 will install but NOT configure.

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()

Hi Scott,
Thank you very much.. Now I am able to run wizard.. but at the end of wizard step I am getting below error
[Info] [1/23/2014 5:48:47 PM]: Endpoint=sb://MSPAPPS.psu.edu.sa/WorkflowDefaultNamespace;StsEndpoint=https://MSPAPPS.psu.edu.sa:9355/WorkflowDefaultNamespace;RuntimePort=9354;ManagementPort=9355
[Info] [1/23/2014 5:48:47 PM]: Processing completed
[Verbose] [1/23/2014 5:48:47 PM]: Validating input and configuration parameters.
[Verbose] [1/23/2014 5:48:49 PM]: Installing auto-generated certificate.
[Progress] [1/23/2014 5:48:49 PM]: Installing auto-generated certificate.
[Verbose] [1/23/2014 5:48:51 PM]: Granting 'Log on as Service' privilege to the RunAs account.
[Progress] [1/23/2014 5:48:51 PM]: Granting 'Log on as Service' privilege to the RunAs account.
[Verbose] [1/23/2014 5:48:52 PM]: Workflow Manager configuration starting.
[Progress] [1/23/2014 5:48:52 PM]: Workflow Manager configuration starting.
[Verbose] [1/23/2014 5:48:55 PM]: Configuring Workflow Manager runtime settings.
[Progress] [1/23/2014 5:48:55 PM]: Configuring Workflow Manager runtime settings.
[Error] [1/23/2014 5:48:55 PM]: System.Management.Automation.CmdletInvocationException: The token provider was unable to provide a security token while accessing 'https://mspapps.psu.edu.sa:9355/WorkflowDefaultNamespace/$STS/Windows/'. Token provider returned
message: 'The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.'. ---> System.UnauthorizedAccessException: The token provider was unable to provide a security token while accessing 'https://mspapps.psu.edu.sa:9355/WorkflowDefaultNamespace/$STS/Windows/'.
Token provider returned message: 'The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.'. ---> System.IdentityModel.Tokens.SecurityTokenException: The token provider was unable to provide a security
token while accessing 'https://mspapps.psu.edu.sa:9355/WorkflowDefaultNamespace/$STS/Windows/'. Token provider returned message: 'The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.'. ---> System.Net.WebException:
The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
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.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.WriteHeaders(Boolean async)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at Microsoft.ServiceBus.TokenProviderHelper.GetWindowsAccessTokenCore(IEnumerator`1 stsUris, Func`2 uriBuilder, String requestToken, TimeSpan timeout, DateTime& expiresIn)
--- End of inner exception stack trace ---
at Microsoft.ServiceBus.TokenProviderHelper.ThrowException(Uri requestUri, WebException exception)
at Microsoft.ServiceBus.TokenProviderHelper.GetWindowsAccessTokenCore(IEnumerator`1 stsUris, Func`2 uriBuilder, String requestToken, TimeSpan timeout, DateTime& expiresIn)
at Microsoft.ServiceBus.WindowsTokenProvider.OnBeginGetWebToken(String appliesTo, String action, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProvider.GetWebTokenAsyncResult..ctor(TokenProvider tokenProvider, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProvider.BeginGetWebToken(String appliesTo, String action, Boolean bypassCache, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingWebToken(ITokenProvider tokenProvider, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
--- End of inner exception stack trace ---
Server stack trace:
at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingWebToken(ITokenProvider tokenProvider, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
at Microsoft.ServiceBus.Messaging.HttpWebRequestExtensions.AddAuthorizationHeader(HttpWebRequest request, ITokenProvider tokenProvider, Uri baseAddress, String action)
at Microsoft.ServiceBus.Messaging.ServiceBusResourceOperations.GetAsyncResult`1.<GetAsyncSteps>d__11.MoveNext()
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.EnumerateSteps(CurrentThreadType state)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.Start()
Exception rethrown at [0]:
at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.ServiceBus.NamespaceManager.OnEndTopicExists(IAsyncResult result)
at Microsoft.ServiceBus.NamespaceManager.TopicExists(String path)
at Microsoft.Workflow.Deployment.Commands.WorkflowServiceConfigHelper.SetWFRuntimeSettings(String resourceDBConnectionString, String config)
at Microsoft.Workflow.Deployment.Commands.AddWFHost.CallWFRuntimeSettings(Service wfserviceInfo, String unencryptedResourceConnectionString)
--- End of inner exception stack trace ---
at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
at Microsoft.Workflow.Deployment.ConfigWizard.CommandletHelper.InvokePowershell(Command command, Action`3 updateProgress)
at Microsoft.Workflow.Deployment.ConfigWizard.ProgressPageViewModel.AddWFNode(FarmCreationModel model, Boolean isFirstCommand)

Configure Workflow Manager 1.0 in Project Server 2013 with FBA

Hi,
Please suggest the ways to configure Workflow manger in Project server 2013 where PWA using FBA
we have tried for below situation, but no luck!!
The workflow manager configured using windows login account, we are associating a FBA site with workflow manager which is
Register-SPWorkflowService -SPSite 'http://FBAsite' -WorkflowHostUri 'http://workflowmanagerapplication:12291'
Following steps are taken care while creating workflow.
We have added users to the user service profile services
User profile synchronization is started
The user by whom we are logged is available in User Profile list
we are not running workflow with share point system account
Final step full synchronization of User Profile Application
Below the error we are getting when workflow run
Resume this workflow
RequestorId: 879e36f9-9db0-3c16-0000-000000000000. Details: An unhandled exception occurred during the execution of the workflow instance. Exception details: System.ApplicationException: HTTP 401 {"Transfer-Encoding":["chunked"],"X-SharePointHealthScore":["0"],"SPClientServiceRequestDuration":["440"],"SPRequestGuid":["879e36f9-9db0-3c16-a91c-356d29becb34"],"request-id":["879e36f9-9db0-3c16-a91c-356d29becb34"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"MicrosoftSharePointTeamServices":["15.0.0.4605"],"X-Content-Type-Options":["nosniff"],"X-MS-InvokeApp":["1;
RequireReadOnly"],"Cache-Control":["max-age=0, private"],"Date":["Sun, 15 Jun 2014 12:44:03 GMT"],"Server":["Microsoft-IIS\/7.5"],"WWW-Authenticate":["NTLM"],"X-AspNet-Version":["4.0.30319"],"X-Powered-By":["ASP.NET"]}
at Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor
executor, BookmarkManager bookmarkManager, Location resultLocation)

Hi Mafeer,
Since this issue is related to Project Server, I would like to recommend you to post there for more effective support:
Project Server General Questions and Answers
Thanks for your understanding.

Workflow Manager 1.0 configuration- Specified RunAs account is invalid

Hello - I am trying to install and configure Workflow manager 1.0. As part of workflow manager configuration specifying the user id in
Configure Service Account section throwing error as "Specified RunAs account is invalid".
I tried different ways and means suggested in forums and KBs - but I think it is unable to validate the user in Active Directory. Our Active Directory is AD 2003 functional level and wondering it has any issues with Workflow manager 1.0?
Here are the environment details:
WF Machine: Windows Server 2008 R2 SP1
AD: Active Directory 2003
Workflow Manager 1.0 installed and also applied the below latest workflow and service bus hotfixes.
http://support.microsoft.com/kb/2799754;
http://support.microsoft.com/kb/2799752
Also moved the service account to the default OU=Users container in AD as specified in below forum but no luck.
http://social.msdn.microsoft.com/Forums/en-US/servbus/thread/3d803e15-606a-4f06-96fe-97c23ad3c01a
I am not sure where the issue is wondering if any one has run into similar issue. Appreciate any feedback.

Thanks for your response.
No it still didnt work, we right clicked the users OU, provided read permissions on it directly not from any groups. as well as for computers OU.
For me it is not showing invalid user, but wizard crashes as soon as we enter the service account details in the wizard. may be since the solution you are providing is not working for me.
http://social.technet.microsoft.com/Forums/office/en-US/d70662fc-8e10-4862-975d-e441bf9c32f0/what-permission-does-the-service-account-requires-on-ad-for-the-workflow-manager-10-to-be?forum=sharepointadmin
However we had one other test account which has full control on many areas is able to pass thru in this wizard with out crashing.
We arent able to get the same permissions applied for prod account as it isnt right to simply take elevated permissions full control on AD Objects.
Windows/AD team is looking for specific permission which this workflow manager requires to provide access.
I dont see this documented with microsoft Either.
SQL DB creation ability, Domain Account, Farm admin - is the criteria i believe.

Timeout while configuring workflow manager (service bus services are stuck on strarting)

Hello,
I cant finish workflow manager configuration. help me please.
I tried:
1) leave the farm (Workflow manager configuration), delete databases, create new farm with default settings - it creates SB&WF farms and on 3d stage I get timeout error.
2) leave the farm, delete databases, delete workflow manager and service bus software, install it again, create new farm with defaults - the same result.
3) leave the farm, delete databases, get powershell commands for "create new farm with default settings", run it step by step - same result.
there are generated powershell commands:
New-SBFarm -SBFarmDBConnectionString '... ManagementDB con string ...' -InternalPortRangeStart 9000 -TcpPort 9354 -MessageBrokerPort 9356 -RunAsAccount 'domain\acc' -AdminGroup 'BUILTIN\Administrators' -GatewayDBConnectionString '... gateway con string
...' -CertificateAutoGenerationKey $SBCertificateAutoGenerationKey -MessageContainerDBConnectionString '... message container con string ...' -Verbose;
New-WFFarm -WFFarmDBConnectionString '... WF managementDB con string ...' -RunAsAccount 'domain\acc' -AdminGroup 'BUILTIN\Administrators' -HttpsPort 12290 -HttpPort 12291 -InstanceDBConnectionString '... WF instanceDB con string ...' -ResourceDBConnectionString
'... wf resourceDB con string ...' -CertificateAutoGenerationKey $WFCertAutoGenerationKey -Verbose;
Add-SBHost -SBFarmDBConnectionString '... ManagementDB con string ...' -RunAsPassword $SBRunAsPassword -EnableFirewallRules $true -CertificateAutoGenerationKey $SBCertificateAutoGenerationKey -Verbose;
I don't see any errors in event log, only timeout error in setup log.
Service bus gateway service is started successfully, Service bus message broker is stuck starting.

dmadelung, thank you for your message.
the problem was with ports. 9000 port was used already. moving to different ports resolved the problem

Unable to find the User Named Account Name@Domain Name while Configuring Workflow Manager

Hi,
I have installed Work Flow Manager,Service Bus and its Cumulative Updates.
While Configuring Workflow Manger using Workflow Manager configuration wizard i am getting the error while creating a Service Bus Namespace.
I have provided the Service Accounts for both Workflow Manager and Service Bus as Domain\Account instead of
Account@Domain.
While looking in to the Power Shell scripts that are poupulated by the GUI i have identified that
Account@Domain is appended to the ManageUsers switch while creating a Service Bus Namespace and the GUI configuration is failing.
    New-SBNamespace -Name 'WorkflowDefaultNamespace' -AddressingScheme 'Path' -ManageUsers 'Domain\Account','Account@Domain' -Verbose;
So i need to modify the Powershell script as below and need to run the Powershell scripts for configuring Workflow Manager.
Is this a bug in GUI Workflow Configuration Wizard or am i doing something wrong.
Please help.
    New-SBNamespace -Name 'WorkflowDefaultNamespace' -AddressingScheme 'Path' -ManageUsers 'Domain\Account' -Verbose;
Scripts Populated from GUI modified for Making it working:
# To be run in Workflow Manager PowerShell console that has both Workflow Manager and Service Bus installed.
# Create new SB Farm
$SBCertificateAutoGenerationKey = ConvertTo-SecureString -AsPlainText -Force -String 'Run As Password' -Verbose;
New-SBFarm -SBFarmDBConnectionString 'Data Source=Server Name;Initial Catalog=SbManagementDB;Integrated Security=True;Encrypt=False' -InternalPortRangeStart 9000 -TcpPort 9354 -MessageBrokerPort 9356 -RunAsAccount 'Domain\Account' -AdminGroup 'Domain\Domain
Group' -GatewayDBConnectionString 'Data Source=Server Name;Initial Catalog=SbGatewayDatabase;Integrated Security=True;Encrypt=False' -CertificateAutoGenerationKey $SBCertificateAutoGenerationKey -MessageContainerDBConnectionString 'Data Source=Server Name;Initial
Catalog=SBMessageContainer01;Integrated Security=True;Encrypt=False' -Verbose;
# To be run in Workflow Manager PowerShell console that has both Workflow Manager and Service Bus installed.
# Create new WF Farm
$WFCertAutoGenerationKey = ConvertTo-SecureString -AsPlainText -Force -String 'Run As Password' -Verbose;
New-WFFarm -WFFarmDBConnectionString 'Data Source=Server Name;Initial Catalog=WFManagementDB;Integrated Security=True;Encrypt=False' -RunAsAccount 'Domain\Account' -AdminGroup 'Domain\Domain Group' -HttpsPort 12290 -HttpPort 12291 -InstanceDBConnectionString
'Data Source=Server Name;Initial Catalog=WFInstanceManagementDB;Integrated Security=True;Encrypt=False' -ResourceDBConnectionString 'Data Source=Server Name;Initial Catalog=WFResourceManagementDB;Integrated Security=True;Encrypt=False' -CertificateAutoGenerationKey
$WFCertAutoGenerationKey -Verbose;
# Add SB Host
$SBRunAsPassword = ConvertTo-SecureString -AsPlainText -Force -String 'Run As Password' -Verbose;
Add-SBHost -SBFarmDBConnectionString 'Data Source=Server Name;Initial Catalog=SbManagementDB;Integrated Security=True;Encrypt=False' -RunAsPassword $SBRunAsPassword -EnableFirewallRules $true -CertificateAutoGenerationKey $SBCertificateAutoGenerationKey -Verbose;
Try
    # Create new SB Namespace
    New-SBNamespace -Name 'WorkflowDefaultNamespace' -AddressingScheme 'Path' -ManageUsers 'Domain\Account' -Verbose;
    Start-Sleep -s 90
Catch [system.InvalidOperationException]
# Get SB Client Configuration
$SBClientConfiguration = Get-SBClientConfiguration -Namespaces 'WorkflowDefaultNamespace' -Verbose;
# Add WF Host
$WFRunAsPassword = ConvertTo-SecureString -AsPlainText -Force -String 'Run As Password' -Verbose;
Add-WFHost -WFFarmDBConnectionString 'Data Source=Server Name;Initial Catalog=WFManagementDB;Integrated Security=True;Encrypt=False' -RunAsPassword $WFRunAsPassword -EnableFirewallRules $true -SBClientConfiguration $SBClientConfiguration -EnableHttpPort
-CertificateAutoGenerationKey $WFCertAutoGenerationKey -Verbose;
Thanks, Vijay Arockiasamy

Hi Vijay
uninstall this and install the one labeled Refresh 1
Kind Regards,
John Naguib
Senior Consultant
John Naguib Blog
John Naguib Twitter
Please remember to mark this as answered if it helped you

Work Manager Configuration Issue with SharePoint 2013

Hi,
We are facing issue to configure the Workflow Manager with SharePoint 2013.
===========================================================
Please provide any solution/inputs to resolve this issue.
Thanks.

Hi ,
According to your description, my understanding is that you got an error when you configured Workflow Manager for SharePoint 2013.
For resolving your issue, please do as the followings:
1.Start -> Programs -> Workflow Manager 1.0 -> Workflow Manager Configuration -> Remove from Farm (not to be confused with SharePoint “farm”)
2.Drop SQL databases for Workflow Manager. (SbGatewayDatabase, SbManagementDB, SBMessageContainer01, WFInstanceManagementDB, WFManagementDB, WFResourceManagementDB)
3.Start-> Programs-> Workflow Manager 1.0 -> Workflow Manager Configuration -> Configure Workflow Manager with Default Settings (Recommended)
4.Ran the wizard just like before and it should be completed successfully this time.
More information, please refer to the link below:
http://www.spjeff.com/tag/workflow-manager-1-0/
I hope this helps.
Thanks,
Wendy
Wendy Li
TechNet Community Support

Currupted Workflow Manager Configuration, RE-Installation Guidence?

Similar Messages

Maybe you are looking for