Skip to main content

Error while creating a new Team Project on TFS 2010

When I tried to create a new Team Project on TFS 2010, the creation failed when I arrived at the Sharepoint part with the following error:

Exception Stack Trace:    at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.HandleSiteCreation(WssCreationContextWrapper contextWrapper, XmlNode taskNode)

   at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.Execute(ProjectCreationContext context, XmlNode taskXml)

Inner Exception Details:

Exception Message: TF249033: The site template is not available for the locale identifier (LCID). The site template name is: VSTS_CMMI_2. The LCID is: 1033. (type SoapException)SoapException Details: <detail exceptionType="TeamFoundationServerException" />

Exception Stack Trace:

--- end Exception entry ---

The reason was caused by a missing Sharepoint template with the name VSTS_CMMI_2 which wasn’t installed automatically after upgrading our TFS server to the 2010 version.

To solve the issue, execute the following steps:

  • Log on to the old Sharepoint site you used before the TFS upgrade.
  • Click on Site Actions and choose Site Settings.
  • On the Site Settings page, click on Site Templates under Galleries.
  • Click on the correct template to download the STP file.
  • After downloading the template package to your PC, log into the new SharePoint site.
  • Select Site Settings from the Site Actions rollover menu.
  • Select Site Templates from the Galleries column.
  • Select Upload. If you have multiple templates you would like uploaded, select Upload Multiple Files from the Upload rollover menu.
  • Browse for template(s) you would like uploaded, then click OK.
  • Your template(s) have been uploaded.
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