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

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

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

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more