RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.
Publishing Test from Visual Studio Team System (VSTS) to Team Foundation Server (TFS)
Getting Access Denied
Example
username@servername
(mailto:username@servername)
2008-10-13 2:21:50         0.28 MB           10/13/2008 3:19:14 PM   Failed   Access to the path '\\DropFolder\Buildname_20080723.3\TestResults\fd8883e0-2153-44c6-8671-6d6db460c4a8\uesrname 2008-10-13 _02_21.trx' is denied.
User does not own build he\she is publishing to
In order to Publish test from Visual Studio Team System to Team Foundation Server (TFS), the Build Service account must have full control to the drop folder and the TFS Service account (if not same as build account) must have full control to the drop folder.
Note however users whom don't own the build they are publishing to may get an Access Denied. To get around this, Configure Everyone to have Full Control on the Drop Share
(right-click on the drop folder, select properties, select Sharing Tab, Select Permission button)
Configure the ACLs on the Folder for Read-Only permissions for Everyone or the people you what to publish.
(right-click on the drop folder, select properties, select Security Tab)
This should allow the TFS Service to configure the directory for the person publishing to complete the task. Note, even through we have given Full Control at the Share level, the folder is still protected via ACLs on the folder.
How to: Publish Test Results
http://msdn.microsoft.com/en-us/library/ms182501.aspx
(http://msdn.microsoft.com/en-us/library/ms182501.aspx)
Â
Share Permissions
http://www.windowsecurity.com/articles/Share-Permissions.html
(http://www.windowsecurity.com/articles/Share-Permissions.html)
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALSâ€) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.