I've got a local iMac with the remotebuild agent, but get this error message when I try to run or debug on my PC:
The remote build client certificate is missing
As a test, I provisioned a remote mac with MacinCloud, and get the same error.
In both scenarios, I've run:
remotebuild resetServerCert
remotebuild generateClientCert
...on the remote machine, received the credentials, and added them to Visual Studio.
Related
Error image Unable to Remote Deploy my Webservice on to the remote machine from local machine. I have two servers that i would be needing to enable web deployment from local system to remote server Windows 2012 system. Upon searching multiple resources i found below steps that need to be ensured before performing the remote deploy using MsDeploy from Local to Remote .
Also Package works fine which is built from Visual Studio if i copy the files on to the remote server and run the command file it is able to deply the windows service on to IIS locally . But i would need this to be deployed from my local machine to remote server*
Steps I tried :
Ensure Web Deploy is installed.
Remote Services are running.
Under Management Service in IIS ensure Enable Remote connections
is enabled.
Ensure 80 and 8172 Ports are enabled and running ( ran the below steps )
Web Deploy is installed on the server that i'm trying to deploy the
package.
I try running the below code and it returns below error :
Command I provide :
C:\Users\xxxxx>net start wmsvc
The requested service has already been started.
C:\Users\xxxxxx>net start msdepsvc
The requested service has already been started.
Command I provide :
C:\Program Files\IIS\Microsoft Web Deploy V3>msdeploy.exe -verb:sync -source:package="C:\Users\xxxxxx\Desktop\" -dest:auto="",ComputerName="https://serveripaddress:8172/MsDeploy.axd",UserName='domain/user',Password='password',AuthType='Basic' -allowUntrusted
Info: Using ID 'someinfoid like : 92c-da-sd-2398as823...... is generated' for connections to the remote server.
Error Code: ERROR_DESTINATION_NOT_REACHABLE
More Information: Could not connect to the remote computer (""). On the remote computer, make sure that Web Deploy is installed and that `the required process ("Web Management Service") is started.
Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_DESTINATION_NOT_REACHABLE.
Error: The remote server returned an error: (404) Not Found.
Error count: 1.
Installed Web Deploy Components
Ensured the Services are enabled ( Web Deploy / Remote Services )
Remote Server : Windows 2012
Local System : Windows 10
When I'm trying to publish using Web Deploy (Visual Studio 2017 for Windows) to a Linux app service hosted in Azure the following error occurs:
Could not connect to the remote computer ("my-linux-api.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.
The remote server returned an error: (405) Method Not Allowed.
The link in the error description seems to refer windows based hosts.
The service is up and running and responds to my request:
How can I fix that?
There is no Web Deploy on Linux. That's a Windows/IIS thing.
Push with git instead. The .scm. service (Kudu) knows how to handle the ASP.NET Core deployment on Linux.
I have VS2015 with RTools and RTVS on a windows 10 machine.
I also have a Server 2012 with SQL Server, with R Server, and RTVS R Services installed.
I cannot connect the Win-10 RTVS to the RServer using Remote connections. I have done the following things:
On the Server:
Installed the Certificate
Installed R Services. Found both Services R Host Broker Service and R User Profile Service alive and running. The associated json is also set.
Found both programs listed on the Windows Firewall for allowed on inbound and outbound connections
Ensured .net 4.6.1 is set
On the Client Workstation:
Installed R Tools for Visual Studio on top of Visual Studio 15 (SSDT)
Installed Microsoft R and other related programs.
Copied and added the certificate from the server to the workstation's list of trusted certificates.
Ensured .net 4.6.1 is set
Added Server to Workstation's list of remote workspaces in VS. Called the workspace 'simulator'
I can telnet to rserver.domain.com with port 5444 to ensure port is listening.
however, when I go to connect to the remote workspace I get this error:
Connecting to R Workspace failed.
Reason: Machine 'Simulator' appears to be online, but the Remote R Service is not running.
>
I'm missing something, and don't know what. Where do I go from here?
Thanks.
I have functionality in an ASP.NET application that runs a cmd process that uses PSCP.EXE (Putty) to copy a file from an external Linux server to the local server. When I run the ASP.NET application interactively by using the Run command in Visual Studio 2010 it works fine. However, when I deploy the application to IIS (on the same server!) and try to run it I get an error coming back from the PSCP.EXE command line. The error is this:
Fatal: Network error: Connection timed out
Does anyone know why I would get a connection timed out error when running the command from IIS 7 on my box, but when I run it through Visual Studio on the same box it works fine?
We have 1 new DEV and 1 new QA server that I am configuring for automated deploys. I got the DEV deploys working. My problem is that the deploy to QA is giving me the below error.
Our build server contains the controller and drop folder. The error occurs when the Invoke deploy command is issued. I have ensured that the Web Management service is running on the web servers.
What could be causing the follow error message?
Error Code: ERROR_DESTINATION_NOT_REACHABLE
More Information: Could not connect to the destination computer ("myWebServer").
On the destination computer, make sure that Web Deploy is installed and that the
required process ("Web Deployment Agent Service") is started.
Error: The remote server returned an error: (404) Not Found.
Error count: 1.
Here is my deploy command:
\\myBuildServer\Builds\MyApp - Deploy to QA\myApp - Deploy to QA_20120827.1\_PublishedWebsites\AppName.UI.Web_Package\Appname.UI.Web.deploy.cmd /M:http://myWebAddress/MsDeployAgentService/ /U:myDomain\tfsUID /P:MyPassword "-setParam:name='IIS Web Application Name',value='MyWebAppName'" /Y
If you're on IIS 7, ensure that WMSvc is installed (add or turn on Windows features) running, that it is configured correctly and enabled in IIS Manager under "Management Service" and that port 8172 is open - try telnet-ing into it.
If IIS 6, install the Web Deploy agent.
For IIS 7 using WMSvc, you should use http://svr:8172/MsDeploy.axd and for MsDepSvc you are already using the right URL (see your /M param).
I've found the whole remote publishing to be a total ballache.
When you install Web Deploy, make sure to select Custom and check all components. This is what solved the issue for me.
Source: Could not reach the Web Deploy endpoint on the specified virtual machine