After you run the Event Manager run all scheduled events, if you missed scheduling a report event or a report event failed, it can be possible to run the report event again.

IMPORTANT! Do not click on the Run All button again, but instead highlight the individual report event, and click the run button.

Report events generally base their results on the Prior Transaction Posting Date at the time you run the report.  Therefore, if you can run the same report event successfully again for the same Prior Transaction Posting Date, then results should be correct. For more information, review The Servicing Director Current Transaction Posting Date Is Incorrect.

You need to run the report event before the next change in the Prior Transaction Posting Date, which is advanced by the next run all scheduled events for the next business day.

If the Event Manager run all scheduled events screen shows a red X before the title of the report event listing in the Scheduled Instances screen, then the red X indicates the event failed to run for some reason, and Event Manager should have logged the error message. Review the information logged about the failed report event to resolve the failure, and then it should be possible to run the report event again.

Workaround:

If one or more report events were missed or failed during the Event Manager run all scheduled events, you should immediately do the following:

IMPORTANT! Do not click on the Run All button.  Do not choose to Run All scheduled events until troubleshooting this problem is completed, and you want to move forward with a new Run All scheduled events for the end of a new business day.

1. Note the exact full title of the event or events that have a red X. Note whether the event type was an Update (Upd), a report (Rpt), a letter (Ltr), or an import/export, as shown in the event title.
2. Stop all users from entering new transactions.  Do not enter new transactions until troubleshooting this problem is completed. Enabling Servicing Director Read-Only mode is one way to do this.  See other articles for more information about how to enable Read-Only mode.
3. Confirm the transaction dates on the system by opening the System Administration application>Table Setup>Company>Transactions tab.  Confirm all three dates listed in the Transact Posting Dates section, for the Current, Prior, and Last. For more information about the transactions dates, review Definitions of the Servicing Director Current, Prior and Last Transaction Dates. 
4. Create the Event Log By Date report from Event Manager, using the start time criteria of the last known good Run All scheduled events. Enter the StartTime > date of last known good Run All scheduled event in the criteria.  For more information review Event Log by Date Report. 
5. Locate and confirm your most recent Servicing Director database backup files.
6. Review the Event Log By Date report you created for the event or events that have a red X and note the exact full error message logged in the report.  Review the error message with your local IT and system administrator to see if there is a local, non-Serivicing Director cause for the issue, which can be resolved.
7. If you find you can resolve the cause of the failed event, you should be able to re-run the event.  You can re-run report events, which are events with the word Report or Rpt in their title.  Other events should not be re-run until further reviewed with Customer Support.  You can re-run the individual report event or events by highlighting each individual event, and clicking the Run button.  Do not click the Run All button.
8. If you cannot resolve the cause of the failed events, or the events are types other than reports, then submit a case through Case Management. 

ArticleNumber:

000071156