ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Error: 'Error while copying the file <Path\file>. Refer to the installation log for details.' when upgrading CCS

book

Article ID: 226920

calendar_today

Updated On:

Products

Control Compliance Suite Standards Server Control Compliance Suite

Issue/Introduction

When upgrading a CCS component or applying a SCU, you get the following error:

Error while copying the file "<Path_to_file\filename>".  Refer to the installation log for details.

The file can be located at the temporary location: "C:\Program files (x86)\Symantec\CCS\Reporting and Analytics\UndeployedFiles".
Copy the file, and then delete it from the temporary location.

 

NOTE: The path and the filename in the error may vary.  See an example below:

 

Cause

The file was locked or in use when CCS tried to replace it during the upgrade.

Environment

Release : 12.5.x

Component : CCS upgrade

Resolution

During the upgrade, the CCS installer could not apply or replace a file because it was in use or locked.  When this happens, CCS will continue the upgrade, but will put the file in the C:\Program files (x86)\Symantec\CCS\Reporting and Analytics\UndeployedFiles directory.  You will need to manually move the file in the UndeployedFiles directory to the proper place for CCS to work correctly.  

  1. Stop all of the CCS services on that server (since we don't know which one the file will impact)
  2. Copy the file from the UndeployedFiles directory and replace the file that is listed in the first error message.  If you get the message that the file is still in use, you may need to reboot the server before you will be able to replace the file.
  3. Move or delete the file from the UndeployedFiles directory.  (Any future upgrades will put any locked files in this directory so you will want to clean it up after you move the files)
  4. Start all of the CCS services.

Additional Information

It is recommended to reboot a CCS component (i.e. Application Server, CCS managers, etc) just before upgrading to make sure there are not any files that are in use or locked to avoid this error.

Attachments