nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why does my CI build get an MSB4236 error?

David FALLAS

A CI build on Windows 2012 server continues to fail with: 'error: MSB4236: The SDK 'Microsoft.NET.Sdk.Web' specified could not be found.'

.Net Core 2.0 is installed correctly - c:\windows\system32> dotnet -- version returns 2.1.2

The Path environment variable contains both C:\Program Files\dotnet and C:\Program Files\dotnet\sdk\2.0.0\Sdks - and the SDK is present at that location.

Why does the agent fail to find the SDK?

Bamboo v6.5.0

Accepted answers

Daniel Santos_157bm4

Hi @David FALLAS,

Let me share some troubleshooting tips that might help you moving forward:

First of all, check what part of the build is reporting this error:
* What is the affected task?
* It it is an script task, or a task that uses an external builder or script, check specifically what command is failing.
Try to run the same command or actions performed by that task from your agent server terminal (no Bamboo involvement).
* If it works, we need to check if the environment variables for your agent are the same of your terminal.
* If it is not working you know there to fix things.
Assuming your terminal works we need to know what is different when using Bamboo.
* Check what are the environment variables from terminal in comparison with your agent JVM environment ones.
** Use the command SET to check the environment variables in the terminal
** Add a script task before the task failing in Bamboo to run the SET command. That will return the variables from inside the agent JVM. If the problem is here you will be able to check what is wrong.
* Check if there is any capability missing in your server capabilities.
Check if this is working for other agents
* if it is working, what is different?

Try to cross the build logs with the agent logs to identify more details of what is causing the issue.
The agent logs can be found at:

<Bamboo_Agent_Home>/logs/atlassian-bamboo.log (application logs)
<Bamboo_Agent_Home>/atlassian-bamboo-agent.log (application logs + JVM logs)

All comments

Daniel Santos_157bm4

Hi @David FALLAS,

Let me share some troubleshooting tips that might help you moving forward:

First of all, check what part of the build is reporting this error:
* What is the affected task?
* It it is an script task, or a task that uses an external builder or script, check specifically what command is failing.
Try to run the same command or actions performed by that task from your agent server terminal (no Bamboo involvement).
* If it works, we need to check if the environment variables for your agent are the same of your terminal.
* If it is not working you know there to fix things.
Assuming your terminal works we need to know what is different when using Bamboo.
* Check what are the environment variables from terminal in comparison with your agent JVM environment ones.
** Use the command SET to check the environment variables in the terminal
** Add a script task before the task failing in Bamboo to run the SET command. That will return the variables from inside the agent JVM. If the problem is here you will be able to check what is wrong.
* Check if there is any capability missing in your server capabilities.
Check if this is working for other agents
* if it is working, what is different?

Try to cross the build logs with the agent logs to identify more details of what is causing the issue.
The agent logs can be found at:

<Bamboo_Agent_Home>/logs/atlassian-bamboo.log (application logs)
<Bamboo_Agent_Home>/atlassian-bamboo-agent.log (application logs + JVM logs)

David FALLAS

Thank you Daniel - your response helped me investigate this in a more systematic way.

The underlying problem was due to changes to the path(s) to the MSBuild binaries and dependencies in the latest Microsoft Build Tools deployment. Some files that Bamboo could not find, and which were the root cause of my build problems, are now in C:\Program Files (x86)\Microsoft Visual Studio\2017\...

We only uncovered this after a number of other builds started to fail as well as my newly added one.

Daniel Santos_157bm4

Hey David,

Great to hear!
I'm glad you could find what was causing the issue and fix it.

\o/

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bamboo

.net