Running 'tf history -version:Wworkspace_name' without specifying TFS workspace owner after workspace name (e.g. '-version:Wworkspace_name;owner' causes tf history command to fail since current user under which jenkins service is running will be used as default workspace owner in tf history query.

Here's a sample log with jenkins running under service account on 'BUILDNODE' machine, account is 'DOMAIN\BUILDNODE1$'>

C:\.jenkins\workspace\expiration\src\test\java:
[expiration] $ "C:\Program Files\TEE-CLC-10.0.0\tf.cmd" history $/Common/development/expiration -noprompt -version:D2011-09-05T08:37:14Z~D2011-09-05T08:37:40Z -recursive -format:detailed -server:http://tfs-server:8080/tfs/DefaultCollection/ ********
No history entries were found for the item and version combination specified.
[expiration] $ "C:\Program Files\TEE-CLC-10.0.0\tf.cmd" history . -recursive -stopafter:1 -noprompt "-version:WHudson-expiration-BuildNode1" -format:brief
An error occurred: TF14061: The workspace Hudson-expiration-BuildNode1;DOMAIN\BUILDNODE1$ does not exist.
FATAL: Executable returned an unexpected result code [100]
ERROR: null

Fix is to allways specify workspace owner in versionspec - that should be the same user specified in tfs-plugin to checkout the code, create/delete workspace, etc.