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)

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

Workflow Manager - Add-WFHost fails with "Could not load file" error

Hello! I'm not sure that its Sharepoint related topic but..
I'm trying to install Workflow Manager using Powershell. I'm successfully created ServiceBus farm, create namespace, Add-SBhost etc. Also, i created WF Farm using New-WFFarm.
Now i'm got SB Configuration and try to add my first host to WF Farm using standard cmdlets:
$SBClientConfiguration = Get-SBClientConfiguration -Namespaces 'WorkflowDefaultNamespace'
(it successfuly gives me some endpoint definitions)
Add-WFHost -WFFarmDBConnectionString $WFFarmDBConStr -RunAsPassword $ServiceAccountPassword -EnableFirewallRules $true -SBClientConfiguration $SBClientConfiguration -CertificateAutoGenerationKey $CertificateAutoGenerationKey
where
$WFFarmDBConStr is typical connection string, i also used this to Get-WFFarm with no errors.
$ServiceAccountPassword and $CertificateAutoGenerationKey are secure strings.
But trouble appears with SBClientConfiguration, cmdlet returns error:
"Cannot validate argument on parameter 'SBClientConiguration'. Could not load file or assebly 'Microsoft.ServiceBus, Version=1.8.0.0, Culture=neutral, PublicKeyToken=<SomeTokenSymbolsHere> or one of its dependencies. The system cannot
find the file specified."
What file it tries to load? I've installed all WorkflowManager binaries with
webpicmd /Install /Product:WorkflowManagerRefresh key and don't know, what can be cause.

Hi lehus,
According to your description, my understanding is that you got an error when you configured Workflow Manager using PowerShell.
Please try to use the following PowerShell command, compare the result:
Add-WFHost -WFFarmDBConnectionString $WFFarmDBConStr -RunAsPassword $ServiceAccountPassword -EnableFirewallRules $true -SBClientConfiguration $SBClientConfiguration
–EnableHttpPort -CertificateAutoGenerationKey $CertificateAutoGenerationKey
-Verbose
Check your process as:
http://lennytech.wordpress.com/2013/06/02/configuring-workflow-manager-1-0-using-powershell/
In addition, whether you could install and configure Workflow Manager with Workflow Manager Configuration Wizard. Please have a try as:
http://prabathf.blogspot.com/2013/02/installing-and-configuring-workflow-for.html
I hope this helps.
Thanks,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support

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

Management Configuration Service failed to process agent configuration request

We're having a SCOM environment with several Management Servers. Since about two days, we're receiving the following alerts in SCOM and Management Server State is Critical:
Name : Management Configuration Service failed to process agent configuration request
Description : Management Configuration Service failed to process agent configuration request.
OpsMgr Management Configuration Service failed to process configuration request
(Xml configuration file or management pack request) due to the following exception
Microsoft.EnterpriseManagement.ManagementConfiguration.DataAccessLayer.DataAccessEx
ception: Data access operation failed
at Microsoft.EnterpriseManagement.ManagementConfiguration.DataAccessLayer.DataAc
cessOperation.ExecuteSynchronously(Int32 timeoutSeconds, WaitHandle stopWaitHandle)
at Microsoft.EnterpriseManagement.ManagementConfiguration.SqlConfigurationStore.
ConfigurationStore.ExecuteOperationSynchronously(IDataAccessConnectedOperation
operation, String operationName)
at Microsoft.EnterpriseManagement.ManagementConfiguration.SqlConfigurationStore.
ConfigurationStore.GetConfiguration(IDictionary`2 agentList,
ConfigurationSignature configurationSignature)
at Microsoft.EnterpriseManagement.ManagementConfiguration.Engine.AgentRequestPro
cessor.ProcessConfigurationRequest(ICollection`1 requestList, Int32&
processedRequestsCount)
at Microsoft.EnterpriseManagement.ManagementConfiguration.Engine.AgentRequestPro
cessor.Execute()
at Microsoft.EnterpriseManagement.ManagementConfiguration.Engine.ThreadManager.R
esponseThreadStart(Object state)
System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout
period elapsed prior to completion of the operation or the server is not
responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait
operation timed out
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean
breakConnection, Action`1 wrapCloseInAction)
at
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand
cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler,
TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlDataReader.TryReadInternal(Boolean setTimeout,
Boolean& more)
at System.Data.SqlClient.SqlDataReader.Read()
at Microsoft.EnterpriseManagement.ManagementConfiguration.SqlConfigurationStore.
AgentConfigGetOperation.ReadAgentPoolInfo(IDataReader reader,
AgentConfigurationBuilder builder)
at Microsoft.EnterpriseManagement.ManagementConfiguration.SqlConfigurationStore.
AgentConfigGetOperation.ReadData(SqlDataReader reader)
at Microsoft.EnterpriseManagement.ManagementConfiguration.DataAccessLayer.Reader
SqlCommandOperation.SqlCommandCompleted(IAsyncResult asyncResult)
ClientConnectionId:e44a346e-adb8-4679-9b0d-b515ac24df95
As of that I'm pretty sure that it's related to a SQL Issue. I think it's related to SQL performance, as the server is available and can be reached:
System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout elapsed prior to completion of the operation or the server is not . ---> System.ComponentModel.Win32Exception (0x80004005): The wait timed out
at ....
Related to the error I also see warning related to "Local Dirty Notification State" and "Delta Synchronization State"
Thanks for any help

Hi,
You may need to check whether your SQL server which hold SCOM database has any performance issue. You can restart related SQL services and system center management configuration service. In addition, please check operation manager event logs on management
server and find out is there any error messages related.
If there is event 31552, then you can try links below to troubleshoot it:
http://blogs.technet.com/b/sudheesn/archive/2009/07/28/getting-31552-exception-sqlexception-timeout-expired-very-frequently-in-scom-server.aspx
http://blogs.technet.com/b/kevinholman/archive/2010/08/30/the-31552-event-or-why-is-my-data-warehouse-server-consuming-so-much-cpu.aspx
In addition, please also try to flush health service state and caches for management server.
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

INS-20802 Automatic Storage Management Configuration Assistant Failed

Dear all,
Please help me to fix this issue, when I install grid infrastructure I have encounter a problem which describe INS-20802 Automatic Storage Management Configuration Assistant Failed.
Could anyone help me to find out this problem?
Thank before hand for you help.
Best Regards,
Vouthea OUN

Dear all,
Please help me to fix this issue, when I install grid infrastructure I have encounter a problem which describe INS-20802 Automatic Storage Management Configuration Assistant Failed.
Could anyone help me to find out this problem?
Thank before hand for you help.
Best Regards,
Vouthea OUN

OpsMgr Management Configuration Service failed to execute 'DeltaSynchronization' engine work item due to the following exception with event id 29181

Hi , sometimes this error shows in event viewer:
OpsMgr Management Configuration Service failed to execute 'DeltaSynchronization' engine work item due to the following exception
Microsoft.EnterpriseManagement.ManagementConfiguration.Interop.ConfigManager.ConfigurationChangeException: Configuration change occurred during delta synchronization. Delta will be restarted
at Microsoft.EnterpriseManagement.ManagementConfiguration.SqlConfigurationStore.ConfigurationStore.WriteConfigurationDelta(IConfigurationDeltaDataSet dataSet)
at Microsoft.EnterpriseManagement.ManagementConfiguration.Engine.DeltaSynchronizationWorkItem.TransferData(String watermark)
at Microsoft.EnterpriseManagement.ManagementConfiguration.Engine.DeltaSynchronizationWorkItem.ExecuteSharedWorkItem()
at Microsoft.EnterpriseManagement.ManagementConfiguration.Interop.SharedWorkItem.ExecuteWorkItem()
at Microsoft.EnterpriseManagement.ManagementConfiguration.Interop.ConfigServiceEngineWorkItem.Execute()
thanks

For this issue, You can refer below link
http://h10025.www1.hp.com/ewfrf/wc/document?cc=se&lc=sv&dlc=sv&tmp_geoLoc=true&docname=c03699441
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

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.

Workflow Manager Backend service fails to start - FatalException

Hi,
I installed Workflow Manager 1.0 (with default recommended configuration) and the Cummulative Update 1 and activated the feature on SharePoint 2013. I restarted my server.
The Workflow Manager Backend service cannot start. An attempt is done every 30" but it's always fails. The errors I see in the event viewer (every 30") are the following:
Error 1
Application: Microsoft.Workflow.ServiceHost.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: Microsoft.Workflow.Common.FatalException
Stack:
   at Microsoft.Workflow.Common.Fx+<>c__DisplayClass2.<FailFast>b__0()
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart()
Error 2
Faulting application name: Microsoft.Workflow.ServiceHost.exe, version: 1.0.20922.0, time stamp: 0x505e1b24
Faulting module name: KERNELBASE.dll, version: 6.2.9200.16451, time stamp: 0x50988aa6
Exception code: 0xe0434352
Fault offset: 0x000000000003811c
Faulting process id: 0x25c0
Faulting application start time: 0x01cefd844175ec32
Faulting application path: C:\Program Files\Workflow Manager\1.0\Workflow\Artifacts\Microsoft.Workflow.ServiceHost.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 7fb79f6a-6977-11e3-9401-0050569055b0
Faulting package full name:
Faulting package-relative application ID:
As a result I cannot deploy workflows on SharePoint using Visual Studio. I get a 500 error during activation of the related feature.
Any ideas?
Dimitris Papadimitriou, Software Development Professional

Hi,
I am not sure if you have solved this but it seems that the WF 1.1 Update requires some more updates in one of the tables in the configuration
database for the Workflow installation. Checkout the database [WFResourceManagementDB] and the table [WorkflowServiceConfig]. You need the flowing entries and values:
WorkflowServiceScopeSnapshotProcessBatchSize
20
WorkflowServiceScopeSnapshotProcessLoopInterval
00:05:00
WorkflowServiceSuspendedInstanceRetentionDuration
30.00:00:00
WorkflowServiceMaxInstanceCompressedSizeKB
5120
BR
Magnus Danielson

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

Installing SharePoint 2013 Workflow Manager offline - Wizard does not show up

Hello guys,I recently tried to install the workflowmanager to the Application Server of my SharePoint 2013 Farm.I used the following commandline as suggested by spence harbar (in his article).SERVER -D:\SP\WorkflowManager\bin>WebpiCmd.exe /Install /Products:WorkflowManager /XML:D:\SP\WorkflowManager\feeds\latest\w
ebproductlist.xml
The wizard does not show up, instead of that, I got an message in my Commandbox:
The software that you obtain using the Web Platform Installer Command Line Tool is licensed to you by its owner. Microsoft g
rants you no rights for third party software.
Successfully loaded primary feed: file:///D:/SP/WorkflowManager/feeds/latest/webproductlist.xml
The following products are not available on this machine or already installed: WorkflowManager
No products to be installed (either not available or already installed)
Can anybody tell me what to do in this situation. I can´t uninstall the software because there is none.
I need help with this! There is no information in the community about this problem :/
Greetings Andre

Hi,
First of all that blog is old and now you should install Workflow Manager Refresh 1.0. To start fresh, uninstall all components of WF Manager from the server and then follow below mentioned steps.
Download Microsoft Web Platform Installer 5.0 on a machine where Internet is there.
Once Installed, go this path in command prompt C:\Program Files\Microsoft\Web Platform Installer and then use this command WebpiCmd.exe /offline /Products:WorkflowManagerRefresh /Path:C:\temp
Copy the temp folder to the WF Manager machine where you wish to install the WF Manager
In destination server, use command prompt with elevated privileges and navigate to the temp/bin directory (in copied folder).
Use this command WebpiCmd.exe /Install /Products:ServiceBus_1_1 /XML:C:\temp\feeds\latest\webproductlist.xml
Then run this command WebpiCmd.exe /Install /Products:WorkflowClient /XML:C:\temp\feeds\latest\webproductlist.xml
Then run this command WebpiCmd.exe /Install /Products:WorkflowManagerRefresh /XML:C:\temp\feeds\latest\webproductlist.xml
-Prashant

Configuration Wizard failed at 8th step after installing sp3 patching in Moss 2007

Hi
While running in the config wizard it failed at 8th step please give me some suggestion on this
[SPManager] [ERROR] [2/9/2014 8:18:52 AM]: ReflexiveUpgrade [SPServer Name=***** Parent=SPFarm Name=SharePoint_Config] failed.
] [ERROR] [2/9/2014 8:18:52 AM]: Logon failure: unknown user name or bad password.
[SPManager] [ERROR] [2/9/2014 8:18:52 AM]: at Microsoft.SharePoint.Search.Administration.MSITLB.IGatherManagerAdmin.SetDefaultAccount(String bstrAccount, String bstrPassword)

Hi Myprofile,
Logon to the front end server with the Farm admin account then
try this from an administrative command prompt
cd "c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN"
then at the
c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN\
run
psconfig -cmd upgrade -inplace b2b -force
Cheers,
Stacy Anothersharepointblog.blogspot.com

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.

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

Workflow manager configuration wizard failing

Similar Messages

Maybe you are looking for