000037579 - How to troubleshoot an export of a report that causes an error to occur in RSA Archer

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

Article Content

Article Number000037579
Applies ToRSA Product Set: Archer
RSA Product/Service Type: RSA Archer 
RSA Version/Condition: All
IssueThis incident is around an error that occurs when exporting a report within Archer. While there are many reasons an export error may occur, this one goes over the scenario of when HTML is copied and pasted within a text area field that is included in the report. 
First, in the user interface, the user may encounter an Error such as this:
Export Error

Next, checking the w3wp logs may show a log entry such as this:

<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="####-##-##T##:##:##.#######Z" />
        <Source Name="Archer.NET" />
        <Correlation ActivityID="{00000000-0000-0000-0000-000000000000}" />
        <Execution ProcessName="w3wp" ProcessID="12232" ThreadID="75" />
        <Channel />
                <TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
                    <Description>An error occurred during a call to extension function 'StripHtml'. See InnerException for a complete description of the error.</Description>
                        <ExceptionType>System.InvalidOperationException, mscorlib, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
                        <Message>An error occurred during a call to extension function 'StripHtml'. See InnerException for a complete description of the error.</Message>
                        <StackTrace>   at ArcherTech.ChannelFramework.Reporting.Xslt.XsltHierarchicalReport.RenderReport(XmlReader data, Stream output)
   at ArcherTech.PrintExport.PrintExportService.RenderSearchData(SearchReport searchReport, SearchStatisticReport searchChart, Boolean printLayout, OutputFormatType format, Stream output, SessionContext sessionContext, Int32 parentContentId, PrintExportOptions options, String toolbarHtml)
   at ArcherTech.Web.Modules.Foundation.Views.PrintExportPresenter.ExportSearchResults(SessionContext sessionContext, SearchReportBase report, PrintExportCriteria printExportCriteria)

From the Log entry above you can see there was an error with the 'StripHtml' function. For this, we can mostly say that the issue might be caused by a text area field.
ResolutionSince this issue is exporting a report, some trial and error steps are necessary to pinpoint the problematic field.
  1. Start by making a copy of the report as to not make any accidental changes to the original.
  2. Next, in the copied report, remove each field 1-by-1 while testing the export in between each removal.
  3. In most cases, this is caused by a text area field since most end users will copy and paste from other sources. 
    • This usually brings along HTML formatting which can cause problems with exports within Archer.
  4. Once the problematic field is found, you can adjust your copy of the report to include the key field/tracking ID field and the problem field.
  5. Next, we are going to filter out the impacted records by adding a filter to the report.
    • In the filter add <problem field name> Does Not Contain "<" (without the quotes).
    • This will filter out the records that have the less than symbol (visible or not) within the fields.
  6. Now you should see a difference in the record count and if you try to export, you should NOT see the error occur.
  7. Now update the filter to <problem field name> Contains "<" (without the quotes).
    • This should give you the impacted records and you may not actually see the less than symbol because of it being an issue with the HTML.
  8. Now that you have the problem records and field you have two options.

  • You can remove the field from the report so that the rest of the report is exportable.
  • You will have to address the data within the problem records for that field manually by copying the field data, pasting into regular notepad to remove the HTML. Then copying it out of notepad and pasting back into the field for the records. 
Currently there isn't a quick an easy way to resolve this if there are thousands of records, however, at least these steps provide a way to troubleshoot and locate the source of the export error.