This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Error creating feature blocking all attempts to update from 4.2.4.00032 to 4.2.4.00033

Other Parts Discussed in Thread: CCSTUDIO

When trying to update from CCS v4.2.4.00032 to v4.2.4.00033 the following error is blocking all attempts to update:

Current configuration contains errors that are not corrected by the requested operation and more errors would be introduced. See details for more information.
  ----- Current configuration problems -----
    Error creating feature "file:/D:/Program Files (x86)/Texas Instruments/ccsv4/eclipse/features/com.ti.ccstudio.hercules.emu_4.2.4.0002/". [D:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\features\com.ti.ccstudio.hercules.emu_4.2.4.0002\feature.xml (The system cannot find the path specified)]
  ----- Configuration problems after the operation -----
    Error creating feature "file:/D:/Program Files (x86)/Texas Instruments/ccsv4/eclipse/features/com.ti.ccstudio.hercules.emu_4.2.4.0002/". [D:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\features\com.ti.ccstudio.hercules.emu_4.2.4.0002\feature.xml (The system cannot find the path specified)]

This occurs when any 1 item is selected to update, whether it is from the web or local file.

How do you modify your local configuration to remove this error?  Or what steps do I need to do to resolve this?

  • Hi John,

    Is D:\ your system drive or did you create the D:/Program Files (x86) directory on your own?

    ki

  • My system drive is c:\.  I created d:\program files (x86) on my own.  By pure happenstance, on this Win7 machine, it has mitigated the UAC issues by doing so.

  • For win7 users we strongly advise not to install in program files due to UAC blocking writes to the folder during program operation.  When you are downloading updates the update process downloads the update packages to your installation directory (doesn't matter if the update site is remote or local) and then runs the installers (which also in turn write to the installation directory).  That first step typically fails on Win7 with UAC on.

    The fact that you created a different program files (x86) and still hit this is odd but windows could be applying this behavior to any directory with that name.

     

    John

  • Actually John I think this has nothing to do with UAC, but with artifacts from previous installer testing.  I just need to know where the config is that initiates the above error and remove it.

  • John,

    Could you rename your ccsv4\eclipse\configuration\org.eclipse.update folder to something else (ccsv4\eclipse\configuration\org.eclipse.update.tmp, for example) and let us know if that helps?  A more blunt approach is to move everything in ccsv4\eclipse\configuration but the .ini file into a temporarly location and let it be rebuilt.

  • Andy,

    Renaming the file worked.  Thanks for the help.