none
Workflow Manager will install but NOT configure. RRS feed

  • Question

  • SUMMARY: Workflow Manager Configuration Wizard force closes when trying to set the USER ID.  I think it has something to do with domain authentication.

    I've looked at just about every post on these forums and I can't find a solution.

    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. 

    Any ideas?

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

    Thursday, December 20, 2012 6:45 PM

All replies

  • I'm not sure what your putting in the USERID field... but...

    The user ID must be in the format username@domain-name or domain\user.

    http://technet.microsoft.com/en-us/library/jj193514 

    Tuesday, January 1, 2013 11:28 PM
  • Hello Bill, thanks for the reply.

    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.

    Wednesday, January 2, 2013 2:55 PM
  • Just a shot in the dark, but one of the Known Issues (http://msdn.microsoft.com/en-US/library/jj193462) is that you'll have trouble if there are any accounts in the local server admins group that aren't in the same domain or have unresolvable SIDs. Maybe check to see if either of those are true in your case. Good luck.
    Friday, January 11, 2013 1:05 AM
  • Interesting, I had checked that out before and have removed all the accounts (but the one I'm installing with) in the Local Administrator group on the server.  It didn't make a difference, but in the same train of thought, I attempted to install Workflow Manager using the Local Admin ACCOUNT (not group) and the program didn't force close!  It didn't let me connect to our SQL machine because it was a non-domain account, but it didn't force close!

    It has to be linked to our domain in some way.  One thing that could be causing the issue is that our primary domain controller is on Windows Server 2003.  Could it be that 2008 R2 AD has to be available for it to work properly?

    Friday, January 11, 2013 5:58 PM
  • Hi Teevo,

    Did you end up finding a solution for this? I have found that I have the exact same issue (server 2008 R2, SP2013), including that by using the local admin account doesnt cause the user account field to crash, but ofcourse I cannot specify the SQL server as it cannot connect.

    The only difference in my case is that I believe we are running our AD from server 2008 R2.

    Wednesday, January 30, 2013 2:58 AM
  • No resolution yet.  I keep cruising the forums to see if anyone else has found anything.

    That's interesting that you're  having issues on 2008 AD.  Is it possible that the Domain Forest is still set to 2003 compatibility?

    Wednesday, January 30, 2013 3:11 PM
  • Ah yes, just found out that we have 2 DCs with AD on both, one is a 2008 R2 and the other is still running 2003.

    Teevo, check out the below link, its not exactly for Workflow Manager but I am having the same issue with the Service Bus Configuration so I am going to guess that they are linked. I am trying to get onto our sysadmin to try out the solution.

    http://social.msdn.microsoft.com/Forums/da-DK/servbus/thread/3d803e15-606a-4f06-96fe-97c23ad3c01a

    Sunday, February 3, 2013 11:40 PM
  • Not necessarily related to your issue but the have recently released a hot fix for workflow manager 1.0

    Description of the Cumulative Update for Service Bus 1.0

    -bill


    • Edited by Bill Burke Thursday, March 21, 2013 1:44 AM
    Thursday, March 21, 2013 1:44 AM