KB9051: "MSIRequest::RunReportDocumentByID(): Error finding report <...> in schedule: HRESULT=0x8004140b" appears in the DssErrors.log when a scheduled report is deleted from the project .

SYMPTOM:
Consider the following example to illustrate this issue:
 

1. Multiple reports are scheduled to a common schedule trigger.
2. One of the scheduled reports is deleted, however, the other scheduled reports remain in the project.

When the schedule is triggered, the following error messages appear in the DssErrors.log:
Object with ID '...' and type 3 (Report Definition) is not found in metadata. It may have been deleted.
SIRequest::RunReportDocumentByID(): Error finding report <...> in schedule: HRESULT=0x8004140b.
MSIScheduler::ExecuteSimpleStmt(): Error executing DssCmdRunReportByID schedule statement for <...>: HRESULT=<-2147216373>.
CAUSE:
These error messages are logged to the DssErrors.log when a report that had been scheduled in the past no longer exists in the project. When the schedule is triggered, all the scheduled reports will execute, except for the deleted report. Since the report in question was not unscheduled before being deleted, a link between the schedule trigger and the report remains in the metadata. When the schedule is triggered, Strategy Intelligence Server looks for the deleted report and logs the error messages above to the DssErrors.log because the report no longer exists.
ACTION:
The error messages themselves can be ignored as long as the report ID that is referenced does indeed no longer exist in the project. The other scheduled reports should not be affected by the error.
In order to cleanly remove all traces of the deleted scheduled report, ScanMD should be run against the metadata. After ScanMD is run, the error messages should no longer appear in the DssErrors.log. For details on using the ScanMD utility, refer to Strategy Knowledge Base document:
KB35809 - Using ScanMD to fix known logical metadata inconsistencies in the Strategy Product Suite
 
KB413152