I have installed Workflow Manager 1.0 in a dedicated domain machine
(I did it in too many different ways getting the same result for my desperation. I tried both MSDN way and harbar.net way. Actually tried some variations there as well esp. involving certificate options suspecting security/authorization issues)

Any hints, help welcome as it already took too long to have SP2013 workflows running :-(

Problem: Despite it is possible to 
* Get the XML from the REST API using IE/Chrome
* Create child scopes (using powershell scripts)
* See that # child scopes > 0 after having created child scopes in REST API XML for root API site from a browser or using workflow manager powershell scripts for enumerating childs 
* Get the XML from the REST API using IE/Chrome for child scopes and see that they are there with properly configured admin groups
it is NOT possible to:
* Fetch info about any child other than root ("/")
* Workflow explorer cannot open up child scopes for property view (it shows #child scopes > 1)
* Sharepoint pairing fails returning 404.

Trying to fix SP pairing, i manually created a child scope (SharePoint) and tried to pair it with SP2013. It did not matter.

I have the following diagnostic (analytic/debug) events from the Workflow Manager Machine:

//Event logs form Workflow Manager 1.0
Re-routing request 'https://XXX:12290/SharePoint/' to 'https://XXX:12290/$Scope'
Scope '/SharePoint' security settings are retrieved from cache.
Scope '/SharePoint' security settings are retrieved from cache.
Windows Identity Present. Name = XXX\sp_farm
The HTTP request was authenticated using the 'Negotiate' credential type and was granted the following permissions: All.
The HTTP request was authorized to perform the specified operation.
Gateway sending HTTP response: StatusCode: 200, ReasonPhrase: 'OK', Version: 1.1, Content: System.Net.Http.ObjectContent`1[[Microsoft.Workflow.Management.ScopeInfo, Microsoft.Workflow.Management, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]], Headers:
{
  Server: Microsoft-WF/1.0.1
  Content-Type: application/xml; charset=utf-8
}

// Things go crazy starting wit this line:
Gateway received request details: Method: GET, RequestUri: 'https://XXX:12290/$System/$Metadata/json/1', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
{
  Host: altemis-svr02.altemis.com.tr:12290
}

//Request is re-routed:
Re-routing request 'https://XXX:12290/$System/$Metadata/json/1' to 'https://XXX:12290/$Scope'

//First message that does not sound good
Scope '/$System/$Metadata/json/1' is not in scope map.

//Comes the exact same messag again
Scope '/$System/$Metadata/json/1' is not in scope map.

//And...
Gateway sending HTTP response: StatusCode: 404, ReasonPhrase: 'Not Found', Version: 1.1, Content: System.Net.Http.ObjectContent`1[[Microsoft.Workflow.Gateway.WorkflowManagementError, Microsoft.Workflow.Gateway, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]], Headers:
{
  E2EActivity: ygPqDXf5HEysw9rCtgh3vQ==
  Scope: /$System/$Metadata/json/1
  NodeId: ALTEMIS-SVR02
  Server: Microsoft-WF/1.0.1
  Content-Type: application/xml; charset=utf-8
}

Muharrem

Hi,

We have a single server Sharepoint 2013 farm (with August 2013 CU) on which we also installedWorkflow Manager 1.0 with CU1. When Workflow Manager Powershellis started as administrator an error below is shown:

We configured the site collection to use that workflow farm.

However when we try to publish a 2013 workflow from SPD 2013 error below prevents to use the workflow on the web:

System.InvalidOperationException: Operation failed with error Microsoft.Workflow.Client.ScopeNotFoundException: Scope '/SharePoint/default' was not found.  HTTP headers received from the server - ActivityId: f737b1ca-07b7-459d-9d8e-093ef9ba9901. NodeId: SRV-BITEST. Scope: /SharePoint/default/7f219fd0-dad3-4fe0-9f01-eed23ef5340e. Client ActivityId : c420479c-ec5c-d03d-32d5-472e64a6c2e0. ---> System.Net.WebException: The remote server returned an error: (404) Not Found.

   at Microsoft.Workflow.C

Have you ever faced the same problems before?

Kind regards

Serkan

Hi!

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

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

Can any one Help me !!!

To solve error !

Hi,

I've downloaded and installed Workflow Manager 1.0 Cumulative Update and Service Bus 1.0 Cumulative Update. But after installing the updates, I can't access the Library workflow settings page. I'm getting unexpected error. Then after investigating the workflow manager log in event viewer, I've found the following error messages:

The asynchronous operation has completed with an exception. Exception message is: System.Data.SqlClient.SqlException (0x80131904): The EXECUTE permission was denied on the object 'InsertTrackingAndStatus', database 'DEV_WFInstanceManagementDB', schema 'dbo'.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.CompleteAsyncExecuteReader()
   at System.Data.SqlClient.SqlCommand.EndExecuteNonQueryInternal(IAsyncResult asyncResult)
   at System.Data.SqlClient.SqlCommand.EndExecuteNonQuery(IAsyncResult asyncResult)
   at Microsoft.Workflow.Management.ExecuteNonQueryAsyncResult.OnEndExecuteSql(IAsyncResult result)
   at Microsoft.Workflow.Management.ExecuteSqlAsyncResult.EndAsyncResult(IAsyncResult result)
   at Microsoft.Workflow.Common.BackoffRetryAsyncResult.IsolateWithRetry(IAsyncResult result)
   at Microsoft.Workflow.Common.AsyncResult.AsyncCompletionWrapperCallback(IAsyncResult result)
ClientConnectionId:2f93882a-8d4c-440d-a3ff-0bd9d1682ad2.

The issue I've found in my Dev environment with Windows Server 2008 R2 SP 1. This is standalone SharePoint farm with DC, SQL Server and SharePoint all installed in the same server. One workaround I have found that if I add the WF user as dbo to the database as well as  'WFServiceOperators' then the error disappear.

Thanks,
Sohel Rana
http://ranaictiu-technicalblog.blogspot.com

As per "Workflow Manager Cumulative Update (February) error" @ http://social.msdn.microsoft.com/Forums/windowsazure/en-US/054d2a58-8847-4a6a-b1ab-05a79f49fe65/workflow-manager-cumulative-update-february-error?forum=wflmgr, there appears to be issues in the Feb CU which results in errors accessing the DB after the CU is applied:

Failed SQL command after 1 tries with error '229'. Exception: System.Data.SqlClient.SqlException (0x80131904): The EXECUTE permission was denied on the object'GetInProgressScopeSnapshots', database 'WFResourceManagementDB', schema 'dbo'

Does anyone know if there has been a patch orsupported workaround published for this?

Re-posting from referenced thread which no longer seems to be monitored:

Hi Chris,

We are also experiencing the issue Mysonemo has detailed above, after applying the Feb CU and then executing workaround script that you posted above against the "Instance Management DB" database. We are now having the following errors logged:

Failed SQL command after 1 tries with error '229'. Exception: System.Data.SqlClient.SqlException (0x80131904): The EXECUTE permission was denied on the object'GetInProgressScopeSnapshots', database 'WFResourceManagementDB', schema 'dbo'.

You stated above that "You need to run the same script on the Management DB as well.".  However, the WFManagementDB doesn’t have a Role called "WFServiceOperators" but instead has a role called "Store.Operators".

- Is there a patch to the Feb CU available to correct the issues in a supported manner?
- If there is not a patch, which method would you prefer us use to resolve this:
a) grant dbo rights
b) grant the role “Store.Operators” rights to the stored proc
c) Other?

Thanks very much

Hi,

I have created very simple ASP New item form which looks as follow:

    <asp:Content ID="Main" ContentPlaceHolderID="PlaceHolderMain" runat="server">
        <SharePoint:FormField runat="server" FieldName="Name" ControlMode="New"/>
        <SharePoint:FormField runat="server" FieldName="Title" ControlMode="New"/>
        <SharePoint:SaveButton runat="server" ControlMode="New"/>
        <SharePoint:GoBackButton runat="server" ControlMode="New"/>
    </asp:Content>

Set it as a New form for Document Set content type using SPD.
Also I created a new Document Library, where Document Set is one of the content types.
Now, when I add new Document Set in this library, I can see my simple form.



After pressing the Save button, I can see new item 123 as expected. 

After that I select it and try to run workflow (2013 SPD WF) on it, but it doesn't start and shows me the following error: "Something went wrong. To try again, reload the page and then start the workflow"



And I can see the following error in the ULS logs:

Failed to look up list item with Id 26 on list with Id 916aff44-93ff-4c93-aeca-b227e249a33a for call to StartWorkflowOnListItem() : System.ArgumentException: Value does not fall within the expected range.     at Microsoft.SharePoint.WorkflowServices.FabricWorkflowInstanceProvider.StartWorkflowOnListItem(WorkflowSubscription subscription, Int32 itemId, IDictionary`2 payload).

I can see that item with id=26 exists. At least I could see it using the following link:

http://mysite/mylist/Forms/Document%20Set/docsethomepage.aspx?ID=26&FolderCTID=0x0120D520005107FFFB3FE12644B0E708E265E4BA8D&List=916aff44-93ff-4c93-aeca-b227e249a33a&RootFolder=%2Frechenzentren%2FServers%2F123&RecSrc=%2Frechenzentren%2FServers%2F123

However, if I create new item using standard form, the same workflow starts well. Workflow is very simple and consists of the only log activity.

What I have tried:

1. Tried to use the same custom form to create item derived from Item in a list. In such a case workflow starts without any issues. So probably, the issue related only to Document Libraries or Document Set.
2. Tried to start 2010 SPD WF on this item. It works well. So, probably this issue is related only to new 2013 WF Manager's WF.
3. Compare all fields of the both items (created by standard and custom forms). The only difference, which I could see is that in the working item, MetaInfo field contains additional value "docset_SkipProvision:SW|True". I tried to add it to the incorrect item, but with no results.

My ideas why it happens:

1. I should do some additional work in my custom form when it comes to Document Set (SharePoint:SaveButton is not enough).
2. It is a bug in platform and standard form do something behind the scenes to overcome it (but what?)


Does anybody have some ideas, why it happens and what could I try for troubleshooting?
Every suggestions are very appreciated.

Kind regards, Michael

Hi everybody I would like to know if there is a way (possibly with powershell) to modify an existing scope. I'm using WFMAN outside of SharePoint and i publish a scope with a DefaultWorkflowConfiguration. Now I need to add one new configuration setting and the only way I found is to delete it and create again with the new key/value...but I think this is not the best way....

Thanks!

Hi everybody, I've read hear http://msdn.microsoft.com/en-us/library/windowsazure/microsoft.activities(v=azure.10).aspx about CreateMessageFromDynamicValue and others activities that I need in a project that I'm implementing on Workflow Manager 1.0, but the problem is that outside the documentation I cannot find those activities...

Again about microsoft.activities.dll (that i found in C:\Program Files\Reference Assemblies\Microsoft\Workflow Manager\1.0\Microsoft.Activities.dll): I try to add the "dynamic activities" toolbox in Visual Studio 2013 on a 4.5 project (the same as the one opened with visual studio 2012) but i receive an incompatibility error...knwo something about this?

Thanks!

We have an issue with user logins and their use in Workflow Manager workflows, these workflows have been created in SharePoint designer.

Background:

* Environment

SharePoint 2013 with WFM 1.0 Feb Update, SharePoint Mar and Apr updates.

* Create two users in AD with the following details

First Name: Jack

Surname: Smi

Login: jsmi@domain

First Name: John

Surname: Smith

Login: jsmith@domain

* Create a Custom List and add a People column.

* Create a list 2013 workflow in SharePoint designer.

* First Action: Set your new people column to = item created by user, using Login value

* Second Action: Write a history record displaying the Display Name of your People column value.

Result:

* Create a list item and start workflow as jsmi@domain (Jack Smi)

* People column displays John Smith (Should be Jack Smi)

* Name displayed in history is John Smith (Should be Jack Smi)

Observation:

* We can reproduce this in at least two separate SharePoint 2013 environments.

* We can make sure the right user is assigned by "Set" action in workflow by using the User ID when copying from the source.

* We can not display the correct users name in any history or emails as choosing to show the Display Name of a people variable forjsmi@domain always show the display name for jsmith@domain.

Help:

* Anyone else come across this issue?

* Know of any work arounds?

Thanks.

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

2 web front end , 2 app. workflow manager installed in APP1 server and workflow client install in 2 web front end and app2 server. Workflow manager 1.0 CU also installed in APP1 server. Configure everything fine. Register SharePoint to use this workflow over AllowOAuthHttp. Create a simple workflow to log history. When i started, it automatic become suspended. User profile was not working and i fixed it but it still suspend right after it started. Error is below. Anyone know what to do to fix this?

RequestorId: 1b185096-ee8a-b2b0-0000-000000000000. Details: RequestorId: 1b185096-ee8a-b2b0-0000-000000000000. Details: An unhandled exception occurred during the execution of the workflow instance. Exception details: System.ApplicationException: HTTP 401 {"x-ms-diagnostics":["3001000;reason=\"There has been an error authenticating the request.\";category=\"invalid_client\""],"SPRequestGuid":["1b185096-ee8a-b2b0-a88a-93955c3ba74c"],"request-id":["1b185096-ee8a-b2b0-a88a-93955c3ba74c"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"SPRequestDuration":["42"],"SPIisLatency":["0"],"Server":["Microsoft-IIS\/7.5"],"WWW-Authenticate":["Bearer realm=\"032b4f11-d27d-4d88-9a2b-d72e5aee798b\",client_id=\"00000003-0000-0ff1-ce00-000000000000\",trusted_issuers=\"00000005-0000-0000-c000-000000000000@*,00000003-0000-0ff1-ce00-000000000000@032b4f11-d27d-4d88-9a2b-d72e5aee798b\"","NTLM"],"X-Powered-By":["ASP.NET"],"MicrosoftSharePointTeamServices":["15.0.0.4420"],"X-Content-Type-Options":["nosniff"],"X-MS-InvokeApp":["1; 

I am in the process of testing WM 1.0 with SharePoint 2013 RTM.  We have dev/staging/production SP farms in our domain.  I'd like to setup different workflow farms to support each of those environment.  I'm starting to see a problem (cannot register SP site to the 2nd farm) when trying to setup the 2nd WM farm.  Before trying to debug, I want to make sure this topology is supported.  I can't find any definite answer in the online docs.

Does anyone know if running 2 Workflow Manaer farms (not clustered) is supported?

Thanks,

Hi,

yesterday we have a problem with our test environment with WFM and SB.

We found Service Bus Message Broker service fill up the CPU.

If we stop the Workflow backend service everything return "normal" (CPU 5% used), but when we started the Workflow backend service the CPU come back to 100%.

In workflow Event Viewer we find the following error:

Service Bus exception swallowed at location ServiceBusMessageSessionContext.OnLockRenewed.
System.OperationCanceledException: A recoverable error occurred while interacting with Service Bus.
Recreate the communication objects and retry the operation.
For more details, see the inner exception. --->
System.TimeoutException: The open operation did not complete within the allotted timeout of 00:00:08.8730368.
The time allotted to this operation may have been a portion of a longer timeout.
---> System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]:
The open operation did not complete within the allotted timeout of 00:00:08.8730368.
The time allotted to this operation may have been a portion of a longer timeout.

Server stack trace:
   at Microsoft.ServiceBus.Messaging.Sbmp.DuplexRequestBindingElement.DuplexRequestSessionChannel.ThrowIfFaultMessage(Message wcfMessage)
   at Microsoft.ServiceBus.Messaging.Sbmp.DuplexRequestBindingElement.DuplexRequestSessionChannel.HandleMessageReceived(IAsyncResult result)

Exception rethrown at [0]:
   at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at Microsoft.ServiceBus.Messaging.Sbmp.DuplexRequestBindingElement.DuplexRequestSessionChannel.DuplexCorrelationAsyncResult.End(IAsyncResult result)
   at Microsoft.ServiceBus.Messaging.Channels.ReconnectBindingElement.ReconnectChannelFactory`1.RequestSessionChannel.RequestAsyncResult.<GetAsyncSteps>b__4(RequestAsyncResult thisPtr, IAsyncResult r)
   at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StepCallback(IAsyncResult result)

Exception rethrown at [1]:
   at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at Microsoft.ServiceBus.Messaging.Channels.ReconnectBindingElement.ReconnectChannelFactory`1.RequestSessionChannel.EndRequest(IAsyncResult result)
   at Microsoft.ServiceBus.Messaging.Sbmp.RedirectBindingElement.RedirectContainerChannelFactory`1.RedirectContainerSessionChannel.RequestAsyncResult.<>c__DisplayClass17.<GetAsyncSteps>b__a(RequestAsyncResult thisPtr, IAsyncResult r)
   at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StepCallback(IAsyncResult result)

Exception rethrown at [2]:
   at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at Microsoft.ServiceBus.Messaging.Sbmp.RedirectBindingElement.RedirectContainerChannelFactory`1.RedirectContainerSessionChannel.EndRequest(IAsyncResult result)
   at Microsoft.ServiceBus.Messaging.Channels.ReconnectBindingElement.ReconnectChannelFactory`1.RequestSessionChannel.RequestAsyncResult.<GetAsyncSteps>b__4(RequestAsyncResult thisPtr, IAsyncResult r)
   at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StepCallback(IAsyncResult result)

Exception rethrown at [3]:
   at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at Microsoft.ServiceBus.Messaging.Channels.ReconnectBindingElement.ReconnectChannelFactory`1.RequestSessionChannel.EndRequest(IAsyncResult result)
   at Microsoft.ServiceBus.Messaging.Sbmp.SbmpTransactionalAsyncResult`1.<GetAsyncSteps>b__36(TIteratorAsyncResult thisPtr, IAsyncResult a)
   at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StepCallback(IAsyncResult result)

Exception rethrown at [4]:
   at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageSession.OnEndRenewLock(IAsyncResult result)
   --- End of inner exception stack trace ---
   at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageSession.OnEndRenewLock(IAsyncResult result)
   at Microsoft.ServiceBus.Messaging.MessageSession.EndRenewLock(IAsyncResult result)
   at Microsoft.Activities.Hosting.ServiceBusUtilities.Isolate(Action callback, Boolean preserveExceptionMessage)
   --- End of inner exception stack trace ---
   at Microsoft.Activities.Hosting.ServiceBusUtilities.Isolate(Action callback, Boolean preserveExceptionMessage)
   at Microsoft.Workflow.Dispatcher.ServiceBusMessageSessionContext.OnLockRenewed(IAsyncResult result)

Someone has the same problem? What cause this problem?

How can we solve this problem?

Kind regards

Samuele

I HATE Workflow Manager 1.0.  Never has anything had me want to bang my head on my desk.  I have uninstalled/reinstalled til I'm blue in the face and each time only the Proxy connection is the only thing listed in Central Admin.  So I can create and run 2013 workflows sucessfully BUT the user requires Contribute permissions to the site which is unacceptable.  I have no idea what I'm doing wrong as I have gone over the scenario and checked and double checked everything.

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

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

Jennifer Knight (MCITP, MCPD)

I am able to use SQL Azure to install the Workflow Manager 1.0 related database and use it successfully (publish & execute).

However I need reporting capabilities on the history of execution and I am trying to install the SQLTrackingService's database on azure. However the script cannot be directly executed on the Azure. Hence I tried to create the db locally and then publish the db to azure. However again there are some compatibility issue.

Any workaround for it?

Thanks.

Hi,

I installed Workflow Manager 1.0 (with default recommended configuration) and the Cummulative Update 1 and activated the feature on SharePoint 2013. I restarted my server.

The Workflow Manager Backend service cannot start. An attempt is done every 30" but it's always fails. The errors I see in the event viewer (every 30") are the following:

Error 1

Error 2

As a result I cannot deploy workflows on SharePoint using Visual Studio. I get a 500 error during activation of the related feature.

Any ideas?

Dimitris Papadimitriou, Software Development Professional

I have a Workflow Manager and Service Bus farm configured and working. I am trying to add a second server to the farm. During configuration, as the second host is being added through Add-SBHost, there is an attempt made to stop and start Service Bus services on the first host. The start fails because the Service Bus Message Broker service gets stuck in the "Starting" state. It retries this 3 times, each try taking around 7 minutes and each time the failure ending with a message that looks like this:

ServiceBus Broker service failed to start, retry count 1. Exception message: Operation timed out..  Stack Trace:   at System.Fabric.FabricRuntime.Create(Action fabricExitCallback)

  at Microsoft.Cloud.ServiceBus.MessageContainerHost.Ring.Join()

  at Microsoft.Cloud.ServiceBus.MessageContainerHost.MessageContainerHostComponent.Open()

  at Microsoft.Cloud.HostingModel.ComponentHost.OpenComponent(IComponent component, RequestTracker tracker)

  at Microsoft.Cloud.HostingModel.ComponentHost.Open()

  at Microsoft.ServiceBus.MessageBroker.Backend.OnStart(String[] args)

This error is preceded by 2 others that present no more information than the above does:

TrackingId: f8ff41e9-53e0-48fc-b4de-b7505d4d5f7b, SubsystemId: NoSystemTracker. Failed to open Messaging Host Component System.TimeoutException: Operation timed out. ---> System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x80071BFF

  at System.Fabric.Interop.NativeRuntime.FabricEndCreateRuntime(IFabricAsyncOperationContext context)

  at System.Fabric.FabricRuntime.NativeFabricRuntimeFactory.InitializeFabricRuntimeEndWrapper(FabricRuntime runtime, AsyncCallOutAdapter adapter)

  at System.Fabric.Interop.Utility.FinishNativeAsyncInvoke[TResult](String functionTag, Func`2 endFunc, TaskCompletionSource`1 source, AsyncCallOutAdapter adapter, Boolean expectCompletedSynchronously)

  --- End of inner exception stack trace ---

  at System.Fabric.FabricRuntime.Create(Action fabricExitCallback)

  at Microsoft.Cloud.ServiceBus.MessageContainerHost.Ring.Join()

  at Microsoft.Cloud.ServiceBus.MessageContainerHost.MessageContainerHostComponent.Open()

and...

Windows Fabric Runtime create failed Exception System.TimeoutException: Operation timed out. ---> System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x80071BFF

  at System.Fabric.Interop.NativeRuntime.FabricEndCreateRuntime(IFabricAsyncOperationContext context)

  at System.Fabric.FabricRuntime.NativeFabricRuntimeFactory.InitializeFabricRuntimeEndWrapper(FabricRuntime runtime, AsyncCallOutAdapter adapter)

  at System.Fabric.Interop.Utility.FinishNativeAsyncInvoke[TResult](String functionTag, Func`2 endFunc, TaskCompletionSource`1 source, AsyncCallOutAdapter adapter, Boolean expectCompletedSynchronously)

  --- End of inner exception stack trace ---

  at System.Fabric.FabricRuntime.Create(Action fabricExitCallback)

  at Microsoft.Cloud.ServiceBus.MessageContainerHost.Ring.Join()

The Windows Fabric Runtime creation itself seems to be retried 6 times, each try taking around 70 seconds and each time it fails, the following information message is posted to the log:

Windows Fabric Runtime create failed (Retries left 6) Exception System.TimeoutException: Operation timed out. ---> System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x80071BFF

  at System.Fabric.Interop.NativeRuntime.FabricEndCreateRuntime(IFabricAsyncOperationContext context)

  at System.Fabric.FabricRuntime.NativeFabricRuntimeFactory.InitializeFabricRuntimeEndWrapper(FabricRuntime runtime, AsyncCallOutAdapter adapter)

  at System.Fabric.Interop.Utility.FinishNativeAsyncInvoke[TResult](String functionTag, Func`2 endFunc, TaskCompletionSource`1 source, AsyncCallOutAdapter adapter, Boolean expectCompletedSynchronously)

  --- End of inner exception stack trace ---

  at System.Fabric.FabricRuntime.Create(Action fabricExitCallback)

  at Microsoft.Cloud.ServiceBus.MessageContainerHost.Ring.Join()

Can anyone throw some light on what could be causing this failure? I am hoping the answer is not uninstall everything and reinstall.

Hello,

in order to install the 26/02/2013 version of the Microsoft Office Developer Tools for Visual Studio 2012, you need to install first the Service Bus 1.0 Cumulative Update 1.

The thing is that I can not install this update, I always get an error:

DownloadManager Information: 0 : Using cached file at C:\Users\Gilles\AppData\Local\Microsoft\Web Platform Installer\installers\ServiceBusCU1\5024FF633CA537CDB1C2903F97E1244457BAEE18\ServiceBus-KB2799752-x64-EN.exe instead of downloading from http://go.microsoft.com/fwlink/?LinkId=285191&CLCID=0x409
DownloadManager Information: 0 : Starting EXE command for product 'Service Bus 1.0 Cumulative Update 1'. Commandline is: 'C:\Users\Gilles\AppData\Local\Microsoft\Web Platform Installer\installers\ServiceBusCU1\5024FF633CA537CDB1C2903F97E1244457BAEE18\ServiceBus-KB2799752-x64-EN.exe /quiet'. Process Id: 6308
DownloadManager Information: 0 : Install exit code for product 'Service Bus 1.0 Cumulative Update 1' is '-1'
DownloadManager Error: 0 : Install return code for product 'Service Bus 1.0 Cumulative Update 1' is Failure
DownloadManager Information: 0 : Product Service Bus 1.0 Cumulative Update 1 done install completed
DownloadManager Information: 0 : Increasing current install to 2

if I run C:\Users\Gilles\AppData\Local\Microsoft\Web Platform Installer\installers\ServiceBusCU1\5024FF633CA537CDB1C2903F97E1244457BAEE18\ServiceBus-KB2799752-x64-EN.exe

I get : "an unexpected internal error has occured."

I am running Windows 8.

Somebody having the same issue?

Thx

Gilles

http://gilleslauwers.wordpress.com

Hi,

We have a single server Sharepoint 2013 farm (with August 2013 CU) on which we also installedWorkflow Manager 1.0 with CU1. When Workflow Manager Powershellis started as administrator an error below is shown:

We configured the site collection to use that workflow farm.

However when we try to publish a 2013 workflow from SPD 2013 error below prevents to use the workflow on the web:

System.InvalidOperationException: Operation failed with error Microsoft.Workflow.Client.ScopeNotFoundException: Scope '/SharePoint/default' was not found.  HTTP headers received from the server - ActivityId: f737b1ca-07b7-459d-9d8e-093ef9ba9901. NodeId: SRV-BITEST. Scope: /SharePoint/default/7f219fd0-dad3-4fe0-9f01-eed23ef5340e. Client ActivityId : c420479c-ec5c-d03d-32d5-472e64a6c2e0. ---> System.Net.WebException: The remote server returned an error: (404) Not Found.

   at Microsoft.Workflow.C

Have you ever faced the same problems before?

Kind regards

Serkan

Hi everybody,

I installed Service Bus 1.0 (and Cumulative Update 1 for Service Bus 1.0) in a lab environment as a prereq for Workflow Manager 1.0 on a Windows Server 2012 R2 with SharePoint 2013 (English locale) on it.

Installation returned no Errors, but configuration Fails.

I set powershell execution policy to unrestricted on all scopes.

When I try to create an New SB Farm, it connects nicely to my SQL Server 2012 BI Edition. But it is unable to create the SB database on SQL ("FailedToDeploySchemaToDatabase").

These are the by-the-book commands I run and the error message. Any help is much appreciated, thanks to everybody out there for having a look.

Windows PowerShell
Copyright (C) 2013 Microsoft Corporation. All rights reserved.

PS C:\Program Files\Service Bus\1.0> $SBCertificateAutoGenerationKey = ConvertTo
-SecureString -AsPlainText  -Force  -String 'dem0str!nG' -Verbose;
PS C:\Program Files\Service Bus\1.0> New-SBFarm -SBFarmDBConnectionString 'Data
Source=SQL\SQL12_01;Initial Catalog=SbManagementDB;Integrated Security=True;Encr
ypt=False' -InternalPortRangeStart 9000 -HttpsPort 9355 -TcpPort 9354 -MessageBr
okerPort 9356 -RunAsAccount 'mydomain\adminaccount' -AdminGroup 'BUILTIN\Adminis
trators' -GatewayDBConnectionString 'Data Source=SQL\SQL12_01;Initial Catalog=Sb
GatewayDatabase;Integrated Security=True;Encrypt=False' -CertificateAutoGenerati
onKey $SBCertificateAutoGenerationKey -MessageContainerDBConnectionString 'Data
Source=SQL\SQL12_01;Initial Catalog=SBMessageContainer01;Integrated Security=Tru
e;Encrypt=False' -Verbose;
New-SBFarm : 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.
At line:1 char:1
+ New-SBFarm -SBFarmDBConnectionString 'Data Source=SQL\SQL12_01;Initial
Catalog=S ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~
    + CategoryInfo          : NotSpecified: (Data Source=SQL...e;Encrypt=False
   :String) [New-SBFarm], SqlException
    + FullyQualifiedErrorId : FailedToDeploySchemaToDatabase,Microsoft.Service
   Bus.Commands.NewSBFarm

PS C:\Program Files\Service Bus\1.0>