000035321 - Scheduled Report Distribution notifications are missing reports in RSA Archer GRC

Document created by RSA Customer Support Employee on Jul 1, 2017•Last modified by RSA Customer Support on Jul 29, 2020
Version 2Show Document
  • Comment • 0
  • View in full screen mode

Article Content

Article Number000035321
Applies ToRSA Product Set: Archer
RSA Version/Condition: All
IssueOne or more reports are missing from emails that are sent by a Scheduled Report Distribution.  The Scheduled Report Distribution may previously have been working as expected, with all reports included.  In some cases, some reports may be sent with the email while others are missing. When looking at the logs, the JobFramework log shows the following messages:

<E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent">
  <ApplicationData>
    <TraceData>
      <DataItem>
        <TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
          <TraceIdentifier>ArcherTech.Notifications</TraceIdentifier>
          <Description>User with userId 2 failed to be impersonated.</Description>
          <AppDomain>ArcherTech.JobFramework.Job.exe</AppDomain>
        </TraceRecord>
      </DataItem>
    </TraceData>
  </ApplicationData>
</E2ETraceEvent>

And


<E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent">
  <ApplicationData>
    <TraceData>
      <DataItem>
        <TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
          <TraceIdentifier>ArcherTech.Notifications</TraceIdentifier>
          <Description>Report Table: ReportName encountered an error and was unable to be downloaded</Description>
          <AppDomain>ArcherTech.JobFramework.Job.exe</AppDomain>
        </TraceRecord>
      </DataItem>
    </TraceData>
  </ApplicationData>
</E2ETraceEvent>



 
CausePermissions for Scheduled Report Distributions are based on the user who originally created the report. If that user account's permissions change so that the user no longer has access to the report, then the Scheduled Report Distribution will not have access to the report. 
Resolution
  1. Check the reports included in the Scheduled Report Distribution to find out what user created them. 
  2. Does that user still have access to run the reports? 
  3. If not, re-create the reports with a different user account, and link the new reports to the Scheduled Report Distribution.
NotesAn idea has been created for this functionality to be changed. You can vote on the idea here.

Attachments

    Outcomes