Windows Azure Web Role Accelerator

Question

I am working on deploying my ASP .NET web application using Windows Azure Accelerator for Web Role. In the Windows Azure Web Host project, I have modified the Web Role Input endpoint (HttpIn) to point to port 8080. After deploying the web host project to Azure, I am successfully able to login to the website manager (http://e345b9be95e146fb8b4124a96dcc241c.cloudapp.net:8080/)

In the website manager I create a new website, giving the hostname as "e345b9be95e146fb8b4124a96dcc241c.cloudapp.net" and port number as 80.

On publishing my ASP .NET application using web deploy, I specify the Service URL as http://e345b9be95e146fb8b4124a96dcc241c.cloudapp.net

But I am getting the following error, while publishing:

"Web deployment task failed.(Remote agent (URL http://e345b9be95e146fb8b4124a96dcc241c.cloudapp.net:8080/MSDEPLOYAGENTSERVICE) could not be contacted.  Make sure the remote agent service is installed and started on the target computer.)
The requested resource does not exist, or the requested URL is incorrect.
Error details:
Remote agent (URL http://e345b9be95e146fb8b4124a96dcc241c.cloudapp.net:8080/MSDEPLOYAGENTSERVICE) could not be contacted.  Make sure the remote agent service is installed and started on the target computer.
An unsupported response was received. The response header 'MSDeploy.Response' was '' but 'v1' was expected.
The remote server returned an error: (404) Not Found.  0 0 WebApplication2
"

 

Answer 1

The issue is using wrong username and password... Nothing else so what i think you are using Web Site Manager Username and Password to Publish the website, Please use your Remote desk top User Name and Password to publish the project.

This will work... try and let me know. 

---

K.Mohamed Faizal, Solution Architect, Singapore, @kmdfaizal
http://faizal-comeacross.blogspot.com/ |AzureUG.SG

Answer 2

I am using the Remote Desktop username and password to publish the project.

Infact, I have kept the username/password same for both web site manager and remote desktop

Answer 3

i had same issue... two things i did to overcome this issue : 1. Update my Visual Studio 2010 to Visual Studio 2010 SP1 and 2. Notice that you must use Remote username and password.  Since you are using user name and password is correct, Pls check the Visual Studio version and update if you are not using VS 2010- SP1

---

K.Mohamed Faizal, Solution Architect, Singapore, @kmdfaizal
http://faizal-comeacross.blogspot.com/ |AzureUG.SG

Answer 4

Hi Sumeethcl,

If you changed the "HttpIn" endpoint to 8080 and want to use 80 port for newly created web site, you need to define an input endpoint for 80 port too otherwise the newly create web site cannot be reached via 80 port.

      <InputEndpoint name="HttpIn" protocol="http" port="808" />
      <InputEndpoint name="AnotherHttpIn" protocol="http" port="80" />

Also if you changed the "HttpIn" endpoint to 8080, you might use http://e345b9be95e146fb8b4124a96dcc241c.cloudapp.net:808/ to publish web site instead of using the original 80 port.

Thanks.

 

---

Wenchao Zeng
Please mark the replies as answers if they help or unmark if not.
If you have any feedback about my replies, please contact [e-mail].
Microsoft One Code Framework

Answer 5

Hi Wenchao Zeng
I hope I do not manually need to add another Binding element in the service configuration file, corresponding to the new InputEndpoint (AnotherHttpIn) I will add

Answer 6

Hi sumeethcl,

> I hope I do not manually need to add another Binding element in the service configuration file, corresponding to the new InputEndpoint.

The binding is configured for the web site. As the web site is added and deployed dynamically via the management page after the Azure service is deploy, I don't think you need to add another binding in the service definition file.

Thanks.

---

Wenchao Zeng
Please mark the replies as answers if they help or unmark if not.
If you have any feedback about my replies, please contact [e-mail].
Microsoft One Code Framework

Answer 7

Hi Wenchao Zeng,

Thanks for the reply. Your suggestions helped me solve my problem. I have another query. How does the webdeploy feature of Visual Studio copies the msdeploy package to Azure blob storage ?

Also is the custom website redeployed in case of failover scenario (i.e. the web host gets re provisioned to another host in case of failure)

Answer 8

Hi sumeethcl,

> How does the webdeploy feature of Visual Studio copies the msdeploy package to Azure blob storage ?

Actually Visual Studio uploads the package to one of role instances and then Windows Azure Accelerator for Web Roles implement the logic to synchronize the site with other instances and blob storage.

> Is the custom website redeployed in case of failover scenario (i.e. the web host gets re provisioned to another host in case of failure)

Yes. Websites will be automatically deployed to the newly created instance.

As it is an open source project, I'd recommend you study directly from the source code.

Thanks.

---

Wenchao Zeng
Please mark the replies as answers if they help or unmark if not.
If you have any feedback about my replies, please contact [e-mail].
Microsoft One Code Framework