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

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
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

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