I am running through the procedure to create a Windows 2012 Server, and I need Remote Access enabled. However, when I run through the installation process, it tells me I need to install IIS. Well I don't want IIS because I will have an Apache server running, but I have no choice. In Windows Server 2008 there was no need to install IIS when configuring Remote Access ( which used to be a part of Network Policy and Access Services ).
What can I do if I need Remote Access, need Apache, and don't want IIS?
To solve this I simply deleted the default website created with IIS, restarted Apache and it works fine.
Related
I have a Windows 2012 Server via VPS hosting.
I installed IIS and MySQL last week.
I have no way to remotely access the MySQL db, so thought I'd try to set things up so that I can access it remotely.
I have installed XAMPP this evening, and installed Apache and PHP onto the server.
My domain name. e.g. mysite.com is linked to the VPS hosting, so that I can go to e.g. localhost/index.html and also mysite.com/index.html and see the same page.
I had to configure apache so that I could connect to it at the same time as running IIS, so access it via localhost:8080/phpMyAdmin/index.php. When connected via remote desktop connection, I can also access that via mysite.com:8080/phpMyAdmin/index.php.
However, if I disconnect the remote desktop connection and try again to get to mysite.com:8080/phpMyAdmin/index.php I get a timeout error.
I seem to only be able to access that URL when on the actual server that the site runs from, even though I can use the full external URL.
I wondered if there any way around this?
We are trying to configure continuous integration with TFS 2012. While queuing a new build, the publish fails with the error:
Build FAILED.
"C:\src\ProjectName.sln" (default target) (1) ->
"C:\src\Website\ProjectName.csproj" (default target) (2) ->
(MSDeployPublish target) ->
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Web\Microsoft.Web.Publishing.targets(4377,5): msdeploy error ERROR_COULD_NOT_CONNECT_TO_REMOTESVC: Web deployment task failed. (Could not connect to the remote computer ("ServerName") using the specified process ("Web Management Service") because the server did not respond. Make sure that the process ("Web Management Service") is started on the remote computer. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_COULD_NOT_CONNECT_TO_REMOTESVC)**
I checked all the points mentioned in the IIS.NET documentation for this error. Both services mentioned, Web Management Service and Web Deployment Agent Service, are running fine. A restart of those services has no change in behavior.
Windows Server 2008 R2 with IIS 7.
Web Deployment Agent Service is running on port 8172.
Web Deploy 3.0
Windows Firewall is not blocking any port on the server.
How can this be fixed?
If you install Web Deploy 3.x BEFORE Web Management Tools are installed, you'll have to re-install Web Deploy. I beat my head against the wall for hours on this.
Install the Web Management Services ("Turn Windows Features On/Off"/Roles -> Web Server -> Management Tools -> Management Service)
Then uninstall Web Deploy (repair didn't work) via the usual Add/Remove Programs control panel
Install Web Deploy 3.x again using Web Platform Installer.
Fixed. /Sigh
Double check in your Web Deploy settings that the name of the website is exactly that of what's in IIS.
Ben Day blogged more about it.
Fix that i saw on another website:
Fix it by adding “http://” to server.
In other words, when server is www.xxxx.com would get the 403 error, but when server is http://www.xxxx.com, then it works.
You need also to indicate the app name e.g 'Default Web Site/MyApp'
That was my error. Once I added /MyApp, it worked.
I got this error when using msdeploy, not TFS. In my case I needed to make sure the user msdeploy is using had permission to deploy to the website.
Find the website in IIS manager, right click and go to Deploy, then Configure Web Deploy Publishing. Find the user used by Web Deploy and setup for this website.
In my case the Internet proxy was enabled on source - which made msdeploy to reach out to internet instead of local ICN.
You should check the logs on your IIS first - see that you actually get to the server, and then you can locate the exact error here - https://support.microsoft.com/en-us/help/943891/the-http-status-code-in-iis-7-0-iis-7-5-and-iis-8-0
Uninstalling and re-installing (not repairing!) after setting up IIS did most of the magic for me.
There is another possible cause of the error. IIS Managemente Service have its own configuration for IP Address Restrictions, which default value is Deny Access for unspecified clients (Windows Server 2012 R2 with IIS 8.5).
You must set this value to Allow or add access to your specific IP address/IP address range using the Allow... button.
Remember, you must Stop the Management Service previously to change this configuration.
When trying to launch solution, I receive the following error:
error : The Web Application Project MyApp is configured to use IIS. The Web server 'http://localhost:64646/' could not be found.
How do I resolve this issue?
I opened IIS and set the TCP port on the Default Web Site to 64646 and the project loaded without error.
You need to install IIS on your development machine.
Using IIS you'll also need to run Visual Studio in Admin Mode as well.
It is recommended that you use IIS Express since it will allow you to run VS without Admin privileges.
You have to install IIS and create the web site in IIS with the matching port number. Someone else created the visual studio web project to use IIS and configured it on their computer. Each person who opens the solution has to have all the websites configured in IIS manually.
You might consider creating a script that auto-creates them in the source repository. You can do it using AppCmd.exe (ADD SITE, ADD APPPOOL, LIST APPPOOL, LIST SITE) (%windir%\system32\inetsrv\AppCmd.exe).
I'm developing a WCF webservice, but when it loads via visual studio in the built in server (Cassini) I cannot access it anyway except via localhost on that machine. I would like to try it with connections from other machines as well though... what's the best way to do this without installing IIS on my box (I can't...stupid system corporate policies prevent it).
You might be able to use / install IIS Express (see this link) without administrative privileges. However sadly Cassini does not allow remote connections.
If I am not mistaken, you should install IIS. Cassini does not support remote connections.
Each time when i start my server , i need to go to IIS and then need to start the each web application manually. i want to start all web application automatic as my server starts. You will wonder why I m shuts down my server again and again. But it is test server. so that only. anyway. which service have to make automatic? It is Windows Server 2003. using IIS V6.0
Check if the iis service is set to start automatically. For this go to the Services MMC and ensure that the World Wide Web Publishing Service is set to start automatically. If there are no problem with the sites, they should start automatically. Also check here: http://www.eggheadcafe.com/software/aspnet/30451499/how-to-set-default-web-s.aspx
IIS(Microsoft web server) server are mostly installed in windows operating system(OS) ,we want to just start a service only,if iis server not installed then easily download and install in windows.
For More Reference