Developing a 2013 Workflow on SharePoint 2013 using Visual Studio 2012, deploying workflow changes does not update the workflow that runs. This has already been posted on the SP 2013 dev forum, but I wanted to check here with the workflow folks. Anyone run into this issue before and/or have tips for solving?

Thanks.

http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/cd543a00-f3ab-4a4a-8682-b81d8330b677

http://blog.randomdust.com

I HATE Workflow Manager 1.0.  Never has anything had me want to bang my head on my desk.  So I can create and run 2013 workflows sucessfully BUT the user requires Contribute permissions to the site which is unacceptable.  Before this a user could have read permission to the site and then contribute on the list and they could start workflows.  I have no idea what I'm doing wrong as I have gone over the scenario and checked and double checked everything.

I do want to add that this is a development environment with one WFE and a seperate SQL server.

If anyone has this up and running without error could you please suggest what incantation and/or candles I might burn to help my process along.  Thank you in advance for any suggestions.

Jennifer Knight (MCITP, MCPD)

I am wanting to set up Workflow server in a 3 node cluster and utilize our F5 hardware load balancer to service the requests.

I cannot find any information on how the load balancing should be configured. Should it just be configured in a round robin method? Do the rules need to be configured with Session Affinity (sticky sessions)?

Hi All,

When I tried to install Workflow Manager 1.0 , I got the following error.

I downloaded the Web Platform Installer and installed it.

Still I get the same error.

Please help me to troubleshoot the error.

Hi!

When I install Work Flow Manager Cumulative Update, I get this error:

[11/15/13 18:34:05] Starting process "C:\Windows\system32\..\sysnative\windowspowershell\v1.0\powershell.exe" -NoLogo -NonInteractive -NoProfile -WindowStyle Hidden -ExecutionPolicy RemoteSigned -File UnifiedWFHotfixUpgrade.PS1 -HotfixType "CS" -PackageType "client" -opcode "PatchBefore" -platform "x64" ...
[11/15/13 18:34:09] Process exit code is -1.
Start-WFHostUpgrade : Login failed for user 'W+dHg7Pnc+2keIKm7q/ByQ=='.
This session has been assigned a tracing ID of 
'4fd5af33-d329-4b56-8da8-48f55bff4df2'.  Provide this tracing ID to customer 
support when you need assistance.
At C:\ProgramData\Microsoft\E-Business Servers 
Updates\Updates\Uninstall2799754\UnifiedWFHotfixUpgrade.PS1:235 char:5
+           Start-WFHostUpgrade -TargetWFVersion $TargetWFVersion
+           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : WriteError: (:) [Start-WFHostUpgrade], SqlExcept 
   ion
    + FullyQualifiedErrorId : WFServiceUpgradeFailed,Microsoft.Workflow.Deploy 
   ment.Commands.StartWFHostUpgrade

Can any one Help me !!!

To solve error !

I have seen in the WF Manager documentation regarding disaster recovery, that it is possible to setup WF in a standby farm pointing to log shipped databases, but the article does not go into any details.

It says:

You could typically opt-in to this model if you want to make sure that you have your secondary farm created and tested even before a disaster strikes. In this model, you provision compute nodes in the new farm before the disaster. After establishing the database pairing relationship, you point this new farm to the secondary databases.

After setting up this new farm, you essentially turn OFF the compute nodes so that they are not running idle. As part of disaster recovery, you have to run the database consistency scripts provided by Workflow Manager.

The details I am missing are the "you point this new farm to the secondary databases" part.

If anybody can provide any assistance it would be greatly appreciated. If I find the answer in the mean time I will post it back here.

Thanks in advance.

Hi,

I am currently installing SharePoint 2013 using Windows Server 2008 R2 SP1 and SQL Server 2008 R2 with SP2.
I have installed Workflow manager 1.0 with Service Bus 1.0 using Web Platform Installer 4.0. I chose ‘Configure Workflow Manager with Custom Settings’ when the Workflow Manager Configuration Wizard launched. Configuration operation successful. When i execute command Register-SPWorkflowService –SPSite “<site collection url>” –WorkflowHostUri “http://....:12291” get error

Register-SPWorkflowService : The term 'Register-SPWorkflowService' is not
recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify
that the path is correct and try again.
At line:1 char:1
+ Register-SPWorkflowService -SPSite ""
-WorkflowH ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Register-SPWorkflowService:Stri
   ng) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
What I do wrong?

When I try with Register-SPWorkflowService for SP2013 integration or run C# samples for workflow manager 1.0 I get"The  remote server returned an error: (404) Not found".

With C# sample code runs,

Scope '/$Activities' was not found.  HTTP headers received from the server - ActivityId: e268765f-9d95-47ed-81fd-c4b38f40bfe0. NodeId: XXXX. Scope: /$Activities/...

The inner exception is:
The remote server returned an error: (404) Not Found.

We have got stuck here for a couple of days and...
The workflow server runs on a dedicated machine than the SQL server for workflow farm DBs...

I found one similar complain for the pre-release versions of the workflow and service bus etc.

Help please...

muharrem

Muharrem

Hi,

I'm trying to remove Workflow Manager from a SharePoint farm (SQL Server 2012, Windows Server 2012, one VM for SharePoint, one separate VM for SQL--installed Workflow on the SharePoint VM with HTTP over oAUTH option) following the instructions in http://msdn.microsoft.com/en-us/library/windowsazure/jj193489(v=azure.10).aspx. The goal is to reinstall Workflow Manager.

However, we've followed the instructions several times and we're still getting an error when we try to install saving that there already is a database connection.

It would be great if we could find the PowerShell commands to see what's still is remaining of the previous installation but have not been able to figure out what commands to use (the PowerShell commands to manage a Workflow Manager installation in a SharePoint 2013 Enterprise on-premise install seem to be all over the place-some in MSDN, some in AZURE support area, some in TECHNET).

Does anybody have any ideas? We don't want to blow away the farm and start again since we have content on the farm already.

Thanks!

Kathryn Birstein, Senior SharePoint Architect

Hi everybody, I have a problem with the maximum persistence size. In my WFs i call an external service that return a very huge message (something like 5MB...) and I receivethe maximum persistable workflow instance bla bla error. The error message talk aboutuncompressed and compressed limits...so I change the farm configuration increasing the WorkflowServiceMaxInstanceSizeKB(for test purpose i set it to 30720!) but I again receive the max limit message BUT with a little difference:

"The maximum persistable workflow instance size is 30720 kilobytes uncompressed and 5120 kilobytes compressed."

As you can see the "compressed" limit does not change and still remain the default one.

Does anyone know which is the correct configuration setting that I have to change?

I also try another way: i put a NoPersistScope around the external service call and the subsequent one that use the service response to invoke other (mine) service the save parts of the message) but in this way the workflow never ends and still remain in the started state; also the subsequent services are not invoked...strange...any idea?

Thanks!

My general question is this: What is the procedure to update a workflow definition?

Currently I have the following situation.

1.Developed a Workflow using Visual Studio 2012

2.The workflow is succesfully deployed/upgraded using Visual Studio

3. The workflow was also successfully deployed on another server using PowerShell commands

4. Changed something on the Workflow definition and created new wsp.

5. Deployed the wsp using powershell (tried couple of things - with and without retracting of the old).

6. But alwasy the old definition of the workflow is run.

7. The workflow manager is updated with the latest CU.

Something that I have noticed is that during the depoyment using VS the following lines can be seen:

 Found 1 deployment conflict(s).  Resolving conflicts ...
  Deleted file 'http://sitename/sites/WorkflowManager/wfsvc/966701ae1da14e2099853fcf24c60a38/Workflow.xaml' from server.
  Deleted file 'http://sitename/sites/WorkflowManager/wfsvc/966701ae1da14e2099853fcf24c60a38/WorkflowStartAssociation' from server.
  Deleted file 'http://sitename/sites/WorkflowManager/wfsvc/966701ae1da14e2099853fcf24c60a38/ItemAddedAssociation' from server.
  Adding solution 'NameOfThesolution.wsp'...

So how can I detect and resolve this conflicts using PowerShell? Or workaround this issue?

Thanks.

Pls help me out.

simple Workflow 2013. using my SharePoint  2013 applications, But I am getting below error. pls feel free and contact below details "smanisekhar555@gmail.com" @ " Cell :- 7259805505"

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

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

Environment: Server 2012 standalone dev environment (single machine farm), VS 2012 Ultimate, SP 2013.

Followed the instructions several times to install / remove / re-install WFM 1.0 and no matter I end up with the following error when I try to debug the SP solution including a project with a couple simple task assignment workflows (in a brief flash window which I managed to screen capture):

Microsoft.Workflow.TestServiceHost.exe Error: 0 : System.IO.InvalidDataException: A required Workflow Configuration 'WorkflowServiceScopeSnapshotProcessBatchSize' is not present. Please add this configuration value.

The debug window (TestServiceHost) then closes, the browser closes and in my debug window in VS the following message appears:

Microsoft.Workflow.TestServiceHost.exe Error: 0 : System.MissingMethodException: Method not found: 'Void Microsoft.Workflow.Tracing.WorkflowEventSource.UnknownIsolateHandledExceptionAction(System.String, Microsoft.Workflow.Tracing.EventTraceActivity)'.

An unhandled exception was thrown: Microsoft.Workflow: System.Threading.ThreadAbortException: Thread was being aborted.
   at System.Threading.WaitHandle.WaitMultiple(WaitHandle[] waitHandles, Int32 millisecondsTimeout, Boolean exitContext, Boolean WaitAll)
   at System.Threading.WaitHandle.WaitAny(WaitHandle[] waitHandles, Int32 millisecondsTimeout, Boolean exitContext)
   at Microsoft.Workflow.Common.IOThreadTimer.TimerManager.OnWaitCallback(Object state)
   at Microsoft.Workflow.Common.IOThreadScheduler.ScheduledOverlapped.IOCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlappedCallback)
   at Microsoft.Workflow.Common.Fx.IOCompletionThunk.UnhandledExceptionFrame(UInt32 error, UInt32 bytesRead, NativeOverlapped* nativeOverlapped)

Any help in correcting this issue is greatly appreciated. Thanks.

Hi guys.

Installed Workflow manager on SharePoint 2013.

Followed this tutorial: http://www.youtube.com/watch?v=6haTejk98hU

When I open SharePoint designer 2013 there are no SharePoint 2013 workflows.

All the steps looking at that YouTube video went thru sucessfully, in event viewer no errror warnings, don't know where to search for the root of the problem.

If I open http://sharepoint2013srvname:12291 I recieve this xml page:

bostjanc

I am getting the following error in the workflow services log when I tried to run a SPD 2013 workflow from as list item. The workflow page comes up with an "An unexpected error has occurred" page when opened:

Error processing management request. Method: GET, RequestUri: http://servername:12291/$Workflows/$Instances?$skip=0&$top=100&monitoringParameter=1f51aa43-2f1c-4fc5-a86d-f638ca57c00d, Error: System.Data.SqlClient.SqlException (0x80131904): The procedure "GetInstances" has no parameter named "@OtherWorkflowStatus".
   at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at Microsoft.Workflow.Gateway.HttpAsyncResult.End[TAsyncResult](IAsyncResult result)
   at Microsoft.Workflow.Gateway.WorkflowServiceGateway.<>c__DisplayClass9d.<EndGetInstances>b__9c()
   at Microsoft.Workflow.Gateway.WorkflowServiceGateway.ExceptionFilter[T](Func`1 body)
   at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
ClientConnectionId:d2039360-b352-4d81-9bb7-b647e2938d06

Can't find anything on google.

Edit: Ok, when I look at the error, it is saying the the "GetInstances" stored procedure in the WFInstanceManagementDB database does not have a parameter named "@OtherWorkflowStatus". For laughs, I added the parameter (which wasn't in there). Now I get the error:

Procedure or function 'GetInstances' expects parameter '@OtherWorkflowStatus', which was not supplied

It seems like there is something not right about my installation. Previously, I couldn't get the workflow backend service to run because there were config values missing from the workflow manager database. At the time I tried to uninstall/reinstall WFM to no avail. I eventually had to manually add the values to get it to work. Something is not right about the WFM install/config process.

I made a designer workflow to one of my DiscussionBoard app in my sharepoint 2013 to send alert email after adding an item. published from designer as a manual start  , if I want to go and start manually  it's throwing an error "Something went Wrong try again or reload the page" . It i publish on item added event from designer it's working well.

The workflow execution error occurs only to the apps Discussion Board for the other custom lists it's working fine. I am able to run manually after adding an item

We have observed that workflows published  with Platform type as “SharePoint 2010” and Discussion Board working as expected .

Any Help much appreciated.Thank you all.

Subhash

I'm trying to Uninstall Workflow Manager 1.0 from "Programs and Features" in the Control Panel. It was part of a failed installation on a SharePoint Server. The Service Bus, Workflow Client, and Windows Fabric all installed fine but when I try to uninstall "Workflow Manager 1.0" Windows Server responds with "The computer is part of a farm. To uninstall, first leave the farm either using "Leave from Farm" option in Configuration Wizard or "Remove-WFHost" cmd-let in PowerShell."

The Deployment Wizard "Leave the Farm" option is not working and I subsequently deleted it. And when I try to run "Remove-WFHost" PowerShell says "The term Remove-WFHost is not recognized. . ."

The Workflow proxy in the Service Applications of the SharePoint installation has been deleted.

Any idea how I can remove Workflow Manager 1.0?

I need to get rid of Workflow Manager 1.0 so that I can start the installation again and hopefully get it installed correctly. . .

Thanks,

Kathryn

Kathryn Birstein, Senior SharePoint Architect