.NET SDK 9.0.307: error MSB4216 "could not create or connect to a task host"

[askpt]

Describe the bug

A clear and concise description of what the bug is.

I am getting this error:
error MSB4216: Could not run the "ReplaceTokenInFileTask" task because MSBuild could not create or connect to a task host with runtime "NET" and architecture "x64". Please ensure that (1) the requested runtime and/or architecture are available on the machine, and (2) that the required executable "C:\Program Files\dotnet\sdk\9.0.307\MSBuild.dll" exists and can be run.

To Reproduce

https://github.com/open-feature/dotnet-sdk-contrib/actions/runs/19278703597/job/55124682365

Exceptions (if any)

Further technical details

details of dotnet --info

This started to happen with the SDK version 9.0.307. Downgrading to 9.0.306 or upgrading to 10.0.100 fixes this issue as you can see here: open-feature/dotnet-sdk/pull/636

It seems it is not isolated per comments here: dotnet/core#10155 (comment), so I would assume it is not related to reqnroll.tools.msbuild.generation.

It is only happening in the Windows runners. Ubuntu and MacOS work fine.

Previous runs:
9.0.307 -> https://github.com/open-feature/dotnet-sdk/actions/runs/19275629307
10.0.100 -> https://github.com/open-feature/dotnet-sdk/actions/runs/19275919896
9.0.111 -> https://github.com/open-feature/dotnet-sdk/actions/runs/19276071981

[marcpopMSFT]

@michalbrabec @rainersigwald for visibility as there are a couple of reports of this: dotnet/core#10155 (comment)

[dessyordanova]

Hello,
We have similar reports from our customers for different Telerik products:
https://www.telerik.com/forums/pipeline-issue-related-to-telerik-licensing-after-upgrading-to-latest-net-9-sdk
https://www.telerik.com/forums/error-reporting-while-creating-build-throught-git-hub-ci-process

[YuliiaKovalova]

ticket with the repro : reqnroll/Reqnroll#921

[marijnbos]

There’s a workaround mentioned in this thread: https://www.telerik.com/forums/telerik-licensing-incompatible-with-netsdk-9-0-307. It involves adding a global.json with the following content:

{
  "sdk": {
    "version": "9.0.306",
    "rollForward": "disable"
  }
}

[askpt]

There’s a workaround mentioned in this thread: https://www.telerik.com/forums/telerik-licensing-incompatible-with-netsdk-9-0-307. It involves adding a global.json with the following content:

{
  "sdk": {
    "version": "9.0.306",
    "rollForward": "disable"
  }
}

I confirm it works. It was our workaround: open-feature/dotnet-sdk#636

[YuliiaKovalova]

To give updates on the investigation.
The issue happens on the attempt to establish connection between dotnet processes due to handshake mismatch on fileVersion.Revision

msbuild/src/Shared/CommunicationsUtilities.cs

Line 106 in e402909

Version fileVersion = new Version(FileVersionInfo.GetVersionInfo(Assembly.GetExecutingAssembly().Location).FileVersion);

the parent node gets the value from C:\Program Files\dotnet\sdk\9.0.307\Microsoft.Build.dll -> Revision 46601
the child one resolves from C:\Program Files\dotnet\sdk\9.0.307\MSBuild.dll -> Revision 51703

Now we are working to figure out the root cause of the misalignment, I will keep you posted on the progress.

[rainersigwald]

Looked at this with @YuliiaKovalova and we understand what happened. There are two copies of MSBuild packages in the world with version 17.14.28 -- the "real" ones built from 09c1be8, and some that our automated build produced when that was merged back into the public branch in b5618cb.

The .NET SDK feed configuration can find both, the correct ones through dotnet-public

https://github.com/dotnet/sdk/blob/432b8e50eb9edad5c839585267ec42b6ab1b8530/NuGet.config#L28

and the mismatched ones through vssdk

https://github.com/dotnet/sdk/blob/432b8e50eb9edad5c839585267ec42b6ab1b8530/NuGet.config#L34

In that situation NuGet picks a feed per package more or less arbitrarily, which resulted in the mismatched bits selected during the official SDK build.

Talking to lots of folks about fix options/timing, no info yet.