How to manually enable DPS or CCS Manager logging in Control Compliance Suite (CCS) v12.5.x

book

Article ID: 151917

calendar_today

Updated On:

Products

Control Compliance Suite Exchange Control Compliance Suite Databases Oracle Control Compliance Suite Windows Control Compliance Suite Control Compliance Suite Standards Server Control Compliance Suite Unix Control Compliance Suite Standards Database

Issue/Introduction

Control Compliance Suite (CCS)

Need to troubleshoot issues on data collections, evaluations, or other DPS or CCS Manager jobs.

Environment

CCS Manager 12.5.x

Resolution

To enable verbose logging on the CCS Manager:

  1. OPTIONAL STEP - If you want delete the current manager logs, you need to stop the CCS managers services so the log files will not be in use.  
    1. On the CCS Manager that you need to enable verbose logs, go to Start -> Run and launch services.msc.  Stop the 'Symantec Data Processing service' and the 'Symantec CCS Manager' services.
    2. Navigate into the %Programdata%\symantec.csm\logs\ccsmanager folder and delete all files and any subfolders in the \ccsmanager folder....they will be recreated when the services are restarted.
    3. Start the 'Symantec Data Processing service' and the 'Symantec CCS Manager' services.
  2. Navigate to \Program Files (x86)\Symantec\CCS\Reporting and Analytics\DPS\ and make a backup of the 'Blade.WorkerProccess.exe.Config' file.  Now open the original Blade.WorkerProccess.exe.Config file using Notepad. 
  • Under the "Logging" section find the value

                  <add key="Log.Severity" value="Warning" />

          and change it to

                 <add key="Log.Severity" value="Verbose" />

                

  1. Save and close the 'Blade.WorkerProccess.exe.Config' file.
  2. In the same directory, make a backup the 'Symantec.CSM.DPS.exe.config' file and then edit the original 'Symantec.CSM.DPS.exe.config' using Notepad.  Once the changes shown below are made, you can then Save and Close the file.
  • Under the "Logging" section find the value

            <add key="Log.Severity" value="Warning" />

          and change it to

                 <add key="Log.Severity" value="Verbose" />

                

     5. Duplicate the issue you are troubleshooting, and when that completes zip up the entire %Programdata%\symantec.csm\logs\ccsmanager folder and attach it to the case for analysis.

     6. Restore the backups (or set the logging back to "Warning") in the 'Blade.WorkerProccess.exe.Config' and 'Symantec.CSM.DPS.exe.config' you modified above to turn off verbose logging on the CCS manager. 


NOTE for enabling verbose logging for CCS Report/Evaluation issues: For troubleshooting issues and enabling verbose logging for CCS Reports events (such as Report generation and evaluation problems, etc) make a backup and then modify the same values above within the 'Blade.Worker.Process.x64.exe.Config' file (the CCS Report and Evaluation processes in CCS are 64 bit).

Additional Information

Refer to the following article for enabling special UNIX command logging:  How can you generate the commands being executed on the target UNIX machine, once a Ad-Hoc Query or CCS Job is implemented?