Are you receiving an error report from Report Sender? This article covers some of the many possible reasons you could get this error and how to fix it.
About This Error
This error means that while trying to get the report from the Salesforce reporting endpoints, it failed. This can happen for a wide variety of reasons. If Salesforce returns an error message, we can catch it and add an additional message along with the error. However, there are a wide variety of issues that can cause a generic response. In this article, we'll take you through our typical steps for troubleshooting.
Generic Errors
If the error is just "Error in exporting Report: [Report Name]," then unfortunately, we didn't get enough details from Salesforce to figure out why the report generation failed. In this scenario, we recommend the following debugging steps:
Verify that the user is still active, and has the CloudAnswers Report Sender permission set.
Have the user log in and go to Report Sender. Click New Schedule (or Reauthorize if the button has changed), and if Report Sender asks to approve access, authorize it. You can click cancel when it goes to the New Schedule page.
Check if the user's profile has Session Setting at Login set to High Assurance. This setting needs to be set to None for Report Sender to work correctly.
Check if any user or organization's settings would prevent our code, running on Salesforce, from accessing the reporting API. Some examples include removing API access, restricting logins to certain IP ranges, or disabling the ability to export reports.
Errors with Additional Details
If the error message includes additional information after the report name, consult this table for fixes.
Error | How to Fix |
Bad file format | Edit the schedule and fix the report format to be a valid value (csv in free edition; csv, xls, xlsx, or inline for Plus). |
Joined Reports are not supported for export | Upgrade to Report Sender Plus to get joined reports or choose a different report. More details |
Report not found | See if the report was deleted or needs to be moved to another folder so the schedule owner can see it. |
Your report could not be sent because Report Sender needs to be authorized to send reports. | Log in as the schedule owner (do not use login-as) and click New Schedule or Reauthorize button to give Report Sender access to the reporting API as this user. More details |
SendEmail failed. First exception on row 0; first error: REQUIRED_FIELD_MISSING, No body supplied for the file attachment.: [fileAttachments] | Change your identity verification settings so that a High Assurance setting is not required for Reports or change the format to XLSX if you're using Plus. More details |
Read timed out | The report took longer than two minutes to generate, which is the longest Salesforce let's us wait. More details. |