Workflow manager 2013 installation????

We migrated to SP2013 and workflows breaked...on search we found need to install workflow manager.
Question: Should we install the workflow manager on Front End & Applications? Also is this required configuration wizard and restart of servers after installing it?
We have 2 Web Front End and 2 Application Servers.

Hi Imran,
As Alex mentioned 2010 workflows don't workflow manager.
Workflow Manager is needed only for 2013 workflows
If you want your 2010 SPD workflows to run in 2013 platform, then you have to recreate the workflow as the assemblies and runtime are different now in SP2013. Also, there
is a change from XOML to XAML format. The activities which are implementations of activity classes, are implemented declaratively by using XAML.
This is what is stated in this link
http://blogs.msdn.com/b/chandru/archive/2013/04/14/upgrading-spd-2010-workflows-to-spd-2013-workflows.aspx
Kind Regards,
John Naguib
Technical Consultant/Architect
MCITP, MCPD, MCTS, MCT, TOGAF 9 Foundation
Please remember to mark your question as answered if this solves your problem

Similar Messages

64bit workflow manager tools installation not working

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

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

Install workflow manager on sharepoint 2013

hi , I install work flow manager .but i could not see workflow 2013 in sharepoint 2013 .why ?

http://technet.microsoft.com/en-us/library/jj658588%28v=office.15%29
There is service application\option in SharePoint 2013 where you can see workflow 2013.
You can see workflow 2013 in designer which comes with Workflow manager 2013. Also you have to configure workflow manager 2013 as per below:
http://www.harbar.net/articles/wfm2.aspx
http://blog.cloudshare.com/2013/01/15/how-to-install-and-configure-workflow-infrastructure-in-sharepoint-2013/
http://lennytech.wordpress.com/2013/06/02/configuring-sharepoint-2013-to-use-workflow-manager-1-0/

Workflow Manager and SharePoint Designer publishing error

Hello all,
I'm hoping for some help in fixing this issue.
I've been trying to publish a workflow using SharePoint Designer only to find that I get this error:
"Errors were found when compilint the workflow. The workflow files were saved but cannot be run."
After clicking on the advanced button it shows error:
System.InvalidOperationException: Operation failed with error Microsoft.Workflow.Client.WorkflowCommunicationException: The request was aborted: The request was canceled. Client ActivityId : 6a78ad9c-6ac6-f03a-0680-003bd46e5f68. ---> System.Net.WebException:
The request was aborted: The request was canceled. ---> Microsoft.SharePoint.SPException: The requested operation requires an HTTPS (SSL) channel.
Ensure that the target endpoint address supports SSL and try again.
Target endpoint address:
Note: the message cuts off after the "Target endpoint address".
Looking on the SharePoint server, when I try and pull up the Workflow Manager site (https://localhost:12290/) I get this response:
<?xml version="1.0"?>
xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
<Code>AuthorizationError</Code><message><Message>The caller does not have the necessary
permissions required for this operation. Permissions granted: None. Required permissions: ReadScope.</Message></message></Error>
I am running this farm with HTTPS and I have registered the SP workflow service with the appropriate application. I have also set the Workflow Management Site bindings in IIS to utilize the same certificate as the default SharePoint site.
At this point, I don't know if the error that I received from Designer is related to the Site error, although I do know that I also have a Development environment that is able to publish workflows just fine. However, this farm uses HTTP rather than HTTPS
so I can only assume that the differences are what's causing the issue. I would appreciate any help that anyone can offer. Thanks!

Hi,
As I understand, you encountered the issue when you published a workflow on SharePoint 2013 workflow platform.
I wonder does it work well before when using 2013 workflow platform? If it works before, did you install any updates or change the configuration to the workflow related settings?
If this is the first time after you installed workflow manager 2013, then I’d recommend you try re-registering workflow service per the link below and post the result:
http://technet.microsoft.com/en-us/library/jj663115(v=office.15).aspx
http://technet.microsoft.com/en-us/library/jj658588(v=office.15).aspx
From the message you accessed workflow host uri, please make sure the account to wfsetup and wfservice account are both in wfadmins group.
http://blogs.msdn.com/b/briangre/archive/2013/02/20/least-privilege-configuration-for-windows-azure-workflow-with-sharepoint-2013.aspx
Regards,
Rebecca Tu
TechNet Community Support

Workflow manager IIS site throws a 403 Forbidden error and published workflows throw an error 400 bad request

Hello All , Request your help on the below issue ,
We have a single server farm SP 2013 where workflow was working as expected but its broken now , Not sure
what caused this. Workflow manager is installed alongside Service Bus. Workflow Manager client is installed on the same SP server.
We are able to create and publish the workflows from SP Designer without errors but when we start the workflow from SharePoint list we get an error " Sorry something went wrong". We have tried creating new workflows but the same problem.
We receive the below error in event viewer.
Error processing management request. Method: PUT, RequestUri: http://server URL:12291/$Workflows/89c767d2-82d2-4bd9-8e5e-dcace81d844f, Error: System.ArgumentException: The remote server returned an error: (400) Bad Request. ---> System.Net.WebException:
The remote server returned an error: (400) Bad Request.
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at Microsoft.ServiceBus.Messaging.ServiceBusResourceOperations.GetAsyncResult`1.EndGetResponse(GetAsyncResult`1 thisPtr, IAsyncResult ar)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StepCallback(IAsyncResult result)
--- End of inner exception stack trace ---
Server stack trace:
Exception rethrown at [0]:
at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Gateway.HttpAsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Gateway.WorkflowServiceGateway.<>c__DisplayClass6a.<EndCreateOrUpdateWorkflow>b__69()
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)
ULS logs give below error
Error 1 - Microsoft.Workflow.Client.InternalServerException: An internal error occured. For more details, please see the server logs. HTTP headers received from the server - ActivityId: ba6e77cb-aaae-41a0-9cc8-1ea817d0045e. NodeId: Servername.
Scope: /SharePoint/default/bc694777-7bbb-473e-ab2d-20087221a97a/5229793b-31a1-44b1-9b0b-374f38b762fd. Client ActivityId : a6daec9c-7139-7034-b4ee-edeb1f96ec2a. ---> System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Client.HttpGetResponseAsyncResult`1.End(IAsyncResult result)
at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest request, T content) -
-- End of inner exception stack trace ---
at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest request, T content)
at Microsoft.Workflow.Client.WorkflowManagementClient.SendRequest[T](HttpWebRequest request, T content)
at Microsoft.Workflow.Client.WorkflowManager.Publish(WorkflowDescription description, Boolean terminateActiveInstances)
at Microsoft.SharePoint.WorkflowServices.FabricWorkflowManagementClient.PublishWorkflow(String serviceGroupName, WorkflowDescription workflow)
at Microsoft.SharePoint.WorkflowServices.WorkflowProxy.CreateDefinitionSubscription(String subscriptionName, String eventSource, List`1 eventTypes, String definitionName, IDictionary`2 metadata, WorkflowEventContext eventContext) StackTrace:
at Microsoft.Office.Server.Native.dll: (sig=35339f9c-8871-4ef1-9118-9c1bd0cb6598|2|microsoft.office.server.native.pdb, offset=131CE)
at Microsoft.Office.Server.Native.dll: (offset=21B4D)
Error 2 - Error publishing workflow subscription (republish or retry publish) information: Microsoft.Workflow.Client.InternalServerException: An internal error occured. For more details, please see the server logs. HTTP headers received
from the server - ActivityId: ba6e77cb-aaae-41a0-9cc8-1ea817d0045e. NodeId:
ServerName. Scope: /SharePoint/default/bc694777-7bbb-473e-ab2d-20087221a97a/5229793b-31a1-44b1-9b0b-374f38b762fd. Client ActivityId : a6daec9c-7139-7034-b4ee-edeb1f96ec2a. ---> System.Net.WebException: The remote server returned an error: (500)
Internal Server Error.
at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Client.HttpGetResponseAsyncResult`1.End(IAsyncResult result)
at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest request, T content) -
-- End of inner exception stack trace ---
at Microsoft.Workflow.Client.ClientHelpers.SendRequest[T](HttpWebRequest request, T content)
at Microsoft.Workflow.Client.WorkflowManagementClient.SendRequest[T](HttpWebRequest request, T content)
at Microsoft.Workflow.Client.WorkflowManager.Publish(WorkflowDescription description, Boolean terminateActiveInstances)
at Microsoft.SharePoint.WorkflowServices.FabricWorkflowManagementClient.PublishWorkflow(String serviceGroupName, WorkflowDescription workflow)
at Microsoft.SharePoint.WorkflowServices.WorkflowProxy.CreateDefinitionSubscription(String subscriptionName, String eventSource, List`1 eventTypes, String definitionName, IDictionary`2 metadata, WorkflowEventContext eventContext)
at Microsoft.SharePoint.WorkflowServices.FabricSubscriptionService.<>c__DisplayClass1.<CreateDefinitionSubscription>b__0()
at Microsoft.SharePoint.WorkflowServices.WorkflowServiceContextExtensions.InvokeWithEcosystemRetry(WorkflowServicesContext context, EcosystemRequiredMethod method)
at Microsoft.SharePoint.WorkflowServices.FabricSubscriptionService.CreateDefinitionSubscription(String subscriptionName, Guid eventSourceId, String eventSource, List`1 eventNames, String definitionName, IDictionary`2 metadata, WorkflowEventContext eventContext)
at Microsoft.SharePoint.WorkflowServices.WorkflowSubscriptionStorageEventReceiver.ItemUpdating(SPItemEventProperties properties)
Error3 - Microsoft.Workflow.Client.InternalServerException: An internal error occured. For more details, please see the server logs. HTTP headers received from the server - ActivityId: ba6e77cb-aaae-41a0-9cc8-1ea817d0045e. NodeId: ServerName.
Scope: /SharePoint/default/bc694777-7bbb-473e-ab2d-20087221a97a/5229793b-31a1-44b1-9b0b-374f38b762fd. Client ActivityId : a6daec9c-7139-7034-b4ee-edeb1f96ec2a. ---> System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
at SPRequest.AddOrUpdateItem: UserPrincipalName=i:0).w|s-1-5-21-182846760-3036401646-508972453-351846, AppPrincipalName= ,bstrUrl=http://sharepointsite ,bstrListName={48A21758-9123-48F0-9BDE-9EB632B07BC6} ,bAdd=False ,bSystemUpdate=False ,bPreserveItemVersion=False
,bPreserveItemUIVersion=False ,bUpdateNoVersion=False ,pbstrNewDocId=00000000-0000-0000-0000-000000000000 ,bHasNewDocId=False ,bstrVersion=16 ,bCheckOut=False ,bCheckin=False ,bUnRestrictedUpdateInProgress=True ,bMigration=False ,bPublish=False ,bstrFileName=<null>
Any help appreciated. Thanks in advance.

Hi,
As I understand, you encountered the issue when you published a workflow on SharePoint 2013 workflow platform.
I wonder does it work well before when using 2013 workflow platform? If it works before, did you install any updates or change the configuration to the workflow related settings?
If this is the first time after you installed workflow manager 2013, then I’d recommend you try re-registering workflow service per the link below and post the result:
http://technet.microsoft.com/en-us/library/jj663115(v=office.15).aspx
http://technet.microsoft.com/en-us/library/jj658588(v=office.15).aspx
From the message you accessed workflow host uri, please make sure the account to wfsetup and wfservice account are both in wfadmins group.
http://blogs.msdn.com/b/briangre/archive/2013/02/20/least-privilege-configuration-for-windows-azure-workflow-with-sharepoint-2013.aspx
Regards,
Rebecca Tu
TechNet Community Support

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

Getting Error while Installing Workflow Manager 1.0 on Sharepoint 2013 On-Prem server

I am trying to install Workflow Manager 1.0 on our SharePoint Server 2013 which is On-Prem installation. The SharePoint Server 2013 is functioning correctly. During the installation of Workflow Manager 1.0 on the same SharePoint 2013 server, I receive the
following message: "Port number 9355 specified for HTTPS Port is blocked" I have checked our firewall Inbound rules and this port is not blocked.
Any reason why this could be happening or did I miss anything?
Thanks Snehal H.Rana SharePoint Consultant

I am happy to inform you that I was able to resolve this error. I configured this on different ports other than 9355. We need to modify 2 files called "ClusterManifest.1.0.xml" and "ClusterManifest.current.xml" in c:\Program
Files\Windows Fabric\Bin. They were pointing to older FQDN under following node:
<NodeList>
<Node NodeName="yourserverfqdn" IPAddressOrFQDN="yourserverfqdn" IsSeedNode="true" NodeTypeRef="DefaultNodeType" />
</NodeList>
These files won't let you edit directly in notepad so you will need to make a copy of these files (just in case). Open up the notepad as "Run As Administrator". Drag these files to the notepad. After you are done editing, save these as original
names but make sure that the extension is .xml
You will also need to do IISReset
That did the trick for me.
Thanks Snehal H.Rana SharePoint Consultant

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”

Not able to complete an installation of workflow manager 1.0

I'm currently trying to install workflow manager 1.0 on a virtual machine Windows Server 2012 hosted in Azure.
SharePoint 2013 is running fine on this machine (I have two others VM: DC and SQL server).
I start Web Platform installer and select Workflow Manager. The download is ok but the installation seems to be frozen at the first step. Nothing happens after 3 hours.
I have also tried the offline installation but same problem, here is what appears in the command line window since 2 hours:
Starting Installation
Started downloading products...
Started downloading: 'Workflow Client 1.0'
Started installing Products...
Downloaded: 'Workflow Client 1.0'
Started installing: 'IIS: Management Service'
Started downloading: 'Microsoft Windows Fabric V1 RTM'
Downloaded: 'Microsoft Windows Fabric V1 RTM'
Started downloading: 'Service Bus 1.0'
Downloaded: 'Service Bus 1.0'
Started downloading: 'Workflow Manager 1.0'
Downloaded: 'Workflow Manager 1.0'
I do the installation Under administrator account...
Do you have an idea how to solve this issue?
Thanks for your help

Hi,
According to your post, my understanding is that you failed to install workflow manager 1.0.
Please make sure you install Workflow Manger correctly. You can refer to:
Install and configure workflow for SharePoint Server 2013
In addition, please check the hosts file on the machine on which installation is being performed. If there are any loopback entries to a localhost IP in the hosts file, comment or remove them temporarily and retry configuration.
Here is a similar blog for you to take a look at:
http://lennytech.wordpress.com/2013/06/02/troubleshooting-configuration-problems-with-workflow-manager-and-service-bus/
More information:
Known Issues in Workflow Manager 1.0
Troubleshooting Workflow Manager 1.0 Management and Execution
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Workflow Manager 1.0 - Service Bus 1.0 installation failure

On a SharePoint 2013, I am trying to set up Workflow Manager 1.0 (version: 2.0.20922.0) using WPI 5.0 (version: 7.1.50430.0).
Windows Server version: Microsoft Windows Server 2008 R2 Datacenter [Version 6.1.7601] SP1. Locale: en-gb.
SharePoint Server 2013 version: 15.0.4569.1000
WPI installer fails at step 2.
Step 1: Execute ASP.NET IIS registration tool - is installed successfully. However, Step 2 fails:
Step 2: Service Bus 1.0. Gives following error
Windows event logs:
Product: Service Bus 1.0 -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action EnableUAC, location: C:\Windows\Installer\MSI41C2.tmp,
command: "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Service Bus 1.0\Service Bus PowerShell.lnk" "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Service Bus 1.0\Service Bus Configuration.lnk"
WPI log.txt:
DownloadManager Information: 0 : Starting install sequence
ThreadId=7
DateTime=2014-06-30T15:04:30.5393958Z
DownloadManager Information: 0 : Using cached file at C:\Users\admin\AppData\Local\Microsoft\Web Platform Installer\installers\ServiceBus\F35D6168BD14B4B152877F9ADECD16B90D6A0F6E\Service_Bus.msi instead of downloading from http://go.microsoft.com/fwlink/?LinkID=258757&CLCID=0x409
ThreadId=3
DateTime=2014-06-30T15:04:30.5462502Z
DownloadManager Information: 0 : Using cached file at C:\Users\admin\AppData\Local\Microsoft\Web Platform Installer\installers\WorkflowManager\99C4319912D17F33BA408A096B163A2132193A93\Workflow_Manager.msi instead of downloading from http://go.microsoft.com/fwlink/?LinkID=258761&CLCID=0x409
ThreadId=3
DateTime=2014-06-30T15:04:30.6050022Z
DownloadManager Information: 0 : Starting EXE command for product 'Execute ASP.NET IIS Registration tool'. Commandline is: 'C:\Windows\sysnative\cmd.exe /C C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -iru'. Process Id: 8276
ThreadId=7
DateTime=2014-06-30T15:04:30.6471078Z
DownloadManager Information: 0 : Install exit code for product 'Execute ASP.NET IIS Registration tool' is '0'
ThreadId=7
DateTime=2014-06-30T15:04:41.9431590Z
DownloadManager Information: 0 : Install return code for product 'Execute ASP.NET IIS Registration tool' is Success
ThreadId=7
DateTime=2014-06-30T15:04:41.9470758Z
DownloadManager Information: 0 : Product Execute ASP.NET IIS Registration tool done install completed
ThreadId=1
DateTime=2014-06-30T15:04:41.9480550Z
DownloadManager Information: 0 : Increasing current install to 2
ThreadId=1
DateTime=2014-06-30T15:04:41.9480550Z
DownloadManager Information: 0 : Starting MSI install for msi 'C:\Users\admin\AppData\Local\Microsoft\Web Platform Installer\installers\ServiceBus\F35D6168BD14B4B152877F9ADECD16B90D6A0F6E\Service_Bus.msi', commandline: 'WEBPI=1 ACTION=INSTALL REBOOT=ReallySuppress'
ThreadId=7
DateTime=2014-06-30T15:04:41.9539302Z
DownloadManager Information: 0 : MSI install return value for product 'Service Bus 1.0' is '1603'
ThreadId=7
DateTime=2014-06-30T15:04:50.0891238Z
DownloadManager Error: 0 : Install return code for product 'Service Bus 1.0' is Failure (There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. )
ThreadId=7
DateTime=2014-06-30T15:04:50.0891238Z
DownloadManager Information: 0 : Product Service Bus 1.0 done install completed
ThreadId=1
DateTime=2014-06-30T15:04:50.0901030Z
DownloadManager Information: 0 : Increasing current install to 3
ThreadId=1
DateTime=2014-06-30T15:04:50.0901030Z
DownloadManager Information: 0 : Service Bus 1.0 installation log: C:\Users\admin\AppData\Local\Microsoft\Web Platform Installer\logs\install\2014-06-30T16.04.30\Service_Bus.txt
ThreadId=7
DateTime=2014-06-30T15:04:50.0901030Z
DownloadManager Warning: 0 : Dependency failed for product 'Workflow Manager 1.0'. Skipping install
ThreadId=7
DateTime=2014-06-30T15:04:50.0901030Z
DownloadManager Information: 0 : Product Workflow Manager 1.0 had a dependency fail. Increasing install product to 4
ThreadId=1
DateTime=2014-06-30T15:04:50.0920614Z
Service_Bus.txt:
MSI (s) (04:C8) [16:04:49:994]: Executing op: ComponentUnregister(ComponentId={BD089387-D1F2-4012-B269-D38D5446C031},ProductKey={F438C511-5A64-433E-97EC-5E5343DA670A},BinaryType=1,)
MSI (s) (04:C8) [16:04:49:995]: Executing op: ComponentUnregister(ComponentId={E7AC164F-EFA7-41AE-9A55-8A4762FFDB1F},ProductKey={F438C511-5A64-433E-97EC-5E5343DA670A},BinaryType=1,)
MSI (s) (04:C8) [16:04:49:996]: Executing op: ComponentUnregister(ComponentId={47014104-90AA-4143-B004-91BBF9764BF2},ProductKey={F438C511-5A64-433E-97EC-5E5343DA670A},BinaryType=1,)
MSI (s) (04:C8) [16:04:49:996]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=0)
MSI (s) (04:C8) [16:04:49:996]: Error in rollback skipped. Return: 5
MSI (s) (04:C8) [16:04:50:008]: Note: 1: 2318 2:
MSI (s) (04:C8) [16:04:50:011]: No System Restore sequence number for this installation.
MSI (s) (04:C8) [16:04:50:011]: Unlocking Server
MSI (s) (04:C8) [16:04:50:018]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
Action ended 16:04:50: INSTALL. Return value 3.
MSI (s) (04:C8) [16:04:50:040]: Note: 1: 1708
MSI (s) (04:C8) [16:04:50:040]: Product: Service Bus 1.0 -- Installation failed.
MSI (s) (04:C8) [16:04:50:041]: Windows Installer installed the product. Product Name: Service Bus 1.0. Product Version: 2.0.20922.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.
MSI (s) (04:C8) [16:04:50:046]: Deferring clean up of packages/files, if any exist
MSI (s) (04:C8) [16:04:50:047]: MainEngineThread is returning 1603
MSI (s) (04:C4) [16:04:50:065]: RESTART MANAGER: Session closed.
MSI (s) (04:C4) [16:04:50:065]: No System Restore sequence number for this installation.
=== Logging stopped: 30/06/2014 16:04:50 ===
MSI (s) (04:C4) [16:04:50:069]: User policy value 'DisableRollback' is 0
MSI (s) (04:C4) [16:04:50:070]: Machine policy value 'DisableRollback' is 0
MSI (s) (04:C4) [16:04:50:070]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (04:C4) [16:04:50:070]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (04:C4) [16:04:50:071]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (04:C4) [16:04:50:072]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (04:C4) [16:04:50:072]: Restoring environment variables
MSI (s) (04:C4) [16:04:50:074]: Destroying RemoteAPI object.
MSI (s) (04:98) [16:04:50:075]: Custom Action Manager thread ending.
MSI (c) (F8:04) [16:04:50:080]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (F8:04) [16:04:50:082]: MainEngineThread is returning 1603
=== Verbose logging stopped: 30/06/2014 16:04:50 ===
Any pointers are appreciated.

Hi,
Here are some links about the similar issue for you to take a look at:
http://social.technet.microsoft.com/Forums/sharepoint/en-US/560b3f29-450c-4ef4-9076-03caaa45e62a/workflow-manager-10-were-sorry-the-product-failed-to-install?forum=sharepointadmin
http://support.esri.com/ja/knowledgebase/techarticles/detail/28695
http://blog.riccardocelesti.it/2013/02/01/workflow-manager-setup-issue/
More information about how to install and configure workflow for SharePoint Server 2013 for your reference:
Install and configure workflow for SharePoint Server 2013
http://technet.microsoft.com/en-us/library/jj658588(v=office.15)
Video series: Install and configure Workflow in SharePoint Server 2013
http://technet.microsoft.com/en-us/library/dn201724(v=office.15).aspx
Best regards
Dennis Guo
TechNet Community Support

What is the windows server 2013 license version than I need to install workflow manager 1.0

what is the windows server 2013 license version than I need to install workflow manager 1.0?
enterprise or standard? can I install it on datacenter?
please provide me with the reference.
thanks

Workflow Manager will work with either SharePoint Enterprise or Standard. It doesn't work well with Foundations since it depends on User Profiles to pass user identity to the workflow. And yes you can install it on Windows Server datacenter edition.
Here are the supported platforms for installation
http://msdn.microsoft.com/en-us/library/jj193487(v=azure.10).aspx
This article talks about integration with SharePoint and states that Foundation is not supported, but it doesn't differentiate between the Server editions, so any edition will do.
http://technet.microsoft.com/en-us/library/jj658588.aspx
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

SharePoint 2013 Update Workflow Manager problems after Service Pack 1

Hello guys,
I've installed the service pack 1 for SharePoint 2013 and then I tried to update the workflow manager, but I always get an error message that the workflow manager could not be updated!
Is the installing order wrong? should I first install the update for the worklfow manager and then the update for SharePoint 2013?
Best regards
Matthias

The error message see below for "Cumulative Update for Workflow Manager 1.0 (KB2799754)
"One of the custom actions failed. The installation cannot continue. See log for details!"
[06/06/14 09:48:44] Performing install.
[06/06/14 09:48:44] At least one of the product packages has been detected.
[06/06/14 09:48:44] preReqUpdateDisplayName is :
[06/06/14 09:48:44]
[06/06/14 09:48:44] Wizard mode on.
The following products will be enhanced:
Workflow Manager 1.0
Attempting to open cached Msi package for product code: {04A7199E-565D-4654-88A3-80A9A7BADDD9}
Successfully opened cached Msi package.
[06/06/14 09:48:48] Opening Service Control Manager...
[06/06/14 09:48:48] Operation succeeded.
[06/06/14 09:48:48] Copying files...
[06/06/14 09:48:48] Checking and creating target directory C:\ProgramData\Microsoft\E-Business Servers Updates\Updates\Uninstall2799754.
[06/06/14 09:48:48] Package Workflow Manager Client 1.0 is not installed. Skipping it.
[06/06/14 09:48:48] Package Workflow Manager Client 1.0 is not installed. Skipping it.
[06/06/14 09:48:48] Package Workflow Manager 1.0 is installed.
[06/06/14 09:48:49] Copying file AppServerV1-WorkflowManagerpatch30.msp ...
[06/06/14 09:48:49] Operation succeeded.
[06/06/14 09:48:49] Copying file AppServerV1-WorkflowManagerpatch30.msp ...
[06/06/14 09:48:49] Operation succeeded.
[06/06/14 09:48:49] Copying file TargetWFVersion.txt ...
[06/06/14 09:48:49] Operation succeeded.
[06/06/14 09:48:49] Copying file UnifiedWFHotfixUpgrade.PS1 ...
[06/06/14 09:48:49] Operation succeeded.
[06/06/14 09:48:49] Copying file Setup.xml ...
[06/06/14 09:48:49] Operation succeeded.
[06/06/14 09:48:49] Copying file Setup.exe ...
[06/06/14 09:48:49] Operation succeeded.
[06/06/14 09:48:49] Package Workflow Manager 1.0 is installed.
[06/06/14 09:48:49] Package code is {04A7199E-565D-4654-88A3-80A9A7BADDD9}.
[06/06/14 09:48:49] Executing preinstall custom actions. 1 actions to execute.
[06/06/14 09:48:49] Starting process "C:\Windows\system32\..\sysnative\windowspowershell\v1.0\powershell.exe" -NoLogo -NonInteractive -NoProfile -WindowStyle Hidden -ExecutionPolicy RemoteSigned -File UnifiedWFHotfixUpgrade.PS1 -HotfixType "CS" -PackageType
"server" -opcode "PatchBefore" -platform "x64" ...
[06/06/14 09:48:50] Process exit code is -1.
get-itemproperty : Cannot find path 'HKLM:\Software\Microsoft\Service Bus\1.0'
because it does not exist.
At C:\ProgramData\Microsoft\E-Business Servers
Updates\Updates\Uninstall2799754\UnifiedWFHotfixUpgrade.PS1:971 char:21
+ $sbinstallpath = (get-itemproperty "HKLM:\Software\Microsoft\Service
Bus\1.0" ...
That's the log file
Best regards
Matthias

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

Error while trying to publish 2013 workflow via designer. Probably a workflow manager backend user account issue?

Hello, I am getting error while publishing the 2013 workflow via designer. Also, under sharepoint designer if I try to delete any workflow then the page just refreshes and the workflow does not get deleted.
I checked the services.msc and found that the workflow backend service was stopped. (this happened as the password of the user under which this serivce was running had changed).
So, the network admin changed the service user to LOCAL SYSTEM and started the service.
Now, the workflow backend service is started. We have run the iisreset also.
However, I am still getting the same error:-
System.IO.InvalidDataException: A response was returned that did not come from the Workflow Manager. Status code = 503:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Service Unavailable</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Service Unavailable</h2>
<hr><p>HTTP Error 503. The service is unavailable.</p>
</BODY></HTML>
Client ActivityId : ee94689c-4e08-b055-fe9c-268d7a94
Please find attached snapshot.
Is the error as a result of the change in service user? Can you tell me what priviledges should the account running the workflow backend service must have?
UPDATE 1:-
We have set the workflow service backend account user as farm admin and also tried to set it to site admin. The service is re-started. Now, for a new web application,
I can delete workflows. However, for existing site, I am not able to delete the existing workflows.. Also, I am not able to publish workflows (present under new and previous sites) and the error is same as described earlier.

Hi Nachiket,
According to your description, my understanding is that you got an error while publishing the 2013 workflow via SharePoint 2013 Designer.
As you have changed the password of this service. Please open IIS and make sure identify of the WorkflowMgmtPool is correct, you can re-type the identify. Then make this pool is started.
Open Services, find Service Bus Message Broker service and Windows Fabric Host Service. Make sure they are running. If not, firstly, start Windows Fabric Host Service, then start Service Bus Message Broker service. If Service Bus Message Broker service is
started, stop and re-start it.
Here are some similar posts for you to take a look at:
http://developers.de/blogs/damir_dobric/archive/2012/10/23/deploying-sharepoint-workflows.aspx
http://developers.de/blogs/damir_dobric/archive/2012/09/18/servicebus-message-broker-service-is-starting-and-starting.aspx
I hope this helps.
Thanks,
Wendy
Wendy Li
TechNet Community Support

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 2013 installation????

Similar Messages

Maybe you are looking for