Workaround: Known issue with tracking changes in a sandbox loaded directly under the drivePublished/Last Updated: September 18, 2009
Author: Priyadarshini Gorur
Client: Rational Team Concert 22.214.171.124 client for Microsoft Visual Studio IDE
When using Rational Team Concert 126.96.36.199 client for Microsoft Visual Studio IDE, when you load a repository workspace directly under the drive, for example C:, the Pending Changes view stops tracking changes the moment you open a shared solution from the sandbox. You also cannot share a new solution. Most source control operations available from Solution Explorer fail.
- You have opened a shared solution, for exmple C:WindowsFormsApplication1WindowsFormsApplication1.sln, and have logged into the corresponding repository, but Pending Changes view still displays the informational message, "Either there are no active workspaces to be tracked or you are not logged into repository."
- Clicking Refresh in Pending Changes view fails with the error "Sandbox C: is not registered, unable to compute pending changes"
- Invoking Show History from the Solution Explorer context menu on a file in a shared solution fails with the error "Resource is not shared with Jazz Source Control."
- Sharing a new solution fails with the error "Cannot nest CFAs C:/ and C:/WindowsFormsApplication2"
The sandbox discovery mechanism written in the Visual Studio client is flawed, and fails for the case where the drive itself, for example C:, is used as the sandbox.
Diagnosing the problem
If you have opened a solution from C:WindowsFormsApplication1WindowsFormsApplication1.sln, for example, go up the folder hierarchy until you locate the .jazz5 folder. If .jazz5 is found directly under C:, then the problem will exist.
Resolving the problem
Close the Visual Studio instance with the problematic solution. Delete .jazz5 and any loaded folders from directly under the C: drive, for example, and backup your work if you have unresolved changes. Load the desired repository workspace again into a folder under the drive, for example C:Sandbox, and open the solution from there. You should now not see any problems listed in the Symptom section anymore.
See the following pages for more information: