Skip to main content

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

Account name: DOMAIN\SomeUser



Detailed Message: TF30065: An unhandled exception occurred.



Web Request Details

Url: http://tfs.internal.somedomain.com:8080/tfs/_tfs_resources/Build/v3.0/BuildService.asmx [method: POST]

User Agent: Team Foundation (devenv.exe, 10.0.40219.1)

Headers: Content-Length=406&Content-Type=application%2fsoap%2bxml%3b+charset%3dutf-8&Accept-Encoding=gzip&Accept-Language=en-US&Expect=100-continue&Host=tfs.internal.somedomain.com%3a8080&User-Agent=Team+Foundation+(devenv.exe%2c+10.0.40219.1)&X-TFS-Version=1.0.0.0&X-TFS-Session=7f33f7f4-765c-46fd-9f4a-bfd6dab598e7&TF-Instance=7f33f7f4-765c-46fd-9f4a-bfd6dab598e7&SOAPAction=http%3a%2f%2fschemas.microsoft.com%2fTeamFoundation%2f2005%2f06%2fBuild%2fBuildService%2f03%2fStopBuilds

Path: /tfs/_tfs_resources/Build/v3.0/BuildService.asmx

Local Request: False

Host Address: 10.10.10.10

User: DOMAIN\SomeUser [authentication type: NTLM]



Exception Message: The type initializer for 'Microsoft.TeamFoundation.Build.Server.BuildInformationNodeBinder' threw an exception. (type TypeInitializationException)



Exception Stack Trace: at Microsoft.TeamFoundation.Build.Server.BuildInformationNodeBinder.Bind()

at Microsoft.TeamFoundation.Framework.Server.ObjectBinder`1.TryMoveNext()

at Microsoft.TeamFoundation.Build.Server.TeamFoundationBuildService.UpdateBuildInformation(TeamFoundationRequestContext requestContext, IList`1 changes, IdentityDescriptor requestedFor)

at Microsoft.TeamFoundation.Build.Server.BuildController.StopBuilds(TeamFoundationRequestContext requestContext, IdentityDescriptor requestedFor, BuildServiceHost serviceHost, IList`1 builds, Boolean force)

at Microsoft.TeamFoundation.Build.Server.TeamFoundationBuildService.StopBuilds(TeamFoundationRequestContext requestContext, IList`1 uris)

at Microsoft.TeamFoundation.Build.Server.BuildWebService.StopBuilds(String[] uris)



Inner Exception Details:



Exception Message: There is not enough space on the disk.

(type IOException)



Exception Stack Trace: at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

at System.IO.FileStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count)

at System.IO.FileStream.FlushWrite(Boolean calledFromFinalizer)

at System.IO.FileStream.Dispose(Boolean disposing)

at System.IO.Stream.Close()

at System.IO.StreamWriter.Dispose(Boolean disposing)

at System.IO.TextWriter.Dispose()

at Microsoft.CSharp.CSharpCodeGenerator.FromSourceBatch(CompilerParameters options, String[] sources)

at Microsoft.CSharp.CSharpCodeGenerator.System.CodeDom.Compiler.ICodeCompiler.CompileAssemblyFromSourceBatch(CompilerParameters options, String[] sources)

at System.Xml.Serialization.Compiler.Compile(Assembly parent, String ns, XmlSerializerCompilerParameters xmlParameters, Evidence evidence)

at System.Xml.Serialization.TempAssembly.GenerateAssembly(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, Evidence evidence, XmlSerializerCompilerParameters parameters, Assembly assembly, Hashtable assemblies)

at System.Xml.Serialization.TempAssembly..ctor(XmlMapping[] xmlMappings, Type[] types, String defaultNamespace, String location, Evidence evidence)

at System.Xml.Serialization.XmlSerializer..ctor(Type type, String defaultNamespace)

at Microsoft.TeamFoundation.Build.Server.BuildSqlXmlColumnBinder`1..ctor(String columnName)

at Microsoft.TeamFoundation.Build.Server.BuildInformationNodeBinder..cctor()

Comments

Popular posts from this blog

Get Your Team Foundation Server Hate On!

[Google ranking skyrockets... ;-)] I'm a big fan of TFS/VSTS. However, there are a good pocket of folks who take issue with the way TFS handles or implements a certain feature. Well this is your chance to vent! I'm planning a presentation around the "Top 10 TFS/VSTS Hates and How to Alleviate Them"...or something along those lines. But I need your help. Post a comment below detailing your dislike. If it's legitimate, I'll highlight it in the presentation and [hopefully] provide an alternative, resolution, or work-around. Thanks in advance! Update 7/19/2008: Version Control and Microsoft

Rollback a Ooops in TFS with TFPT Rollback

Rhut roe, Raggie. You just checked in a merge operation affecting 100's of files in TFS against the wrong branch. Ooops. Well, you can simply roll it back, right? Select the folder in Source Control Explorer and...hey, where's the Rollback? Rollback isn't supported in TFS natively. However, it is supported within the Power Tools leveraging the command-line TFPT.exe utility. It's fairly straightforward to revert back to a previous version--with one caveot. First, download and install the Team Foundation Power Tools 2008 on your workstation. Before proceeding, let's create a workspace dedicated to the rollback. To "true up" the workspace, the rollback operation will peform a Get Latest for every file in your current workspace. This can consume hours (and many GB) with a broad workspace mapping. To work around this, I create a temporary workspace targeted at just the area of source I need to roll back. So let's drill down on our scenario... I'm worki

Installing the .Net Framework 3.0 SP1 on Windows 2003 Server

I'm building an [automated] build server requiring the .Net 2.0 and 3.0 runtime. Unfortunately, at my client, they leverage a proxy server. The standard .Net 3.0 SP1 framework redist is really just a bootstrapper. Logged in as a local admin on the box, I didn't have the opportunity to authenticate the installation EXE with my domain credentials. So, the install kept timing out. Finally, I found this helpful post from Aaron Ruckman on how to download the very elusive, full framework package. It's here , BTW (x86). I finally get the full installation EXE downloaded to a fileshare, re-run the install and wham--" XPSEPSC: XPS must be installed..." Excuse you? This isn't an XPS ...it's a VM. I found a few MSDN posts here and here outlining the problem. I'm still not clear on what XPSEPSC does (Google yielded little) but you can download it here (x86) . After installing XPSEPSC, the framework installed without issue. Update : Somewhat related, there i