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

Similar Messages

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

Workflow Manager & User Profile Service Application for Extranet Web application

Hi,
Recently i have setup HA WF Manager farm and associated it with Intranet web application (on-prem). Now i want to use the same farm for our extranet environment (on-prem) but extranet environment is not associated with UPA. Since user profile application
is not available for extranet environment so workflow does not work.
Now if I try to use existing UPA or create a new UPA for extranet environment, then i am exposing users data to all partner and collaborators. But for workflows to work it is necessary that users profile should be there in profile database.
Is there any way that I can run workflows in extranet environment without exposing user profile data to partners/collaborators? Thanks.
-Prashant

Thanks for the reply Paul, but this does not solve the problem.
Actually in MySite web application external users group is not at all added with any permissions but just to check your suggestion i have given permission to externals group with Deny Read permission. Now UPA is associated to the extranet web application
and when i access user profile data using RESP API using a partner account I can still see the data. For e.g. I am using this URL
https://extranet.abc.com/_api/SP.UserProfiles.PeopleManager/GetPropertiesFor(accountName=@v)?@v='abc\uname'
When I hit this URL in browser using partner account, it shows the profile data of the account passed in the URL.
MySite web application is https://mysite.abc.com and on this web application external users group is added under policy with Deny Read permissions. Thanks.
-Prashant

Configuring Workflow Manager for SharePoint 2013

I have gone through the configurations of Workflow and SharePoint to use the new Workflow Manager 1.0 several times now, and keep getting the below errors.
My environment is set up with 2 servers, 1 SP Web Applicatin and 1 SQL. Workflow is installed on the SQL server. These errors are from the SQL Server.
Event ID 22
Service Bus exception swallowed at location ServiceBusNamespaceListener.GetSessionAndStateWithRetryAsyncResult.HandleException. Microsoft.ServiceBus.Messaging.MessagingException: The token provider service was not avaliable when obtaining a token for 'https://srv22.domain.com:9355/WorkflowDefaultNamespace/$STS/Windows/'. ---> Microsoft.ServiceBus.TokenProviderException: The token provider service was not avaliable when obtaining a token for 'https://srv22.domain.com:9355/WorkflowDefaultNamespace/$STS/Windows/'. ---> System.Net.WebException: The remote server returned an error: (502) Bad Gateway.
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at Microsoft.ServiceBus.TokenProviderHelper.GetWindowsAccessTokenCore(IEnumerator`1 stsUris, Func`2 uriBuilder, String requestToken, TimeSpan timeout, DateTime& expiresIn)
--- End of inner exception stack trace ---
at Microsoft.ServiceBus.TokenProviderHelper.ThrowException(Uri requestUri, WebException exception)
at Microsoft.ServiceBus.TokenProviderHelper.GetWindowsAccessTokenCore(IEnumerator`1 stsUris, Func`2 uriBuilder, String requestToken, TimeSpan timeout, DateTime& expiresIn)
at Microsoft.ServiceBus.WindowsTokenProvider.OnBeginGetToken(String appliesTo, String action, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProvider.GetTokenAsyncResult..ctor(TokenProvider tokenProvider, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProvider.BeginGetToken(String appliesTo, String action, Boolean bypassCache, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingToken(ITokenProvider tokenProvider, Uri baseAddress, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
--- End of inner exception stack trace ---
Server stack trace:
at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingToken(ITokenProvider tokenProvider, Uri baseAddress, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.GetAuthorizationHeader(String action)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.CreateWcfMessageInternal(String action, Object body, Boolean includeToken)
at Microsoft.ServiceBus.Messaging.Sbmp.AcceptMessageSessionForNamespaceAsyncResult..ctor(SbmpMessagingFactory messagingFactory, ReceiveMode receiveMode, Int32 prefetchCount, CreateControlLinkSettings controlLinkSettings, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessagingFactory.OnBeginAcceptMessageSession(ReceiveMode receiveMode, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.Messaging.MessagingFactory.AcceptMessageSessionAsyncResult.<GetAsyncSteps>b__29(AcceptMessageSessionAsyncResult thisPtr, TimeSpan t, AsyncCallback c, Object s)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.EnumerateSteps(CurrentThreadType state)
Exception rethrown at [0]:
at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Dispatcher.ServiceBusNamespaceListener.GetSessionAndStateWithRetryAsyncResult.EndAsyncResult(IAsyncResult result)
at Microsoft.Workflow.Common.BackoffRetryAsyncResult.IsolateWithRetry(IAsyncResult result)
Event ID 370
The Workflow Manager cannot contact Service Bus service after retrying for '12' minutes. Please verify if the Service Bus service is up and running. The Workflow Manager failed at location 'ServiceBusNamespaceListener.GetSessionAndStateWithRetryAsyncResult.HandleException' due to exception: Microsoft.ServiceBus.Messaging.MessagingException: The token provider service was not avaliable when obtaining a token for 'https://srv22.domain.com:9355/WorkflowDefaultNamespace/$STS/Windows/'. ---> Microsoft.ServiceBus.TokenProviderException: The token provider service was not avaliable when obtaining a token for 'https://srv22.domain.com:9355/WorkflowDefaultNamespace/$STS/Windows/'. ---> System.Net.WebException: The remote server returned an error: (502) Bad Gateway.
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at Microsoft.ServiceBus.TokenProviderHelper.GetWindowsAccessTokenCore(IEnumerator`1 stsUris, Func`2 uriBuilder, String requestToken, TimeSpan timeout, DateTime& expiresIn)
--- End of inner exception stack trace ---
at Microsoft.ServiceBus.TokenProviderHelper.ThrowException(Uri requestUri, WebException exception)
at Microsoft.ServiceBus.TokenProviderHelper.GetWindowsAccessTokenCore(IEnumerator`1 stsUris, Func`2 uriBuilder, String requestToken, TimeSpan timeout, DateTime& expiresIn)
at Microsoft.ServiceBus.WindowsTokenProvider.OnBeginGetToken(String appliesTo, String action, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProvider.GetTokenAsyncResult..ctor(TokenProvider tokenProvider, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProvider.BeginGetToken(String appliesTo, String action, Boolean bypassCache, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingToken(ITokenProvider tokenProvider, Uri baseAddress, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
--- End of inner exception stack trace ---
Server stack trace:
at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingToken(ITokenProvider tokenProvider, Uri baseAddress, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.GetAuthorizationHeader(String action)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.CreateWcfMessageInternal(String action, Object body, Boolean includeToken)
at Microsoft.ServiceBus.Messaging.Sbmp.AcceptMessageSessionForNamespaceAsyncResult..ctor(SbmpMessagingFactory messagingFactory, ReceiveMode receiveMode, Int32 prefetchCount, CreateControlLinkSettings controlLinkSettings, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessagingFactory.OnBeginAcceptMessageSession(ReceiveMode receiveMode, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.Messaging.MessagingFactory.AcceptMessageSessionAsyncResult.<GetAsyncSteps>b__29(AcceptMessageSessionAsyncResult thisPtr, TimeSpan t, AsyncCallback c, Object s)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.EnumerateSteps(CurrentThreadType state)
Exception rethrown at [0]:
at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Dispatcher.ServiceBusNamespaceListener.GetSessionAndStateWithRetryAsyncResult.EndAsyncResult(IAsyncResult result)
at Microsoft.Workflow.Common.BackoffRetryAsyncResult.IsolateWithRetry(IAsyncResult result).
The error messages suggested to me that the issue was being caused by our proxy server. I have removed the proxy server from the equation by removing the proxy settings.
I then also tried to navigate to the url in the error messages. When i navigate to https://srv22.domain.com:9355/WorkflowDefaultNamespace/$STS/Windows/ i get a 400 Bad Request. When i change the address to https://srv22.domain.com:9355/WorkflowDefaultNamespace/$sts/Windows/
($sts in Lower Case rather than Upper Case) i get a response from the Workflow server.
I have searched high and low for a solution to this, and cannot find one, can anybody shed any light on the situation.
Thanks in advance
Paul

Hi Paul,
Here is a similar post with bad gateway error related to proxy and gateway settings, you can take a look.
http://social.technet.microsoft.com/Forums/sharepoint/en-US/73a909d2-226d-454e-a8ca-c5e62dc8caac/setup-windows-azure-workflow-addwfhost-error-wfmanagementwftopic-and-token-provider-service
Thanks
Daniel Yang
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

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

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.

Error with Oracle Workflow Manager

Hi
Oracle workflow has just been installed on my first middle tier from the Content management SDK 9.0.4 CD.
( I have also an old working installation on the second middle tier, pointing to an old database 9.2.0.2)
When I click on the Oracle Workflow Manager link in the oracle enterprise manager console
I get the message : An error has occurred! Use Browser's Back button to go to previous page."
versions
DB 9.2.0.7.0 on AIX 5.3
OAS infr 9.0.2.3 on linux AS-2.1 2.4.9-e.3smp
OAS mid tier A 9.0.4.1 on linux AS-2.1 2.4.9-e.25BOOT
OAS mid tier B 9.0.4.1 on linux AS-2.1 2.4.9-e.40smp
LOGS
em-web-access.log:
172.25.21.97 - - [07/Feb/2006:16:46:06 +0100] "GET /emd/console/oam/wfm/sysStatus$ctxName1=mid904.ausmid.auselda.it$farm=mid904.ausmid.auselda.it$type=oracle*workflow$ctxType1=oracle*ias$target=mid904.ausmid.auselda.it*Oracle20Workflow HTTP/1.1" 302 288
172.25.21.97 - - [07/Feb/2006:16:46:06 +0100] "GET /emd/console/oam/oamErrorPage$key=error1 HTTP/1.1" 200 6184
em.nohup:
06/02/07 16:46:06 java.lang.reflect.InvocationTargetException
06/02/07 16:46:06 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
06/02/07 16:46:06 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
06/02/07 16:46:06 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
06/02/07 16:46:06 at java.lang.reflect.Method.invoke(Method.java:324)
06/02/07 16:46:06 at oracle.apps.oam.workflow.handlers.WfOnLoadHandler.setDBConnection(WfOnLoadHandler.java:231)
06/02/07 16:46:06 at oracle.apps.oam.workflow.handlers.WfOnLoadHandler.doLoad(WfOnLoadHandler.java:119)
06/02/07 16:46:06 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
06/02/07 16:46:06 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
06/02/07 16:46:06 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
06/02/07 16:46:06 at java.lang.reflect.Method.invoke(Method.java:324)
06/02/07 16:46:06 at oracle.cabo.servlet.event.MethodEventHandler.handleEvent(Unknown Source)
06/02/07 16:46:06 at oracle.cabo.servlet.event.TableEventHandler.handleEvent(Unknown Source)
06/02/07 16:46:06 at oracle.cabo.servlet.event.TableEventHandler.handleEvent(Unknown Source)
06/02/07 16:46:06 at oracle.cabo.servlet.event.BasePageFlowEngine.handleRequest(Unknown Source)
06/02/07 16:46:06 at oracle.cabo.servlet.AbstractPageBroker.handleRequest(Unknown Source)
06/02/07 16:46:06 at oracle.cabo.servlet.ui.BaseUIPageBroker.handleRequest(Unknown Source)
06/02/07 16:46:06 at oracle.cabo.servlet.PageBrokerHandler.handleRequest(Unknown Source)
06/02/07 16:46:06 at oracle.cabo.servlet.UIXServlet.doGet(Unknown Source)
06/02/07 16:46:06 at oracle.sysman.emSDK.svlt.EMServlet.doGet(EMServlet.java:313)
06/02/07 16:46:06 at oracle.sysman.eml.app.Console.doGet(Console.java:152)
06/02/07 16:46:06 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
06/02/07 16:46:06 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
06/02/07 16:46:06 at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:778)
06/02/07 16:46:06 at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:317)
06/02/07 16:46:06 at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:793)
06/02/07 16:46:06 at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:270)
06/02/07 16:46:06 at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
06/02/07 16:46:06 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
06/02/07 16:46:06 at java.lang.Thread.run(Thread.java:534)
06/02/07 16:46:06 Caused by: java.lang.NullPointerException
06/02/07 16:46:06 at oracle.apps.oam.workflow.stdalone.ias.WfIASIntgUtil.setDBConnection(WfIASIntgUtil.java:293)
06/02/07 16:46:06 ... 29 more
06/02/07 16:46:06 null
06/02/07 16:46:06 java.lang.Exception
06/02/07 16:46:06 at oracle.apps.oam.workflow.handlers.WfOnLoadHandler.setDBConnection(WfOnLoadHandler.java:239)
06/02/07 16:46:06 at oracle.apps.oam.workflow.handlers.WfOnLoadHandler.doLoad(WfOnLoadHandler.java:119)
06/02/07 16:46:06 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
06/02/07 16:46:06 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
06/02/07 16:46:06 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
06/02/07 16:46:06 at java.lang.reflect.Method.invoke(Method.java:324)
06/02/07 16:46:06 at oracle.cabo.servlet.event.MethodEventHandler.handleEvent(Unknown Source)
06/02/07 16:46:06 at oracle.cabo.servlet.event.TableEventHandler.handleEvent(Unknown Source)
06/02/07 16:46:06 at oracle.cabo.servlet.event.TableEventHandler.handleEvent(Unknown Source)
06/02/07 16:46:06 at oracle.cabo.servlet.event.BasePageFlowEngine.handleRequest(Unknown Source)
06/02/07 16:46:06 at oracle.cabo.servlet.AbstractPageBroker.handleRequest(Unknown Source)
06/02/07 16:46:06 at oracle.cabo.servlet.ui.BaseUIPageBroker.handleRequest(Unknown Source)
06/02/07 16:46:06 at oracle.cabo.servlet.PageBrokerHandler.handleRequest(Unknown Source)
06/02/07 16:46:06 at oracle.cabo.servlet.UIXServlet.doGet(Unknown Source)
06/02/07 16:46:06 at oracle.sysman.emSDK.svlt.EMServlet.doGet(EMServlet.java:313)
06/02/07 16:46:06 at oracle.sysman.eml.app.Console.doGet(Console.java:152)
06/02/07 16:46:06 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
06/02/07 16:46:06 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
06/02/07 16:46:06 at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:778)
06/02/07 16:46:06 at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:317)
06/02/07 16:46:06 at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:793)
06/02/07 16:46:06 at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:270)
06/02/07 16:46:06 at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
06/02/07 16:46:06 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
06/02/07 16:46:06 at java.lang.Thread.run(Thread.java:534)
06/02/07 16:46:06 null
webwfm.log:
[16:46:6:941, 2/7/06] getDBConnection: :DBConnection object not found in session, unable to get Connection
[16:46:6:945, 2/7/06] java.lang.Exception
at oracle.apps.oam.workflow.handlers.WfOnLoadHandler.setDBConnection(WfOnLoadHandler.java:239)
at oracle.apps.oam.workflow.handlers.WfOnLoadHandler.doLoad(WfOnLoadHandler.java:119)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at oracle.cabo.servlet.event.MethodEventHandler.handleEvent(Unknown Source)
at oracle.cabo.servlet.event.TableEventHandler.handleEvent(Unknown Source)
at oracle.cabo.servlet.event.TableEventHandler.handleEvent(Unknown Source)
at oracle.cabo.servlet.event.BasePageFlowEngine.handleRequest(Unknown Source)
at oracle.cabo.servlet.AbstractPageBroker.handleRequest(Unknown Source)
at oracle.cabo.servlet.ui.BaseUIPageBroker.handleRequest(Unknown Source)
at oracle.cabo.servlet.PageBrokerHandler.handleRequest(Unknown Source)
at oracle.cabo.servlet.UIXServlet.doGet(Unknown Source)
at oracle.sysman.emSDK.svlt.EMServlet.doGet(EMServlet.java:313)
at oracle.sysman.eml.app.Console.doGet(Console.java:152)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:778)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:317)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:793)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:270)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:534)

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 Configuration Issue Windows Server 2012 R2 / SQL 2014

Hello All,
Environment: SharePoint 2013 Enterprise with SP1
Farm consists of
2 App Server, 2 Web Server and 2 SQL Servers all the server have Windows 2012 R2
OS . The SQL backend is SQL Server 2014
Installed Workflow manager on the Web server, the configuration ran fine without any errors. Trying to browse the workflow management site via IIS Manager encountered Certificate Error clicked Continue to this website which gives a HTTP 403 Forbidden and
following detail message
This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage.
Checked the web site Workflow Management Site in the IIS manager which has only one folder bin . I was not able to submit the Screenshot
I have installed the latest patch for the Workflow manager and the Service Bus
Question I have
Should there be more folder under the Workflow Management Site.
Why is the Web site not showing the web page
Is workflow manager supported for Windows Server 2012 R2 and SQL 2014
Thanks
Dhanraj

Hi Dhanraj,
I captured the screenshot from my IIS Manager on workflow server. There is only bin folder under Workflow Management site
If I browser workflow host uri from IIS Manager
https://localhost:12290, I received certification error, and I chose the continue to this website, it returned me as follow:
From the link: http://support.microsoft.com/kb/2902007/en-us It is supported on Windows Server 2012 r2 if you have install latest update.
Here is an article which talks about error:
http://www.sp2013blog.com/Lists/Posts/Post.aspx?ID=36
In addition, here is the reference for troubleshooting workflow manager 1.0 management:
http://msdn.microsoft.com/en-us/library/jj193529(v=azure.10).aspx#AnalyzingWorkflowManagementLogs
You could also open SharePoint Designer 2013 and see if you could create a workflow on platform 2013.
Regards,
Rebecca Tu
TechNet Community Support

AppFabric and Service Bus

Can someone please tell me what Microsoft AppFabric 1.1 for Windows Server - is doing for SharePoint
and what about the Service Bus?
Reason for asking...got a WF issue...and I was advised to update the service bus...but that wouldn't update because the AppFabric was installed....

Windows Server AppFabric is installed as a prerequisite for SharePoint 2013. AppFabric is installed as an extension to the Windows Server Application Server Role and consist of two main components:
Distributed caching
Service and workflow management
An enterprise service bus (ESB)
is a software architecture model used for designing and implementing communication between mutually interacting software applications in a service-oriented
architecture (SOA).
Read these articles:
http://blogs.msdn.com/b/besidethepoint/archive/2013/03/27/appfabric-caching-and-sharepoint-1.aspx
SharePoint 2013: AppFabric and Distributed Cache Service
Hello Service Bus 1.0, Workflow 1.0 and SharePoint Workflow Host
MS Service Bus
[custom.development]

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.

What is SAP ESB (Enterprise Service Bus)?

Hi fellow sdners gurus I have been reading threads about SAP SOA and ESB.
I do not want to start a debate on wether XI is an ESB, but more of a statement to what is SAP ESB (if XI it is, then be it).
1) What is SAP ESB (Enterprise Service Bus) today (I could not find a clear answer to is)?
2) Who uses this SAP ESB in production currently and what kind of environment (i.e. strictly SAP backend systems, or combination of various vendors backend systems)?
Can someone share some light on this topic?
As a reminder, an ESB is expected to exhibit the following characteristics (source Wikipedia):
     It is usually operating-system and programming-language agnostic; for example, it should enable interoperability between Java and .NET applications.
     It uses XML (eXtensible Markup Language) as the standard communication language.
     It supports web-services standards.
     It supports various MEPs (Message Exchange Patterns) (e.g., synchronous request/response, asynchronous request/response, send-and-forget, publish/subscribe).
     It includes adapters for supporting integration with legacy systems, possibly based on standards such as JCA
     It includes a standardized security model to authorize, authenticate and audit use of the ESB.
     To facilitate the transformation of data formats and values, it includes transformation services (often via XSLT or XQuery) between the format of the sending application and the receiving application.
     It includes validation against schemas for sending and receiving messages.
     It can uniformly apply business rules, enriching messages from other sources, the splitting and combining of multiple messages and the handling of exceptions.
     It can provide a unified abstraction across multiple layers
     It can route or transform messages conditionally, based on a non-centralized policy (i.e. no central rules-engine needs to be present).
     It is monitored for various SLA (Service Level Agreement) threshold message latencies and other SLA characteristics.
     It (often) facilitates "service classes," responding appropriately to higher and lower priority users.
     It supports queuing, holding messages if applications are temporarily unavailable.
Your help is greatly appreciated.
Kind Regards,
Jean-Michel

PI or XI is the ESB from SAP side. PI is not a full pledged ESB on a reference model of ESB idea but it is the the framework SAP provide as a ESB product.
A Standard Based ESB Reference Model should fullfil the following features in a framework.
ESB Features    Service Enablement Phase (1, 2, 3)
1)     Message brokering between heterogeneous environments
2)     Supports asynchronous, synchronous, publish and subscribe messaging
3)     Supports synchronous and asynchronous bridging
4)     Supports message formats of SOAP
5)     Support for message format of SOAP with attachments
6)     Support for xml message
7)     Support for structured non-XML data
8)     Support for raw data message
9)     Support for text data message
10)     Sport for e-mail with attachment message
11)     Heterogeneous transports between service end points
12)     Supports for FILE protocols
13)     Supports for FTP protocols
14)     Supports for HTTP protocols
15)     Supports for HTTPS protocols
16)     Supports for Multiple JMS providers
17)     Supports for RMI protocols
18)     Supports for web service protocols
19)     Supports for CORBA protocols
20)     Supports for DCOM protocols
21)     Supports for E-mail (POP, SMTP, IMAP) protocols
22)     Support for advanced transformation engine
23)     Support for configuration-driven routing
24)     Message routing based policies
25)     Support for call-outs to external services to support complex routing
26)     Support for point-to-point routing
27)     Support for one-to-many routing scenarios
28)     Support for request response model
29)     Support for publish-subscribe models
30)     Service monitoring
31)     Service logging
32)     Service auditing with search capabilities.
33)     Support for capture of key statistics for message and transport attributes including message invocations, errors, and performance, volume, and SLA violations.
34)     Supports clusters and gathers statistics across the cluster to review SLA violations
35)     Support for service provisioning
36)     Support deployment of new versions of services dynamically through configuration
37)     Migrates configured services and resources between design, staging and production
38)     Supports multiple versions of message resources that are incrementally deployed with selective service access through flexible routing
39)     Configurable policy-driven security
40)     Supports the latest security standards for authentication, encryption-decryption, and digital signatures
41)     Supports SSL for HTTP and JMS transports
42)     Supports multiple authentication models
43)     Policy-driven SLA enforcement
44)     Establishes SLAs on a variety of attributes including
a.     Throughput times
b.     Processing volumes
c.     Success/failure ratios of message processes
d.     Number of errors
e.     Security violations
f.     Schema validation issues
45)     Initiates automated alerts or enables operator-initiated responses to rule violations using flexible mechanisms including
a.     E-mail notifications
b.     Triggered JMS messages
c.     Triggered integration processes with a JMS message
d.     Web services invocations with a JMS message
e.     Administration console alerts.
46)     Support for having multiple LOBs manage their own service bus based on their policies, and a service bus at an enterprise level that could act as a broker for sharing services across the various business units.
47)     Support for agent plug-in to support following features
48)     External providers service access for security
49)     External providers service management
50)     External providers transaction container
a.     External providers business orchestration (BPEL Engine) and business work flow service container
51)     Transaction support on message level
52)     IDE Integration
53)     Open standards

Workflow Manager 1.0 Refresh with Service Bus 1.1 Error

Hi I have installed and configured Workflow Manager 1.0 Refresh with Service Bus 1.1.
I didn't face any errors while installing or configuring the SB 1.1 and WFM 1.0.
I used the Workflow Configuration Wizard to configure the SB 1.1 and WFM 1.0 instances.
I have some workflows where I have custom code activities that put messages into the topic or pull messages from the topic.
I'm able publish these WFs to the scope as well.
However, when I try to execute these workflows, it throws up the following error:
Could not load file or assembly 'Microsoft.ServiceBus, Version=2.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT:
0x80131040)
I checked the ServiceBus dll version that is present in the WF Artificats and WFWebroot/Bin folders and find that the versions of this dll in both the folders is: 2.0.40131.0 (the version of the dll in the Service Bus folder is 2.1.30904.0).
How do I get the WFM to load the latest SB 1.1 dll?

What is the account used to install Workflow in Staging and Dev environment
I assume that Workflow in Staging might be installed with different account that can cause issue
Also check ULS log and Event log on Workflow manager server and sharepoint server when workflow does not execute
I assume it is working on DEV so I dont trust DEV environment. Try the same setup on a different machine(Preferred new).
Also check server level permission for the account like if working and non working account can access system drive.
If this helped you resolve your issue, please mark it Answered

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

Workflow manager Service Bus 407 error

After installing and configuring Workflow Manager on SharePoint 2013 farm I am able to create workflows in SP Designer in 2013 and publish them on the server with no errors. New workflows do show up in the application, but will not run. I found
the indication in ULS that something went wrong
Workflow revision number mismatch! Current workflow store revision is 13 and workflow host scope has revision 0
Operational event viewer logs on the Workflow Manager Host showing up these events:
Log Name: Microsoft-Workflow/Operational
Source: Microsoft-Workflow
Date: 5/2/2014 2:00:31 PM
Event ID: 22
Task Category: (65512)
Level: Warning
Keywords: Dispatcher,Management
User: domain\user
Computer: FQDN
Description:
Service Bus exception swallowed at location ServiceBusNamespaceListener.GetSessionAndStateWithRetryAsyncResult.HandleException. System.UnauthorizedAccessException: The token provider was unable to provide a security token while accessing 'https://fqdn:9355/WorkflowDefaultNamespace/$STS/Windows/'. Token provider returned message: ''. ---> System.IdentityModel.Tokens.SecurityTokenException: The token provider was unable to provide a security token while accessing 'https://FQDN:9355/WorkflowDefaultNamespace/$STS/Windows/'. Token provider returned message: ''. ---> System.Net.WebException: The remote server returned an error: (407) Proxy Authentication Required.
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at Microsoft.ServiceBus.TokenProviderHelper.GetWindowsAccessTokenCore(IEnumerator`1 stsUris, Func`2 uriBuilder, String requestToken, TimeSpan timeout, DateTime& expiresIn)
--- End of inner exception stack trace ---
at Microsoft.ServiceBus.TokenProviderHelper.ThrowException(Uri requestUri, WebException exception)
at Microsoft.ServiceBus.TokenProviderHelper.GetWindowsAccessTokenCore(IEnumerator`1 stsUris, Func`2 uriBuilder, String requestToken, TimeSpan timeout, DateTime& expiresIn)
at Microsoft.ServiceBus.WindowsTokenProvider.OnBeginGetToken(String appliesTo, String action, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProvider.GetTokenAsyncResult..ctor(TokenProvider tokenProvider, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProvider.BeginGetToken(String appliesTo, String action, Boolean bypassCache, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingToken(ITokenProvider tokenProvider, Uri baseAddress, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
--- End of inner exception stack trace ---
Server stack trace:
at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingToken(ITokenProvider tokenProvider, Uri baseAddress, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.GetAuthorizationHeader(String action)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.CreateWcfMessageInternal(String action, Object body, Boolean includeToken)
at Microsoft.ServiceBus.Messaging.Sbmp.AcceptMessageSessionForNamespaceAsyncResult..ctor(SbmpMessagingFactory messagingFactory, ReceiveMode receiveMode, Int32 prefetchCount, CreateControlLinkSettings controlLinkSettings, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessagingFactory.OnBeginAcceptMessageSession(ReceiveMode receiveMode, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.Messaging.MessagingFactory.AcceptMessageSessionAsyncResult.<GetAsyncSteps>b__29(AcceptMessageSessionAsyncResult thisPtr, TimeSpan t, AsyncCallback c, Object s)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.EnumerateSteps(CurrentThreadType state)
Exception rethrown at [0]:
at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Dispatcher.ServiceBusNamespaceListener.GetSessionAndStateWithRetryAsyncResult.EndAsyncResult(IAsyncResult result)
at Microsoft.Workflow.Common.BackoffRetryAsyncResult.IsolateWithRetry(IAsyncResult result)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Workflow" Guid="{B2885F6E-231C-43FF-BBEA-7516148FF6FE}" />
<EventID>22</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>65512</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000210</Keywords>
<TimeCreated SystemTime="2014-05-02T18:00:31.600519200Z" />
<EventRecordID>323735</EventRecordID>
<Correlation ActivityID="{C756E6D1-A7DC-4DA5-BA9D-D38DFD199CBC}" />
<Execution ProcessID="4084" ThreadID="4112" />
<Channel>Microsoft-Workflow/Operational</Channel>
<Computer>FQDN</Computer>
<Security UserID="S-1-5-21-436374069-1326574676-725345543-5309" />
</System>
<EventData>
<Data Name="location">ServiceBusNamespaceListener.GetSessionAndStateWithRetryAsyncResult.HandleException</Data>
<Data Name="exception">System.UnauthorizedAccessException: The token provider was unable to provide a security token while accessing 'https://********************:9355/WorkflowDefaultNamespace/$STS/Windows/'. Token provider returned message: ''. ---> System.IdentityModel.Tokens.SecurityTokenException: The token provider was unable to provide a security token while accessing 'https://****************:9355/WorkflowDefaultNamespace/$STS/Windows/'. Token provider returned message: ''. ---> System.Net.WebException: The remote server returned an error: (407) Proxy Authentication Required.
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at Microsoft.ServiceBus.TokenProviderHelper.GetWindowsAccessTokenCore(IEnumerator`1 stsUris, Func`2 uriBuilder, String requestToken, TimeSpan timeout, DateTime& expiresIn)
--- End of inner exception stack trace ---
at Microsoft.ServiceBus.TokenProviderHelper.ThrowException(Uri requestUri, WebException exception)
at Microsoft.ServiceBus.TokenProviderHelper.GetWindowsAccessTokenCore(IEnumerator`1 stsUris, Func`2 uriBuilder, String requestToken, TimeSpan timeout, DateTime& expiresIn)
at Microsoft.ServiceBus.WindowsTokenProvider.OnBeginGetToken(String appliesTo, String action, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProvider.GetTokenAsyncResult..ctor(TokenProvider tokenProvider, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProvider.BeginGetToken(String appliesTo, String action, Boolean bypassCache, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingToken(ITokenProvider tokenProvider, Uri baseAddress, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
--- End of inner exception stack trace ---
Server stack trace:
at Microsoft.ServiceBus.TokenProviderUtility.GetMessagingToken(ITokenProvider tokenProvider, Uri baseAddress, String appliesTo, String action, Boolean bypassCache, TimeSpan timeout)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.GetAuthorizationHeader(String action)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageCreator.CreateWcfMessageInternal(String action, Object body, Boolean includeToken)
at Microsoft.ServiceBus.Messaging.Sbmp.AcceptMessageSessionForNamespaceAsyncResult..ctor(SbmpMessagingFactory messagingFactory, ReceiveMode receiveMode, Int32 prefetchCount, CreateControlLinkSettings controlLinkSettings, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessagingFactory.OnBeginAcceptMessageSession(ReceiveMode receiveMode, TimeSpan timeout, AsyncCallback callback, Object state)
at Microsoft.ServiceBus.Messaging.MessagingFactory.AcceptMessageSessionAsyncResult.<GetAsyncSteps>b__29(AcceptMessageSessionAsyncResult thisPtr, TimeSpan t, AsyncCallback c, Object s)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.EnumerateSteps(CurrentThreadType state)
Exception rethrown at [0]:
at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Dispatcher.ServiceBusNamespaceListener.GetSessionAndStateWithRetryAsyncResult.EndAsyncResult(IAsyncResult result)
at Microsoft.Workflow.Common.BackoffRetryAsyncResult.IsolateWithRetry(IAsyncResult result)</Data>
</EventData>
</Event>
no proxy is configured on the system and gateway address is accurate.

are you accessing the site from your local machine or on the server? also could you please tell us if your sharepoint server and Client
are on same domain. Looks Like Token services having the issue.
As i saw you are using the SSL, check the below post may help.
http://social.technet.microsoft.com/wiki/contents/articles/13708.installing-workflow-manager-failed-with-could-not-establish-trust-relationship-for-the-ssltls-secure-channel.aspx
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

Workflow Manager 1.0 - Service Bus 1.0 installation failure

Similar Messages

Maybe you are looking for