TFS Integration Tools - Issue: Unable to resolve conflict as Access to the path is denied

TL;DR; Explains how changing WorkSpaceRoot in TFS Integration Tools can cause access denied errors and details how to fix permission issues by updating folder rights.

Published on 28 August 2012

Written by Martin Hinshelwood

1 minute read

https://nkdagility.com/resources/5Bzu9VOxj_C

If you change the WorkSpaceRoot in “C:Program Files (x86)Microsoft Team Foundation Server Integration ToolsMigrationToolServers.config” you may get an access to path is denied when manually resolving conflicts as per TFS Integration Tools – Issue: TF10141 No Files checked in as a result of a TFS check-in failure .

Figure: Sorry we were unable to resolve the conflict

Applies to

TFS Integration Tools, version 2.2, March 2012

Findings

If you altered WorkSpaceRoot in MigrationToolServers.config because you encountered some path problems then you will not have the correct permissions on the folder.

Figure: Permission for TFSIPEXEC_WPG is missing

This is because when you changed the path the TFS Integration Platform did not add the required permissions to it.

Solution

Add the TFSIPEXEC_WPG permission to the folder with full rights.

Figure: Model dialog galore

Once you have added permissions you will be able to resolve the conflicts…

Connect with Martin Hinshelwood

If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.

Our Happy Clients

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.