Web Deployment Tool (MS Deploy)
Web Deploy on Windows Web Server 2008 R2
Last post Apr 23, 2010 03:02 PM by mark stega
Apr 22, 2010 08:24 PM|Mark Stega|LINK
I have v1.1 of Web Deploy installed on a new Windows Web Server 2008 R2 x64 and want to publish a Silverlight app/web site to the server. My first attempt failed with an inability to connect to the server. There is no issue browsing to a test web application
from the source system to the target system. If I understand correctly, the deploy service doesn't get started automatically, so, working on the remote system I first tried to do a "net start wmsvc" and received an error of 'unknown service'. I then looked
in the IIS Manager and there is no management icon when I am at the level of the server. The web platform installer shows that Web Deploy 1.1 is installed.
Its it compatinble with Windows Web Server 2008 R2 x64? What is the secret to access its configuration & starting the service if it is compatible?
Apr 22, 2010 09:16 PM|devonlazarus|LINK
Web Deploy 1.1 is compatible, we are using it internally on our systems.
A couple of things to try:
If you have the service started, then you should be able to point your Web Deployment package to http://$server_name:80/msdeployagentservice/
Hope this helps. Starting the MsDepSvc is key to success here (as well as firewall and permissions).
Apr 22, 2010 10:05 PM|Mark Stega|LINK
OK - I had no references to the service even though the web platform installer said it was installed. So I download3ed the x64 .msi file for 1.1 and ran it. It turns out that the only installed component was the IIS Manager UI Module and Remote Agent
Service was not. So I selected RemoteAgentService to be installed and now I have a directory "C:\Program Files\IIS\Microsoft Web Deploy" that has MsDepSvc.Exe located within. When I try to execute it, I get an immediate popup of "Web Deployment Agent Service
has stopped working" with choices of debug/close.
Under Admin tools->Services I see no entry for MS Deployment Services...
Apr 23, 2010 01:51 PM|Mark Stega|LINK
Some progress -- I realized I had to do a "net start msdepsvc" and that apparently got the service started. I created a firewall exception for msdepsvc.exe and for port 8172. But still no luck connecting. So I did a netstat -a on the server and it appeared
that the deployment service is not lsitening on that port. In the process of trying to understand what was going on I removed the deployment service and reinstalled. The key to success was reading the installation description of the deployment service.
That shows that it is going to be installed to listen on "http://+80/MSDEPLYAGENTSERVICE". So I went back to VS2010 and tried to publish again. There is a hint for the service URL as "https://RemoteServer:8172/MsDeploy.axd" in the publish dialog but what
actually gets used is whatever you enter in the dialog plus an appended "/MSDEPLOYAGENTSERVICE" so the actual hint really should be "http://RemoteServer:80". I then received an error indicating that the application pool for the deploy was V2 and needed to
be V4. So I changed the default application pool to be V4. Finally, success in publishing.
I then tried to actually bring the web application up in IE with "http://localhost/appName" I fail with a "Could not load file or assembly 'System.ServiceModel.DomainServices.Hosting, Version=188.8.131.52...or one of its dependencies". I guess This is nothing
to do with web deployment at this point and I need to take this to an IIS/Silverlight forum?
Apr 23, 2010 02:49 PM|devonlazarus|LINK
Sounds like you had fun discovering the differences between the documentation and the implementation ;)
You've nailed everything from the install of the remote agent to the differences in ports.
You probably need to set the reference you have in your project for that dll to be "Copy Local," re-publish and it should work.
My guess is you've referenced that library because another library needs it, not because you've actually written code against it. In that scenario, the compiler will not copy the dll to the bin folder unless you specifically tell it to.
Apr 23, 2010 03:02 PM|Mark Stega|LINK
Thanks - it wasn't fun, but it did work in the end (Although I wish the service did show up in the service manager and the IIS manager). I am going to temporarily do the 'copy local' scheme until I figure out which package is the SL4/RIA services runtime.