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.

  • Resolved

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

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?

John Hall

MCU Safety & Security Software

If my reply answers your question please click on the green button "Verify Answer"

  • Hi John,

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

    ki

    -----------------------------------

    Did you read the CCS Forum Guidelines & FAQ? If not, PLEASE read it. If you haven't read it in awhile, please read it again to see if any updates were made.

    Having CCS problems? Check out the CCS Troubleshooting Guide

    Looking for CCS Training? Check out the CCS Training Site

    Curious about the status of a bug and know the tracking ID? Track it via the public bug tracking portal

    NOTE: When a bug is filed and a tracking ID is provided, the thread may then be suggested as "TI Thinks Resolved". Why? Please read the first FAQ of the CCS Forum Guidelines & FAQ

  • In reply to Ki-Soo Lee:

    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.

    John Hall

    MCU Safety & Security Software

    If my reply answers your question please click on the green button "Verify Answer"

  • Guru 109290 points

    In reply to John Hall:

    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

     


    If my reply answers your question please click the "This resolved my issue" button

  • In reply to JohnS:

    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 Hall

    MCU Safety & Security Software

    If my reply answers your question please click on the green button "Verify Answer"

  • Genius 13590 points

    In reply to John Hall:

    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.

  • In reply to AndyW:

    Andy,

    Renaming the file worked.  Thanks for the help.

    John Hall

    MCU Safety & Security Software

    If my reply answers your question please click on the green button "Verify Answer"

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.