I been working on this for so long and couldn't make any conclusion on why this is not working. Hoping to get help from someone.
I am trying to do Microsoft web deployment using command prompt with the below command
"testDeploy.deploy.cmd /t"
This works fine in my local machine. Also it works fine on my dev machine when I try remote deploying of the same application with the command including username and password fields
More Information: Could not connect to the destination computer <"machineName"> using the specified process ("Web Deployment Agent Service"> because the server did not respond. Make sure that the process <"Web Deployment Agent Service"> is started
on the destination computer.
Error: The remote server returned an error: (503) Server Unavailable.
Error count: 1.
I have tried everything. There is absolutely no firewall is running and I can see "web deployment agent service" has already running on the server. The local deployment on this same QA machine works fine but not when it comes to remote deployment. Any help
on this will be very much appreciated.
btw., When I run the below command in my QA machine I get an error to make sure remote agent service is installed which I tried reinstalling it as well but of no avail to resolve the issue
Error: Object of type 'appHostConfig' and path '' cannot be created. Error: Remote agent (URL http://localhost/MSDEPLOYAGENTSERVICE) could not be contacted. Make sure the remote agent service is installed and started on the target computer. Error: An unsupported response was received. The response header 'MSDeploy.Response' was ' ' but 'v1' was expected. Error: The remote server returned an error: (503) Server Unavailable. Error Count: 1.
Yes. It seems to be running "Web Deploy Management Service". Anyway I think I am giong to use alternative deployment method as I guess there might be some hidden/router firewall been applied on my QA server. Thanks for your help necro. If there's anything
I have to check please let me know. Much appreciated of your time...
I was trying to make the deployment through command prompt. Now I tried using the VS2010 Build->publish->WebDeploy and it works fine when I tick the "Allow untrusted certificate". Any suggestion on how to make the same to work using command prompt. The command
that fails for me is
Thanks for that link but my command still fails after including -allowUntrusted. For now I am going to stick with doing the deployment using VS web deploy. Thanks again for all your help
--
Kam
Marked as answer by Dino He - MSFT on May 30, 2012 10:14 AM
This is not an acceptable answer. I am experiencing the same situation and deploying through Visual Studio is not practical. Anyone from Microsoft have anything to add?
If it helps, my situation involves a webform project that is signed. I have a separate MVC project that is deployed from the same server to the same destination server, as a different website. That works fine.
For anyone else stumbling across this thread. My issue ended up being a misspelling of the site name in IIS. Fixing that enabled msdeploy to complete. Perhaps a more useful error could have been "Unable to find site <my misspelled version>"
kamaleswaran
Member
73 Points
87 Posts
MS Remote WebDeploy
May 23, 2012 03:13 PM|LINK
Hi there
I been working on this for so long and couldn't make any conclusion on why this is not working. Hoping to get help from someone.
I am trying to do Microsoft web deployment using command prompt with the below command
"testDeploy.deploy.cmd /t"
This works fine in my local machine. Also it works fine on my dev machine when I try remote deploying of the same application with the command including username and password fields
"testDeploy.deploy.cmd /t /m:<machineName> /u:<UserName> /p:<Password>"
Now when I try it on the QA server (Remote deploy similar to dev machine), it throws an error saying
"Error Code: Error_could_not_connect_to_remotesvc"
More Information: Could not connect to the destination computer <"machineName"> using the specified process ("Web Deployment Agent Service"> because the server did not respond. Make sure that the process <"Web Deployment Agent Service"> is started on the destination computer.
Error: The remote server returned an error: (503) Server Unavailable.
Error count: 1.
I have tried everything. There is absolutely no firewall is running and I can see "web deployment agent service" has already running on the server. The local deployment on this same QA machine works fine but not when it comes to remote deployment. Any help on this will be very much appreciated.
btw., When I run the below command in my QA machine I get an error to make sure remote agent service is installed which I tried reinstalling it as well but of no avail to resolve the issue
Command: "msdeploy.exe -verb:dump -source:appHostConfig,computername=localhost"
Error: Object of type 'appHostConfig' and path '' cannot be created.
Error: Remote agent (URL http://localhost/MSDEPLOYAGENTSERVICE) could not be contacted. Make sure the remote agent service is installed and started on the target computer.
Error: An unsupported response was received. The response header 'MSDeploy.Response' was ' ' but 'v1' was expected.
Error: The remote server returned an error: (503) Server Unavailable.
Error Count: 1.
Thanks in advance for your time
Kam
necro_mancer
Star
8089 Points
1590 Posts
Re: MS Remote WebDeploy
May 24, 2012 06:04 AM|LINK
hi kamaleswaran,
have you opened the necessary port 8172 on your QA server? Please try to TELNET to this port to check the status
Professional SQL 2008 R2 Service
kamaleswaran
Member
73 Points
87 Posts
Re: MS Remote WebDeploy
May 24, 2012 08:05 AM|LINK
Hi necro
Thanks for the reply. Yes I have checked telnet and my port is open
K
Kam
necro_mancer
Star
8089 Points
1590 Posts
Re: MS Remote WebDeploy
May 25, 2012 06:16 AM|LINK
hi there,
Have you made sure the MS Deploy service is running on your system?
Professional SQL 2008 R2 Service
kamaleswaran
Member
73 Points
87 Posts
Re: MS Remote WebDeploy
May 25, 2012 08:18 AM|LINK
Yes. It seems to be running "Web Deploy Management Service". Anyway I think I am giong to use alternative deployment method as I guess there might be some hidden/router firewall been applied on my QA server. Thanks for your help necro. If there's anything I have to check please let me know. Much appreciated of your time...
Kam
kamaleswaran
Member
73 Points
87 Posts
Re: MS Remote WebDeploy
May 25, 2012 09:32 AM|LINK
Hi Necro
I was trying to make the deployment through command prompt. Now I tried using the VS2010 Build->publish->WebDeploy and it works fine when I tick the "Allow untrusted certificate". Any suggestion on how to make the same to work using command prompt. The command that fails for me is
"testDeploy.deploy.cmd /t /m:<machineName> /u:<UserName> /p:<Password>"
also tried
"testDeploy.deploy.cmd /y /m:<machineName> /u:<UserName> /p:<Password> /g:true"
Kam
tdykstra
Contributor
4465 Points
625 Posts
Microsoft
Moderator
Re: MS Remote WebDeploy
May 25, 2012 02:11 PM|LINK
You can add -allowUntrusted=true to the command line.
http://technet.microsoft.com/en-us/library/dd569089(v=WS.10).aspx
kamaleswaran
Member
73 Points
87 Posts
Re: MS Remote WebDeploy
May 25, 2012 03:12 PM|LINK
Thanks for that link but my command still fails after including -allowUntrusted. For now I am going to stick with doing the deployment using VS web deploy. Thanks again for all your help
Kam
jgeurts
Member
6 Points
5 Posts
Re: MS Remote WebDeploy
Nov 05, 2012 02:15 PM|LINK
This is not an acceptable answer. I am experiencing the same situation and deploying through Visual Studio is not practical. Anyone from Microsoft have anything to add?
If it helps, my situation involves a webform project that is signed. I have a separate MVC project that is deployed from the same server to the same destination server, as a different website. That works fine.
msdeploy
jgeurts
Member
6 Points
5 Posts
Re: MS Remote WebDeploy
Nov 05, 2012 03:25 PM|LINK
For anyone else stumbling across this thread. My issue ended up being a misspelling of the site name in IIS. Fixing that enabled msdeploy to complete. Perhaps a more useful error could have been "Unable to find site <my misspelled version>"
msdeploy