Workaround: Cannot create a workspace from a snapshot that contains inaccessible components
Michael Valenta
Last Updated: May 24, 2012
Build Basis: Rational Team Concert 4.0
Summary
Using the SCM CLI, the creation of a workspace from a snapshot will fail if the snapshot contains components that are not accessible to the user performing the create operation.
More Information
ProblemExecuting the following command with the SCM CLI will fail if there are components in the snapshot named SnapshotName that are not accessible to the specified user. For example, where the user’s username is “bob”:
scm create workspace --repository-uri https://[server.name]:9443/jazz --username bob WorkspaceName --snapshot SnapshotName
The resulting failure will look something like this:
Problem running 'create workspace': CRJAZ1319E Illegal read access: User "bob" attempted to read item(s) having the following type(s): BaselineWorkarounds
The workaround for this issue is to create the workspace in the RTC Eclipse based client by following these steps:
- Install and start the RTC Eclipse client.
- In the Team Artifacts view, create a repository connection.
- Right-click the connection, select Manage Connected Project Areas from the context menu, then select the project area that contains the stream the snapshot is associated with.
- In the Team Artifacts view, expand the entry for the project area, then expand the Source Control entry.
- Right-click the stream name, and select Show > Snapshots in the context menu.
- In the Search view, right-click the desired snapshot and select New > Repository Workspace from Snapshot in the context menu.
- In the editor that opens, click Save to create the workspace.
Related Information
The following work item contains details about the issue:
Copyright © 2012 IBM Corporation
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means.
Learn more here.