Skip to main content

TFS 2013 installation error: TF400069 You must install either SQL Server Analysis Services version 11.0

Rolling out a Team Foundation Server environment is always an adventure. Everytime I discover some new stuff. Last week at a customer I was setting up a new Team Foundation Server 2013 server when I got the following error message:

TF400069: You must install either SQL Server Analysis Services version 11.0 or the SQL Server Client Tools.

clip_image002

Did I forgot to install something? I went through the SQL Server Installation wizard(slow!) to see that I had indeed the SQL Server Client Tools installed. Just in case, I removed and reinstalled them… no difference. I had no clue so I even tried to install the SQL Server Analysis Services but even that made no difference.

It took me some time to figure out what I did wrong. Let’s have a second look at the error message (and especially look at the highlighted text):

TF400069: You must install either SQL Server Analysis Services version 11.0 or the SQL Server Client Tools.

Team Foundation Server 2013 requires at least SQL Server 2012 with SP1, I had installed the SQL Server 2008 R2 version Verwarde emoticon.

Labels:

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.
Read more

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...
Read more

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         ...
Read more