When creating a report generation job you specified to export the report to a specified path. You are using a remote console (remote to the CCS application server) and when browsing for the location of the export path you choose a local folder (local to the CCS console). The report does not get written to this folder.
The export path chosen is relative to the CCS Data Processing Service (DPS) server that had the "Reporting Service" role assigned, not the remote CCS console. This behavior is by design for the following reasons. It's unlikely that the CCS application server has the rights to write directly to the file system on which the remote console is running. On top of that, these jobs can be scheduled to run at any time and thus the file system on which the remote console is running could be off-line at the time the report generation job is running.
The most favorable solution would be that you specify a network path such as \\my-file-server\my-reports. You would have to make sure that the service account under which the CCS Data Processing Service (DPS) server service is running has write access to that file server folder. You can then connect to that file server share from the console machine to retrieve the reports.
Alternatively you could specify a path that is local to the CCS Data Processing Service (DPS) server in the report generation job and share that folder on the application server itself and then connect to that share from the console machine to retrieve the reports.
In case of multiple DPS servers with the Reporting Service role, the only way to get it to work properly is to define a UNC network path such as \\my-file-server\my-reports.
Control Compliance Suite 9.x, 10.x and 10.5.x