000038096 - ITSVP Vulnerability Historical Data Feed fails with "Error processing file" when a Values List field has a selected Value with more than one space in RSA Archer

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

Article Content

Article Number000038096
Applies ToRSA Product Set: Archer
RSA Product/Service Type: RSA Archer (On-Premise)
RSA Version/Condition: 6.4.1.2
Issue
  • The ITSVP Vulnerability Historical Data Feed fails with "Error Processing file ... Files successfully processed will be used."
  • The ITSVP Vulnerability Historical Data Feed fails with No data processed due to either all files are skipped or none exist

User-added image


Additionally, the following error is found in the JobFramework log files:

<E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent">
  <System xmlns="http://schemas.microsoft.com/2004/06/windows/eventlog/system">
    <EventID>3</EventID>
    <Type>3</Type>
    <SubType Name="Error">0</SubType>
    <Level>2</Level>
    <TimeCreated SystemTime="2019-08-29T20:50:13.6022680Z" />
    <Source Name="ArcherTech.DataFeed" />
    <Correlation ActivityID="{305dab20-bf13-45ee-935b-22aeaaeb1470}" />
    <Execution ProcessName="ArcherTech.JobFramework.Job" ProcessID="7804" ThreadID="1" />
    <AssemblyVersion>6.6.400.1038</AssemblyVersion>
    <Channel />
    <Computer>(redacted)</Computer>
  </System>
  <ApplicationData>
    <TraceData>
      <DataItem>
        <TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
          <TraceIdentifier>ArcherTech.DataFeed</TraceIdentifier>
          <Description>Error processing file 'file:///C:/Program%20Files/RSA%20Archer/Repository/50001/Datafeed/Vulnerability_Historical_Data/d6cacc49-52f1-4b62-9b2c-06a3a204f724_1.txt'.  Files succesfully processed will be used.</Description>
          <AppDomain>ArcherTech.JobFramework.Job.exe</AppDomain>
          <Exception>
            <ExceptionType>Saxon.Api.DynamicError, saxon9ee-api, Version=9.8.0.6, Culture=neutral, PublicKeyToken=e1fdd002d5083fe6</ExceptionType>
            <Message>org.xml.sax.SAXParseException; systemId: file:///C:/Program%20Files/RSA%20Archer/Repository/50001/Datafeed/Vulnerability_Historical_Data; lineNumber: 29; columnNumber: 43; Attribute name "PRODUCTION" associated with an element type "Device_Count_AVAILABLE_FOR" must be followed by the ' = ' character.</Message>
            <Source>ArcherTech.DataFeed</Source>
            <StackTrace>   at ArcherTech.DataFeed.Transformers.SaxonXSLTTransformer.TransformXML(Uri sourceFile, TransporterStream targetStream)
   at ArcherTech.DataFeed.Transporters.TransformTransporter.TransformSourceFile(Uri sourceFile, Uri destinationFileName)
   at ArcherTech.DataFeed.Transporters.TransformTransporter.ProcessFile(Uri sourceFile)
   at ArcherTech.DataFeed.Transporters.Transporter.ProcessFileInternal(Uri sourceFile)</StackTrace>
          </Exception>
        </TraceRecord>
      </DataItem>
    </TraceData>
  </ApplicationData>
</E2ETraceEvent>
CauseThe issue is caused because a values list has been updated to contain a value that has more than 1 space.
ResolutionThe issue with the feed will be fixed in a later release.
WorkaroundEdit values list values to remove spaces from the values list value.

Important Note: 
The data feed will now complete successfully. However, the Historical trending app will also need to be updated for this selected value to be captured.

For example, if you've added additional device status values (such as Available For Production), but in the OOB historical feed we are only actively accounting for a Device Status = Active when performing our calculations.  Another example might be where a client adds a VSR Overall Status. The xml node that is generated successfully now in the JS, would need to map in the feed, after a field is also created in the Historical app to capture the data. The out of the box feed supports very specific metrics and dimensions.  If those are altered, there is work necessary to capture those new values in the Vulnerability Historical Data application.

Attachments

    Outcomes