To Identify failures for the Report Scheduler try looking for possible error logs generated at the below locations:
1) Check ‘Plug-in Trace Logs’ entity for errors (via Advanced Find)
Note : Ensure that you have set the Plugin trace logging to ‘All’ or ‘Exception’ (from within Settings ➤ Administration ➤ System Settings) You may need to have ‘System Administrator’ role to perform the above.
Look for plug-in trace log records where ‘Type Name’ contains ‘Report Scheduler’ Open the specific record and look for errors.
2) Check the ‘RS Event Logs’ entity for errors. (available under Settings ➤ IOTAP AddOns) Look for RS event logs records created at around the same time when the report ran. Open the specific record and check the Description field.
3) Check the ‘System Jobs’ entity for errors (via Advanced Find) Look for system job records where ‘System Job Name’ contains ‘Report Scheduler’ Open the specific record and look for errors.
Some of the Most common Issues and their Causes/Resolution
Issue: Licensed User count exceeded
a) Verify the actual user count in CRM. (Settings ➤ Security ➤ Users)
b) Verify the actual user count identified by Report Scheduler Settings ➤ Solutions ➤ Report Scheduler ➤ Profile and License tab Confirm the Actual user value.
If it’s a licensing error you can reduce or manage the number of users in the system using Security Groups in this article or purchase a higher tier.
Issue: JavaScript Issues while creating/updating a RS Scheduled Record
Report Scheduler version 13.0.0.0 or below does not support UCI. Ensure that you are using the CRM Classic Interface while creating or updating a Scheduled Record.
You can force the usage of the classic interface by appending “forceClassic=1” token to the URL: e.g. https://XXX.crm.dynamics.com/main.aspx?forceClassic=1
Issue: Currency Code issues while scheduling reports on CRM instances with multiple currencies
There was a known issue reported while scheduling reports with currency fields when CRM had multiple currencies configured. This issue has been resolved in Report Scheduler version 13.0.0.0.
Please download and install the same from the below link: https://www.work365apps.com/report-scheduler-release-notes/
Please find the list of Valid/Invalid scenarios when you have currency fields in your scheduled view
- Report has only actual currency field - Valid
- Report has only base currency field – Invalid (To fix this ensure to add the actual currency field to the view)
- Report has both actual and base currency fields – Valid
- Report has only actual currency field (summarized on actual currency field) – Only valid if all records have a single currency
- Report has only base currency field (summarized on base currency field) – Invalid (To fix this ensure to add the actual currency field to the view)
- Report has both actual currency and base currency fields (summarized on actual currency field) - Only valid if all records have a single currency
- Report has both actual currency and base currency fields (summarized on base currency field) – Valid
Issue: Time Out Issue
The Report Scheduler uses the Dynamics CRM resources and services to generate the email required to send a report. This process has an internal limit of 2 minutes.
If the view results in more records (generally > 500) than the Report Scheduler may not handle the report generation and the email send will fail.
Try any of the below steps depending on how the report has been configured:
- Modify the View to return a smaller result set
- Remove any Grouping or Summary configured for the RS scheduled record
The resolution here would be to change the view to limit the number of records it generates thereby reducing the time it takes to process the view.
To run any report instantly, select the scheduled time as the current hour. The report scheduler ignores the minutes in the time part. Any change in scheduled day/days or time will result in re-trigger of report scheduler workflow.
Issue: FetchXml is incorrect OR Invalid xml
FetchXml or any other xml issue (reported in logs) should ideally happen in case of a changed or broken view. If fields or view items have changed (after they have been configured in Report Scheduler) the Report Scheduler may not be able to continue sending the Reports. In this case it is best to create simple view and Send a Test Email with a new view.
To further troubleshoot the issue – create a New Scheduled Report
- With simple To fields for the Email recipients
- Eliminate the complexity in the view
- Use Advanced find to Test the view
Modify the ‘scheduled time’ in the existing report to attempt to resend it
Error: Some columns not populated in report while scheduling reports
There could be situations when the report generated does not have values populated in some of the columns. This ideally highlights an issue with the CRM View.
Follow the below steps to rectify the problem.
- Open Advanced Find and select the Entity & View which does not work as expected.
- Click on ‘Results’ and confirm that the erroneous column is displayed and indeed contains values.
- Click on ‘Download FetchXml’. (This should download an xml file)
- Open the downloaded file and search for the erroneous field
Note : You will need to search it based on the schema name of the field
If you don’t find the field in the file, please customize the view (from within Settings -> Customizations) and remove the erroneous field from the list of columns in the view. Save and Publish the customizations. Again add back the erroneous field in the view.
Save and Publish the customizations. Follow steps #1 to 4 above and confirm if the field is generated in the FetchXml file. If yes, trying running the scheduled report again.
Error: Some columns not populated in report while scheduling Activity reports
Activities in CRM has a special field of ‘PartyList’ datatype. Please refer the below link for the list of these fields.
These fields are not supported for scheduling. While scheduling activities ensure that no such field are available on the scheduled view. In case, these fields are needed on the scheduled view, you may need to write custom logic to pull values from these fields and populate the same in a custom text field. The custom text field can then be displayed in the scheduled view.
Error: Report Scheduler looks working but does not send Email OR Report Scheduler is not sending Email OR Report Scheduler ‘Test Email’ functionality seems to work but does not send Email
This could happen for a variety of reasons. It may happen in case of any issues/errors, however it could also happen in case of any configuration issues.
Below are some of the common checks you should consider:
1. Check if there is an outgoing Email activity created for the Scheduled Report within CRM using Advanced Find.
If the Scheduled Report Email record exists and is lying in the ‘Pending Send’ state it generally indicates a problem with the CRM Email Configuration AND/OR the ‘From’ User’s mailbox configuration.
If the emails are not being sent for only a specific User, it generally indicates a problem with the Users mailbox configuration. Browsing to Settings ➤ Email Configuration ➤ Mailboxes and running the ‘Test & Enable Mailbox’ for the particular mailbox should help identify potential issues.
Make sure you have the right user/settings configured in the Report Scheduler configuration page
2. Within Dynamics 365 browse to Settings ➤ Processes
Look for the process named ‘Report Scheduler’. Ensure that the owner of this process is an Active CRM User and has ‘Access Mode’ on his user record set to ‘Read-Write’
Issue: Multi-User Scheduling not emailing Reports to all Users
In case of situations where report is not sent to all users, ensure that the below conditions are met while scheduling a report
- The Entity view scheduled via Report Scheduler should be a System view.
- The CRM User view scheduled via Report Scheduler should be a System view
- Ensure all users available in the targeted User view has been assigned the 'IOTAP RS' role.
- Ensure all users available in the targeted User view have an email id assigned.
- To ensure that the report generated for each user is based on their roles ensure the Entity view scheduled does not have any filter on the ‘Owner’ column.
Issue: Report not sent. No Errors in Logs OR Report errored out and no longer runs for the scheduled days OR Forcefully re-run the Report Scheduler Jobs
All reports are scheduled via a background workflow job. There could be situations, where the workflow was not able to run or it stopped running (for reasons unknown).
In such scenarios it is possible to restart the workflow manually. Browse to ‘RS Scheduled Records’ home grid. Select the records which do not seem to run as expected. Click ‘Run Workflow’ on the command bar. Run the ‘Report Scheduler’ on demand workflow.
Try refreshing the grid after a couple of minutes. And check the date value in the ‘Next Scheduled’ column. On successful completion there should be date populated in this field, which is when the report would run next.
Issue: Cannot read property 'document' of null
This issue is on UCI with older version of report scheduler.
If you are on Dynamics 365 UCI then download version v14.0.0.5 which is UCI compatible version. Refer below link to download the latest version. https://www.work365apps.com/report-scheduler-release-notes/
Issue: The column already exist
Cause: The CRM View configured to be scheduled may probably have duplicate attributes in the FetchXml Query. In case you find any duplicate values, this may indicate a Microsoft product issue.
Identify: Open Advanced Find and select the Entity and View on which the issue occurs and click the ‘Download FetchXML’ button. (refer screenshot below)
Open the downloaded file in a text editor and check for if the fetchxml contains duplicate attributes. In the sample below, the there are 2 instances of address1_city.
Resolution: In case of the above a simple workaround would be remove the erroneous column from the view (from within CRM customizations) If you still need the field on the view, you may need to create a new view and try.
Alternatively, one can raise a ticket with Microsoft to identify the cause of the duplicate attribute in FetchXML