000039462 - Data Import into Advanced Workflow enabled application fails with "The operation is not valid for the state of the transaction" in_Archer

Document created by RSA Customer Support Employee on Dec 18, 2020
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000039462
Applies ToRSA Product Set: RSA Archer
RSA Product/Service Type: RSA Archer (On-Premise)
RSA Version/Condition:
IssueData Import fails when all of the below are true:
  1. Data Import into an application that contains an enabled Advanced Workflow
  2. The Data Import is intended to enroll records into Advanced Workflow that were not previously enrolled or did not previously exist.
  3. Import has an error stating the "Advanced Workflow job failed to start."
  4. Advanced Workflow Service is running.
  5. Advanced Workflow job troubleshooter, and designer is accessible in the User Interface from all Job and Web Servers.
  6. The below error is logged in the Advanced Workflow Service logs

<E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent">
<System xmlns="http://schemas.microsoft.com/2004/06/windows/eventlog/system">
  <SubType Name="Error">0</SubType>
  <TimeCreated SystemTime="2020-11-04T16:33:19.7669523Z" />
  <Source Name="Archer.NET" />
  <Correlation ActivityID="{00000000-0000-0000-0000-000000000000}" />
  <Execution ProcessName="WpAsyncScriptMonitor" ProcessID="6680" ThreadID="11696" />
    <TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
     <Description>AsyncScript Monitor max evaluation retries exceeded (1), moving job 1926:CUST into error state.  Last error: The Workpoint.BPM.ServiceContracts.Monitor.IAsyncScriptExecute.ExecuteByIdDb operation had the following error:  The operation is not valid for the state of the transaction.</Description>
---------- Exception ----------
The Workpoint.BPM.ServiceContracts.Monitor.IAsyncScriptExecute.ExecuteByIdDb operation had the following error:  The operation is not valid for the state of the transaction.

Server stack trace:
   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 ad)
   at Workpoint.Monitors.AsyncScript.a.b(Object v)</Message>

CauseIf the Advanced Workflow Service takes too long to enroll any specific record into Advanced Workflow, then Data Import fails with an error.
ResolutionThis issue will be fixed in a future release.
WorkaroundIncreasing the amount of time allowed for the Advanced Workflow Service to process a record has been known to resolve the issue.
  1. Stop Advanced Workflow Service
  2. Locate the following file: C:\Program Files\RSA Archer\Services\Workpoint\conf\WorkpointSettings.config

  3. Locate the following entry:

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


  1. AND change it to:

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

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