Menu
I have been getting the error "Error_Connection_Terminated" when trying to deploy a site to my localhost from the developer command prompt using MSDeploy and I am at the end of my rope trying to figure out whats causing it, the error is pretty ambiguous as to what the problem actually is. I've set privileges for the deploy folder correctly and I have restarted the Web Deployment Agent Service numerous times in the services window. I have gone over many solution's already posted on the net but to no avail as none of them deal with using the developer command prompt and instead only offer solution's by using visual studio itself.
Would anyone with experience with MSDeploy or IIS, be able to shed some light or advise on how to solve this.
the error states "Error_Connection_Terminated Error: Unexpected end of file has occurred. The following elements are not closed: results. Line 1, position 550. Error count: 1."
414
deploy. cmd file or by using MSDeploy.exe directly, you need to specify a computer name or a service endpoint for your deployment. If the destination web server is configured for deployment using the Web Deploy Remote Agent service, you specify the target service URL as your destination.
Is Web Deploy installed? You can verify web deploy is installed by going to the "Programs and Features" control panel and looking for "Microsoft Web Deploy 2.0" in the list of installed programs. If it is not there, you can install it via the Web Platform Installer by going to the "Products" tab.
To check that the Web Deployment Agent Service is runningOn the Start menu, point to Administrative Tools, and then click Services. Locate the Web Deployment Agent Service row, and verify that the Status is set to Started. If the service is not already started, click Start.
Web Deploy is an extensible client-server tool for syncing content and configuration to IIS. Web Deploy is used primarily in two scenarios: Developers use it to sync (aka 'publish') a compiled web applications (ASP . Net, PHP etc) from developer tools (Visual Studio, WebMatrix, etc) to IIS.
I had the same problem and was able to successfully deploy after closing Fiddler on the machine on which I was running MSDeploy.
This would fit with Marcello's findings - I assume that he had Fiddler open and that he closed it when he rebooted.
143
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
