Adding Workflow Manager 1.0 databases to AlwaysOn Groups

Hi,
I have workflow farm with 3 servers for high availability. But I need help to add the workflow manager 1.0 databases to AlwaysOn availability group to have high availability for workflow databases too.
Thanks & Regards,
Kunal

check this article for detailed implementation.
http://www.wictorwilen.se/Tags/Workflow%20Manager
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Similar Messages

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.

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

Error when running workflow form list item - workflow manager SharePoint 2013

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.

Here is what I had to do to get it working:
Leave the WFM (Workflow Manager) farm using the WFM config tool
Uninstall WFM, Service Bus, and the CU's from control panel
Uninstall Workflow Manager Client if it exists in the control panel, it didn't in mine
Delete the following databases in SQL Server:
SbGatewayDatabase
SbManagementDB
SBMessageContainer01
WFInstanceManagementDB
WFManagementDB
WFResourceManagementDB
Delete the workflow proxy service in Central Admin (important)
Application Management > Manage Service Applications
Highlight (select) the Workflow Service Application Proxy service (don’t click the hyperlink)
Select “Delete” from the ribbon.
Restart the server
Reinstall
Enable the workflow proxy service in CA for the web app, the 2013 workflow option will not show up in SPD unless you do this.
Application Management > Manage Web Applications
Select your web app
Select “Service Connections” from the ribbon
Check the Workflow Service Application Proxy item and click “OK”

Workflow Manager Cumulative Update (February) error

Hi,
I've downloaded and installed
Workflow Manager 1.0 Cumulative Update and
Service Bus 1.0 Cumulative Update. But after installing the updates, I can't access the Library workflow settings page. I'm getting unexpected error. Then after investigating the workflow manager log in event viewer, I've found the following error messages:
The asynchronous operation has completed with an exception. Exception message is: System.Data.SqlClient.SqlException (0x80131904): The EXECUTE permission was denied on the object 'InsertTrackingAndStatus', database 'DEV_WFInstanceManagementDB', schema 'dbo'.
   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.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.CompleteAsyncExecuteReader()
   at System.Data.SqlClient.SqlCommand.EndExecuteNonQueryInternal(IAsyncResult asyncResult)
   at System.Data.SqlClient.SqlCommand.EndExecuteNonQuery(IAsyncResult asyncResult)
   at Microsoft.Workflow.Management.ExecuteNonQueryAsyncResult.OnEndExecuteSql(IAsyncResult result)
   at Microsoft.Workflow.Management.ExecuteSqlAsyncResult.EndAsyncResult(IAsyncResult result)
   at Microsoft.Workflow.Common.BackoffRetryAsyncResult.IsolateWithRetry(IAsyncResult result)
   at Microsoft.Workflow.Common.AsyncResult.AsyncCompletionWrapperCallback(IAsyncResult result)
ClientConnectionId:2f93882a-8d4c-440d-a3ff-0bd9d1682ad2.
The issue I've found in my Dev environment with Windows Server 2008 R2 SP 1. This is standalone SharePoint farm with DC, SQL Server and SharePoint all installed in the same server. One workaround I have found that if I add the WF user as dbo to the database
as well as 'WFServiceOperators' then the error disappear.
Thanks,
Sohel Rana
http://ranaictiu-technicalblog.blogspot.com

I ran the provided SQL script on our Workflow Manager databases. I commented out the EXEC line and added a 'PRINT @Cmd'. This allowed me to view the actual commands the script would execute. These commands were generated:
GRANT EXECUTE ON [AddDbUserToRole] TO [WFServiceOperators]
GRANT EXECUTE ON [AddLoginAndUser] TO [WFServiceOperators]
GRANT EXECUTE ON [AddUserToServiceAdmins] TO [WFServiceOperators]
GRANT EXECUTE ON [AddUserToServiceOperators] TO [WFServiceOperators]
GRANT CONTROL, REFERENCES ON TYPE::[DebugTraceRecordValues] TO [WFServiceOperators]
GRANT EXECUTE ON [DeleteExpiredInstances] TO [WFServiceOperators]
GRANT EXECUTE ON [DeleteInstances] TO [WFServiceOperators]
GRANT EXECUTE ON [DeleteInstancesByScopeId] TO [WFServiceOperators]
GRANT EXECUTE ON [DeleteSystemInstances] TO [WFServiceOperators]
GRANT CONTROL, REFERENCES ON TYPE::[EntityIds] TO [WFServiceOperators]
GRANT CONTROL, REFERENCES ON TYPE::[EntityNames] TO [WFServiceOperators]
GRANT EXECUTE ON [FormatNTGroupName] TO [WFServiceOperators]
GRANT EXECUTE ON [GetDebugTraces] TO [WFServiceOperators]
GRANT EXECUTE ON [GetInstanceCount] TO [WFServiceOperators]
GRANT EXECUTE ON [GetInstanceDebugTraces] TO [WFServiceOperators]
GRANT EXECUTE ON [GetInstanceDebugTracesByWorkflowId] TO [WFServiceOperators]
GRANT EXECUTE ON [GetInstanceMetadata] TO [WFServiceOperators]
GRANT EXECUTE ON [GetInstances] TO [WFServiceOperators]
GRANT EXECUTE ON [GetInstancesById] TO [WFServiceOperators]
GRANT EXECUTE ON [GetInstancesByWorkflowId] TO [WFServiceOperators]
GRANT EXECUTE ON [GetInstanceStatusHistory] TO [WFServiceOperators]
GRANT EXECUTE ON [GetInstanceStatusHistoryRecordsByWorkflowId] TO [WFServiceOperators]
GRANT EXECUTE ON [GetInstancesToRestore] TO [WFServiceOperators]
GRANT EXECUTE ON [GetInstanceTelemetryData] TO [WFServiceOperators]
GRANT EXECUTE ON [GetMappedVariables] TO [WFServiceOperators]
GRANT EXECUTE ON [GetStatusHistory] TO [WFServiceOperators]
GRANT EXECUTE ON [GetStillReferencedWorkflows] TO [WFServiceOperators]
GRANT EXECUTE ON [GetStoreVersion] TO [WFServiceOperators]
GRANT EXECUTE ON [GetSystemInstances] TO [WFServiceOperators]
GRANT EXECUTE ON [GetUpdatedInstances] TO [WFServiceOperators]
GRANT CONTROL, REFERENCES ON TYPE::[Guids] TO [WFServiceOperators]
GRANT EXECUTE ON [HasPermissionToPerform] TO [WFServiceOperators]
GRANT EXECUTE ON [InsertInstanceDebugTraceRecords] TO [WFServiceOperators]
GRANT EXECUTE ON [InsertInstanceStatusHistoryRecords] TO [WFServiceOperators]
GRANT EXECUTE ON [InsertNotStartedInstanceRecord] TO [WFServiceOperators]
GRANT EXECUTE ON [InsertTrackingAndStatus] TO [WFServiceOperators]
GRANT CONTROL, REFERENCES ON TYPE::[InstanceStatusValues] TO [WFServiceOperators]
GRANT CONTROL, REFERENCES ON TYPE::[MetadataValues] TO [WFServiceOperators]
GRANT CONTROL, REFERENCES ON TYPE::[MetadataValuesWithInstanceId] TO [WFServiceOperators]
GRANT EXECUTE ON [OnInstanceEndedWithStatusDetail] TO [WFServiceOperators]
GRANT EXECUTE ON [OverrideTrackingAndStatus] TO [WFServiceOperators]
GRANT EXECUTE ON [ResetInstancesToNotStarted] TO [WFServiceOperators]
GRANT CONTROL, REFERENCES ON TYPE::[StatusHistoryRecordValues] TO [WFServiceOperators]
GRANT CONTROL, REFERENCES ON TYPE::[TrackingRecordValues] TO [WFServiceOperators]
GRANT EXECUTE ON [UpdateInstanceWorkflowStatus] TO [WFServiceOperators]
GRANT CONTROL, REFERENCES ON TYPE::[Variables] TO [WFServiceOperators]
GRANT CONTROL, REFERENCES ON TYPE::[WorkflowIds] TO [WFServiceOperators]
I ran the script against both 'WFInstanceManagementDB' and 'WFResourceManagementDB'. I also ran it against 'WFManagementDB', but the script didn't generate any GRANT commands for that database.
So I enabled the EXEC command and reran the script against both databases. Almost immediately I could see a drop in CPU utilization on our workflow server. Also the errors disappeared from the Event Log. To be safe I also rebooted the server.
This seems to have fixed our problem. I'd still like to have an official KB article or update for this problem, though.

Workflow Manager 1.0 (SharePoint 2013): The process was terminated due to an unhandled exception

I am seeing large numbers of the following errors appearing in the event log of the SharePoint 2013 application server hosting Workflow Manager 1.0:
Log Name: Application
Source: Application Error
Date: [Date/Time]
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: [Application Server]
Description:
Faulting application name: Microsoft.Workflow.ServiceHost.exe, version: 1.0.20922.0, time stamp: 0x505e1b24
Faulting module name: KERNELBASE.dll, version: 6.2.9200.16864, time stamp: 0x531d34d8
Exception code: 0xe0434352
Fault offset: 0x0000000000047b8c Faulting process id: 0x691c Faulting application start time: 0x01cfc2776b3f0d74
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: b8157bf8-2e6a-11e4-9413-00155d38891d Faulting package full name:
Faulting package-relative application ID: Event Xml:
Log Name: Application
Source: .NET Runtime
Date: [date/time]
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: [same application server]
Description:
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()
Event Xml:
Log Name: System
Source: Service Control Manager
Date: [date/time]
Event ID: 7031
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: [Same application server]
Description:
The Workflow Manager Backend service terminated unexpectedly. It has done this 895 time(s). The following corrective action will be taken in 30000 milliseconds: Restart the service.
Event Xml:
The SharePoint 2013 farm is updated through the September 2014 PU (KB2995902). Topology: 1 App, 2 WFEs. Workflow Manager 1.0 installed to the App server. Workflow Manager 1.0 cumulative updates one
and two have not been installed. The Service Bus Gateway and Service Bus Message Broker services are started. The Workflow Manager Backend service can be started, but then quickly stops.
Thoughts? Resolution? I would be grateful for any assistance.

Hi Stephan,
As I understand, you are encountering the issue that Workflow Manager Backend service terminating each time. May I know did you run the update cmdlets after you installed the updates for SharePoint server 2013? Please confirm it per the link below:
http://technet.microsoft.com/en-us/library/dn133867.aspx
If you haven’t run the updates cmdlets, I suspect this is an install issue. I’d suggest you re-install workflow manager to resolve the issue:
1) Leave WFM/SB Farm
2) Uninstall updates and application in the following order and one at a time:
Service Bus CU1
Workflow Manager CU1
Service Bus 1.0
Workflow Manager 1.0
Workflow Manager Client 1.0
Microsoft Windows Fabric
3) Log into SQL server and delete Service Bus and Workflow Manager databases.
SBManagementDB
SBGatewayDB
SBMessageContainer01
WFManagementDB
WFInstanceManagementDB
WFResourceManagementDB
4) Install in the following order one at a time through Web Platforms Installer:
Workflow Manager 1.0
Service Bus 1.0 CU1
Workflow Manager 1.0 CU1
Regards,
Rebecca Tu
TechNet Community Support

Can you install Workflow Manager 1.0 on Central Admin App Server Machine in 3-tier SharePoint Farm?

Hi,
I have just realised when looking at doing a Workflow that 2013 Workflows not available (you need to install Workflow Manager Farm). I understand why from a tenant installation perspective, but we are on-premise.
Can someone tell me if I can install Workflow Manager 1.0 (seen you have to now install WM 1.0 Refresh version) on the Central Admin App Server Machine in a 3 tier SharePoint farm. 3 WFE, 4 APP Servers, 1 DB Server and 1 DB Analysis Services Server.
I did test on a test farm 1WFE, 1 APP Server (with CA) and 1 Database Server. We are getting issues with the WFE Server having issues booting up or losing connection - possibly faulty network card. This may in no way be related to the install,
but just in case.
Any help appreciated.
Thanks.
John.

Yes, you can install WFM on any server in a SharePoint farm.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Do i need another Virtual machine rather than sharepoint server to install workflow manager ?

Hi ,
I have installed sharepoint 2013 on a single server with a built-in-database. And i have installed OWA in another virtual machine. Now i am trying to create a workflow. I have downloaded and installed sharepoint designer and workflow
manager in the sharepoint 2013 itself. Do i need to install workflow manager in another server and make it to communicate with sharepoint server ? And how to email-id in workflow when i tried in sharepoint designer we have select the user. How to allocate
e-mail id for users ?

Creating new VM is choice of your architecture. Workflow Manager only requires below.
Workflow Manager 1.0. Email ID will be automatically picked from the participants from AD.
.NET Framework 4 Platform Update 3 or .NET Framework 4.5
Service Bus 1.0
Workflow Client 1.0
PowerShell 3.0
The following additional requirements must be met before you can run Configuration Wizard to configure Workflow:
Instance of SQL Server 2008 R2 SP1, SQL Server Express 2008 R2 SP1, or SQL Server 2012.
TCP/IP connections or named pipes must be configured in SQL Server.
Windows Firewall must be enabled.
Ports 12290 and 12291 must be available.
Bala

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.

Oracle Workflow Manager, Agent Listener, and Java Mailer problem

Hi,
I am not sure this topic to this forum, since this might be installation issue.
But I am hitting a big wall.
I had Windows 2000 SP4.
I have already installed Oracle Database 10gR1, Oracle Developer 10gR2, and Oracle Workflow 2.6.3 Standalone previously.
Including :
- Oracle Workflow Server 2.6.3
- Oracle Workflow Builder 2.6.3.5
- Apache HTTP Server 9.0.4
- Workflow Middle Tier
Anything seems to right, including the Notification Mailer and the Business Event.
And I had also made backup of them surely.
Now,
I'd like to change into Oracle Database 10gR2 because :
1. Some errors I found when I tried to call a Report from Oracle Form.
Unable to connect to Report Server ...
I thought Oracle Database 10gR1 is not suitable for Oracle Developer 10gR2.
2. And in the OWF 2.6.3 Workflow Home Page, there was no Logout button (which I found in OWF 2.6.4)
I removed my previous installation including Oracle Workflow.
After strugglineg in the installation of Oracle Database 10gR2, now I am facing another problem with Oracle Workflow.
I succesfully installed Oracle Workflow 2.6.4 Server and Oracle Workflow Manager (standalone version),
and the Oracle Workflow Middle Tier.
After I launch Oracle Workflow Configuration Assisstant, everthing seems to be normal.
I succed to open the Oracle Workflow Home Page (and found the Logout button there)
Next, I tried to navigate to the Oracle Workflow Manager.
1. I start the OC4J_Workflow_Management_Container --> initialized
2. OC4J_Workflow_Component_Container
The following error line appeared in the OC4J command prompt
06/05/26 10:31:40 LOG_ID_UNKNOWN : oracle.apps.fnd.cp.gsc.Logger.Logger(String,
int) : Logging to System.out until necessary parameters are retrieved for Logger
to be properly started.
06/05/26 10:31:40 LOG_ID_UNKNOWN : oracle.apps.fnd.cp.gsc.SvcComponentContainer.
initializeStateMachine() : BEGIN [default implementation]
06/05/26 10:31:40 LOG_ID_UNKNOWN : oracle.apps.fnd.cp.gsc.SvcComponentContainer.
getNewWorkflowContext() : BEGIN
06/05/26 10:31:45 LOG_ID_UNKNOWN : oracle.apps.fnd.cp.gsc.SvcComponentContainer.
loadGlobalParameters() : BEGIN
06/05/26 10:31:48 oracle.apps.fnd.wf.common.ContextFactoryException: Unable to g
et connection from data source because the following Exception occurred -> java.
sql.SQLException: ORA-28000: the account is locked
06/05/26 10:33:57 Oracle Application Server Containers for J2EE 10g (9.0.4.1.0)
initialized
3. finally it initialized
Next I tried to go to Oracle Workflow Manager from related link of Enterprise Manager
It is said that the OWF_MGR is locked
(I surprised since I had UNLOCKED the OWF_MGR after the installation and succeed to login at the Workflow Home Page)
And the following error line appeared in the commaned prompt after that
06/05/26 10:35:03 OrionCMTConnection not closed, check your code!
06/05/26 10:35:03 Logical connection not closed, check your code!
06/05/26 10:35:03 (Use -Djdbc.connection.debug=true to find out where the leaked
connection was created)
4. I re-UNLOCK the OWF_MGR and login to Oracle Workflow Manager
I noticed that the Agent Listener and Notification Service is Unavailable
(In OWF 2.6.3, The Agent Listener was started and Notification Service was waiting to be configured)
I tried to start one of the Agent Listener, but the following error appeared
ERROR: The Service Component Container is not running
Well, I had the same problem when installing the OWF 2.6.3
I tried to uninstall (remove) and re-install it like I had done before in OWF 2.6.3
(based on someone's post in Oracle's forum)
But this time, the re-installation won't fix this problem. (It was succeed in the OWF 2.6.3)
Everytime I start the OC4J, using wfmgrstart.bat and wfsvcstart.bat
the OWF_MGR is re-LOCKED(TIME) automatically.
And the servlet (WFALSNRSVC and WFMLRSVC) are not running.
I am worry, since I cannot use the Notification Mailer if this problem had not fixed yet.
(In OWF 2.6.3, the mailer was not available until those servlet is Started)
Sorry for the long post.
Any help would be grateful.
Many thanks,
Buntoro

Hi,
Finally, I have found the solution.
Step :
1. Start all of the Oracle Service, except for the OC4J
If you have already started OC4J, then stop them
Unlocked the <wf_manager_user>
2. Search in your Oracle Home : data-sources.xml
There should be two files,
one is in the ...\OC4J_Workflow_Component_Container\application-deployments\WFALSNRSVCApp
the other is in ...\OC4J_Workflow_Component_Container\application-deployments\WFMLRSVCApp
3. Make sure, you create back up of them.
4. Replace the following line
password="->pwForOwfMgr"
with
password="<your_wf_manager_password>",
should be look like this
password="a"
5. Now start the OC4J using wfmgrstart.bat and wfsvcstart.bat
6. Next, login to the Oracle Workflow Manager
This worked for me.
Hope this will help someone who has the same problem.
Buntoro

Workflow manager 1.0 : runtime error 400 running Add-WFHost "The api-version in the query string is not supported"

Installing Workflow Manager 1.0 for SharePoint Server 2013 SP1 everything is fine until the last step of the configuration and last powershell command :
Add-WFHost -WFFarmDBConnectionString 'myconnectionstring' -RunAsPassword $WFRunAsPassword -EnableFirewallRules $true -SBClientConfiguration $SBClientConfiguration -CertificateAutoGenerationKey $WFCertAutoGenerationKey -Verbose;
gives me the following error :
Add-WFHost : The remote server returned an error: (400) Bad Request. The api-version in the query string is not supported. Either remove it from the Uri or use one of '2012-03'..TrackingId:412684e3-3539-468e-91e6-17838c6eaa55_GS
P,TimeStamp:04/04/2014 12:54:11
At line:1 char:1
Can't find anything about this subject except this
thread which does not help me that much in SharePoint dev env ...
Removing workflow manager 1.0 and service bus (leave the farm using wizzard, remove binaries and databases) does not help.
Who already faces this issue and how can I try to resolve it ?
Best regards !
Alexandre DAVID

The API version is hardcoded in Microsoft.ServiceBus.dll, which ships as part of the Service Bus. Each version of this lib has a different string.
If you install workflow manager 1.0, here are the pre-requisites:
.NET Framework 4 Platform Update 3 or .NET Framework 4.5
Service Bus 1.0
Workflow Client 1.0
PowerShell 3.0
The following are the pre-requisites to configure Workflow Manager 1.0
Instance of SQL Server 2008 R2 SP1, SQL Server Express 2008 R2 SP1, or SQL Server 2012.
TCP/IP connections or named pipes must be configured in SQL Server.
Windows Firewall must be enabled. [Windows Firewall is Off on target server]
Ports 12290 and 12291 must be available.
Here are the reference for installing and configuring Workflow Manager 1.0:
http://lennytech.wordpress.com/2013/06/02/installing-workflow-manager-1-0/
http://lennytech.wordpress.com/2013/06/02/configuring-workflow-manager-1-0/
http://social.technet.microsoft.com/Forums/en-US/c74507fb-ac2d-405f-b19c-2712b1055708/workflow-manager-10-configuration-service-bus-for-windows-server-the-api-version-is-not?forum=sharepointadmin

Sharepoint 2013 Workflow manager setup SQL serverinstance "Failure in connecting to SQL Server"

Hi Guys
im having issues with installing work flow manager.
this installation has gone ok, but when I'm in the configuration stage, and type in the SQL server instance, it returns with failure in connecting to SQL server.
this happens with SSL and with out SSL
I look forward to your responses
Kindest regards
Jack

Make sure that you have installed workflow manager updates on the server.
Follow these two steps first:
Add
WFSetup account (installer account) to SQL Server security group and give him
SysAdmin permission.
Add WFSetup to Workflow server in machine
administrator group, so user can login as worklfow administrator.
Enter database machine name and test it.
Adnan Amin MCT, SharePoint Architect | If you find this post useful kindly please mark it as an answer :)

Workflow Manager service in Error state after Dec14 CU install

After installing Dec 14 CU and updating the WF farm to CU2 I tried to run the cmdlets as per here -
https://technet.microsoft.com/en-us/library/dn133867.aspx?f=255&MSPPError=-2147217396
$credential = [System.Net.CredentialCache]::DefaultNetworkCredentials
$site = Get-SPSite https://teams.sharepoint.com
$proxy = Get-SPWorkflowServiceApplicationProxy
$svcAddress = $proxy.GetWorkflowServiceAddress($site)
Copy-SPActivitiesToWorkflowService -WorkflowServiceAddress $svcAddress -Credential $credential -Force $true
This errors:
Copy-SPActivitiesToWorkflowService : An internal error occured. For more details, please see the server logs. Client
ActivityId : cb2a40af-2c50-4e5c-8ac2-c5436c351b89.
At line:1 char:1
+ Copy-SPActivitiesToWorkflowService -WorkflowServiceAddress $svcAddress -Credenti ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (Microsoft.Share...WorkflowService:CopySPActivitiesToWorkflowService) [Copy
   -SPActivitiesToWorkflowService], InternalServerException
    + FullyQualifiedErrorId : Microsoft.SharePoint.WorkflowServices.PowerShell.CopySPActivitiesToWorkflowService
I then ran get-WFFarmstatus on the WF server (3 in the farm) and see that the service is stopped on all the WF servers with a warning:
WFserver1      WorkflowServiceBackend
Stopped
WARNING: Endpoint https://WFserver1:12290/ is not responding: The remote server returned anerror: (500) Internal Server Error.
WFserver1      WorkflowServiceFrontEnd
Stopped
Checked the underlying services and IIS on the 3 WF servers and these are all now started but the WF service cannot be started:
net start WorkflowServiceBackend
The Workflow Manager Backend service is starting.
The Workflow Manager Backend service could not be started.
A system error has occurred.
System error 1067 has occurred.
The process terminated unexpectedly.
The WF operational logs show this:
Unhandled exception in AppDomain:
Microsoft.Workflow.Common.FatalException: An unrecoverable error occurred. For
diagnostic purposes, this English message is associated with the failure: 'A
required Workflow Manager configuration
'WorkflowServiceScopeSnapshotProcessBatchSize' is not present. Please add this
configuration value.'. ---> System.IO.InvalidDataException: A required
Workflow Manager configuration 'WorkflowServiceScopeSnapshotProcessBatchSize'
is not present. Please add this configuration value. <o:p></o:p>
at
Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result) <o:p></o:p>
at
Microsoft.Workflow.Service.WorkflowServiceBackendHost.OnStartCompleted(IAsyncResult
result) <o:p></o:p>
There is a suggested fix for this here -
http://www.guideushow.com/sharepoint/solved-workflowservicescopesnapshotprocessbatchsize-is-not-present/
(http://www.guideushow.com/sharepoint/solved-workflowservicescopesnapshotprocessbatchsize-is-not-present/)
<o:p></o:p>
I’d like to at least get some feedback as to whether this is safe/supported (MS doesn’t like
any tinkering with the DBs…) – or whether we should go down the uninstall/reinstall
the Workflow farm route - thanks
J

Hi,
For your issue, try to provid EXECUTE permission for role "WFServiceOperators".
Add Workflow service account as “WFServiceOperators” into the database. Here are the steps to apply permissions:
Open the Query Window and Select the database “WFInstanceManagementDB”
Write the following line of script:
GRANT EXECUTE TO WFServiceoperators
Hit Execute.
Repeat the steps for database “WFResourceManagementDB”
Here are similar issue posts, you can use as a reference:
https://social.msdn.microsoft.com/Forums/office/en-US/351b72e1-1664-43c5-8c2b-ffb307bef38e/cant-access-workflow-status-page-after-workflow-manager-cu2?forum=sharepointadmin
https://social.msdn.microsoft.com/forums/azure/en-US/054d2a58-8847-4a6a-b1ab-05a79f49fe65/workflow-manager-cumulative-update-february-error?forum=wflmgr
Best Regards,
Lisa Chen
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Error with configuring workflow manager

Starting
System.Management.Automation.CmdletInvocationException: An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change
the alias to a valid name.
An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.
An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name. ---> System.Data.SqlClient.SqlException:
An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.
An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.
An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.
в System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
в System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
в System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
в System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
в System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite)
в System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
в System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
в System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
в System.Data.Linq.SqlClient.SqlProvider.Execute(Expression query, QueryInfo queryInfo, IObjectReaderFactory factory, Object[] parentArgs, Object[] userArgs, ICompiledSubQuery[] subQueries, Object lastResult)
в System.Data.Linq.SqlClient.SqlProvider.ExecuteAll(Expression query, QueryInfo[] queryInfos, IObjectReaderFactory factory, Object[] userArguments, ICompiledSubQuery[] subQueries)
в System.Data.Linq.SqlClient.SqlProvider.System.Data.Linq.Provider.IProvider.Execute(Expression query)
в Microsoft.ServiceBus.Commands.Common.ServerManagementStoreDataContext.CreateServerAdministratorLogin(String loginName)
в Microsoft.ServiceBus.Commands.Common.SecurityHelper.CreateServerAdministratorRole(String accountName, String connectionString)
в Microsoft.ServiceBus.Commands.NewSBFarmBase.InstallManagementDB(String connectionString, String adminGroup, String runAsName)
в Microsoft.ServiceBus.Commands.NewSBFarmBase.ProcessRecord()
--- Конец трассировки внутреннего стека исключений ---
в System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
в Microsoft.Workflow.Deployment.ConfigWizard.CommandletHelper.InvokePowershell(Command command, Action`2 updateProgress)
в Microsoft.Workflow.Deployment.ConfigWizard.ProgressPageViewModel.CreateSBFarm(FarmCreationModel model)

Hi, I have tried in two separate environments to create a new workflow farm and am getting the same error. I have already installed the Feb CU for both workflow manager and the service bus. I rebooted all servers after installing.
I noticed a message in the UI saying "Configuration operation failed. Please drop databases and use ‘Create a New Farm’ again." When I look in SQL Management Studio no databases have been created. The new farm wizard fails on the first step.
Any ideas on a fix for this? Changing the format of the account as above didn't work for me. I am using a SQL alias on my server, would this cause any problems? When I test the connection to the DB from the wizard all tests pass.

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

Adding Workflow Manager 1.0 databases to AlwaysOn Groups

Similar Messages

Maybe you are looking for