The item $/{CompanyName}/Drops may not be cloaked because it does not have a mapped parent. (type WorkingFolderException)

Question

I'm facing the same issue as this one on Team Foundation Service Preview. My gated Check Ins are failing as build fails. Team is not able to commit code. Any quick help is appreciated.

I can also provide with error logs. So let me know if needed. Error Details are below.

Exception Message: The item $/{CompanyName}/Drops may not be cloaked because it does not have a mapped parent. (type WorkingFolderException)
Exception Stack Trace:    at Microsoft.TeamFoundation.Client.Channels.TfsHttpClientBase.HandleReply(TfsClientOperation operation, TfsMessage message, Object[]& outputs) in d:\a1\dd\alm\tfs_core\Framework\Client\Channels\TfsHttpClientBase.cs:line 670
   at Microsoft.TeamFoundation.VersionControl.Client.Repository.CreateWorkspace(Workspace workspace) in d:\a1\dd\alm\tfs_core\SourceControl\Client\Proxy\Repository.cs:line 130
   at Microsoft.TeamFoundation.VersionControl.Client.Client.CreateWorkspace(CreateWorkspaceParameters cwp) in d:\a1\dd\alm\tfs_core\SourceControl\Client\Client.cs:line 2183
   at Microsoft.TeamFoundation.Build.Client.BuildClientUtil.CreateWorkspace(VersionControlServer versionControl, String name, IEnumerable`1 folders, String comment, IEnumerable`1 wsSecurity) in d:\a1\dd\alm\tfs_core\Build\Client\BuildClientUtil.cs:line 53
   at Microsoft.TeamFoundation.Build.Workflow.Activities.TfCreateWorkspace.Execute(CodeActivityContext context) in d:\a1\dd\alm\tfs_core\Build\Workflow\Activities\VersionControl\TfCreateWorkspace.cs:line 67
   at System.Activities.CodeActivity`1.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
   at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)

Inner Exception Details:

Exception Message: The item $/{CompanyName}/Drops may not be cloaked because it does not have a mapped parent. (type SoapException)SoapException Details: <detail serveritem="$/{CompanyName}/Drops">
Exception Stack Trace:</detail>

---

.Net Developer

Answer 1

Does this issue with TFSP relate to the integration toolkit at all? What are you doing when you get the error message? Did this used to work? If so, what changed just before the break?

---

Trevor Hancock (Microsoft)
Please remember to "Mark As Answer" the replies that help.

Answer 2

I think one of the team member stopped a build while it was in progress for long time. And then this problem came up.

---

.Net Developer

Answer 3

IsmailS,

Is this issue still happening? If so, have you tried to recreate the build definition?

---

Trevor Hancock (Microsoft)
Please remember to "Mark As Answer" the replies that help.

Answer 4

The issue is solved now. It was solved by somebody else so I don't know the solution. Anyway, I think either this should not be expected when a running build is stopped or if it cannot be avoided then, the stop button should not be provided in first place.

---

.Net Developer

Answer 5

If you can find out what was done to fix this and reply back, I am sure the community as a whole would appreciate it. Thanks for the reply though, just the same.

---

Trevor Hancock (Microsoft)
Please remember to "Mark As Answer" the replies that help.

Answer 6

I've got the same problem. Happens after about 15 seconds.
Exception Message: The item $/{teamprojectnamegoeshere}/Drops may not be cloaked because it does not have a mapped parent. (type WorkingFolderException)

Anyone got a solution?

edit: might have something to do with the workspace settings, I selected the $/{teamprojectnamegoeshere}/Development folder because I only want that branch.

Answer 7

Looks like a bug, or are branches not supported?

If you set the workspace to the path of the Branch, you get the 'drops...' error.
If you set it at root, you don't get the error, but CI builds fire for all branches (plus all branches are 'downloaded' before build)

Answer 8

Anyone know why their needs to be a "Cloaked" Workspace defined for the drops folder? I noticed that some of my other builds did not have this so I deleted it and I have no issues with the error message, or with the build, including building branchs.

---

Thanks Noel

Answer 9

It does indeed work without the cloak of the drops folder. I thought the drop might not be available through source control in that case, but it is.

I now have the workspace set to the branch instead of the root and removed the cloak. Both development and main build are good now.

Answer 10

I solved this issue ... i hope :)

You need set in Build definition - Workspace  two rows:

Row 'Active' must be set to Team Project Source Control root folder = $/{CompanyName}
Row 'Cloaked' is set by TF Service to folder "$/{CompanyName}/Drops" and must be mapped as child of 'Active' row. A 'Cloaked' folder cannot be cloaked if the folder does not have a mapped parent (for example, $/parent/child can only be cloaked if there is a mapping for $/ or $/parent).

In next settings "Build Defaults" I set :

 ..... and ... Build succeeded!

Info about TF Service Builds : http://tfs.visualstudio.com/en-us/learn/build/setup-ci-build-in-vs