[error]Process 'msbuild.exe' exited with code '1'

Mohammad Aftab 0 Reputation points

I am deploying the BizTalk project to Azure DevOps for CI/CD. In Azure DevOps, I created a new Agent called "Test pool". when I create a Build pipeline, I am getting the below error. Build solution BizTalkDevOpsDemo.sln View raw log Starting: Build solution BizTalkDevOpsDemo.sln ============================================================================== Task : Visual Studio build Description : Build with MSBuild and set the Visual Studio version property Version : 1.199.0 Author : Microsoft Corporation Help : https://learn.microsoft.com/azure/devops/pipelines/tasks/build/visual-studio-build ============================================================================== "C:\agents_work_tasks\VSBuild_71a9a2d3-a98a-4caa-96ab-affca411ecda\1.199.0\ps_modules\MSBuildHelpers\vswhere.exe" -version [17.0,18.0) -latest -format json "C:\agents_work_tasks\VSBuild_71a9a2d3-a98a-4caa-96ab-affca411ecda\1.199.0\ps_modules\MSBuildHelpers\vswhere.exe" -version [17.0,18.0) -products Microsoft.VisualStudio.Product.BuildTools -latest -format json "C:\agents_work_tasks\VSBuild_71a9a2d3-a98a-4caa-96ab-affca411ecda\1.199.0\ps_modules\MSBuildHelpers\vswhere.exe" -version [16.0,17.0) -latest -format json "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\msbuild.exe" "C:\agents_work\3\s\BizTalkDevOpsDemo.sln" /nologo /nr:false /dl:CentralLogger,"C:\agents_work_tasks\VSBuild_71a9a2d3-a98a-4caa-96ab-affca411ecda\1.199.0\ps_modules\MSBuildHelpers\Microsoft.TeamFoundation.DistributedTask.MSBuild.Logger.dll";"RootDetailId=b9c461fa-80fe-47b3-b0ff-4060efbee80c|SolutionDir=C:\agents_work\3\s|enableOrphanedProjectsLogs=true"*ForwardingLogger,"C:\agents_work_tasks\VSBuild_71a9a2d3-a98a-4caa-96ab-affca411ecda\1.199.0\ps_modules\MSBuildHelpers\Microsoft.TeamFoundation.DistributedTask.MSBuild.Logger.dll" /p:OutputPath=C:\agents_work\3\a\BTS\BizTalkDevOpsDemo\ /p:VisualStudioVersion="16.0" /p:_MSDeployUserAgent="VSTS_f82be4ec-4c29-4226-9dfa-8eb0a30e25b0_build_6_0" MSBUILD : error MSB1009: Project file does not exist. Switch: C:\agents_work\3\s\BizTalkDevOpsDemo.sln [error]Process 'msbuild.exe' exited with code '1'. Finishing: Build solution BizTalkDevOpsDemo.sln ![200732-capture1.png][1] [1]: /api/attachments/200732-capture1.png?platform=QnA

Microsoft BizTalk Server
Microsoft BizTalk Server
A family of Microsoft server products that support large-scale implementation management of enterprise application integration processes.
359 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Kamlesh Kumar 3,861 Reputation points

    Hi There,

    Thank you for asking this question on the Microsoft Q&A Platform.

    First of all this is not BizTalk server issue, it's more an Azure DevOps issue. Though I am adding some solution that can be helpful for you,


    Kamlesh Kumar
    BizTalk Techie

    If this answer solved your problem, please click the Verify Answer button (found below the answer) to help other users who have the same question.

  2. David Downing 701 Reputation points

    When you are building a BizTalk Server Solution on a DevOps agent, you need to make sure all the BizTalk SDK/Nuget components are also on the new agent you created. Refer to the following for BTS MSBuild information: https://learn.microsoft.com/en-us/biztalk/core/standalone-msbuild

    One thing you can do is log onto the agent, open a command window and navigate to the folder where the project is located and try to build it yourself. Make sure all the required BizTalk SDK components have been installed on the Agent.

    When you run the BizTalk Server Installer on the agent, make sure the development tools/SDK are included. In some cases you may need third party SDKs as well or a specific version of Windows, PowerShell,... the list goes on.

    If you can build it on your development computer, make sure the agent is similar in terms of VS Build tools, Windows, and any other dependencies required by your BTS solution.

    0 comments No comments