I have windows 10 (pro) and IIS 10 installed on Server A. I was trying to publish a Web API from Visual Studio 2015 on Machine B to Server A, but I get the following error.
web deployment task failed. (Could not connect to the remote computer ("172.26.50.17") . On the remote computer, make sure that Web Deploy is installed and that the required process ("Web Management Service") is started.
I understood from googling that the web server need to have Management Service installed and running. I have installed web platform installed and I can see that the "Web depoy 3.6 without bundled SQL support(latest)" component installed.
But I still do not see management service icon under "management" section on IIS. Could anyone please help me understand this?
I solved it by installing the Web Platform Installer (Web PI).
Then you can add a lot of tools using this Web PI. One of those tools is Management Service which can be enabled via Web PI.
If you do that and still cannot see the Management Service, try closing and opening the IIS Manager again.
UPDATE:
For Windows 10 and later, see the #RBT comment below.
Related
How can I configure Web Deploy on Windows 10? Should it work?
I found information about Web Deploy on Windows 8, there it isn't working.
How is it in Windows 10?
Microsoft is being super sneaky about this, but it appears they have removed the ability to use web deploy remotely from ALL non server os's. Even in Windows 7, if you do all of the newest updates, the deploy menu vanishes in IIS. So if you want to use web deploy it seems like your only option is to shell out some bucks for a server os.
HOWEVER, I was able to get FTP publishing configured and working on my Windows 10 machine, which works almost as well. Just install the FTP server under control panel => programs and settings => install windows components. Then open iis mgr and right click on your site and a configure FTP publishing option should pop up. The configuration is a pain and not straightforward, but if you mess with it you'll figure it out.
Then in Visual Studio right click on your project, hit publish, then in the first screen in the drop down there is the good old fashioned ftp option. Good luck!
EDIT
From OP's response, another solution is to simply share the root folder on the server, so for example
C:/inetpub/www
Then mount that share on your development box, I mounted it as the P:\ drive for production, and Q:\ drive for qa. Then in visual studio on the publish screen just select deploy to file system and deploy to that mapped drive, works like a charm and is far simpler than setting up FTP.
Ok, I did this (in Windows 10):
Uninstalled Web Deploy 3.6 from control panel(didn't help).
Downloaded Web Deploy 3.6 installer, then ran uninstall from the installation menu.
Downloaded Microsoft Web Platform Installer 5.0.
From the Web Platform Installer 5.0, I installed Web Deploy 3.5 + Web Deploy 3.5 without bundled SQL Support
I seem to have the deploy context menu back when I right click a site.
Make sure you do the following:
Install web Deploy 3.6
Go to Server Manager > IIS
Under Server Roles go down to Web Server (IIS), expand this tree and select Management Tools.
Make sure "Management Service" is checked
Go to Services, Make sure "Web Management Services" is started. (go ahead and make it automatic while you're in there).
Now you'll see the "Configure Web Deploy Publishing" option under the Deploy menu on IIS. From there make sure you have port 8172 open from the IP you are publishing from.
Installing WebDeploy 2.1 (available from the Web Platform Installer) gives you a 'Deploy' option on your website in Windows 10
See: https://serverfault.com/questions/253292/why-dont-i-have-deploy-actions-available-in-iis-7-manager
I had a working IIS 7.5 with Web Deploy 3.5 configuration such that the "Import/Export Application" feature in the right hand action pane showed up and functioned properly. Unfortunately I had to remove and reinstall IIS, and now the Import/Export functionality does not show up in the Actions pane, as if Web Deploy was not installed.
I tried to reinstall using the automated installer at http://www.iis.net/downloads/microsoft/web-deploy, but when I run it, the installer seems to think that Web Deploy is already installed and does not offer me any reinstall/uninstall option.
How can I force a reinstall of WebDeploy or force IIS to recognize that Web Deploy is still installed?
Go to http://www.iis.net/downloads/microsoft/web-deploy
Scroll to the bottom of the page to the "Download Web Deploy" header
Click the x86 or x64 link next to your language of choice. Do not click the WebPI link.
Once downloaded, click on the installer to open it.
Click Next
Click the Remove button
Now you can reinstall it using the Web Platform Installer, or just use the standalone.
On a side note...
If you don't see the Deploy options in IIS once you've reinstalled Web Deploy, try running IIS as Administrator. Hope this helps.
I am running IIS on my development machine on Windows 7. Web Deploy 3.6 seem to break something as the Import / Export Application options are not available. Had to uninstall 3.6 via control panel add/remove programs and then install 3.5 via Web PI.
I've installed Web Deployment Tool 2.1 then restart IIS Manager and the Import/Export Application appeared.
I was running a 'gallery template' Windows Server 2012 VM on Azure. Web Platform Installer said Web Deploy 3.5 was already installed. At first I thought this neat feature had been removed/moved.
In Add/Remove Programs, saw that Web Deploy 3.6 Beta was installed. Removed it and reinstalled 3.5 (without SQL stuff) via Web PI.
Ran IIS Manager as admin and all works fine.
Update - A new Azure VM also had this problem, but had 3.6 Beta3 installed. Again, removed and reinstalled 3.5 via WebPI.
None of the other answers here fixed this for me with Visual Studio 17 on Windows 10. The fix was here: https://developercommunity.visualstudio.com/content/problem/230372/web-deply-40-msi-location.html
Web Deploy 4 has moved to be distributed with Visual Studio 2017. This is nuts because the Web Deploy service and the Import/Export tools are for server administrators and not devs. The discussion in the link says they are working on adding Web Deploy 4 to the Web Platform Installer, but have encountered a few issues (read: we didn't create a proper deployment for it the first place.)
The fix for me was to uninstall Web Deploy 4 from Control Panel-Apps & features, then reinstall from the MSI provided with Studio. Look in C:\ProgramData\Microsoft\VisualStudio\Packages for a folder like Microsoft.VisualStudio.WebDeploy.Msi,version=...,chip=x64. The MSI file is within that. More detail in the link I mentioned.
My guess is if the IIS Manager is not turned on at the time Studio (and therefore Web Deploy) is installed, the hook for Import/Export can't be created.
My situation is slightly different as I never had the import/export menus. For what it's worth:
I tried to install the Web Deploy installer. It said that a newer version was installed. I tried repairing Web Platform Installer. Nothing changed. I tried changing but was told there were individual components. I tried uninstall/reinstalling WebPlatformInstaller.
After that, the IIS Manager showed a Web Platform Installer icon under the Management section after restarting, but still no Deploy menu on the right click.
Double-clicking that icon started the installer where I could then search for web deploy. There was a Web Deployment Tool 2.1 that was not installed. Clicking Add then Install and restarting IIS Manager (not run As Administrator) was all that was needed to get the Deploy menu:
According to this Microsoft document, the Web Platform Installer should have started automatically. Never did. But it is in the start menu. The steps are the same weather you start it from IIS Manager or standalone.
I have a web application asp.net to deploy to Windows Azure. This application contains one web role. I try to run it on local first. But when debugging, I catch this error from VS2010: "Window Azure Tools for Microsoft Visual Studio
The Web Browser can not be started. To resolve this problem, you must restart Windows."
I have restarted windows several times, but there was no luck.![enter image description here][1]
I've search so hard to find the solution for this problem but there's nothing seems work for me. I'm a newbie in Windows Azure, it's really a big trouble with me. Please help me! Thanks a lot. Best Regards.
There could be two problems:
Problem with your IIS settings: It is possible that there is a problem with your IIS in your machine which could not be restarted when VS2010, wants to run it.
To verify it what you can do it launch your Web Role using "View in Browser" setting and see if your Web Role can run in IIS, you will see the web role started in a URL as http:\localhost:XXXXX and that would be the first step to resolved.
Problem will your Windows Azure SDK which could not launch the WebBrowser to run in IIS
If you don't have problem in this step #1, then it is possible that Windows Azure SDK has some problem trying to start your IIS from external process and this could be caused by corrupted SDK installation or any other reason.
If that is the case try:
remove all Windows Azure SDK components from your machine.
Restart the machine, Install Azure SDK from here for VS2010
After SDK install, restart the VS2010 in admin mode and try created a hello world webrole and see what happens.
I have a web application asp.net to deploy to Windows Azure. I try to run it on local first. But when debugging, I catch this error from VS2010:
"There was an error attaching the debugger to the IIS worker process
for URL 'http://127.255.0.0:82/' for role instance
'deployment16(6).WindowsAzureProject2.WebApplication3_IN_0'.
Unable to start debugging on the web server ......."
I've search so hard to find the solution for this problem but there's nothing seems work for me. I'm a newbie in Windows Azure, it's really a big trouble with me.
I had similar problem with Windows 8, debuging a cloud application with Visual Studio 2012 RTM and Azure SDK 1.71, when trying to launch the application into the compute emulator. It was a very simple app, but I used Azure diagnostics. At the end these are two things I have changed that have work for me, both turning on Windows 8 features (so go to Win8 and open 'Turn Windows Features On/Off'.
Activate the checkboxes for:
Internet Information Services Hostable Web Core
Internet Information Services > World Wide Web Services > Application Development Features > ASP.NET 4.5
Internet Information Services > World Wide Web Services > Health and Diagnostics > Tracing
Internet Information Services > Web Management Tools > IIS Management Scripts and Tools
That worked for me, it makes sense, as I'm using Visual Studio 2012 and trying to get some trace information using diagnostics in Azure.
I hope this will work for you or give some tip about the problem. In the case of being useful information, remember to vote as response or as value tip.
Thanks,
Mike
This usually happens when there's a problem with the project to be deployed to the emulator (WindowsAzureProject2 in your case).
Try the following:
Check %UserProfile%\AppData\Local\dftmp\IISConfiguratorLogs\IISConfigurator.log file for the error messages. See more details in this answer.
Make sure your project can be started without the emulator. It's a web project, so just try to start it as a regular web project. Or publish it to the separate folder and try to create a website in IIS of it.
Check your *.csdef and *.cscfg files to make sure all the configuration is correct.
Make sure that the build output of your project is not empty. You can do this by going to IIS, find the site with the name similar to deployment16(6).WindowsAzureProject2.WebApplication3_IN_0, right click --> Explore.... Make sure that this folder is not empty and contains all the files required to start a web project successfully.
BTW, there's a similar question: Debugger can't connect when starting local azure project
Follow step 11 from http://www.microsoft.com/en-us/download/details.aspx?id=35448. Worked for me on Windows 8 with Oct 2012 SDk
I just have today the same problem trying to Debug locally with Azure Storage Emulator in Windows 7. So in the Azure project properties, in Web tab, I checked the radio button 'Use IIS Express' and it debugged without problem. I hope this helps someone.
I encountered this exact same problem when I upgraded an existing Azure solution to the Azure SDK 2.1. After some hunting around I uncovered that the upgrade had automatically set the "Local Development Server" setting to "Use IIS Web Server".
Changing the "Local Development Server" setting to "Use IIS Express" fixed the problem immediately.
To access this setting right-click the Azure cloud project file in your solution, select the "Properties" option, tab down to "Web" and you'll see the following setup.
Also, make sure you run Visual Studio as administrator
Please check the version of emulator you have installed. If your code is created in older sdk and you have a new emulator installed it will give you this error.
Check the version of Azure APIs in your project, go to Project > references and right click on Azure dlls to check the version, same sdk version must be installed on the system, higher are optional as azure 2.x are not backward compatible.
I'm using IIS 7.5 on Windows Server 2008 R2 x64 Enterprise Edition. In the project we have developed with ASP.NET 4.0 we used WCF Service. But it doesn't run over domain when the software is running from local computer. Otherwise, I am getting the following error:
HTTP Error 404.3-Not Found
The page you are requesting cannot be served because of the extension
configuration. If the page is script, add a handler. If the file should
be downloaded, add a MIME map.
You should install IIS sub components from
Control Panel -> Programs and Features -> Turn Windows features on or off
Internet Information Services has subsection World Wide Web Services / Application Development Features
There you must check ASP.NET (.NET Extensibility, ISAPI Extensions, ISAPI Filters will be selected automatically). Double check that specific versions are checked. Under Windows Server 2012 R2, these options are split into 4 & 4.5.
Run from cmd:
%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -ir
Finally check in IIS manager, that your application uses application pool with .NET framework version v4.0.
Also, look at this answer.
In my case, along with Mekanik's suggestions, I was receiving this error in Windows Server 2012 and I had to tick "HTTP Activation" in "Add Role Services".
In windows server 2012, even after installing asp.net you might run into this issue.
Check for "Http activation" feature. This feature is present under Web services as well.
Make sure you add the above and everything should be awesome for you !!!
I was having trouble accessing wcf service hosted locally in IIS. Running aspnet_regiis.exe -i wasn't working.
However, I fortunately came across the following:
Rahul's blog
which informs that servicemodelreg also needs to be run:
Run Visual Studio 2008 Command Prompt as “Administrator”.
Navigate to C:\Windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation.
Run this command servicemodelreg –i.