pendingchanges.tf1 cannot be found

java.io.FileNotFoundException: {project-path}\$tf\pendingchanges.tf1 (The system cannot find the path specified)

I have never seen this issue before. I am generally able to track them down but not in this case. Hoping you can help.

I will attach build log. The solution file is fine. I have other solutions building fine. This one is an older build though, a .Net project. I am able to open and build using VS 2022. 

0
4 comments
Hi,

The error message indicates that your build process is attempting to access the file pendingchanges.tf1 under \$tf\, but the file does not exist. This issue is likely related to Team Foundation Version Control (TFVC), which is part of Azure DevOps.

The file pendingchanges.tf1 is associated with TFVC’s workspace tracking. To resolve this issue, ensure that the workspace is correctly mapped and initialized:

- Run tf workspace in a Developer Command Prompt to verify workspace mappings.
- Run tf workspaces /s:{server-url} to check workspace details.

Additionally, outdated or corrupt TFVC cache can cause issues. If possible, clear the workspace before running the build again.

If the issue persists, please:

- Attach the build agent log and build log.
- Confirm whether the build is running on a build agent.

Files can be uploaded via https://uploads.jetbrains.com/. Please let us know the exact id after the upload.

Best Regards,
Tom
1

I deleted the Team City workspace. This fixed the problem for a few builds but now its back. Reporting a different file. I am sure this has something to do with the TFS system as you explained.

Failed to perform checkout on agent: Failed to checkout repository version 9975: java.io.FileNotFoundException: C:\TeamCity\buildAgent\work\d6bfde4a44d9c944\Code\ApiBridge.sln\$tf\0\095e0600-fa91-4ee3-9485-c04900bf272d.gz (The system cannot find the path specified)

I have again dumped the whole workspace and watched as Team City made a new one. This time it still kicked out the error. Is there another cache location that I should clear?

0

I uploaded the full log 

Upload id: 2025_06_05_26xCpDKDDAdLm7UdR4w81U (file: Brisk_-_Development_DEV_-_Bridge_Service_1472.log)

0

Hi Hal,

Could you please try deleting the following items to ensure a clean state:

1. Clear the TFS workspace

  • Open the Developer Command Prompt for Visual Studio.
  • Run the following command to list all workspaces on the agent machine:
tf workspaces /owner:* /computer:<agent-machine-name>
  • Identify the workspace with a name like TeamCity-<hash>, then delete it:
tf workspace /delete TeamCity-<hash>

If this VCS root is used by multiple agents, repeat the above steps for each one.

2. Delete the TeamCity agent-side VCS cache

On the build agent machine, delete the following directory:

C:\TeamCity\buildAgent\system\caches\tfs

This folder contains the cached .gz patch files used by TeamCity.

Best Regards, 

Tom

0

Please sign in to leave a comment.