000037949 - In RSA Archer when running a search, exporting search results or opening a record, an error occurs during the export process: An exception was thrown while assembling content

Document created by RSA Customer Support Employee on Oct 8, 2019Last modified by RSA Customer Support Employee on Mar 26, 2020
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000037949
Applies ToRSA Product Set: Archer
RSA Version/Condition: 6.x
 
IssueWhen attempting to do one of the following throws the below error in Archer:
  1. Export a report.
  2. Running a search/report.
  3. Open a record.
Exporting...
An error has occurred during the export process. The export file cannot be completed.
User-added image

 


<Exception>
  <ExceptionType>ArcherTech.Datasource.Content.Assembler.ContentGetHandlerException, ArcherTech.Datasource.Content, Version=6.5.400.1033, Culture=neutral, PublicKeyToken=null</ExceptionType>
  <Message>ArcherTech.Datasource.Content.Assembler.ContentGetHandlerException: An exception was thrown while assembling content.</Message>
  <Source>ArcherTech.Datasource.Content</Source>
  <StackTrace>
  at ArcherTech.Datasource.Content.Assembler.HandleAssembleException.LoadFields(SessionContext session, IEnumerable`1 baseContents, IEnumerable`1 fieldDefinitions)
   at ArcherTech.Kernel.Brokers.ContentBroker.LoadFields(IEnumerable`1 permissionedbaseContents, IList`1 fieldDefinitions)
   at ArcherTech.Kernel.Brokers.ContentBroker.Get(IList`1 contentIds, IList`1 fieldIds)
   at ArcherTech.Kernel.Managers.ContentManager.Get(SessionContext sessionContext, IList`1 contentIds, IList`1 fieldIds)</StackTrace>
  <InnerException>
    <ExceptionType>System.ArgumentException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
    <Message>An item with the same key has already been added.</Message>
    <Source>mscorlib</Source>
    <StackTrace>
  at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
   at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
   at ArcherTech.Utility.ExtensionMethods.CollectionExtensions.AddRange[K,V](IDictionary`2 source, IEnumerable`1 listToAdd, Func`2 getKeyFunc)
   at ArcherTech.Datasource.Content.Assembler.AssembleContent.LoadFields(SessionContext session, IEnumerable`1 baseContents, IEnumerable`1 fieldDefinitions)
   at ArcherTech.Datasource.Content.Assembler.LoadContentBaseFields.LoadFields(SessionContext session, IEnumerable`1 baseContents, IEnumerable`1 fieldDefinitions)
   at ArcherTech.Datasource.Content.Assembler.AddFieldsWithoutValues.LoadFields(SessionContext session, IEnumerable`1 baseContents, IEnumerable`1 fieldDefinitions)
   at ArcherTech.Datasource.Content.Assembler.SetCalcFieldErrors.LoadFields(SessionContext session, IEnumerable`1 baseContents, IEnumerable`1 fieldDefinitions)
   at ArcherTech.Datasource.Content.Assembler.HandleAssembleException.LoadFields(SessionContext session, IEnumerable`1 baseContents, IEnumerable`1 fieldDefinitions)</StackTrace>
  </InnerException>
</Exception>


 
CauseThere may be other causes for this issue and this article just addresses one cause. This can be caused by Advanced Workflow where there is a loopback transition that causes the record to be more than one current workflow node. 
ResolutionThe first thing that you must do is identify the record that is causing the issue. This can be done by modifying your search until your search includes a single record but still fails. This will likely require many attempts to get it identified.

Once you know the record then you must remove all columns from the report except the key field and the field with the system tracking id. If this allows the record to be returned in a search, you know that there is a problem with one of the fields.

To fix this issue you can open the record in the Job Troubleshooter to see if there are multiple active nodes (green nodes).
 
User-added image


Only one node should be active. This is typically caused by a loopback transition that is incorrectly configured. A loopback transition should only return the record to a node previously visited and is identified by a dotted line as shown in the screenshot above.

You must fix the transition then re-enroll the record. To re-enroll the record, you must delete the job from the job troubleshooter.
 
User-added image 


Once it is deleted, you can re-enroll the record based on the record enrollment configuration in your Advanced Workflow setup.
User-added image
NotesNew records should no longer get into this state starting in 6.7.0.1 as the bad path is not allowed.

Attachments

    Outcomes