000037271 - RSA Archer Data feeds sporadically stop running as scheduled and the error is logged "This failure occurred while attempting to connect to the Principle server."

Document created by RSA Customer Support Employee on Apr 8, 2019
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000037271
Applies ToRSA Product Set: Archer
RSA Product/Service Type: RSA Archer (On-Premise)
RSA Version/Condition: 6.4.0.2
Issue
  • The data feeds are scheduled to run but sporadically do not run as scheduled.   
  • The data feeds continue running normally as scheduled only after being manually started by the user.
  • The scheduled column of data feeds is blank for data feeds that should run as scheduled and are not currently running.


During the last scheduled execution of the data feed, the following error message can be found in the Archer Jobframework.JOB log files.
 

<E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent">
    <System xmlns="http://schemas.microsoft.com/2004/06/windows/eventlog/system">
        <EventID>2</EventID>
        <Type>3</Type>
        <SubType Name="Error">0</SubType>
        <Level>2</Level>
        <TimeCreated SystemTime="2019-01-30T06:00:36.9799925Z" />
        <Source Name="ArcherTech.JobFramework" />
        <Correlation ActivityID="{aa9c6853-d495-497b-a00b-e5ecc5e0c2f3}" />
        <Execution ProcessName="ArcherTech.JobFramework.Job" ProcessID="5560" ThreadID="1" />
        <AssemblyVersion>6.4.10200.1028</AssemblyVersion>
        <Channel />
        <Computer>SERVER</Computer>
    </System>
    <ApplicationData>
        <TraceData>
            <DataItem>
                <TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
                    <TraceIdentifier>ArcherTech.JobFramework</TraceIdentifier>
                    <Description>Suspended Error</Description>
                    <AppDomain>ArcherTech.JobFramework.Job.exe</AppDomain>
                    <Exception>
                        <ExceptionType>System.Transactions.TransactionInDoubtException, System.Transactions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
                        <Message>The transaction is in doubt.</Message>
                        <Source>System.Transactions</Source>
                        <StackTrace>   at System.Transactions.TransactionStateInDoubt.EndCommit(InternalTransaction tx)
   at System.Transactions.CommittableTransaction.Commit()
   at System.Transactions.TransactionScope.InternalDispose()
   at System.Transactions.TransactionScope.Dispose()
   at ArcherTech.JobFramework.Job.WF3JobRunner.OnWorkflowSuspended(Object sender, WorkflowSuspendedEventArgs e)</StackTrace>
                        <InnerException>
                            <ExceptionType>System.Data.SqlClient.SqlException, System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
                            <Message>Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.  This failure occured while attempting to connect to the Principle server.</Message>
                            <Source>.Net SqlClient Data Provider</Source>
                            <ContextData>
                                <HelpLink.ProdName>Microsoft SQL Server</HelpLink.ProdName>
                                <HelpLink.EvtSrc>MSSQLServer</HelpLink.EvtSrc>
                                <HelpLink.EvtID>-2</HelpLink.EvtID>
                                <HelpLink.BaseHelpUrl>http://go.microsoft.com/fwlink</HelpLink.BaseHelpUrl>
                                <HelpLink.LinkId>20476</HelpLink.LinkId>
                            </ContextData>
                            <StackTrace>   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
   at System.Data.SqlClient.TdsParserStateObject.ReadSniSyncOverAsync()
   at System.Data.SqlClient.TdsParserStateObject.TryReadNetworkPacket()
   at System.Data.SqlClient.TdsParserStateObject.TryPrepareBuffer()
   at System.Data.SqlClient.TdsParserStateObject.TryReadByte(Byte&amp; value)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean&amp; dataReady)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.TdsExecuteTransactionManagerRequest(Byte[] buffer, TransactionManagerRequestType request, String transactionName, TransactionManagerIsolationLevel isoLevel, Int32 timeout, SqlInternalTransaction transaction, TdsParserStateObject stateObj, Boolean isDelegateControlRequest)
   at System.Data.SqlClient.SqlInternalConnectionTds.ExecuteTransactionYukon(TransactionRequest transactionRequest, String transactionName, IsolationLevel iso, SqlInternalTransaction internalTransaction, Boolean isDelegateControlRequest)
   at System.Data.SqlClient.SqlDelegatedTransaction.SinglePhaseCommit(SinglePhaseEnlistment enlistment)</StackTrace>
                            <InnerException>
                                <ExceptionType>System.ComponentModel.Win32Exception, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
                                <Message>The wait operation timed out</Message>
                                <Source />
                                <StackTrace />
                            </InnerException>
                        </InnerException>
                    </Exception>
                </TraceRecord>
            </DataItem>
        </TraceData>
    </ApplicationData>
</E2ETraceEvent>


 
CauseArcher's default connection timeout is 15 seconds. If the SQL Server does not respond to the connection request within 15 seconds, then the connection to the database fails. Due to this failure, the next execution of the data feed does not get scheduled and does not run.
ResolutionIn the Archer Control panel for the instance, on the database tab, Increase connection timeout setting on the to a duration recommended by a Database Administrator.
 

Attachments

    Outcomes