Skip to main content

TFS 2012 Update 1 issue: Assigned to field is ‘Unknown’ in all reports

After upgrading from Team Foundation Server 20120 to 2012, everything looked OK. However when we looked at the reports, we saw that all user names were gone and the only value we saw was ‘Unknown’.  I took a look at the Team Foundation Server database, but all data was there as expected. So clearly something went wrong, when building the data warehouse.

Our first attempt to fix it, was just doing a full rebuild of the warehouse but no luck. The issue was still there.

I started to look around on the Internet and discovered the following update: Update to Team Foundation Server Update 1 (KB2803625)

In the list of issues this update fixes, I discovered point 5, which was exactly the issue we were having:

  1. Collections that are attached to a server that is running TFS 2012 Update 1 may lose permissions
  2. Group scopes may incorrectly cause permission errors
  3. Severe decrease in performance after TFS 2012 Update 1 is installed
  4. Identity sync jobs may fail repeatedly
  5. Warehouse is not updated correctly, or fields that represent a person are not filled
  6. Users can see names of collections of which they are not a member
  7. You cannot remove a user or a group after you attach a collection to a TFS 2012 Update 1 server
  8. You cannot view artifacts that reference an identity that is no longer a part of a collection

So I downloaded and installed the update on the TFS application tier.

Remark: After installing the patch, you will need to manually initiate a rebuild of the warehouse in order to correctly populate the fields which reference people for the latest revisions of work items.

After the rebuild, the issue was gone and the data was finally there…

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