Initializing Indexer inputs – Last Update: Split input database Invalid Path
Webserver0.0.log
2022-07-29 11:00:06 WARNING: #{18} [BaseDIReportExecutorImpl.execute] Report execution failed
com.symc.matrix.report.ReportFailedException
at com.symc.matrix.report.executor.impl.MultiTierReportExecutorImpl._split(MultiTierReportExecutorImpl.java:189)
at com.symc.matrix.report.executor.impl.MultiTierReportExecutorImpl.split(MultiTierReportExecutorImpl.java:143)
at com.symc.matrix.report.executor.impl.BaseDIReportExecutorImpl.execute(BaseDIReportExecutorImpl.java:465)
at com.symc.matrix.report.ReportSubsystem$MasterReportRunner.run(ReportSubsystem.java:602)
at java.lang.Thread.run(Thread.java:748)
2022-07-29 11:00:06 INFO: #{18} [EventsManager.publishEvent] WARNING: [REPORT_FAILED@ms.vtas.local@null] Fri Jul 29 11:00:06 EDT 2022 The report Consumption by Folder Report failed to execute (args: [Consumption by Folder Report])
Copy the failing scheduled report to a new report
This will copy the old report and assign the Created By as the active user on the new report
For larger environments with a large number of reports that are failing, you can update the reports database and replace the CREATOR of the reports to an active user.
1. On the Management Server, create a backup a copy. of
2. Open an elevated command prompt (Run as administrator) and navigate to
3. Run the following command to update the CREATOR of the reports.
sqlite3.exe
Example:
C:\Users\administrator.VTAS>cd "\Program Files\DataInsight"\bin
C:\Program Files\DataInsight\bin>sqlite3.exe C:\DataInsight\data\console\reports\sqlite_reports.db "update report set creator = 'JKong@VTAS' where creator = 'CHird@VTAS'";
4. In the Data Insight console, review the list of reports to confirm that the Created By is now the active user.
This issue occurs when the CREATOR of a scheduled report is deleted from Data Insight. Data Insight requires all scheduled reports to have an active Data Insight user as the creator.

In addition, this issue may occur if there are problems in bi-directional communication between the Management Server and the other Data Insight nodes over port 8383. Ensure that no firewall rules on any of the Data Insight nodes are blocking incoming or outgoing communications over that port.
There are a couple of solutions for this issue depending on the environment.