When you run the Report Generation job, the job is completed with error messages similar to the following:
This user isn't allowed to sign in to this computer.
Error generating final processed report. Database logon failed.
In this scenario, you cannot view predefined or customized reports by using Crystal Reports, even though the Report Generation job is completed. All other features of Control Compliance Suite work with TLS 1.2.
You may observe this issue in the following Control Compliance Suite deployment scenario:
Control Compliance Suite Manager in reporting role is installed on one computer, and CCS Production Database and CCS Reporting Database are installed on another computer. (For supported versions of database servers, see Software Requirements.)
Report Generation job is completed with 'Database logon failed' error for CCS
The error occurs because after you enable TLS 1.2, Crystal Reports cannot communicate with the database server. To reestablish this communication, see the Solution section in this article.
CCS 12.5 (ETA January 2019) is scheduled to have a fix for this issue. Also Symantec engineering is looking at the possibility of providing Quick Fixes for earlier versions of CCS (possibly late November\early December of 2018). Contact Symantec CCS support to determine if those QFs have been released. To address this issue without QFs or upgrading to CCS 12.5, the predefined and custom report templates you use must be customized using a separate installation of Crystal Reports SDK. You must customize a predefined report template, and then follow the troubleshooting steps mentioned in the Resolving the Crystal Report communication error issue section in the attached Crystal_Report_Communication_Error_with_TLS_1.2.pdf document.