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.
Related
I'm having issues with ASP.NET Core 6 app on my VPN Windows server 2019. Basically, I have Syncfusion OCRProcessor with tesseract files, but my application can't find part of the path for tesseract binaries on server when locally is working fine (on server error message is "cannot find part of the path C:\inetpub\wwwroot\myapp\x64").
After contacting Syncfusion support didn't solve the issue, I have checked for permissions in file system, double checked the locations of the binaries on IIS, checked if dll's are blocked in from Windows in file system. I have tried to connect from my machine with VS 2022 Community to my VPN server (public IP address) to try to debug the application, but going trough all the documents about remote debugging, still I can't connect to my app and hit the breakpoint in code to determine what is happening..
I have installed remote debugger for VS 2022 onto server, configure it and started, I have published application again over web deploy with debug config to IIS, but I just don't understand next step - how to attach to the process on external server..
Most of the videos and documentation suggests that IIS is installed locally on development machine, or IIS is on some PC in local network, but I have public server.. Can anyone help with the advice how to proceed further?
Thanks!
Ok, I have managed to connect debugger from VS 2022 to IIS.
The issue was in port, firewall and also in description on Microsoft help site https://learn.microsoft.com/en-us/visualstudio/debugger/remote-debugging-aspnet-on-a-remote-iis-7-5-computer?view=vs-2022 where in step 3 is written "Set the Qualifier field to and press Enter." - you need to enter ip address and port into connection target textbox.
After succesfull logging in onto server, I needed to select w3wp.exe process with title "CoreApp: https://.. ", set breakpoint in VS 2022 and open ASP.NET Core app in browser. After that I managed to debug application on IIS.
Hope this would be helpful to someone!
I can't get my IIS site to run and I've tried most of the solutions I've seen. I started with a clean IIS server for testing this. If I try to access via the DNS name I get a 503. If instead I get on the webserver and run dotnet path\to\app.dll it starts without issue, and I can then curl localhost:5000/weatherforecast and get back the default JSON. So the app itself is clearly fine and working, it's something in the IIS config. Here's what I did:
Installed the .NET Core Hosting Bundle on my Windows Server 2019 system, then rebooted.
Ran Computer Management and in System Tools -> Local Users and Group -> Groups I added the domain account to both Users and IIS_IUSRS groups.
In IIS Manager I created a new site and set the binding to my DNS name on port 80.
Set the application pool for that new site to No Managed Code for the CLR version and set the identity to the domain account.
Created a default VS 2019 ASP.NET Core API, set the target framework to .NET 5.0
Published, via a Folder Profile, with a target framework of net5.0 and a runtime of win-x64.
Restarted the IIS site then went to http://my.domain.name/weatherforecast and got a 503.
I'm not even remotely close to being an IIS administrator, so at this point I don't know how to further debug the issue.
I attempts to setup IIS (version 6.0, windows 2003 server) sit in front of IBM WAS server so that it can route all specific traffic to IBM WebSphere application server. I've things setup on both UAT and pre-production IIS web server and its works just fine. The problem happens now, however, only in production server. I investigated the websphere plugin logs (defined in plugin-cfg.xml) and found the following errors
iisWASPlugin_http.dll Out-of-process ISAPI extension request failed.
Tried google the solution but no luck.
Setup procedures is summarized below
Install IBM Installation Manager
Install Web Server Plug-ins for IBM WebSphere Application Server and Version 8.5.0.0 through IBM Installation Manager
Copy Plugin-cfg.xml, Plugin-key.db, Plugin-key.sth from WAS to web server.
Configurate IIS web site - create virtual directory named sePlugins, Add ISAPI filter with iisWASPlugin_http.dl, add Web service extension
Create plugin-cfg.loc, paste the full path of plugin-cfg.xml to plugin-cfg.loc
The procedures above already working in UAT and pre-production environment.
Details setup procedures is exactly the same as the url below
http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=%2Fcom.ibm.websphere.express.doc%2Finfo%2Fexp%2Fae%2Ftins_manualWebIIS.html
(Refer to "Configure IIS Version 6.0." section)
Note: IIS have "IIS 5.0 isolation mode" turned on.
Any help / hints is greatly appreciated.
Thanks in advance.
Regards.
The error gone after a server reboot...
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).
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