Home → Problems →

msdeploy and useChecksum bug

• Edit

pawelburzynski

16 Jan, 2015 11:25 AM

Hi,

I have been using appveyor for some time to deploy my applications to both live and staging environments.

Some applications on deployment return error (1/16/2015 11:11:20 AM) An error occurred when the request was processed on the remote computer.

When I log into the server to see the msdeploy application logs they say:

A tracing deployment agent exception occurred that was propagated to the client. Request ID '106cd5b1-676c-43fd-bd37-4a3ae41b1b28'. Request Timestamp: '1/16/2015 10:38:11 AM'. Error Details:
System.NotImplementedException: The method or operation is not implemented.
   at Microsoft.Web.Deployment.IncompleteParameterReplacementProvider.GetFilteredStream()

I have been googling it for some time now and it looks like there is a bug in msdeply when used with useChecksum option

As there is no fix from Microsoft, would it be possible to specify whether or not to include this option during deployment?

Thanks,
Pawel

1. Support Staff 1 Posted by Feodor Fitsner on 16 Jan, 2015 08:00 PM

   

   Hi Pawel,

   Do you have by chance a sample application to reproduce this bug?

   Adding "Do not use checksum" flag is not a problem.

   • Edit

2. Support Staff 2 Posted by Feodor Fitsner on 17 Jan, 2015 01:09 AM

   

   "Do not user checksum" option has been implemented. Will deploy it this week.

   • Edit

3. 3 Posted by pawelburzynski on 19 Jan, 2015 08:58 AM

   

   Hi Feodor,

   Thank you very much. The problem is strange as it occurs with some applications and not with others and seems completely random.

   As soon as it is deployed I will let you know if this helps.

   Thanks,
   Pawel

   • Edit

4. Support Staff 4 Posted by Feodor Fitsner on 19 Jan, 2015 05:38 PM

   

   It's been deploy. There is a new "Do not use checksum for comparing files" option on Web Deploy settings. Let me know how that worked.

   • Edit

5. 5 Posted by pawelburzynski on 27 Jan, 2015 10:20 AM

   

   Thank you very much, this resolved the problem.
   This thread can be closed.

   Thanks,
   Pawel

   • Edit

6. pawelburzynski closed this discussion on 27 Jan, 2015 10:20 AM.