I have a website set up with a staging slot on Azure Websites. I am having trouble getting web deployment to work from Visual Studio 2012. I keep getting this error when I try to publish to staging or production:
Error 23 Web deployment task failed. (Could not connect to the remote computer ("[MYSITENAME].scm.azurewebsites.net") 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.)
When I go to publish, I select the staging site (or even the regular site) from the profile list dropdown. I "Validate Connection" and that turns out just fine. In the Settings area, under Databases, there are 2 options with the same name for each of the connections which is a bit odd.
Can anyone help? Thank you!
Related
I'm trying to get to grips with Google Cloud for a University Project.
I have created a .NET Google Cloud project on VS 2019 and I'm trying to deploy it to my Windows 2016 server on Google Cloud Platform.
However I keep getting the error:
D:\Program Files\Microsoft Visual Studio\MSBuild\Microsoft\VisualStudio\v16.0\Web\Microsoft.Web.Publishing.targets(4284,5): msdeploy error ERROR_DESTINATION_NOT_REACHABLE: Web deployment task failed. (Could not connect to the remote computer ("35.235.58.62"). On the remote computer, make sure that Web Deploy is installed and that the required process ("Web Management Service") is started.
What I've tried so far:
Checking server's firewall is open for inbound 8172
Disabled home PC firewall to make sure that wasn't the issue
Installed Web Platform Installer on the server
Added ISS Management Service through Web Platform Installer
Enabled remote connections on ISS
Any advice or help on the solution would be greatly appreciated.
Have you installed web deploy on your remote server?
Remote deployment also rely on Web deploy Agent service or Web management Service . Please ensure they have been started. Then you could check whether port number has been opened by making test with Tcping.exe from remote server.
The link provide the steps about how to publish with Management service from remote server：
Web Deploy from Visual Studio 2012 to a remote IIS 8 server
Just remember to set firewall rule like this:
Please ensure port 8172 has been enabled in both windows firewall and Google cloud external firewall.
If the management service is not working, you could try remote agent
https://learn.microsoft.com/en-us/aspnet/web-forms/overview/deployment/configuring-server-environments-for-web-deployment/configuring-a-web-server-for-web-deploy-publishing-remote-agent
The second part from Jokies Ding got it to work for me. (I'm unable to leave a comment on his post due to my stackoverflow reputation points not being 50 yet) I feel like I correctly followed google's instructions for getting web deploy to work with visual studio, but I was unsuccessful.
This below worked for me.
If the management service is not working, you could try remote agent
https://learn.microsoft.com/en-us/aspnet/web-forms/overview/deployment/configuring-server-environments-for-web-deployment/configuring-a-web-server-for-web-deploy-publishing-remote-agent
Following the online steps from google instructions to setup web deploy it should be something like this:
install web deploy
add user to IIS Manager Permissions
[skip] check google's firewall rules (VPC network>firewall rules) port 8172 (this won't be necessary since this remote agent route uses port 80)
start using https://learn.microsoft.com/en-us/aspnet/web-forms/overview/deployment/configuring-server-environments-for-web-deployment/configuring-a-web-server-for-web-deploy-publishing-remote-agent
(this is from step 5 instructions) add server name as host name in Site Bindings
(this is from step 5 instructions) ensure "Web Deployment Agent Service" service is running
configure visual studio publish profile using attached screenshot example (I was unable to get "Visual Studio > Build > Publish [Project Name] to Google Cloud..." to work.)
When you install Web Deploy, make sure to select Custom Setup and check all components. This is what solved the issue for me. IIS Deployment Handler wasn't selected
Source: Could not reach the Web Deploy endpoint on the specified virtual machine
I done with the asp.net-core api application at the back end and using angular-cli for the front end. Everything worked fine on localhost kestrel server or IIS express using Visual studio 2017 but on hosting on IIS locally, I do get the page loaded but its only problem when i try to login I get 500 server error but I dont get any information regarding error. It will be helpful if anybody tells me how to get it working on IIS
I tried to fix by changing some settings on the IIS server but I got no clue or fix.
Please download my source code and try running it https://github.com/abhilashlegend/DatingApp
I expect it to work as in the localhost server on the IIS
I fixed the problem go to SQL server management studio and under the database connection you find Security folder -> Logins. Right click and create new login IIS APPPOOL\datingapp
and under user Mapping select the database you want to grant access and select the database membership role db_datareader and db_datawriter and click ok. Restart sql server and iis server and fixed.
From web.config, Just set stdoutLogEnabled="true" and check the aspnetcore log files. You should check the file where stdoutLogFile attribute points.
I really need some help. It is driving me crazy and I don't know why it is not working.
Basically I am just trying to deploy my project to Google Cloud, but the process is bringing me an error and I can't understand why. The error below:
MSDeployPublish: Start Web Deploy Publish the Application/package to
https://35.238.89.74:8172/msdeploy.axd?site=MySite... Starting Web
deployment task from source:
manifest(\MySiteFolder\obj\Release\Package\UANL.SourceManifest.xml) to
Destination: auto(). C:\Program Files (x86)\Microsoft Visual
Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\Web\Microsoft.Web.Publishing.targets(4292,5):
msdeploy error ERROR_COULD_NOT_CONNECT_TO_REMOTESVC: Web deployment
task failed. (Could not connect to the remote computer
("35.238.89.74") 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.)
[\MySiteFolder\MySite.csproj] Publish failed to deploy. Done
Building Project "\MySiteFolder\MySite.csproj" (WebPublish target(s))
-- FAILED.
It is something that I can't do anything (I guess) because it is inside Google Cloud application.
I saw something related to Firewall but I checked everything and seems to be fine. I don't if I am right, but if it is the problem, please give me a step by step, because it is so confusing.
Thanks in advance for you help!!
This error ERROR_COULD_NOT_CONNECT_TO_REMOTESVC cost me two days to figure out that for my case, the site name didn't match. The site name on the remote IIS server was different from the site name i had set in visual Studio for the deployment
I am attempting to deploy a web site remotely using the Web Deployment Agent Service. When running the cmd file generated by Visual Studio using /m command switch, I get the following error:
Error Code: ERROR_COULD_NOT_CONNECT_TO_REMOTESVC
More Information: Could not connect to the remote computer ("x.x.x.x") using the specified process ("Web Deployment Agent Service") because the server did not respond. Make sure that the process ("Web Deployment Agent Service") is started on the remote computer. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_COULD_NOT_CONNECT_TO_REMOTESVC.
Error: The remote server returned an error: (500) Internal Server Error.
I checked the link and it has 3 suggestions. Make sure the service is running which it is. Make sure that the user is an administrator which it is and make sure the firewall isn't blocking the traffic which it isn't.
I turned on wireshark to see if that would get any clues and I get the initial 401 Unauthorized from the deployment service and then the client makes the request again using NTLMSSP_NEGOTIATE. That is when the deployment service returns the 500.
I am guessing it is some sort of permissions thing on my deployment server, but I can't narrow it down. Does anyone know where the Web Deployment Agent Service logs or how to turn on logging for that service?
If you look at this article about setting up Web Deployment server
https://technet.microsoft.com/en-us/library/dd722796(v=ws.10).aspx
in step 6 it points to this artical about setting up logging adn tracing
https://technet.microsoft.com/en-us/library/ee461173(v=ws.10).aspx
Did it work previously? I've had the same issue, WebDeploy suddenly broke down after a reboot on 19th december, some windows update. I've had to remove WebDeploy 3.6 from program and Features and then to uninstall the IIS Webmanagement Role through the server manager.
After rebooting i've installed Web Deploy 3.6 for Hosting Servers through Web Platform installer again and it worked again.
This is being a pain. I had a working logging system using web services but connecting to my local. Now i have launched them onto my web server i have come across a dilemma.
When i create an account the program goes through the web service and saves the information on the web server.
But now when i go to log in. I get this error:
"Unable to automatically step into the server. Connecting to the
server machine "EXAMPLE.COM" failed. The Visual Studio Remote Debugger
does not support this edition of windows.
Anyone have any ideas?
Thank you
If you want to remote debug the web services which are running on remote server you have to install the Remote Debugger on that server where they are depoyed. Here you can find how to do that
After this you can attach the remote process as you normally would do for a local one.