000036702 - RSA Archer 6.x Advanced Workflow (AWF) records sporadically fail to progress to next node

Document created by RSA Customer Support Employee on Sep 7, 2018
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000036702
Applies ToRSA Product Set: Archer
RSA Product/Service Type: Advanced Workflow
RSA Version/Condition: 6.x
IssueRSA Archer records may fail initial enrollment or various nodes throughout the Advanced Workflow stages with the following message:
 
There was an error processing this record.
Please contact your administrator and tell them this record could not go past the 'Update Content' page.

 


User-added image


The following exceptions are found in the Archer.AdvancedWorkflow log file:

<E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent"> 
    <System xmlns="http://schemas.microsoft.com/2004/06/windows/eventlog/system"> 
        <EventID>0</EventID> 
        <Type>3</Type> 
        <SubType Name="Error">0</SubType> 
        <Level>2</Level> 
        <TimeCreated SystemTime="2018-03-15T15:42:52.3447861Z" /> 
        <Source Name="Archer.NET" /> 
        <Correlation ActivityID="{00000000-0000-0000-0000-000000000000}" /> 
        <Execution ProcessName="WpAsyncScriptMonitor" ProcessID="9620" ThreadID="2272" /> 
        <AssemblyVersion>6.3.101.1002</AssemblyVersion> 
        <Computer>ARCHER-WEB-01</Computer> 
    </System> 
    <ApplicationData> 
        <TraceData> 
            <DataItem> 
                <TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord"> 
                    <TraceIdentifier>Archer.NET</TraceIdentifier> 
                    <Description>AsyncScript Monitor max evaluation retries exceeded (1), moving job XXXX:CUST into error state.  Last error:
                    The Workpoint.BPM.ServiceContracts.Monitor.IAsyncScriptExecute.ExecuteByIdDb operation had the following error:  
                    Error executing Available agent script XX:XXXX (Script with ID:DB XX:XXXX was not found.)  for activity XXXXX:CUST:1 (XXXXX)
                    in job XXXXX:CUST:  The operation is not valid for the state of the transaction.</Description> 
                    <AppDomain>WpAsyncScriptMonitor.exe-WpAppDomain</AppDomain> 
                    <Exception> 
                        <Message>
---------- Exception ----------
[System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]]
The Workpoint.BPM.ServiceContracts.Monitor.IAsyncScriptExecute.ExecuteByIdDb operation had the following error:  
Error executing Available agent script XXX:XXXX (Script with ID:DB XXX:XXXX was not found.)  for activity XXXXX:CUST:X (XXXXXX) in job XXXX:CUST:  
The operation is not valid for the state of the transaction.

Server stack trace: 
   at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)
   at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
   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& msgData, Int32 type)
   at Workpoint.BPM.ServiceContracts.Monitor.IAsyncScriptExecute.ExecuteByIdDb(String dsn, IdDb scriptIdDb, SymbolTableData symbolData, ScriptExecuteOptions options)
   at Workpoint.Monitors.AsyncScript.a.h(a a)
   at Workpoint.Monitors.AsyncScript.a.b(Object a)</Message> 
                    </Exception> 
                </TraceRecord> 
            </DataItem> 
        </TraceData> 
    </ApplicationData> 
</E2ETraceEvent>
CauseThe Workpoint database timeout of one minute is not enough.
ResolutionA fix for this issue will be available in future release.
WorkaroundAs a workaround,
  1. Stop the Advanced Workflow Service
  2. Locate WorkpointSettings.config file in C:\Program Files\RSA Archer\Services\Workpoint\conf.
  3. Locate the following entry:



<transactionConfiguration20 transactionIsolationProperty="ReadCommitted" transactionTimeoutProperty="60" esInteropOptionProperty="None" />


  1. Change the value from 60 to 300, as shown:


<transactionConfiguration20 transactionIsolationProperty="ReadCommitted" transactionTimeoutProperty="300" esInteropOptionProperty="None" />



  1. Save the configuration file.
  2. Start the Advanced Workflow Service.

Note: Engineering does NOT recommend setting the transactionTimeoutProperty above 300.

Attachments

    Outcomes