You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I attempted to use IISWebAppDeploymentOnMachineGroup@0 on my server to deploy my application to an IIS site, an error occurred. The error message in the pipeline is as follows:
##[debug]arguments:
##[debug]arguments:
##[debug] -verb:sync
##[debug] -verb:sync
##[debug] -source:IisApp='D:\azurepipeline\ACRM_UT_vsts-agent-win-x64-3.227.2\_work\1\s\270\publish'
##[debug] -source:IisApp='D:\azurepipeline\ACRM_UT_vsts-agent-win-x64-3.227.2\_work\1\s\270\publish'
##[debug] -dest:iisApp='Default Web Site/ACRM_T'
##[debug] -dest:iisApp='Default Web Site/ACRM_T'
##[debug] -enableRule:AppOffline
##[debug] -enableRule:AppOffline
##[debug] -enableRule:DoNotDeleteRule
##[debug] -enableRule:DoNotDeleteRule
"D:\azurepipeline\ACRM_UT_vsts-agent-win-x64-3.227.2\_work\_tasks\IISWebAppDeploymentOnMachineGroup_1b467810-6725-4b6d-accd-886174c09bba\0.229.0\node_modules\azure-pipelines-tasks-webdeployment-common\MSDeploy3.6\MSDeploy3.6\msdeploy.exe" -verb:sync -source:IisApp='D:\azurepipeline\ACRM_UT_vsts-agent-win-x64-3.227.2\_work\1\s\270\publish' -dest:iisApp='Default Web Site/ACRM_T' -enableRule:AppOffline -enableRule:DoNotDeleteRule
##[debug]Exit code 3762504530 received from tool 'D:\azurepipeline\ACRM_UT_vsts-agent-win-x64-3.227.2\_work\_tasks\IISWebAppDeploymentOnMachineGroup_1b467810-6725-4b6d-accd-886174c09bba\0.229.0\node_modules\azure-pipelines-tasks-webdeployment-common\MSDeploy3.6\MSDeploy3.6\msdeploy.exe'
##[debug]Exit code 3762504530 received from tool 'D:\azurepipeline\ACRM_UT_vsts-agent-win-x64-3.227.2\_work\_tasks\IISWebAppDeploymentOnMachineGroup_1b467810-6725-4b6d-accd-886174c09bba\0.229.0\node_modules\azure-pipelines-tasks-webdeployment-common\MSDeploy3.6\MSDeploy3.6\msdeploy.exe'
##[debug]STDIO streams have closed for tool 'D:\azurepipeline\ACRM_UT_vsts-agent-win-x64-3.227.2\_work\_tasks\IISWebAppDeploymentOnMachineGroup_1b467810-6725-4b6d-accd-886174c09bba\0.229.0\node_modules\azure-pipelines-tasks-webdeployment-common\MSDeploy3.6\MSDeploy3.6\msdeploy.exe'
##[debug]STDIO streams have closed for tool 'D:\azurepipeline\ACRM_UT_vsts-agent-win-x64-3.227.2\_work\_tasks\IISWebAppDeploymentOnMachineGroup_1b467810-6725-4b6d-accd-886174c09bba\0.229.0\node_modules\azure-pipelines-tasks-webdeployment-common\MSDeploy3.6\MSDeploy3.6\msdeploy.exe'
Error: The process 'D:\azurepipeline\ACRM_UT_vsts-agent-win-x64-3.227.2\_work\_tasks\IISWebAppDeploymentOnMachineGroup_1b467810-6725-4b6d-accd-886174c09bba\0.229.0\node_modules\azure-pipelines-tasks-webdeployment-common\MSDeploy3.6\MSDeploy3.6\msdeploy.exe' failed with exit code 3762504530
at ExecState._setResult (D:\azurepipeline\ACRM_UT_vsts-agent-win-x64-3.227.2\_work\_tasks\IISWebAppDeploymentOnMachineGroup_1b467810-6725-4b6d-accd-886174c09bba\0.229.0\node_modules\azure-pipelines-task-lib\toolrunner.js:943:25)
at ExecState.CheckComplete (D:\azurepipeline\ACRM_UT_vsts-agent-win-x64-3.227.2\_work\_tasks\IISWebAppDeploymentOnMachineGroup_1b467810-6725-4b6d-accd-886174c09bba\0.229.0\node_modules\azure-pipelines-task-lib\toolrunner.js:926:18)
at ChildProcess.<anonymous> (D:\azurepipeline\ACRM_UT_vsts-agent-win-x64-3.227.2\_work\_tasks\IISWebAppDeploymentOnMachineGroup_1b467810-6725-4b6d-accd-886174c09bba\0.229.0\node_modules\azure-pipelines-task-lib\toolrunner.js:839:19)
at ChildProcess.emit (node:events:513:28)
at maybeClose (node:internal/child_process:1100:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)
Retrying to deploy the package.
I went to the Event Viewer on my host and found a clear error message as follows:
I found msdeploy.exe and was able to reproduce the issue using the command prompt.
However, I found it strange because there are different agents for different projects on the same server, and they all use the IISWebAppDeploymentOnMachineGroup@0 task. So I went to the directory of another project's agent and found the same msdeploy.exe, but it was able to run without any issues.
I realized that this might be a path length limitation issue, so I conducted an experiment by shortening the directory path of my previously lengthy folders. After doing so, the task was able to run without any issues.
Hi @samnchiu, thanks for the feedback and detailed investigation! Have you tried to move the ms-deploy folder from the failed path to another location (with the shorter path), did it work?
I have experimented with moving it from the failed path to a shorter one, and it indeed works fine. Therefore, I believe it's indeed a path length limit issue. However, I haven't specifically tested to determine the exact length that exceeds the limit.
Hi @samnchiu, it seems like the problem is mostly related to the task/msdeploy, was can't do much from the agent's side. Please create the ticket on gh in the task repository.
I am closing this issue, please feel free to reopen it,
What happened?
When I attempted to use IISWebAppDeploymentOnMachineGroup@0 on my server to deploy my application to an IIS site, an error occurred. The error message in the pipeline is as follows:
I went to the Event Viewer on my host and found a clear error message as follows:
I found msdeploy.exe and was able to reproduce the issue using the command prompt.
However, I found it strange because there are different agents for different projects on the same server, and they all use the IISWebAppDeploymentOnMachineGroup@0 task. So I went to the directory of another project's agent and found the same msdeploy.exe, but it was able to run without any issues.
I realized that this might be a path length limitation issue, so I conducted an experiment by shortening the directory path of my previously lengthy folders. After doing so, the task was able to run without any issues.
Providing path of success and failure below:
The above information is provided for reference. Please let me know if any additional information is needed. Thank you.
Versions
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
No response
Version controll system
No response
Relevant log output
The text was updated successfully, but these errors were encountered: