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.

CCS/MSP-EXP432P401R: CCS Cloud not working on any domain lab computers/domain accounts, only works with local admin account

Part Number: MSP-EXP432P401R

Tool/software: Code Composer Studio

One of the engineering departments are looking to implement using the CCS Cloud for their class for the spring semester.  I have been testing with the professor on attempting to get this installed. 

We are able to install the web browser extension fine and install  the TI Cloud Agent Application fine when on a regular domain user account, however to be able to install the actual application we have to put in a domain administrative account credential.  

I have tested installing the application to a public shared folder created on the root c: and installed within users/public.  However whenever we try to run the Energia Sketch Blink Test while logged into a regular domain account it keeps bringing up the popup stating:

"Could not launch TI Cloud Agent:  Failed to start TICloudAgent.  Please perform the actions listed below and try your operation again"

When I logon with the local administrator account through it works fine, just had to add node.exe through the firewall, which I then added through the domain firewall as well then tested again and still getting the same issue.  

Has anyone had success in installing in a lab domain environment?

  • Hi Mandeep, the link is not working for me, getting a "Server Error in "/" Application" page

  • Hi Luke,
    There was an extra period in the hyperlink above. Try the below:
    e2e.ti.com/.../542779

    Thanks
    ki
  • Thanks for the link correction. Looking at that post:

    "TI Cloud Agent is a per user install. So, your user will not see the install from the local administrator account. You could try to edit the windows registry and add an entry for the user to see the administrator install. You would have to duplicate HKEY_CURRENT_USER\Software\Google\Chrome\NativeMessagingHosts\com.ti.cloudagent from the local administrator account."

    Could you elaborate on this a bit more.

    Are you saying I should duplicate the registry key and edit the Administrator to the profile that will be using it:

    C:\Users\Administrator\AppData\Local\Texas Instruments\TICloudAgent\resources\Chrome\com.ti.ticloudagent.json
  • Hi Mandeep,

    I duplicated the String and changed the profile to the domain profile name that I was testing with. I did this change while logged into the local admin. I logged off then logged into the domain with a domain account and tried it again and the same issues persist. I then looked into the registry while on the domain user and it does not have the key ~\NativeMessagingHosts\ , I attempted trying by adding it manually along with the key "com.ti.cloudagent" and then manually adding the string key with the path to the domain user instead of "Administrator" The issue is still persisting.
  • Sorry Luke. This is all experimental. What did you specify as the install dir path when you installed cloud agent. By default it installs to the user profile. So try the following

    1) move %USERPROFILE%\TICloudAgent to a directory available to all user such as c:\ti\TICloudAgent
    2) Copy C:\Users\Administrator\AppData\Local\Texas Instruments\TICloudAgent\resources\Chrome\com.ti.ticloudagent.json to c:\ti\TICloudAgent as well
    3) update the reg entry to point to the new location of com.ti.ticloudagent.json
    4) update "path" in com.ti.ticloudagent.json to point to c:\\ti\\TICLOU~1/ticloudagent.bat
    5) update "userDataRoot" in c:\ti\TICloudAgent\config.json to be something available to all users as will such as c:\ti\TICloudAgent\deviceSupport. This is where any content downloaded on demand to support a particular device goes, if it hasn't already been installed.

    Note the above steps should make the install available to all user on the machine. However, Adding device support will still require admin access (run kernal drivers), so you may have to run as admin first time just to install device support (debug a device from the admin account to initiate an install). Subsequent uses of the same device by admin or other users will not attempt to install device support and should just work.
  • Thanks Mandeep, I will give this a try tomorrow and update afterwards.
  • No worries. We just don't support this particular use case. However, it has come up a few times and I'll see if support for this could be improved.
  • Thanks for taking the time to help out, it is much appreciated since you guys dont technically support this case.

    I have tried the steps you suggested, however, now when on the local admin account and try to do the test run on the cloud services, I am getting the error of "Spawn ENOENT"

    I then tested on a domain user account, but it is still asking to download the TI CLoud Agent Application.  I checked the registry editor and when logged into a domain account I am not even seeing the HKEY_CURRENT_USER\Software\Google\Chrome\NativeMessagingHosts\ key as it is missing, but shows up when local admin is logged in.  I logged back on to the local admin and now it is asking to install the TI Cloud Agent Application again.

    The steps I used when logged into as local admin:

    1. Installed the extension

    2. Downloaded the Ti Cloud Agent Application

    3. Installed the Ti Cloud Agent Application, but changed the install directory to "c:\ti\TiCloudAgent"

    4. Copied C:\Users\Administrator\AppData\Local\Texas Instruments\TICloudAgent\resources\Chrome\com.ti.ticloudagent.json to c:\ti\TiCloudAgent\

    5. Navigated to HKEY_CURRENT_USER\Software\Google\Chrome\NativeMessagingHosts\com.ti.cloudagent and changed the path to c:\ti\ticloudagent\com.ti.ticloudagent.json

    6. Opened com.ti.ticloudagent.json.  Did not need to change the path as the path was already set to C:\\ti\\TICLOU~1/ticloudagent.bat

    7. Created new folder in root of TiCloudAgent directory called devicesupport

    8. Opened and editted config.json and updated the "userDataRoot" to "C:\ti\TiCloudAgent\devicesupport"

    9.  Refreshed the CSS Cloud and hit run.  Everything seemed to run good and installed drivers to the device support folder, then it threw the "spawn ENOENT"

    Any suggestions?

  • Try creating the "devicesupport" directory.

  • Hi Mandeep,

    You may have missed that I did this already in step 7 of my previous post.
  • Let me see if I can re-create this locally in our test env.
  • Luke,

    So I was able to reproduce this and get it to work. Here are the exact steps I followed. Try the following

    1) Log into Admin account
    2) Uninstall chrome browser extension, delete previous cloud agent install
    3) log into the cloud ide and try to debug your project
    4) Follow prompt to install extension and agent, but install agent into c:\ti
    5) create c:\ti\devicesupport\db directory structure ( make sure this folder structure has write access)
    6) update "userDataRoot" in config.json to "c:\\ti\\devicesupport"
    7) Copy C:\Users\Administrator\AppData\Local\Texas Instruments\TICloudAgent\resources\Chrome\com.ti.ticloudagent.json to c:\ti
    8) go back to the ide and refresh window and try to debug again.

    At this point you should be able to debug as admin user with a fully working shared install under c:\ti

    Now to get it working as non admin user
    1) Log in to the non admin account
    2) run "regedit.exe" and manually add the key (HKEY_CURRENT_USER\Software\Google\Chrome\NativeMessagingHosts\com.ti.cloudagent) and set it to point to c:\ti\com.ti.ticloudagent.json
    4) Log into cloud ide and debug
    5) If the user does not have the extension installed, you will get a prompt to install the extension and agent. ONLY INSTALL THE EXTENSTION
    6) refresh window and everything should work
  • Thank you Mandeep,

    I will give this a try on Monday and post the results.
  • Hi Mandeep,
    I have tried the directions you provided. I was able to debug fine while logged into the local administrator account, however it still does not allow me to run and I still get the same error of:

    Run failed!
    Spawn ENOENT

    When I login as the domain user/nonadmin user, after adding the registry key and pointing it to the com.ti.ticloudagent.json file, then trying to run the debug from the cloud. The popup come sup saying that it could not launch TI Cloud Agent: Failed ot start TICloudAgent, then gives only the option to download and install the application.
  • Can you confirm the location of the com.ti.ticloudagent.json. Can you also check and close any orphaned "node.exe" processes.

  • com.ti.ticloudagent.json is currently located in the root of c:\ti as per the instructions. The full path is c:\ti\com.ti.ticloudagent.json and all the folders and read/write persmissions. There were no node.exe processes running.
  • Working Solution :

    1) Log into Admin account
    2) Uninstall chrome browser extension, delete previous cloud agent install
    3) log into the cloud ide and try to debug your project
    4) Follow prompt to install extension and agent, but install agent into c:\ti
    5) create c:\ti\devicesupport\db directory structure ( make sure this folder structure has write access)
    6) update "userDataRoot" in config.json to "c:\\ti\\devicesupport"
    7) Copy C:\Users\Administrator\AppData\Local\Texas Instruments\TICloudAgent\resources\Chrome\com.ti.ticloudagent.json to c:\ti
    8) go back to the ide and refresh window and try to debug again.

    At this point you should be able to debug as admin user with a fully working shared install under c:\ti

    Now to get it working as non admin user
    1) Log in to the non admin account
    2) run "regedit.exe" and manually add the key (HKEY_CURRENT_USER\Software\Google\Chrome\NativeMessagingHosts\com.ti.ticloudagent) and set it to point to c:\ti\com.ti.ticloudagent.json
    4) Log into cloud ide and debug
    5) If the user does not have the extension installed, you will get a prompt to install the extension and agent. ONLY INSTALL THE EXTENSTION
    6) refresh window and everything should work
  • Mandeep,

    Thanks for all the help, it seems that solution worked with the webex session, however, when I try to replicate that on our lab machines I am getting mixed results. I tested on 4 different machines that have the same image and have not had the TI software installed on it yet. The first one I was able to get it working on the first non admin domain account. However, I wanted to test it when another user logs in so I used a different account, I made sure the registry key was still there pointing to the c:\ti\com.ti.ticloudagent.json. When I went to the cloud IDE to test it gave me the Run Failed! Spawn ENOENT. I then logged back into the first non admin account that had worked previously and then it wasnt working anymore giving the same Run Failed! Spawn ENOENT error.

    I tried the same directions on another lab machine, everything worked fine up until testing with the local account, where It kept bringing up the popup to install the application.

    The same issue happened on the third test machine.

    The issue of Run Failed! Spawn ENOENT. came up on the fourth machine on the first non admin account test.

    It's very odd, I'm wondering if it is something one our end (domain settings/group policies)
  • I forgot to mention, the machine that we tested with the webex session, I logged into another non admin test account and tested and that machine just brings up the popup to download the ticloudagent application.
  • On the working webex session machine did you update the register entry for the second non admin user?
  • I did not update it for the second non admin user, due to I checked the registry before I tried the cloud IDE and saw the NativeMessagingHosts\com.to.tocloudagent key was already there with the path pointing to c:\ti\com.ti.ticloudagent.json already. I exported the registry key from the non admin account that did work that we used and imported into the second non admin account and tried it again, and the popup still comes up.
  • I think I may have figured it out, I was trying to run a .reg file with the exported registry that points to the ticloudagent.json file, however, on our domain in order to run a .reg file it has to be under an administrator account. When I was using my admin account to give permission to run the .reg file on a non admin account, it added the registry to the admin account.

    So I opened regedit in the non admin account which for our domain is not suppose to have privileges to change the registry, and low and behold that registry key was missing. So I manually added it to the registry on the non admin account then tested again and it worked. I will test it on the other PC's as well now.
  • Odd. I am bit out of ideas at this point.. But the popup to install coming up is an indication of something being off in the registry. I'll read a bit more.. but try adding the key under HKEY_LOCAL_MACHINE, that is suppose to work for all user on the machine (see stackoverflow.com/.../add-a-key-to-hkey-current-user-for-all-users)
  • Hi Mandeep,

    Thanks for the resource, I have done a bit of testing and I’ve found at least for me that the registry key is very very temperamental in how it works.  I attempted to try creating the key in the HKLM hive and usually it will work under the local admin or even domain admin profile (doesn’t matter as long as it has admin rights).  However, when you try to login as a non admin domain user the HKLM key does not seem to work as I will still get the Run Failed Spawn EONENT error.  I then tried deleting the HKCU Key as they were both populated in both hives and just use the HKLM key, still the same.

    I then proceeded to try to creating a script file to run a logon script through GPO with a .reg file and a batch script, there were two problems with this, it required user input which caused a blank screen for non admin accounts as they could not gain access the to user prompt.  And even testing with allowing it through on an admin account the CSS Cloud would still give an error even though the registry file under HKCU changed to the correct values.  I then tried running a scheduled task on startup to add the registry file but same issues here.

    I ended up changing to using a REG ADD command in a script, and it ran perfectly without user input, and updated the registry in the HKCU hive.  After much testing it seemed to be working fine, so I put it in the Programdata Startup folder for Win 10 to have it run at startup.  It runs at startup and added the key to the HKCU Hive for each domain user, however the same issues arise of the CSS Cloud giving the same spawn error. 

    After much testing I found that the HKCU entry does not like being tampered with really at all except for once.  I found also that it does not like being changed unless by the actual user logged in vs loading user hives or pushing through third part programs, or GPO, or startup solutions.  The REG ADD script I am using seems to work perfectly if you manually add it, but does not work if you try to use the same exact script through logon scripts/startup.  I believe I found a solution, it’s not ideal but so far it is working, Ill know better once the students return and get a stress test on it.

    Here are the steps I took from a fresh install of our image:

    1. Login to PC with admin account
    2. Go to: https://dev.ti.com and log into the CCS Cloud with Chrome
    3. Input your TI Credentials
    4.  (IF not done, File -> Energia Sketch, open blink test) Click Debug
    5. Popup will come up to install extension and application
      1. Click “Install” browser extension
      2. Click “Download” and install the TI Cloud Agent Application
    6. Open ticloudagent_2_tixds110.exe
      1. Install to c:\ti
    7. Run firewall exception for domain for node.exe
    8. Create folder “devicesupport” in c:\ti root, then create new folder “db” within devicesupport as follows: c:\ti\devicesupport\db
    9. Edit c:\ti\TICloudAgent\config.json to point to devicesupport folder:
      1. "userDataRoot" : "C:\\ti\\devicesupport"
    10. Copy C:\Users\administraiveaccount\AppData\Local\Texas Instruments\TICloudAgent\resources\Chrome\com.ti.ticloudagent.json to c:\ti\com.ti.ticloudagent.json
    11. Point HKEY_CURRENT_USER\SOFTWARE\Google\Chrome\NativeMessagingHosts\com.ti.ticloudagent to c:\ti\com.ti.ticloudagent.json
    12. Give \ti folder permissions
    13. Go back to CCS Cloud, hit refresh 
      1. Two sets of drivers will install, allow them both; requires user input.

    At this point it should be working on admin account,

    1.  When logged into a domain/non admin account run the following command (I use this in a batch file that allows users to just open it and requires no user input):
      1. REG ADD HKEY_CURRENT_USER\SOFTWARE\Google\Chrome\NativeMessagingHosts\com.ti.ticloudagent /d c:\ti\com.ti.ticloudagent.json /F
    2. At this point the user should just goto the CSS Cloud and only install the Chrome extension.

  • Luke McMasters said:

    Hi Mandeep,

    Thanks for the resource, I have done a bit of testing and I’ve found at least for me that the registry key is very very temperamental in how it works.  I attempted to try creating the key in the HKLM hive and usually it will work under the local admin or even domain admin profile (doesn’t matter as long as it has admin rights).  However, when you try to login as a non admin domain user the HKLM key does not seem to work as I will still get the Run Failed Spawn EONENT error.  I then tried deleting the HKCU Key as they were both populated in both hives and just use the HKLM key, still the same.

    I then proceeded to try to creating a script file to run a logon script through GPO with a .reg file and a batch script, there were two problems with this, it required user input which caused a blank screen for non admin accounts as they could not gain access the to user prompt.  And even testing with allowing it through on an admin account the CSS Cloud would still give an error even though the registry file under HKCU changed to the correct values.  I then tried running a scheduled task on startup to add the registry file but same issues here.

    I ended up changing to using a REG ADD command in a script, and it ran perfectly without user input, and updated the registry in the HKCU hive.  After much testing it seemed to be working fine, so I put it in the Programdata Startup folder for Win 10 to have it run at startup.  It runs at startup and added the key to the HKCU Hive for each domain user, however the same issues arise of the CSS Cloud giving the same spawn error. 

    After much testing I found that the HKCU entry does not like being tampered with really at all except for once.  I found also that it does not like being changed unless by the actual user logged in vs loading user hives or pushing through third part programs, or GPO, or startup solutions.  The REG ADD script I am using seems to work perfectly if you manually add it, but does not work if you try to use the same exact script through logon scripts/startup.  I believe I found a solution, it’s not ideal but so far it is working, Ill know better once the students return and get a stress test on it.

    Here are the steps I took from a fresh install of our image:

    1. Login to PC with admin account
    2. Go to: https://dev.ti.com and log into the CCS Cloud with Chrome
    3. Input your TI Credentials
    4.  (IF not done, File -> Energia Sketch, open blink test) Click Debug
    5. Popup will come up to install extension and application
      1. Click “Install” browser extension
      2. Click “Download” and install the TI Cloud Agent Application
    6. Open ticloudagent_2_tixds110.exe
      1. Install to c:\ti
    7. Run firewall exception for domain for node.exe
    8. Create folder “devicesupport” in c:\ti root, then create new folder “db” within devicesupport as follows: c:\ti\devicesupport\db
    9. Edit c:\ti\TICloudAgent\config.json to point to devicesupport folder:
      1. "userDataRoot" : "C:\\ti\\devicesupport"
    10. Copy C:\Users\administraiveaccount\AppData\Local\Texas Instruments\TICloudAgent\resources\Chrome\com.ti.ticloudagent.json to c:\ti\com.ti.ticloudagent.json
    11. Point HKEY_CURRENT_USER\SOFTWARE\Google\Chrome\NativeMessagingHosts\com.ti.ticloudagent to c:\ti\com.ti.ticloudagent.json
    12. Give \ti folder permissions
    13. Go back to CCS Cloud, hit refresh 
      1. Two sets of drivers will install, allow them both; requires user input.

    At this point it should be working on admin account,

    1.  When logged into a domain/non admin account run the following command (I use this in a batch file that allows users to just open it and requires no user input):
      1. REG ADD HKEY_CURRENT_USER\SOFTWARE\Google\Chrome\NativeMessagingHosts\com.ti.ticloudagent /d c:\ti\com.ti.ticloudagent.json /F
    2. At this point the user should just goto the CSS Cloud and only install the Chrome extension.

    After much testing I have confirmed that this method works correctly in a lab/domain environment for multiple nonadmin users.  I will probably test this with deployment options during image creation if this is still needed by the professors in the future. 

    I created a simple batch file to help automate a majority of this (assuming correctly editted config.json file is in the root folder path).  The last two commands are not necessary, they just create a folder ont he public desktop for all users which copies the reg add batch files the nonadmin users will need to use, and also just a .url shortcut link to the CCS cloud.

    @ECHO OFF

    REM Firewall_Exception
    netsh firewall add allowedprogram "C:\ti\TICloudAgent\node.exe" TICloudAgent enable >nul

    REM Create_devicesupport\db_Directory
    if not exist "c:\ti\devicesupport\db\" mkdir c:\ti\devicesupport\db

    REM Copies_Editted_json
    copy /y "%~dp0\config.json" C:\ti\TICloudAgent

    REM Copies_cloudagentjson_To_Correct_DIR
    copy /y "C:\Users\administrative account name here\AppData\Local\Texas Instruments\TICloudAgent\resources\Chrome\com.ti.ticloudagent.json" "C:\ti\com.ti.ticloudagent.json"

    REM Sets_Folder_Permissions
    icacls "c:\ti" /grant Users:(OI)(CI)F

    REM Add_REG
    REG ADD HKEY_CURRENT_USER\SOFTWARE\Google\Chrome\NativeMessagingHosts\com.ti.ticloudagent /d c:\ti\com.ti.ticloudagent.json /F

    REM Create TI Cloud Tools Folder
    if not exist "c:\users\public\desktop\TI Cloud Tools" mkdir "c:\users\public\desktop\TI Cloud Tools"

    REM Copy Icon to c:\windows and puts shortcut and batch on public desktop
    copy /y "%~dp0\ti.ico" "c:\windows\"
    copy /y "%~dp0\TI Cloud - RUN ONLY ONCE.bat" "c:\users\public\desktop\TI Cloud Tools\"
    copy /y "%~dp0\TI Cloud Tools.url" "c:\users\public\desktop\TI Cloud Tools\"

    Thanks for the help Mandeep and pointing me in the right direction, it is much appreciated.

  • Just to update unfortunately this did not work.  It was mixed results where some PCs worked while others still got the SPAWN:EOENT error even thought the installs were all the exact same even on freshly imaged machines where I did the exact same steps on all the machines. 

    If anyone has success for lab deployments in future I would like to hear how you did it or maybe we could collaborate.