0

I am unable to install the VSTS Agent Azure VM extension on an Azure VM. I tried both the Install extension blade in the Azure portal and the Powershell option. When I try from the portal it just gets stuck at transitioning. If I run the Powershell script it gets stuck trying to connect to server.

I was able to install it on another server without any issues. The 2 servers are part of a web farm so they are exact images.

I am following the steps detailed at this url https://learn.microsoft.com/en-us/vsts/build-release/concepts/definitions/release/deployment-groups/howto-provision-deployment-group-agents?view=vsts .

I am trying to deploy from VSTS to an Azure VM.

This is the screen when I try to run the powershell script.

enter image description here

webdevbing
  • 322
  • 1
  • 3
  • 12
  • Do you mean the way Run the installation script on the target servers (shows in https://learn.microsoft.com/en-us/vsts/build-release/concepts/definitions/release/deployment-groups/howto-provision-deployment-group-agents?view=vsts#run-the-installation-script-on-the-target-servers) also fail to deploy the deployment group to your Azure VM? And can you share related screen shots for the error you meet? – Marina Liu May 03 '18 at 06:03
  • There is no error. It just shows "connecting to server" or similar and stays there. I can only try the script again in the next change window as its a production server. If I try to install from the Azure portal extensions blade it doesnt complete either. No error just the status shows "transitioning". – webdevbing May 03 '18 at 16:48
  • Can you show the screen shot when running the copied script on your VM by PowerShell (note: the PowerShell should be run as administrator)? – Marina Liu May 04 '18 at 06:31
  • I've added a screen shot. Last time I ran it it went one step further and tried to connect to the server. This time it got stuck here itself. – webdevbing May 10 '18 at 11:02
  • The script downloads the VSTS Agent and then configure it automatically. What's the result if you do it manually? – Eddie Chen - MSFT May 16 '18 at 01:52
  • @EddieChen-MSFT the screen shot is from when I run it manually. It just stays on that screen. – webdevbing May 17 '18 at 02:55
  • @Bipindas I mean download the VSTS agent and extract it manually. And then run config command to config it manually. – Eddie Chen - MSFT May 17 '18 at 04:19
  • @EddieChen-MSFT will this work with deployment groups? – webdevbing May 24 '18 at 05:37
  • @Bipindas Yes, it will work. – Eddie Chen - MSFT May 31 '18 at 02:48
  • @MarinaLiu-MSFT I've updated the screen shot to the point where it says connecting to server and stays there. – webdevbing May 31 '18 at 09:54

1 Answers1

0

Run the config file directly (from C:/vstsagent folder) in cmdline and try again with dev.azure.com/{organisation name} url.

Stephen Rauch
  • 47,830
  • 31
  • 106
  • 135
  • Please provide more detail. Under c:\vstsagent there are 2 folders, A1 and A2. Which config should I run? And what do you mean by try again with dev.azure.com/{organisation name} – webdevbing Nov 15 '18 at 09:36
  • Can you please share screenshot of the vsts agent folder. AFAIK, there shoudn’t be any a1 or a2 folders inside that. Also, can you download and extract the vsts agent file and run the config file manually ( in command prompt as admin). I think someone has already mentioned about it + run in command prompt ( I got the same issue waiting for server when running in power shell) – Devinder Rana Nov 18 '18 at 01:32
  • A1 and A2 appears be to be duplicated folders when I try to run the extension twice. I cleared them out for a fresh start. When I run config directly it doesn't ask me for the Deployment Group. It only asks for the Agent Pool. It seemed to complete but the server wasn't showing up in the deployment pool. – webdevbing Nov 23 '18 at 07:00