We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.

Barracuda PST Enterprise

How can I enable logging for the PST Enterprise Copy Service on the Copy Agent server

  • Type: Knowledgebase
  • Date changed: 2 years ago
Solution #00007422

Scope

PST Enterprise, v3.2 or later

Answer:

OVERVIEW

When troubleshooting issues with the PST Enterprise Copy Service, you may need to collect log files from the Copy Agent server. This process will explain how to enable logging, where to find the log files and how to disable logging again for the PST Enterprise Copy Service.


HOW TO STEPS

To enable logging on the Copy Agent server,
  1. Browse to the Copy Service installation directory, by default: C:\Program Files (x86)\Barracuda\PSTEnterprise\PSTCopyService
  2. Run 'ConfigurePSTEnterpriseAgent.exe'.
  3. Check the box 'Diagnostic tracing of the agent service' and then click the 'Save changes and restart agent' button.
  4. Carry out the same action that produced the error, e.g. run client processing with a PST copy/move policy assigned.
  5. Once the error has been reproduced, browse to the Logs folder in the installation directory, by default:
    C:\Program Files (x86)\Barracuda\PSTEnterprise\PSTCopyService\Logs
  6. Zip the C2C PST Copy Service.log and C2C PST Copy Service.log.old files in this folder and send to your Support Representative for diagnostics.

To disable the Copy Service logging again,
  1. Browse to the Copy Service installation directory, by default: C:\Program Files (x86)\C2C Systems\Barracuda\PSTCopyService
  2. Run 'ConfigurePSTEnterpriseAgent.exe'.
  3. Uncheck the box 'Diagnostic tracing of the agent service' and then click the 'Save changes and restart agent' button.

This process will provide a detailed log of the process that produced the error. Your Support representative will be able to review the log and determine the root cause of the issue.