Skip to main content

Team Foundation Server 2015–New build agents–Installation issue

Yesterday I talked about the new agent based build system introduced in TFS 2015. I mentioned how easy it was to install them, … until you get into trouble. Today I encountered an issue when rolling out an agent on existing server. When I invoked the ConfigureAgent.ps1 script, it failed with the following message:

PS C:\build> .\ConfigureAgent.ps1
Unblocking files
The term 'Unblock-File' is not recognized as the name of a cmdlet, function, script file, or operable program. Check th
e spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\build\ConfigureAgent.ps1:12 char:52
+ Get-ChildItem -Path $currentLocation | Unblock-File <<<<  | out-null
    + CategoryInfo          : ObjectNotFound: (Unblock-File:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

The term 'Unblock-File' is not recognized as the name of a cmdlet, function, script file, or operable program. Check th
e spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\build\ConfigureAgent.ps1:13 char:67
+ Get-ChildItem -Recurse -Path $currentLocation\Agent | Unblock-File <<<<  | out-null
    + CategoryInfo          : ObjectNotFound: (Unblock-File:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Cannot find an overload for "Combine" and the argument count: "3".
At C:\build\ConfigureAgent.ps1:15 char:43
+ $agentLocation = [System.IO.Path]::Combine <<<< ($currentLocation, 'agent', 'vsoAgent.exe')
    + CategoryInfo          : NotSpecified: (:) [], MethodException
    + FullyQualifiedErrorId : MethodCountCouldNotFindBest

Write-Error : File not found:
At C:\build\ConfigureAgent.ps1:19 char:16
+     Write-Error <<<<  "File not found: $agentLocation"
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Microsoft.PowerShell.Commands.WriteErr
   orCommand

When I invoked the $PSVersionTable.PSVersion command, it returned me the following:

Major  Minor  Build  Revision
-----  -----  -----  --------
2      0      -1     -1

To run the ConfigureAgent.ps1 script, at least version 3 of Powershell is required. Downloading a more recent version should solve the problem.

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...