TeamCity 10.0.2 + TFS 2015 Update 3 - Local Workspace?

We have just upgraded from TFS 2010 to TFS 2015 Update 3, migrating onto a new server.

After updating the settings in TeamCity with a new VCR Root and TFS URL, the build fails with the following:

10:36:33] [Updating sources] Will perform clean checkout. Reason: Checkout directory is empty or doesn't exist
[10:36:33] [Updating sources] Cleaning *****
[10:36:33] [Updating sources] Using vcs information from agent file: 6b3989a4_*****.xml
[10:36:33] [Updating sources] VCS Root: ***** (1s)
[10:36:33] [VCS Root: *****] revision: 69114
[10:36:33] [VCS Root: *****] Using .net working mode
[10:36:33] [VCS Root: *****] Clean checkout flag was set by the build agent
[10:36:33] [VCS Root: *****] Receiving workspace
[10:36:34] [Receiving workspace] Using workspace TeamCity-A2-mb2z5b6330j82eq31tvi2ldv52;(TFS server name removed)\TeamCity/(Build server name removed)
[10:36:34] [VCS Root: *****] Updating sources to revision: 69114
[10:36:34] [Updating sources] Failed to perform checkout on agent: Failed to perform TFS clean checkout. [2020-06-09 10:36:34,377] ERROR - JetBrains.TeamCity.Tfs.Program - TF14061: The workspace TeamCity-A2-mb2z5b6330j82eq31tvi2ldv52;Team City does not exist.

I tried using the TF command in C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE to create a workspace of the same name, for the same user and owner, and it produced an error, saying the workspace was remote, and it should be a local workspace.

It is not possible to create a local workspace with the above command, so how on earth did TeamCity build on the previous server? I see no evidence of any workspaces with the above names, apart from in the settings files, in the cache folder, for the build agent(s).

It's not an option to perform further upgrades just yet.


Can anyone help?

1 comment
Comment actions Permalink

My theory is that local workspaces are structured differently for older versions TFS, and the old tool is using the new service and getting confused.

We changed to use check out on server in the end, and we use a fixed path for builds anyway. Also the TeamCity server is the same machine as the build agent - so it worked the same.


Please sign in to leave a comment.