locked
App Service. Set Custom Domain with PowerShell. How can cancel or stop the jobs? RRS feed

  • Question

  • Hello,

    we use Azure Stack in Version 1.1910.24.108 with App Service in Version 1.8.

    We deployed App Service and set custom domains with PowerShell:
    Set-AzureRMWebApp -Name 'app' -ResourceGroupName 'app-grp' -HostNames @('app123.lab','app.lab')

    But it was a misstake in DNS. If we start the job again, we get the following message:

    WARNING: 14:46:24 - Could not set custom hostname app123.lab. Details: Microsoft.Rest.Azure.CloudException: Cannot modify this site because another operation is in progress. Details: Id: dcaf7ca5-07ec-4a5e-8e3b-5b3dd3df36a5, OperationName: Update, CreatedTime: 3/9/2020 9:10:11 AM, RequestId: , EntityType: 0
       at Microsoft.Azure.Management.WebSites.WebAppsOperations.<CreateOrUpdateHostNameBindingWithHttpMessagesAsync>d__73.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.Azure.Management.WebSites.WebAppsOperationsExtensions.<CreateOrUpdateHostNameBindingAsync>d__137.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.Azure.Commands.WebApps.Utilities.WebsitesClient.AddCustomHostNames(String resourceGroupName, String location, String webAppName, String[] hostNames)

    "operationName": {
    "value": "Microsoft.Web/sites/hostNameBindings/write",

    "localizedValue": "Microsoft.Web/sites/hostNameBindings/write"

    But how can we stop or delete the running job?



    • Edited by DenBir Monday, March 9, 2020 2:47 PM
    Monday, March 9, 2020 2:20 PM

Answers

  • typically these jobs should not last longer than 45 minutes before they time out. If you are using a full Azure Stack Hub multi-node installation and not an ASDK, your best bet is to contact Azure Support for the best way to stop this operation. 

    If you are still having the issue after 45 minutes on the ASDK, you can try to stop and start the ASDK, which will also rest the App Service RP. 

    Tuesday, March 10, 2020 2:27 AM

All replies

  • typically these jobs should not last longer than 45 minutes before they time out. If you are using a full Azure Stack Hub multi-node installation and not an ASDK, your best bet is to contact Azure Support for the best way to stop this operation. 

    If you are still having the issue after 45 minutes on the ASDK, you can try to stop and start the ASDK, which will also rest the App Service RP. 

    Tuesday, March 10, 2020 2:27 AM
  • It is a integrated system with 4nodes. The job is already running for 24 hours. We contact now the support.

    Thanks.

    Tuesday, March 10, 2020 8:49 AM