It's a rough time (9PM EST) but some of the TFS heavyweights created a Virtual TFS User Group. Your local ALM group (COALMG) clearly is superior in community and value, however. ;-)
TFS Error | The type initializer for 'Microsoft.TeamFoundation.Build.Server.BuildInformationNodeBinder' threw an exception.
Posting this one for the search engines. If you ever receive the exception "The type initializer for 'Microsoft.TeamFoundation.Build.Server.BuildInformationNodeBinder' threw an exception.", more than likely, your drive space is at 0 on your TFS application tier box.
I encountered this at a client recently. The root cause was that IIS logs had filled up the OS drive (C:\). I switched IIS logging to the applications drive (D:\) which cleaned up the OS drive and resolved the issue.
Detailed message:
TF53010: The following error has occurred in a Team Foundation component or extension:
Date (UTC): 6/7/2011 4:18:53 PM
Machine: TFSATBOX
Application Domain: /LM/W3SVC/8080/ROOT/tfs-1-129519118182628600
Assembly: Microsoft.TeamFoundation.Framework.Server, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Service Host: 7ecfbd77-b386-4d75-b038-b05474782696 (DefaultCollection)
Process Details:
Process Name: w3wp
Process Id: 3676
Thread Id: 5752
Ac…
I encountered this at a client recently. The root cause was that IIS logs had filled up the OS drive (C:\). I switched IIS logging to the applications drive (D:\) which cleaned up the OS drive and resolved the issue.
Detailed message:
TF53010: The following error has occurred in a Team Foundation component or extension:
Date (UTC): 6/7/2011 4:18:53 PM
Machine: TFSATBOX
Application Domain: /LM/W3SVC/8080/ROOT/tfs-1-129519118182628600
Assembly: Microsoft.TeamFoundation.Framework.Server, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Service Host: 7ecfbd77-b386-4d75-b038-b05474782696 (DefaultCollection)
Process Details:
Process Name: w3wp
Process Id: 3676
Thread Id: 5752
Ac…
Comments