CCS error: “HRESULT E_FAIL has been returned from a call to a COM component”.


Article ID: 156004


Updated On:


Control Compliance Suite Windows


Unable to run asset import jobs, data collections, or some queries directly on the CCS Data Collector. 

Inside of the CCS console the job will fail with the error:

              “HRESULT E_FAIL has been returned from a call to a COM component”.

 This same error may be displayed inside of the RMS console for queries that contain registry checks

  “HRESULT E_FAIL has been returned from a call to a COM component”.


Eight dot 3 naming is not enabled on the volume (drive) that the Data Collector (AKA Information server) is installed on.   The particular query being run required compression and the compression utility being used on the Information server uses 8.3 (short) path names.  Because the compression utility cannot locate the query result files it cannot compress them.  However the information server is looking for the results to be in a compressed file format and when it cannot locate the compressed files the results are then unavailable.



1. Go to the root of the drive that the Data Collector Information server is installed on.

2. Type the command:  dir /x

     ---- Output showing the shortname of the folders present on this drive should display along with the long folder names. 

For example if the Information server was installed somewhere on the F: drive:

 F:\>dir /x
 Volume in drive F is New Volume
 Volume Serial Number is 48CC-090B

 Directory of F:\

03/09/2012  02:14 PM    <DIR>          PROGRA~1     Program Files
               0 File(s)              0 bytes
               1 Dir(s)  21,243,781,120 bytes free


If the short folder names such as PROGRA~1 do not display then your registry settings for the "NtfsDisable8dot3NameCreation" key need to be changed.  This key is located in your registry at:  HKEY_LOCAL_MACHINE_SYSTEM\CurrentControlSet\Control\FileSystem


WARNING: The possible settings for this key are dependent on the OS.  For Windows 2003 and 2008 systems the keys can be either of the following:

            0 - Enable 8dot3 name creation on this volume

            1 - Disable 8dot3 name creation on this volume


        For Windows 2008 R2 there are now four settings:

            0 - Enable 8dot3 name creation on all volumes on the system

            1 - Disable 8dot3 name creation on all volumes on the system

            2 - Set 8dot3 name creation on a per volume basis
            3 - Disable 8dot3 name creation on all volumes except the system volume

      Furthermore on Windows 2008 R2, line commands using the "fsutil" utility can be used to set this registry key.  These same commands are not available in Windows 2003 or base Windows 2008 OS. 

      Here is the syntax for using the fsutil command to change 8dot3 naming in the file system:

                         fsutil 8dot3name set

                         usage : set [0 through 3] | [<Volume Path> 1 | 0]

                         Note: if you specify a volume in the command then you would need to make the setting equal to a "2" as per the above choices.



3. Make sure that everything that is running from F:\ Program Files (x86)” or its child folder is closed on that machine. This includes all services, command prompts, folders and files. This step is to ensure that you done get “Access is denied” error when executing below command.

4. Open command prompt as Administrator

5. Goto F: drive on command prompt

6. Make sure that you are at root of F: drive and then run the following command...

    fsutil file setshortname “Program Files (x86)” “Progra~1”

7. If the command succeeds, you don’t get any message and you will be returned to F:\> prompt.  Just to cross verify that the command succeeded run the   dir prog* /x    command. In the output of the command verify that you should see a shortname. If short name is visible in the output it means that the problem is solved


CAVEAT:  Domain Group Policies can push down settings for 8dot3 naming convention.  If you set this registry key but find that shortnames do not appear on the volume, then it is possible that the setting is being overridden by a GPO.  This particular setting is not normally visible in the Local Machine policy without expanding the machine policy browser on the machine.   Check with the Active Directory administrator whether they have enabled a restriction on 8dot3 naming via the Group Policy.