Web deployment task failed. (Could not complete the request)

Question

I want to publish my project but:

Error1

Web deployment task failed. (Could not complete the request to remote agent URL 'https://xxxxx:xxxx/msdeploy.axd?site=VoIP'.)

Could not complete the request to remote agent URL 'https://xxxxx:xxxx/msdeploy.axd?site=VoIP'. The request was aborted: The request was canceled. COM object that has been separated from its underlying RCW cannot be used.

Does anybody know what's wrong?

It seems that just restarting Visual Studio often fixes this. — Gert Arnold, Aug 03 '12 at 22:13
I just had this in the context of publishing to Windows Azure. A restart of VS2012 Premium fixed it as Gert suggested. Thanks. — foolshat, Aug 31 '12 at 19:26
Doing a restart of VS2012 worked for me, I did have it open for quite a while. — Agile Noob, Feb 15 '13 at 02:30
This fixes it for me, but I have to restart VS every 3-4 times I push — lehn0058, May 24 '13 at 00:44
I've also found restarting the Web Deployment Agent Service on the server is sometimes required — Alan Macdonald, Jun 11 '13 at 10:52
I guess someone could report this BUG to Microsoft, if it hasn't been done before — Mauricio Gracia Gutierrez, Aug 15 '13 at 17:41
The answer here: http://stackoverflow.com/questions/5841370/cant-get-my-ec2-windows-server-2008-web-stack-instance-to-receive-publishings helped me greatly in a similar-sounding case. — solublefish, Nov 13 '13 at 17:36

score 2 · Answer 1 · edited May 23 '17 at 12:31

2

This is a bug and was fixed, but only if you have the Azure SDK:

Publish Wizard Errors in VS2010 and 2012

http://connect.microsoft.com/VisualStudio/feedback/details/773902/every-now-and-then-i-cant-publish-to-azure-get-com-object-that-has-been-separated-from-its-underlying-rcw-cannot-be-used

edited May 23 '17 at 12:31

Community

1
1

answered Aug 15 '13 at 21:03

DSway

752
14
33

score 0 · Answer 2 · answered Jan 27 '19 at 08:08

0

1) Open port 8172 on server if not

2) Make sure you have web deployment tools installed

answered Jan 27 '19 at 08:08

Timeless

7,338
9
60
94

score 0 · Answer 3 · answered Jun 18 '19 at 15:01

0

In my case I found that internet proxy was enabled for the account, which was making the MSDeploy request to go to internet instead of local network.

answered Jun 18 '19 at 15:01

Fairoz

828
2
8
21

score 0 · Answer 4 · answered Feb 07 '23 at 21:44

In my case when I attempted to restart the Web Management service it would fail... Manually restarting using:

Net start wmsvc

gave me the response:

A service specific error occurred: 2147483656.

That led me to this article.

Effectively I had deleted the cert used by Management Services when updating my SSL certificates (forehead slap), and it didn't know which cert to use.

I went into IIS, clicked on the Server, double clicked the Management Service screen.

I then selected my new SSL Certificate, clicked apply, then restart and I was back in business.

Web deployment task failed. (Could not complete the request)

4 Answers4