TFS 2010 / Build / Custom Workflow / CreateDirectory Activity - by Aleks

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 687392 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 9/6/2011 8:23:22 AM
Access Restriction Public
Moderator Decision Sent to Engineering Team for consideration

Description

Hi,

I'm currently creating custom Build and I'm using the CreateDirectory Activity to create a folder on a remote computer.

The build server and the remote computer are on the same domain. The build is run using 'MyDomain\TFS_Service' account.

On the remote computer, the share where the build should create a directory is configured in order that 'MyDomain\TFS_Service' account has full control (share and local permission).

When I run the build, I get : Failed to create directory '\\remotemachine\Share\Directory2Create'.  User 'MyDomain\TFS_Service' needs write permissions to the path.

Workaround : In the "Share permissions" of the remote computer shared folder, give the tfs build server machine the full control has explain in part 8, second bullet of this link : http://msdn.microsoft.com/en-us/library/bb778394.aspx
Sign in to post a comment.
Posted by Justin [MSFT] on 9/27/2011 at 7:05 AM
I tried this on my machine and it works. Please verify that your build service account does have permissions. A good way to check this is to log into the build machine using those credentials and attempt to create the directory manually.

If that doesn't lead you to the problem, please contact Microsoft Product Support.
Posted by Aleks on 9/22/2011 at 7:13 AM
I added an attachment with a screenshot of the Build server configuration. It is not using Network service account. It is using TFS_Service account as explained.
Posted by Jim [MSFT] on 9/21/2011 at 7:45 AM
Based on this comment:

Workaround : In the "Share permissions" of the remote computer shared folder, give the tfs build server machine the full control has explain in part 8, second bullet of this link : http://msdn.microsoft.com/en-us/library/bb778394.aspx

It looks like the Team Foundation Build Service is running as "Network Service" on the build machine rather than 'MyDomain\TFS_Service'. That would explain the behavior you're seeing. Please use the Team Foundation Administration Console on the Build Server to verify the identity the Build Service is running as and verify that your permissions are configured appropriately.
Posted by MS-Moderator09 [Feedback Moderator] on 9/18/2011 at 11:40 PM
Thank you for submitting feedback on Visual Studio 2010 and .NET Framework. Your issue has been routed to the appropriate VS development team for review. We will contact you if we require any additional information.
Posted by MS-Moderator01 on 9/6/2011 at 8:42 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)