Return
-
Title
Error: "Secure Copy Command Line has stopped working" -
Description
When opening the console, the error below is displayed:“Secure Copy Command Line has stopped working.Windows can check online for a solution to the problem”
In the Application.evt log of the Secure Copy server, Event ID 1000 or Event ID 1026 may appear. -
Cause
1. The log folder is full. There is no space available to write log files.2. UAC (User Account Control) on the console server is blocking a message or window.3. The Secure Copy set-up file has become corrupted.4. The job settings need to be adjusted. -
Resolution
1. Open the Secure Copy Logs sub-directory (By default C:\Program Files\Quest\Secure Copy 7\Logs\)Delete some existing logs to create space, orRedirect the logs repository to another storage area, orDisable the option to create logs during the job, (Secure Copy console | Jobs | Performance | Enable logging)2. Close Secure Copy. Reopen the application by right clicking and selecting ‘Run As Administrator’ (hold the “Shift” key if needed to see 'Run as' option). If Secure Copy now opens as expected, the problem may be averted in the future by creating a shortcut on the desktop that runs under the Local Administrator privilege, or by disabling UAC on the machine.3. Open the installation folder for Secure Copy on the server and rename the SecureCopy.ssd file and reopen Secure Copy.4. Lower the Performance | thread count and batch settings to the lowest setting.Break the job up into smaller jobs.If none of the steps above resolve the issue, uninstall Secure Copy and reinstall the application.