Replace Tokens : The task does not carry an implementation that is compatible with your current operating system 'Windows(X64)'

[jamescarters]

2024-11-07T16:27:59.7992242Z ##[error]A supported task execution handler was not found. The task does not carry an implementation that is compatible with your current operating system 'Windows(X64)'. Contact the task author for more details.
2024-11-07T16:27:59.7995027Z ##[section]Finishing: Replace tokens in Set Parameters files

[koeneijkemans]

I had the same issue, but updating the azagent software on my build agent resolved this for me.

[Ztomporo]

I am also having this issue. Seems to be caused from the downgrade of Min Agent version?

[LIbanez23]

I'm having the same issue. Our agents are version 2.181.2 so they're well above the min agent version.

Does anyone have a workaround?

[tegaaa]

@colindembovsky My customer is also having the same issue.

[jdholbrook81]

We're running into this.

Another oddity, it is saying task version 1.2.162?

v1.4.162 (Latest) of the extension is installed, and the latest task version for ReplaceTokens is 1.2.28, so not sure how we got 1.2.162 unless the extension patch overwrites the task patch?

Starting: ReplaceTokens
==============================================================================
Task         : Replace Tokens
Description  : Replaces tokens in a file using RegEx. Values come from any variable defined in the current Environment.
Version      : 1.2.162
Author       : Colin Dembovsky (colinsalmcorner.com)
Help         : [More Information](https://github.com/colindembovsky/cols-agent-tasks/tree/master/Tasks/ReplaceTokens)
==============================================================================
##[error]A supported task execution handler was not found. The task does not carry an implementation that is compatible with your current operating system 'Windows(X64)'. Contact the task author for more details.

[jdholbrook81]

In the event it helps anyone else, I found this (apparently undocumented in the sense I couldn't find it in the rest api docs) rest api call to update agents programmatically and created a script to update all Environment agents as these can't be set to auto-update. Once they were all up to date the minAgentVersion bump was no longer an issue.

https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devops&tabs=yaml%2Cbrowser#how-can-i-trigger-agent-updates-programmatically-for-specific-agent-pool