Dienstag, 24. Januar 2012 01:55
One of our users is getting the following error when trying to use the "diff" feature via the diff.aspx page:
TF14019: The changeset 134134 does not exist.
The URL she is trying to access in this case is:
This feature does work for others. She can do a "compare" via both the web client and in Visual Studio 2010. To see if it is a permissions issue, we temporarily added her to the Project Administrators group for the TFS project. This didn't work. Any advice would be greatly appreciated.
Dienstag, 24. Januar 2012 17:20
What happens when she tries to open that changeset (CS134134) using Team Explorer?
Dienstag, 24. Januar 2012 19:32
The changeset doesn't actually exist. The changeset before 134135 is 133456, and there's nothing in between. She is able to open the changesets that do exist in Team Explorer.
For users that have this working, the diff.aspx would search for the previous changeset and display the diff between the current changeset (134135) and that previous one (133456). But for her it shows that error.
Mittwoch, 25. Januar 2012 03:20Moderator
Thanks for your post.
Do you mean that she can open changeset 134134 in Team Explorer on her client? If yes, can she compare the changeset 134135 with changeset 134134 with no error?
Please logon other clients using her account, then try to reproduce that scenario on that client, if diff.aspx works fine on other client, it seems that issue only relate to client, please clean the Cache on her client, and try again.
we can clean the Cache manually:
1. Clean the Cache folder on client computer. The folder path is: C:\Users\username(Team Explorer user name)\AppData\Local\Microsoft\Team Foundation\3.0\Cache(os: Windows Server 2008 R2)
2. Clean the Cache folder on Server machine. The folder path is: C:\Users\username(Web access user name)\AppData\Local\Microsoft\Team Foundation\3.0\Cache(os: Windows Server 2008 R2)
3. After cleaned, on Server machine, click Start and select Run… to open the dialog box, then input iisreset.exe and click OK, wait it run completely.
John Qiao [MSFT]
MSDN Community Support | Feedback to us