Publish to Azure Error


 


I recently ran in to an issue I have not seen before. I was trying to publish to Azure App Services from my local Visual Studio 2022 and it failed with an error of:

     "Error 706 Web deployment task failed. (Could not connect to the remote computer ("xxx.scm.azurewebsites.net") using the specified process ("Web Management Service") because the server did not respond. Make sure that the process ("Web Management Service") is started on the remote computer. Learn more at:http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_COULD_NOT_CONNECT_TO_REMOTESVC.)"

It took me a couple of hours to troubleshoot and resolve this issue. This post is to document what I did to fix the error so next time I run into this error; I have documentation on how to resolve it.

Process Followed

I have always published my blog post sample code to Azure App Services from my local machine for a number of years. I think this might have been the first time using Visual Studio 2022, that might have been the variable that changed. 

I went to publish a new application using the same process I always have done:

    •  Click publish in Visual Studio
    •  Select Azure as the target
    •  Select Azure App Service
    •  Select My subscription
    •  Selected an unused instance
    •  Then clicked Finish
 
Once back to the publish screen, I clicked publish. The application built and then I received the popup error.

Troubling Shooting Steps

I tried a couple of times just to make sure. Then I tried the following, but all had the same result: 

For step 5, I selected a new instance 

  1.   I cleaned out the publish profiles I had
  2.   Tried again with a new publish profile
  3.   Starting Googling for a resolution
  4.   Several google results stated to put this setting in the Application App settings
    1.  WEBSITE_WEBDEPLOY_USE_SCM = False
    2.  I placed it first in my local app settings file
    3.  I then added it as an application setting in the configuration in Azure for the App service
  5.   In Azure I downloaded a new publish profile and used that one
  6.   In Azure I reset the publish profile and tried that one.
  7.   Then in Azure I deleted the old App Service instance and created a new one.
    1.   Repeated b and c from above
  8.   An article stated you had to be an Admin to publish
  9.   Closed Visual studio
  10.   Opened as Admin
  11.  Tried to publish again 

It was at this point I was getting frustrated. I decided to take and break. Taking a break turned out to be a clever idea. As I started troubleshooting again, I remember a comment of a comment on a Stock Overflow. It stated this is a local error and to check your firewall.


Resolution

I searched and found that Visual Studio uses TCP Port 4026. I opened my fire wall on my Windows 11 desktop and sure enough the post was blocked. I opened the port. At this port I was able to publish to Azure. 

I figured I had fixed the issue and moved on to the next step in my project. The next day I started a fresh instance of Visual Studio made changes and tried to publish and it failed, again. I double checked the port, and it was fine. That's when it dawned on me that I was also signed in as admin the last time I published. I exited visual studio and started it as admin. I was now able to publish.

 

Full Resolution

    1. Ensure port 4026 is open for TCP
     2. Start Visual Studio 2022 as administrator
 

I am not sure if these are new requirements for Visual Studio 2022 or something in Windows 11 change the security. Either case, it cost me several hours to investigate and resolve this issue. Hopefully posting this will help someone else save a little time.

 

Comments

Post a Comment

Popular posts from this blog

Yes, Blazor Server can scale!

Image
From the very beginning of the release of Blazor Server naysayers have incorrectly stated that Blazor Server can not scale.  They usually state that the limit is 5,000 concurrent users. There are several misconceptions and wrong assumptions about their statement.  Let's break it down and get a better understanding of Blazor server-side scaling. What is the "limit" for users When Microsoft talks about the need to scale an application, what they are saying is that when a normal response for any concurrent user is taking longer than 200 ms, the system is not performant and needs to scale. We will accept that definition: If any normal user response is taking longer than 200 ms, the system needs to scale for concurrent users. By a normal response, we are referring to a page get, a post, etc.  Large database access requests would not be included in this measurement. What is scaling There are 2 common ways to scale, scale, out horizontally, and scale-up, up vertically. In our di...
Read more

Blazor - Cool Blur Loading Page

Image
  I was working on a project and wanted an original way of showing the user the application was loading besides using the normal "Loading...." text.  I came across a website page and thought I could refactor that into what I was looking for. When my application starts, it displays a full-screen image with a count down while the page loads.  As a special effect, I want to unblur the image the closer it gets to the applicaiton finishing loading.  Once the teh count down is done, we pause for 1 sec, for effect, then proceed to the application.  I think it turned out pretty cool.  See the demo here . I used the server side Blazor project template in my example, but the code should work on any Blazor template. Template changes 1. Rename the original Index.razor page to "home".  Besure to change the routing at the top of the page as well.      @page "/home" 2. Create a new Index.razor page     a. Add routing      ...
Read more

Blazor new and improved Search Box

 Back in March, I posted a new Blazor data grid with a search box ( see post ).  Since then I have found a new and improved search box that I wanted to implement.  The search part is implemented the same.  What I added was the ability for the user to narrow down the search by selecting which field they wanted to search on.  This will help the user find what they are looking for and in a large collection, the search will end up being faster. The goal of making the change was to make the search box a new component and have it handle the UI functionality part. Prep Work Here is the prep work I did before adding the search box: Started with the source code from the post listed above. Upgraded the project to .Net 5 Upgraded the Nuget packages that were out of date. Ensured every build and run. Change to a Component I wanted to create a component for the search box so I could use it in other applications.   1. Create a Folder under UIControls called "SearchB...
Read more