000033513 - Workflow Service is Unavailable in RSA Archer 6.1

Document created by RSA Customer Support Employee on Jul 11, 2016•Last modified by RSA Customer Support Employee on Apr 22, 2017
Version 2Show Document
  • Comment • 0
  • View in full screen mode

Article Content

Article Number000033513
Applies ToRSA Product Set: Archer
RSA Version/Condition: 6.1
O/S Version: Windows Server 2012/2012 R2
IssueWhen creating a new Advanced Workflow in an application, receiving Workflow Service unavailable. Error logs indicate the following:
<TraceRecord Severity="Critical" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
 <TraceIdentifier>Archer.Kernel.WorkflowService</TraceIdentifier>
 <Description>Advanced workflow HTTP request error:</Description>
 <AppDomain>/LM/W3SVC/1/ROOT/RSAarcher-1-131123867797996714</AppDomain>
 <Exception>
 <ExceptionType>System.Net.Http.HttpRequestException, System.Net.Http, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a</ExceptionType>
 <Message>An error occurred while sending the request.</Message>
 <Source>mscorlib</Source>
 <StackTrace>
 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
 at ArcherTech.Kernel.Services.Workflow.WorkpointService.&lt;WrapHttpRequest&gt;d__89.MoveNext()
 </StackTrace>
 <InnerException>
  <ExceptionType>System.Net.WebException, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
  <Message>Unable to connect to the remote server</Message>
  <Source>System</Source>
  <StackTrace>
  at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
  at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
  </StackTrace>
   <InnerException>
   <ExceptionType>System.Net.Sockets.SocketException, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
   <Message>No connection could be made because the target machine actively refused it 127.0.0.1:8080</Message>
   <Source>System</Source>
   <StackTrace>
   at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket&amp; socket, IPAddress&amp; address, ConnectSocketState state, IAsyncResult asyncResult, Exception&amp; exception)
   </StackTrace>
  </InnerException>
 </InnerException>
 </Exception>
</TraceRecord>
CauseThe client is using an outdated web.config or previously had Archer 6.0 installed which used port 8080. Even making the modification within Archer Control Panel to port 8000 will not resolve this issue.
ResolutionThe resolution is to add the following information to the web.config on all web servers in the environment.
<appSettings>
    ...
    <add key="workflowBaseUrlOverride" value="http://localhost:8000" />
    ...
</appSettings>

After this is done, an iisreset must be performed.
WorkaroundNone is available.

Attachments

    Outcomes