Error reporting while Creating Build throught GIT-Hub CI Process

0 Answers 190 Views
Licensing
Ashok
Top achievements
Rank 1
Iron
Ashok asked on 11 Nov 2025, 04:10 AM

Hi team,

We recently upgraded Telerik ASP.Net MVC to 2025.3.825, All the changes are good But when we try to create build the code through GIT-Hub CI/CD process getting below error.

 

Can you please help us to resolve the issue.

D:\actions-runner\_work\TestProject\Source\Test\packages\Telerik.Licensing.1.6.16\build\Telerik.Licensing.targets(29,3):
 error MSB4062: The "Telerik.Licensing.Tasks.ResolveTelerikProducts" task could not be loaded from the
 assembly D:\actions-runner\_work\TestProject\Source\Test\packages\Telerik.Licensing.1.6.16\build\..\tasks\netstandard2.0\Telerik.Licensing.Tasks.dll. 
 Could not load file or assembly 'Microsoft.Build.Utilities.Core, Version=15.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or 
 one of its dependencies. The system cannot find the file specified. Confirm that the <UsingTask> declaration is correct, 
 that the assembly and all its dependencies are available, and that the task contains a public class that 
 implements Microsoft.Build.Framework.ITask. [D:\actions-runner\_work\TestProject\Source\Test\Test.Web\Test.Web.csproj]

Jan
Top achievements
Rank 1
commented on 11 Nov 2025, 03:16 PM

I think the issue is related to the latest SDK that came with VS today ((17.14.20)

C:\Program Files\dotnet\sdk\9.0.307

as a workaround you might change your toolsets to MsBuild. Here's what the AI overlords gave me:

In Rider den Toolset/Build Host auf Visual Studio MSBuild umstellen
Rider → SettingsBuild, Execution, DeploymentToolset and Build

  • Use MSBuild version: MSBuild from Visual Studio (statt „.NET SDK MSBuild“)
Ricardo
Top achievements
Rank 1
commented on 11 Nov 2025, 07:09 PM

Same problem here, failing my build pipelines after upgrading to latest sdk.
Gustavo
Top achievements
Rank 1
commented on 11 Nov 2025, 07:32 PM

Same problem here, failing my build pipelines after upgrading to latest sdk.
Aaron
Top achievements
Rank 1
Veteran
commented on 11 Nov 2025, 08:50 PM

Same (or very similar) problem here. One project on version 2025.3.1002, another on version 2025.1.227, both are experiencing the same problem as of about 9:45 AM Eastern this morning. The Telerik package hasn't been upgraded in either project in a while, the only change today seems to be that .NET 10 was released.

This is the error we're getting:

C:\WINDOWS\ServiceProfiles\NetworkService\.nuget\packages\telerik.licensing\1.6.16\build\Telerik.Licensing.targets(29,3): error MSB4216: Could not run the "ResolveTelerikProducts" 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.

This is happening with builds from GitHub Actions. When I try to build manually within Visual Studio, it works fine. I'm guessing the difference is the automated process pulled in newer SDK stuff whereas I haven't updated Visual Studio yet (updated to 17.14.19 yesterday but today 17.14.20 is available).

Pablo
Top achievements
Rank 1
commented on 12 Nov 2025, 02:56 AM | edited

Same here, I have self-hosted Azure agents (Windows Server), and all my build pipelines are failing.
I configured them to use Linux Azure-hosted pipelines works fine, but using Azure Windows-based agents fails. Why Linux and building in my local workstation work, but not on my Windows server and Azure?

Aaron
Top achievements
Rank 1
Veteran
commented on 12 Nov 2025, 02:22 PM

This sounds very similar to the issue described in another forum post: Pipeline issue related to Telerik.Licensing after upgrading to latest .Net 9 SDK in UI for Blazor | Telerik Forums

A response from someone at Telerik indicates the problem is due to a Microsoft bug: SDK-9.0.307: Could not run the "ReplaceTokenInFileTask" task on Windows runners · Issue #12751 · dotnet/msbuild

There is also a workaround in the other forum post.

Again, I'm not positive if the problem described here is the same as the one in this other forum post, but they sound too similar to not be related.

Anton Mironov
Telerik team
commented on 13 Nov 2025, 12:03 PM

Hi all!

The described issue is already known and elaborated in the threads below from yesterday, November 11th, 2025:

The issue seems to be caused by the new .NET SDK version 9.0.307 that was released on 11.11.2025. The main issue seems to be tracked in:

Having a global.json with

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

is expected to solve the problem.

Please give it a try and let me know whether it has a positive impact on your end.

 

Kind Regards,
Anton Mironov

No answers yet. Maybe you can help?

Tags
Licensing
Asked by
Ashok
Top achievements
Rank 1
Iron
Share this question
or