Power Platform Install Tools task failing on Windows x64

[mpil]

In version 2.0.40 of build tools, the "Power Platform Install Tools" task started failing on self-hosted agents with Windows x64. It was working fine in version 2.0.33.

We have temporarily switched to Azure Pipelines with ubuntu-latest image which has fixed this.

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.

[LMSSonos]

same issue with the new release. any way to force to install the older version?

[mpil]

@LMSSonos I think it automatically installs the newest version for a given organisation and you can't change the version it uses:

[theofilomoraes]

@LMSSonos I think it automatically installs the newest version for a given organisation and you can't change the version it uses:

I also think this happens because you can´t set the version, only select the 2. or 1..

[theofilomoraes]

This error is also happening here

[tehcrashxor]

v2.0.40 moved from the 2+ year out-of-support Node 10 runner to Node 16, so my guess is that Node 16 isn't installed on your self-hosted agents.

FYI, @anpetroc

[petrochuk]

For selfhosted we do have older VSIX assets of the extension which can be used: https://github.com/microsoft/powerplatform-build-tools/releases

Here are the changes @tehcrashxor is talking about:

https://github.com/microsoft/powerplatform-build-tools/pull/424

https://github.com/microsoft/powerplatform-build-tools/pull/436

[LMSSonos]

Thanks, I worked around using the old version like this in the pipeline

 - task: PowerPlatformToolInstaller@2.0.33 
    displayName: "Power Platform Tool Installer"

[petrochuk]

Some background: https://devblogs.microsoft.com/devops/node-runner-update-guidance-for-azure-pipelines-task-authors/

For customers who do not want to run End-of-Life versions of Node, we provide the pipelines-agent-* release feed that excludes Node 6. By March 2023, this feed will exclude Node 10 as well as Node 6. Customers that install this (self-hosted) agent can only run tasks that use a non-EOL runner (Node 16 today). Any tasks not updated to use Node 16 will fail for agents deployed from this release feed.

Later in 2023, we will start removing End-of-Life Node runners from our Hosted agents as well We will provide a method for customers to still use tasks dependent on the Node End-of-Life runners before we remove those runners from Hosted agents.

[Robinson308]

I am seeing the same error on our self-hosted agents. I have upgraded Node.js to v18.17.1 on one agent & restarted. Power Platform Install task is still failing however - what else do I need to do to fix this?

[sashi-inss]

I have done below so far in our self hosted agent and problem still persists, any further suggestion?

• Upgraded the agent to latest
• Updated the operating system
• Installed the Node.JS 16.x inside the agent
• added Node Tool install (16.x) task to the pipeline

[petrochuk]

@sashi-inss can you enable diagnostics on your pipeline run and share log files?

[quaresma-cq]

Same error here.

[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.

• Self-Hosted windows agent - Failed
• Azure windows server latest agent - Failed
• Azure ubuntu latest agent - Success

[sashi-inss]

@sashi-inss can you enable diagnostics on your pipeline run and share log files?

log.txt

[petrochuk]

It is not clear from the log Agent's architecture. I understand the machine is x64 but what about the Azure DevOps agent?

[sashi-inss]

The issue has been fixed for us after upgrading the DevOps Agent to latest version, below is the link for latest version https://vstsagentpackage.azureedge.net/agent/3.225.0/vsts-agent-win-x64-3.225.0.zip

[petrochuk]

Just heads up notice that Node 16 is on accelerated deprecation path as well.

https://github.com/microsoft/azure-pipelines-agent/issues/4239

[ericregnier]

The issue has been fixed for us after upgrading the DevOps Agent to latest version, below is the link for latest version https://vstsagentpackage.azureedge.net/agent/3.225.0/vsts-agent-win-x64-3.225.0.zip

This worked for me as well!

[quaresma-cq]

Fixed just updating the agent

[Robinson308]

Updating the Agent version to 3.225.0 fixed it for me also.