Effective Thoughts

(Cross-posted at http://www.coalmg.org/ ) Both Alexei and I enjoy working on the COALMG group. However, within the last few months, both of us took on new roles in our careers and struggle to find the time to line up speakers and keep things running smoothly. To that end, we would like to open up COALMG to new leadership. Alexei and I would still remain involved (as well as Brian Prince) from a "board"/guidance perspective but we want someone to really drive: schedule strong presenters, question the current setup, drive membership, sponsors, etc. We have a great following and there's tons of potential. COALMG is a fantastic opportunity for someone with energy, a passion for great software and a desire to get involved in the community. We look forward to hearing from you! If you're interested, shoot me an email at jeff dot hunsaker at gmail.

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: 367

If you're experiencing "Query execution failed for dataset 'ds[Whatever]'. ", more than likely, your warehouse processing is failing. Going into the Admin Console or invoking the web service directly , invoking the Start Rebuild action, I kept receiving a TF221122. Finally, when I added the account under "Account for accessing data sources" under the "Analysis Services" tab to the SQL Server Tfs_Warehouse database TFSEXECROLE role, processing began to succeed again. Whew.