Error while replacing updated .dll files during a CCS upgrade or content installation
search cancel

Error while replacing updated .dll files during a CCS upgrade or content installation

book

Article ID: 170903

calendar_today

Updated On:

Products

Control Compliance Suite Control Compliance Suite Standards Server

Issue/Introduction

Control Compliance Suite (CCS)

When you upgrade CCS 12.6.x components, or applying a SCU to update the content, it is possible that some .dll files in the installation package are not upgraded if they are currently in use or locked at the time of the upgrade or installation. The following error may be displayed in the console, but not always, especially if you use LiveUpdate to upgrade the CCS components:

Error while copying the file <filename>. Refer to the installation logs for details.
The file can be located at the temporary location: <file location>. Copy the file, and then delete it from the temporary location.

Example of the error below: (the same error will still occur in CCS 12.5.x and 12.6.x)

Environment

CCS 12.6.x Product Update (PU) upgrades or Security Content (SCU) upgrades

Resolution

From SCU 2017-3 onwards, if a .dll file is not replaced or upgraded successfully during CCS upgrade/installation, the new file is saved in the 'UnDeployedFiles' folder to be replaced manually.

The Undeployed Files folder is created at the following location:

<CCS Installation Directory>\Symantec\CCS\Reporting and Analytics\UnDeployedFiles

This folder contains the .dll files that are not replaced because they are in use by another process during the upgrade/installation. The folder also contains the Details.txt file. The Details.txt file provides the following information:

  • Date and time when the UnDeployedFiles folder was created
  • Name of the .dll file that is not installed successfully
  • Location where the .dll file needs to be replaced

You must manually replace the .dll files at the respective locations. To replace the undeployed .dll files, do the following:

  1. Stop ALL of the CCS Services on the affected CCS component (Application Server and/or Manager).
    See the following KB on the correct order to stop and restart the CCS services:
    The correct order to stop and start the services for the CCS Application Server
  2. Copy the .dll files from the Undeployed Files folder.
  3. Replace the files to the respective locations as per the Details.txt file.
  4. Start the CCS Services that were stopped in Step 1.
  5. Delete the UndeployedFiles folder.