I am trying to learn how to setup Web Deploy functionality on both sides Server and host/client computer. Created a Windows Server 2012 Web Server in Hyper-V and able to access default web page in host/client computer. On server installed Web Maintenance Service, Web Deploy 3.5 and performed all the required steps e.g. "Configure Web Deploy Publishing" and added Administrator to IIS Manager Permission for the website in IIS. I disabled Firewall totally to make it work for the first time.
On client computer I created a dummy MVC Application in Visual Studio and trying to create publish profile for this app. As soon as I hit the Validate Connection I got the option to receive and save the security certificate from server but after that in gives me following warning (snapshot):
Tried doing all the steps all over but no luck.
I am open to all feedback. Thanks in advance.
Found the solution. Instead of adding publish information manually, I am suppose to use publishsetting file generated in server through "Configure Web Deploy Publishing" feature of IIS. Server address ends with file name which ends with .axd
Related
I am using SharePoint 2019 on premise and hosting our .net application into it.
I created a site in share point using port 80 and i can deploy my application into it with no problem.
while creating multiple site to host the same application system is not allowing to host application other than 80
Error:-
error occurred in deployment step recycle IIS application pool the local sharepoint server is not available.Check the server is running and connected to the sahre point farm
Please try to do some troubleshooting:
Clear the visual studio's cache.
Open VS as Administrator.
IIS reset executed before every deploy.
Use the account has full control and is the primary site collection administrator.
Restart the server.
Similar issue for reference: Getting Error occurred in deployment step 'Recycle IIS Application Pool': A task was canceled when deploying custom action to Sharepoint
I'm getting a time out error in VS Publish Web module when trying to validate my http connection to our Azure VM. I'm simply looking for a better way for our small dev team to deploy our MVC website to the VM other than publishing to file or publishing to FTP.
I've got Web Deploy on our Windows 2016 server, and the proper
services are running.
Remote Service is installed with Web Deploy.
Port 8172 is open and I am able to connect using Telnet from my
remote box.
I updated the pubxml file with:
<AllowUntrustedCertificate>True</AllowUntrustedCertificate>
<UseMsDeployExe>true</UseMsDeployExe>
<UserName>un</UserName>
<Password>pw</Password>
Not sure what else to try at this point, but this has been a PITA to say the least. Thanks for any input! FYI - This is not Azure Classic.
Screenshot of Error
I was trying to publish a web application to remote server (amazon windows server 2012) using Visual Studio 2012. Following is the error I am getting.
Web deployment task failed. (Could not connect to the remote computer ("amazon-server-name"). On the remote computer, make sure that Web Deploy is installed and that the required process ("Web Management Service") is started.
I did go through several articles mentioning this issue. Also both the web management service and web deployment agent service is running on remote machine. Also in IIS’s management service part I did enable the remote connection. When try to deploy a website from server machine itself, it’s working. But from my local machine to windows server it’s showing error like cannot connect to remote server. Anyone has any clue on how to solve this issue?
Note: Microsoft Web Deploy tool 3.5 is running on both server and the local machine.
Looking forward.
What happens when you try just using FTP in Visual Studio? You mentioned "web project", I know some Visual Studio things are iffy with connecting to web servers. Just try a simple FTP into the server, then you should be able to save/test/deploy projects and files that way.
If you're still having problems, there's just an unlimited amount of problems that could cause this (hence why I don't work on Windows servers anymore). Could be ports, firewalls, security settings, folder permissions, user privileges, any combination of things. Good luck.
I have a remote Windows 2012 server running IIS 8 from which I am hosting a web application. My local development box is running Visual Studio 2012. Currently I am publishing my app as a web deployment package (.zip), RDP'ing to the production server, copy + pasting to a folder and deploying the application from within IIS. My question is, what changes do I need to make to deploy directly to IIS from Visual Studio 2012 using the web deploy option?
I have tried to follow this guide but it refers to a service URL which I must obtain from my hosting company. I don't have a hosting company, my server is co-located.
I am presented with the following options:
Is the username and password the one I use for the RDP account? I already have Web Deploy 3.0 installed on IIS do I need to enable further settings?
OK I found the solution but it took me a whole day to get it working! Basically the steps are as follows. This is very sketchy but see the detailed guides below which helped me.
Enable the IIS Web Management role feature.
Install Web Deploy 3.0 (or higher). Make sure to customise the install to include the handlers (See notes below). If you're not presented with this option go to add/remove programs, find webdeploy, right click and select "change" option.
In IIS click on the server node and find the "Management Service" icon. Enable remote access and configure a dedicated IIS User for remote deployment (These will be the credentials that will go in the user name and password boxes).
At the site level in IIS assign this user to manage the website.
Make sure port 8172 is open on the web server (you can check this port here).
Try reconnecting from Visual Studio. There was some trial and error here for me but the error messages do link to a MS guide for decoding :)
Even after connecting successfully I had to wrangle with permissions, so my IIS user had sufficient privileges to create the app pool, directories and general file management jobs.
The following links really helped!
Configuring the handler on the web server:
http://www.iis.net/learn/publish/using-web-deploy/configure-the-web-deployment-handler
Connecting via Visual Studio:
http://msdn.microsoft.com/en-us/library/dd465337(v=vs.110).aspx
NOTES:
To ensure the handler is running, login into your IIS server and point your browser to the following URL.
https://<servername>:8172/MsDeploy.axd
F12 to open up the dev tools to see the HTTP response. Also MsDeploy also creates IIS logs in inetpub/logs which should give you some clue if you're having connectivity problems.
I had the same problem and this post was very useful to help me solve the issue. I had anyhow serious troubles while trying to install Web Deploy on my Windows Server 2012. The installation of Web Deploy 3.0 was giving me several errors and it couldn't be completed.
I tried to solve the problem installing "Microsoft Web Platform Installer 5.0" from http://www.microsoft.com/web/downloads/platform.aspx but it didn't solve it.
I thought it was due to Firewall Settings, Authorizations issues, Users without permissions or something like that. Finally I found out it wasn't due to any of the mentioned reasons.
I found the most simple solution and I hope it will help other users too: it was enough to download Web Deploy 3.5 installation directly from Microsoft Website:
http://www.microsoft.com/en-us/download/details.aspx?id=39277
This may sound banal but it solved it. I was able to install "Web Management Service" but not the second needed IIS service "Web Deployment Agent Service".
I have been using an open source WebDAV framework named "Sphorium" for quite some time to talk to my data repository.. I have been using Cassini web server to host my WebDAV server module and everything was working just fine if I map the server as a web folder in my system. However, i found that Cassini web server does not support "https". So, I started looking out for deploying my WebDAV server application in IIS.. So I built a website in ASP .Net which talks to the Sphorium WebDAV module and authorizes the user. And when I run my website using the VS Debugger, it gets hosted on the ASP .Net development web server, prompts for the credentials and works just fine. However, if I publish my web app and try to host in in IIS, and try to browse, it prompts me for the password for 3 times and finally says "Unauthorized"...
Could someone pls throw some light on how I can use IIS in this case? Do I have to give any permissions?