Sharepoint 2013 -> Workflow Error logs

Hello, Wondering if someone can help with SharePoint Workflow Manager installation.

I have followed the instructions from the Microsoft website and all seemed to go well.

When I check SharePoint Manage applications and lookup the workflow services status it reports back Workflow is connected, and in SPD2013 I am able to select 2013 workflows.

 If I browse to the local on IIS I get this page returned:

 <ScopeInfo xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/workflow/2012/xaml/activities">
  <ChildScopeCount>1</ChildScopeCount>
  <DefaultWorkflowConfiguration />
  <Description>Root Scope</Description>
  <LastModified>2014-01-18T13:41:38.14</LastModified>
  <LastRevised>2014-01-18T13:41:38.14</LastRevised>
  <Path>/</Path>
- <SecurityConfigurations>
- <ScopedSecurityConfiguration i:type="WindowsSecurityConfiguration">
  <Name>Microsoft.Workflow.Management.Security.WindowsSecurityConfiguration</Name>
  <WorkflowAdminGroupName>BUILTIN\Administrators</WorkflowAdminGroupName>
  </ScopedSecurityConfiguration>
  </SecurityConfigurations>
  <Status>Active</Status>
  </ScopeInfo>

If I create a workflow on SPD2013 and try to publish it, it says there has been an error.

In the workflow operation logs I get this message, can anyone help me with fixing the workflows 2013?

Service Bus exception swallowed at location NamespaceSender.SendMessageRetryAsyncResult.HandleException. System.OperationCanceledException: The token provider was unable to provide a security token while accessing 'https://sharepointserver:9355/WorkflowDefaultNamespace/$STS/Windows/'. Token provider returned message: 'Unable to connect to the remote server'. ---> System.UnauthorizedAccessException: The token provider was unable to provide a security token while accessing 'https://sharepointserver:9355/WorkflowDefaultNamespace/$STS/Windows/'. Token provider returned message: 'Unable to connect to the remote server'. ---> System.IdentityModel.Tokens.SecurityTokenException: The token provider was unable to provide a security token while accessing 'https://sharepointserver:9355/WorkflowDefaultNamespace/$STS/Windows/'. Token provider returned message: 'Unable to connect to the remote server'. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 192.168.1.37:9355
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
   --- End of inner exception stack trace ---
   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.SbmpMessageSender.GetOverheadSize()
   at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessageSender..ctor(String path, SbmpMessagingFactory messagingFactory, SbmpMessageCreator messageCreator, LinkInfo linkInfo)
   at Microsoft.ServiceBus.Messaging.Sbmp.CreateSenderLinkSettings..ctor(SbmpMessagingFactory messagingFactory, String entityName, Nullable`1 entityType, String transferDestinationEntityName)
   at Microsoft.ServiceBus.Messaging.Sbmp.SbmpMessagingFactory.OnBeginCreateMessageSender(String transferDestinationEntityName, String viaEntityName, TimeSpan timeout, AsyncCallback callback, Object state)
   at Microsoft.ServiceBus.Messaging.MessagingFactory.CreateMessageSenderAsyncResult.<GetAsyncSteps>b__19(CreateMessageSenderAsyncResult thisPtr, TimeSpan t, AsyncCallback c, Object s)
   at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.EnumerateSteps(CurrentThreadType state)
   at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.Start()

Exception rethrown at [0]:
   at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at Microsoft.ServiceBus.Messaging.MessagingFactory.EndCreateMessageSender(IAsyncResult result)
   at Microsoft.Activities.Hosting.ServiceBusUtilities.Isolate[TResult](Func`1 callback, Boolean preserveExceptionMessage)
   --- End of inner exception stack trace ---
   at Microsoft.Activities.Hosting.ServiceBusUtilities.Isolate[TResult](Func`1 callback, Boolean preserveExceptionMessage)
   at Microsoft.Workflow.Management.ServiceBusNamespaceSender.CreateMessageSenderAsyncResult.OnMessageSenderCreated(IAsyncResult result)
   at Microsoft.Workflow.Common.AsyncResult.SyncContinue(IAsyncResult result)
   at Microsoft.Workflow.Management.ServiceBusNamespaceSender.CreateMessageSenderAsyncResult..ctor(ServiceBusNamespaceSender owner, String topicPath, EventTraceActivity traceId, AsyncCallback callback, Object state)
   at Microsoft.Workflow.Management.ServiceBusNamespaceSender.OnBeginCreateBatch(String scopePath, EventTraceActivity traceId, AsyncCallback callback, Object state)
   at Microsoft.Activities.Hosting.NamespaceSender.SendMessageRetryAsyncResult.CreateAsyncResult(AsyncCallback callback, Object state)
   at Microsoft.Workflow.Common.BackoffRetryAsyncResult.IsolateWithRetry(IAsyncResult result)


Thank you in advance.

Regards

Darren
DarrenEleyAsked:
Who is Participating?
 
DarrenEleyConnect With a Mentor Author Commented:
I uninstalled it all, and then followed the steps in this guide, and it all worked perfectly.

http://lennytech.wordpress.com/2013/06/02/configuring-sharepoint-2013-to-use-workflow-manager-1-0/

Darren
0
 
Justin SmithSr. System EngineerCommented:
What is the topology?  Single server?  You may need to disable Loopback check.

Click Start, click Run, type regedit, and then click OK.
In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
Right-click Lsa, point to New, and then click DWORD Value.
Type DisableLoopbackCheck, and then press ENTER.
Right-click DisableLoopbackCheck, and then click Modify.
In the Value data box, type 1, and then click OK.
0
 
DarrenEleyAuthor Commented:
Hello, Yes it is a single server. I will give it a try now.

Thank you, I will post the results asap.

Regards

Darren
0
 
DarrenEleyAuthor Commented:
I had a sneaky suspicion that I had already done, it, and confirmed. Its already there. :(

Regards

Darren
0
 
DarrenEleyAuthor Commented:
Reading a lot of articles on installing Workflow manager, I found that this solution was the best to get the service up and running.

Was not my solution.

Darren
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.