mcdonaldn

When Right Clicking on a folder/file (e.g. $/MyTeamProject/MyProject/mainline) and Clicking on "View History" with Team Explorer we're getting the following Error "No history entries were found for the item and version combination specified"

We can see the files/folders, tree through them, open them but can't do a Get Latest Version on the files/folders. When we do we get the standard message "Files/Folders are already up to date" which is odd as the user interface says "Not Downloaded" under the Latest column in Source Control.

Not surprising, there is nothing in the App Tier's Event Viewer.

I've never seen this error before Has anyone else run into this problem




Re: Team Foundation Server - Version Control "No history entries were found for the item and version combination specified"

mcdonaldn

After a bit more exploration, apparently this error can be caused by lack of permissions on the Source Control folder you get the error on. See here for the details.

I'd argue the error message needs some massaging.






Re: Team Foundation Server - Version Control "No history entries were found for the item and version combination specified"

Richard Berg MSFT

If you don't have the Read permission to an item, we pretend it doesn't exist. This design is consistent throughout TFS. Annoying sometimes, but doing anything else has serious security implications. A lot of customers don't want users to be able to detect that $/SuperSekrit exists if they don't have permission.




Re: Team Foundation Server - Version Control "No history entries were found for the item and version combination specified"

mcdonaldn

Thanks Richard. Is there any reason why you don't send a message like "Unable to Access due to lack of permissions" or something more friendly than "Error: history entries were found for the item and version combination specified"

In my mind, the "Error" message seems to indicate something structurally is wrong verses you simply don't have permissions.

Just my two cents.

Mac






Re: Team Foundation Server - Version Control "No history entries were found for the item and version combination specified"

Richard Berg MSFT

Like I said, it's a security thing. Telling you that the command failed due to lack of permissions would disclose private information -- namely, that an item with that name exists.