Skip to main content

Scrum for Team System Template and Sharepoint problems

After upgrading a TFS from 2008 to 2010 at one of my clients, the default.aspx in the SharePoint portal for every TFS site that was using the Scrum for Team System template failed to load. Instead I got a 404 error. I noticed that the problem only occurred for the earliest projects which were created using the 1.2 version of the template. Projects created with the 2.x version kept working.


So I took a look in the log at: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS. Between all the information I found the following error message:

Cannot get ghost document: 1033\SCRUM\default.aspx
Failed to find <ListTemplate> tag corresponding to ID "104", tried both onet.xml for site definition ID "10719" language "1033" and global site definition. Operation failed.
Failed to determine the setup path of the list schema for list template 104.

The issue shows itself existing SFTS 1.2 projects showing a 404 error when navigating to the root of the Team Portal. This has been caused by the removal of files required for the WSS template. I found the following blog that describes the steps to fix the problem: http://consultingblogs.emc.com/sfts/archive/2008/04/28/sharepoint-fix-for-scrum-for-team-system-2-1-upgrades.aspx

However after executing the steps mentioned in the blog post, the sites still failed to load. I restored the backup files again and tried another solution. I browsed directly to the configuration pages by adding ‘_layouts/settings.aspx’ to the sites url. There I choose to reset the style by clicking the Reset to site definition option. Afterwards I was finally able to load the sites(although the layout was really messed up).

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