• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 39 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

DRA829J-Q1: CCS 10.1.1.00004 unattended installer hangs under LocalSystem (SCCM)

franziskus
Genius 9050 points

Part Number: DRA829J-Q1
Other Parts Discussed in Thread: CCSTUDIO

Hi,

my customer is facing issues with installing CCS:

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

We are facing a deployment issue with Code Composer Studio 10.1.1.00004 silently installed via SCCM (PSADT, LocalSystem context) on Windows 10/11 x64.

 

Command used:

```

ccs_setup_10.1.1.00004.exe --mode unattended --unattendedmodeui none --prefix C:\ti\ccs1011 --debuglevel 4 --debugtrace C:\Windows\Temp\ccs_install.log

```

 

Symptom: the installer never returns control to the calling script. No exit code is produced, SCCM stays "In progress" until timeout. However, the installation itself completes successfully (`ccstudio.exe` present, registry key created, CCS works after a manual reboot).

 

Logs show:

- `bitrock_installer_*.log`: `installed successfully`, sometimes followed by `Reboot required: true`.

- `ccs_install.log`: `CCS_WARNING: Can't create ... CCSExternalReferences` and a trailing `<errorDump>` block.

 

We suspect the post-install `CCSExternalReferences` step spawns a JVM that resolves `user.home` to `C:\Windows\System32\config\systemprofile` under LocalSystem and stays orphaned, preventing the wrapper from exiting.

 

Already tried, without success: overriding `USERPROFILE`/`HOMEDRIVE`/`HOMEPATH`, pre-creating the target folders in `System32`/`SysWOW64`/`Sysnative`, increasing the SCCM run time, reproducing locally with `psexec -s` (same behavior, so it's not SCCM-specific).

 

Could you please tell us:

1. Is this a known behavior of the CCS 10.x unattended installer under LocalSystem?

2. Is there a flag to disable the `CCSExternalReferences` post-install step, or to force the JVM `user.home`?

3. What is the official list of return codes, and the expected code when a reboot is required?

4. Is this fixed in a later CCS release?

 

Logs available on request (`ccs_install.log`, `bitrock_installer_*.log`, SCCM `AppEnforce.log`).

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

Best regards

  • 0
    TI__Guru**** 484311 points

    Hello,

    franziskus said:
    1. Is this a known behavior of the CCS 10.x unattended installer under LocalSystem?

    I am not aware of such an issue with that version of the installer

    franziskus said:
    2. Is there a flag to disable the `CCSExternalReferences` post-install step, or to force the JVM `user.home`?

    There is not.

    franziskus said:
    3. What is the official list of return codes, and the expected code when a reboot is required?

    I am not aware of any such list.

    franziskus said:
    4. Is this fixed in a later CCS release?

    I do not recall any such fix.

    However I would encourage trying a later CCS version. CCS 10.x is very old and no longer supported. Is there any particular reason why you are looking to install such an old version?

    Thanks

    ki