-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AzureRmWebAppDeployment error: "cmd.exe failed with return code: 4294967295" #3312
Comments
@TomDroste , Thanks for reporting the issue. Is this an intermittent issue? It looks like the DLL's are getting locked. Can u try to stop the App Service, deploy and then start the app?
You can also deploy to slots and swap the slot with production. |
I´m experiencing the same issue, same error code and our pipeline worked perfectly until a few weeks ago. |
@mikaeldiener , Can u try to stop-start app service using Azure PowerShell Task? If you are using a local agent, there will be error.txt file in the DefaultWorking Directory of Build/Release folde. Can you queue a build/Release with In the same working directory, you will also have |
The manual start-stop seems to have worked (will test again with the nightly build.deploy), but I have the start-stop in the task enabled. So something went wrong there. I was using the online agent. When I have the problem again I will use a local agent to generate the folder. p.s. my app was an asp.net core application |
@vincentdass ASP.NET Core, with two types of web projects (webclient and webapi), each deployed to separate App Services in Azure. The deployment error seems to appear at random intervalls, but fails more than 95% of the time. I´ve tried to manually stop the deployment slot and the deployment was successfull. However, this has worked for more than a year without the need of stop the App Service before deploying, until a few weeks ago.
|
For start-stop Azure App Service Slot , we need to use different command.
|
Same issue, resolved as part of VSTS by using stop/start Azure tasks. Not the ideal situation and would like to see if we can't resolve this back to working how it worked previously. |
The actual issue of app service issue is fixed by Azure core team. here is the reference of the issue dotnet/aspnetcore#694 (comment) for any further issues, please post there. As the original issue is fixed by App Service team I am closing this issue. |
This issue is totally still happening intermittently
|
To follow up on this issue |
Hi @onionhammer , do these intermittent errors occurs even when the app offline option is set? |
@arjgupta yes. |
Had this happen just now on one of our deploys. The following options are ticked Why does "Take App Offline" not shutdown the web app? |
Hi @onionhammer , @UsmanMohammad , can you please tell us what kind of web app are you running? Also, are you using web jobs? If yes, then what type? |
@arjgupta not using any web jobs. It's an ASP.NET core app running on full .NET 4.6.2. |
Hi @onionhammer , If you get the FILE_IN_USE again, can you please try the following in kudu console:
|
Before enabling 'Take App Offline'Just ran into it when deploying;
Back in process explorer 'MyApp.exe' is no longer runniong, the two w3wp.exes are. The app is now offline. -- I'll test again with 'Take App Offline' enabled.. |
Hi @onionhammer , any update for the case when you enable the 'Take App Offline' feature and get the file_in_use error? |
Nope, so far it seems to work with that option set. |
@onionhammer, @UsmanMohammad |
@niadak Nevermind. Just happened again. Even with the '-enableRule:AppOffline' argument
|
Another random, fun, failure during deployment
|
@onionhammer Scaling my service plan up and then down again solved this issue for me. |
@onionhammer did you get this working, i am getting this myself now suddenly, been fine for many months and nothing has changed; looking in console i can see that ApplicationInsightsProfiler is in the jobs folder but i cant go in because I get Access denied" |
@coderangerdan, taking the App Offline should solve this issue. Please follow the below steps to do this: |
Still happening |
Still happening with me. |
@carltierney , @davenewza , can you please share the logs for the same release? Do you have any webjobs running in your App Service? (including Application Insights) |
Started seeing this error happening intermittently a few days ago for an ASP.NET Core project. The "Take app offline" option is checked. There are no webjobs or Application Insights projects running for this app. The error code from logs is ERROR_FILE_IN_USE, the main application DLL seems to be locked |
@dennis-yemelyanov , Currently there is an thread for the same issue. |
FWIW, adding -retryInterval:6000 -retryAttempts:10 (and variations on that) does not seem to unblock this issue for me In my case, I'm deploying a functionapp on a dynamic service plan using the new tooling that came with vs 15.3. I'm currently running 15.3.2. |
@pauldalyii, can you please share the logs for the release? |
Here's the log for the deployment step that is failing in the release: After adding the Application Insights site extention, I get the following error on the scm page:
|
@pauldalyii , thanks for the logs. If Application Insight extension is enabled in your App Service, there is a possibility of hitting FILE_IN_use issue. The error you are facing is quite different. Taking this thread with Azure App Service team to debug the issue. |
Thanks. Let me know if I can provide any other information. My alias is padal if you want to hop on a skype call. |
@pauldalyii any updates? I just got the same error. |
@DivineOps , Can you share the logs and the app type (Web App / Function App) that you are trying to deploy? |
@vincentdass just a plain ARM template with a Web App resource tied to an Application Insights resource (from an Agile hackathon lab, if that helps) |
@DivineOps , Can you please share the link to the ARM template your are using? |
I have the same issue. I have an app plan with 3 website (dev / pre prod / prod) and it looks like the deploy process get stuck, it timeout after 6h and the cpu stay at 100% usage I have to restart each web site to drop the cpu to normal... |
@x3r10n , this issue seems to be different. Can you please share the debug logs to investigate? |
@vincentdass Sure, heres the info from my dev environment : 2017-09-18T21:21:34.5851826Z ##[section]Starting: Deploy Azure App Service it doesn't say much :( I did not send the cancel myself. I guess it's a 'timeout'. 2017-09-18T23:40:08.2912947Z ##[section]Starting: Deploy Azure App Service ********************** 3000 lines of files names *********************** 2017-09-19T05:39:04.8772793Z ##[error]The operation was canceled. I think it was this slow because the app service cpu was probably already at 100% because of some stuck deploy process from de DEV deploy |
same problem here... with .Net Core web app |
@bhuvanpasham , can you please share the debug logs (set variable |
This is happening with me at the moment each time I deploy |
I fixed this by having to do the following:- You can fix this by using azure powershell step by doing this:- |
@gsuttie A recommendation would be upgrading to 4.* task version and use RunFromPackage to deploy. Please note that this makes the package folder read only. For more information go through https://aka.ms/azurermwebdeployreadme |
I do get the same error for deploying it to the deployment group- local servers |
We had a fully operational pipeline the last few months, but for some reason last week it stopped working. All we know is that cmd.exe stopped with an errorcode 4294967295.
2016-12-27T10:27:51.8017874Z Successfully updated deployment History at https://secretcollect-dev.scm.azurewebsites.net/deployments/1351482834471320
2016-12-27T10:27:51.8017874Z ##[debug]task result: Failed
2016-12-27T10:27:51.8017874Z ##[error]Error: Error: C:\Windows\system32\cmd.exe failed with return code: 4294967295
2016-12-27T10:27:51.8330487Z Finishing task: AzureRmWebAppDeployment
2016-12-27T10:27:51.8330487Z ##[error]System.Exception: Task AzureRmWebAppDeployment failed. This caused the job to fail. Look at the logs for the task for more details.
2016-12-27T10:27:51.8330487Z ##[error] at Microsoft.TeamFoundation.DistributedTask.Worker.JobRunner.Run(IJobContext jobContext, IJobRequest job, IJobExtension jobExtension, CancellationTokenSource tokenSource)
When I looked inside the logs I did find an error earlier on, but no explanation why.
016-12-27T10:27:42.8982848Z [command]C:\Windows\system32\cmd.exe /C C:\AzureBuildAgent_work\bc03c043f\msDeployCommand.bat
2016-12-27T10:27:43.1795473Z Info: Using ID '39a389a9-7406-446d-b6d2-884720daf80b' for connections to the remote server.
2016-12-27T10:27:45.4034302Z Info: Using ID '91573987-3767-4af7-b918-d9b5d1639b48' for connections to the remote server.
2016-12-27T10:27:46.4115541Z Info: Updating file (secretcollect-dev\SecretCollect.AuthorizationFilters.dll).
2016-12-27T10:27:51.3213992Z ##[debug]rc:4294967295
2016-12-27T10:27:51.3213992Z ##[debug]rc:4294967295
2016-12-27T10:27:51.3213992Z ##[debug]success:false
2016-12-27T10:27:51.3213992Z ##[debug]success:false
I've attached the logs here, hoping some of you may have a solution.
Deployment logs.txt
The text was updated successfully, but these errors were encountered: