000031745 - Archer-To-Archer data feed  "Service Connection Failure" with "There was no endpoint listening" in log

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000031745
Applies ToRSA Product Set: Archer
RSA Product/Service Type: Data Feed
RSA Version/Condition: 5.5 SP2
Platform: Windows
IssueArcher-to-Archer Data feed goes directly from "Pending" to "Faulted" state.
The following content can be found in the log:
<E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent">
    <System xmlns="http://schemas.microsoft.com/2004/06/windows/eventlog/system">
        <EventID>3</EventID>
        <Type>3</Type>
        <SubType Name="Error">0</SubType>
        <Level>2</Level>
        <TimeCreated SystemTime="2015-10-22T05:01:03.3491238Z" />
        <Source Name="ArcherTech.DataFeed" />
        <Correlation ActivityID="{073e3cca-f610-44b1-80d6-a0adec37bf48}" />
        <Execution ProcessName="ArcherTech.JobFramework.Job" ProcessID="4828" ThreadID="1" />
        <AssemblyVersion>5.5.20103.1001</AssemblyVersion>
        <Channel />
        <Computer>[removed]</Computer>
    </System>
    <ApplicationData>
        <TraceData>
            <DataItem>
                <TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
                    <TraceIdentifier>ArcherTech.DataFeed</TraceIdentifier>
                    <Description>Could not log in to the web service.  This could be due to the uri '[removed]' being invalid or invalid credentials.</Description>
                    <AppDomain>ArcherTech.JobFramework.Job.exe</AppDomain>
                    <ContextData>
                        <LogReferenceId>102215-050103-2867</LogReferenceId>
                        <DataFeedId>23</DataFeedId>
                        <DataFeedName>A2A__Findings__Rescan_Requests</DataFeedName>
                        <DataFeedHistoryId>29970</DataFeedHistoryId>
                    </ContextData>
                    <Exception>
                        <ExceptionType>System.ServiceModel.EndpointNotFoundException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
                        <Message>There was no endpoint listening at [removed] that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.</Message>
                        <Source>mscorlib</Source>
                        <StackTrace>
Server stack trace:
   at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
   at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)
   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
 
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&amp; msgData, Int32 type)
   at ArcherTech.DataFeed.ArcherAPIWebServiceGen.generalSoap.CreateDomainUserSessionFromInstance(CreateDomainUserSessionFromInstanceRequest request)
   at ArcherTech.DataFeed.ArcherAPIWebServiceGen.generalSoapClient.CreateDomainUserSessionFromInstance(String userName, String instanceName, String password, String usersDomain)
   at ArcherTech.DataFeed.Transporters.ArcherWebServiceTransporter.GetSessionToken(String url)</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.GetRequestStream(TransportContext&amp; context)
   at System.Net.HttpWebRequest.GetRequestStream()
   at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()</StackTrace>
                            <InnerException>
                                <ExceptionType>System.Net.Sockets.SocketException, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
                                <Message>A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond [removed]:80</Message>
                                <Source>System</Source>
                                <StackTrace>   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   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>
            </DataItem>
        </TraceData>
    </ApplicationData>
</E2ETraceEvent>
Cause
  • URL configured in the transport tab of the Archer-To-Archer datafeed is invalid.
  • A firewall blocking communications between the server running the RSA Archer Job Engine service and the URL configured in the data feed.
ResolutionTo resolve the issue, the following must be performed:
  • Verify URL configured in the transport tab of the Archer-To-Archer data feed is valid.
  • Open ports 80 and 443 from each server running the RSA Archer Job Engine service to the web server / load balancer.
WorkaroundWhen it is not possible to open ports 80 / 443 from the services server to the web servers: 
Workaround #1: 
Workaround #2: 
NotesVerify connectivity:
  1. Log into the server running the RSA Archer Job Engine service as the service account running the RSA Archer jJob Engine Service.
  2. Open a web browser
  3. Confirm that the ../ws/general.asmx URL configured in the Transport tab of the Archer-To-Archer datafeed can be opened from the web browser without any certificate errors or authentication prompts.
  4. Repeat for each server running the RSA Archer Job Engine Service.

Attachments

    Outcomes