"Could not find a part of the path" error - TFS On-Premises

[johndpalm]

I can't get the Tokenizer to work. It appears to attempt to access a temp file that is not being created. I've checked the build server and no subfolders are being created below the 1.1.1 directory. There is not further detail in the logs.

Starting task: Tokenizer: Transform Source filename

---

Executing the powershell script: E:\agent\tasks\Tokenizer\1.1.1\tokenize.ps1
Environment: default

Could not find a part of the path 'E:\agent\tasks\Tokenizer\1.1.1$\SharkTank\SharePoint\SharkTank.App.Theme\SharkTank.App.Theme-dev\SharkTank.App.Theme\AppManifest.xml.tmp'.

Cannot find path 'E:\agent\tasks\Tokenizer\1.1.1$\SharkTank\SharePoint\SharkTank.App.Theme\SharkTank.App.Theme-dev\SharkTank.App.Theme\AppManifest.xml.tmp' because it does not exist.

Cannot find path 'E:\agent\tasks\Tokenizer\1.1.1$\SharkTank\SharePoint\SharkTank.App.Theme\SharkTank.App.Theme-dev\SharkTank.App.Theme\AppManifest.xml.tmp' because it does not exist.

Cannot find path 'E:\agent\tasks\Tokenizer\1.1.1$\SharkTank\SharePoint\SharkTank.App.Theme\SharkTank.App.Theme-dev\SharkTank.App.Theme\AppManifest.xml.tmp' because it does not exist.

---

Finishing task: Tokenizer

---

Task Tokenizer failed. This caused the job to fail. Look at the logs for the task for more details.
Worker Worker-a740cbb8-b10b-4cba-8bb2-6f69a7bed906 finished running job a740cbb8-b10b-4cba-8bb2-6f69a7bed906

[zevanreg]

I faced this problem also. The cause is that when DestinationPath parameter is relative (e.g. $/Default/Solution/Project/TestFile.xml) it comes to tokenize.ps1 not resolved as it is in SourcePath:

2016-07-26T10:28:03.9101847Z SourcePath = C:\agent_work\2\s\Solution\Project\TestFile.xml
2016-07-26T10:28:03.9131880Z DestinationPath = $/Default/Solution/Project/TestFile.xml

In addition - this happens only when adding tokenizer task in Build definition. When adding tokenizer task in Release definition - it works just fine and DestinationPath is being resolved correctly.

[harshil93]

I will take a look at this. This seems to be a TFVC specific problem.