• Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 700 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Workspace on mapped network drive not accessible after upgrade

Eric Pruett
Intellectual 1375 points

Host OS (Virtualized in Parallels 10): Windows 7 Professional, Service Pack 1
CCS Version: 6.1.0.00104 

Problem: After upgrading a CCS component (have noticed with ARM compiler and with CCS main upgrade from 6.01 to 6.1), at first launch, CCS fails to find workspaces or link projects which are on a mapped network drive. In my case, the 'network' drive is a mapped drive that comes from the host OS outside of the virtualized Windows OS.

Procedure:

  1. Install CCS
  2. Upgrade CCS component which would normally require the smaller installation window at next CCS launch
  3. Observe smaller automatic installation window at CCS restart
  4. After the installation window closes, an error appears stating that the workspace cannot be found or opened, please select a new workspace
  5. Cancel to close CCS
  6. Reopen CCS, and it finds the workspace just fine.

Tips:

  • If you select a new workspace at furst launch after upgrade instead of quitting, all links to mapped network drives in the first boot after upgrade are automatically mapped to the UNC path instead of the mapped drive letter. When building, compilation fails because windows does not allow cmd.exe to be invoked on a target in a UNC path.
  • TI__Genius 14520 points

    HI Eric, 

    Could you let me know whether the workspace error dialog that you see is like the picture below or is it different? Please adjust paths to match your system. 

    Also, when you mentioned mapped network drive which parallels sharing method did you use?   

    http://kb.parallels.com/en/122567 

  • in reply to MartinS
    TI__Intellectual 1375 points

    Hi MartinS,

    Yes, the dialog box you post is the dialog I receive, with a 'Z:/...' path.

    I am sharing folders from my mac with the 'Shared Folders Tool' listed on the parallels link, selecting 'Home folder only' in the 'Share Folders' drop down from step 3 on that page. My workspace was in a subdirectory of my home folder on my mac.

  • in reply to Eric Pruett
    TI__Genius 14520 points

    Hi Eric, 

    That dialog means that workspace directory is being used by another instance of CCS. You would get the same dialog if you started CCS twice. It does not mean that the folder can not be found. I am speculating as I do not have this setup to reproduce. However, I think when update asks to restart, it terminates CCS (which should remove the "lock" on the workspace) and then starts again, when it starts again either the old process is still there or that "lock" has not been removed yet. I am not sure how mapping works, but may be there is a delay in synchronization of mapped folders due to virtualization. 

    Martin