Jiange Sun's WebLog

You may encounter TF53010 if your TFS 2008 is running on Windows 2008

2008-10-29T20:52:00Z

Issue:

=====

Your TFS 2008 is running on Windows 2008 and you noticed this error from w3wp.exe in EventLog:

TF53010: The following error has occurred in a Team Foundation component or extension:

Date (UTC): 10/28/2008 12:19:30 AM

Machine: %MachineName%

Application Domain: /LM/W3SVC/99096959/ROOT/Services-1-128487152825933232

Assembly: Microsoft.TeamFoundation.Common, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727

Process Details:

Process Name: w3wp

Process Id: 3528

Thread Id: 2896

Account name: %AccountName%

Exception: COMException

Message: Retrieving the COM class factory for component with CLSID {080D0D78-F421-11D0-A36E-00C04FB950DC} failed due to the following error: 800703fa.

Stack Trace:

at System.DirectoryServices.ActiveDirectory.DirectoryEntryManager..ctor(DirectoryContext context)

at System.DirectoryServices.ActiveDirectory.DomainController.FindOneInternal(DirectoryContext context, String domainName, String siteName, LocatorOptions flag)

at System.DirectoryServices.ActiveDirectory.DomainController.FindOneWithCredentialValidation(DirectoryContext context, String siteName, LocatorOptions flag)

at System.DirectoryServices.ActiveDirectory.DomainController.FindOne(DirectoryContext context, LocatorOptions flag)

at Microsoft.TeamFoundation.Server.DomainProperties..ctor(String domain)

at Microsoft.TeamFoundation.Server.DomainProperties.GetDomainProperties(String domain)

at Microsoft.TeamFoundation.Server.ADAccessor.ExtractIdentity(Boolean includeMembers, IdentitySeen identitySeen, ProcessIdentity processIdentity)

at Microsoft.TeamFoundation.Server.ADAccessor.ExtractIdentity(Boolean includeMembers)

at Microsoft.TeamFoundation.Server.IdentityStoreAccessor.ReadIdentityFromSource(String sid, Boolean includeMembers)

at Microsoft.TeamFoundation.Server.GroupSecurityService.ReadIdentityFromSource(SearchFactor factor, String factorValue)

Root Cause:

==========

This is due to a design change in Windows 2008. This wasn’t an issue in Win2k3, because the OS would let us hold onto HKCU after the user logged out.

Resolution:

=========

Set “Load User Profile” to True for the IIS Application Pool “Microsoft Team Foundation Server Application Pool” .

TFS SDK will cause InvalidProgramException while running as 64 bit

2008-03-28T17:18:00Z

Issue:

=====

You create a C# project that uses TFS SDK. But it crashes when you try to run it on a X64 bit OS machine:

Unhandled Exception: System.InvalidProgramException: Common Language Runtime detected an invalid program.

at Microsoft.TeamFoundation.Client.TeamFoundationServerFactory.GetServer(String name)

at TFSTestProject.Program.Main(String[] args)

This is the code that causes crash:

TeamFoundationServer tfs = TeamFoundationServerFactory.GetServer("http://<server>:<port>",);

Root Cause:

==========

The TFS OM is not going to work correctly in a native 64-bit mode. For C# project, it’s default platform target is “Any CPU” (aka, X64 on a 64-bits OS).

Resolution:

=========

Go to Project Property of your C# project, click on Build tab, set “Platform Target” to x86, rebuilt. Now the program will run as a 32 bit executable and TFS OM work fine.

A potential issue when running TFC 2005 and 2008 SxS

2008-03-19T20:26:00Z

If you have both TFC 2005 and 2008 installed on a Vista box, you may run into this issue with TFC 2008:

---------------------------

Microsoft Visual Studio

---------------------------

Method 'get_CanEnableIme' on type 'Microsoft.VisualStudio.TeamFoundation.WorkItemTracking.QueryEditor' from assembly 'Microsoft.VisualStudio.TeamFoundation.WorkItemTracking, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' is overriding a method that is not visible from that assembly.

---------------------------

You will also notice:

1. TFC 2005 works fine.

2. TFC 2008 still have the same issue after uninstalling TFC 2005.

3. Installing hotfix from http://support.microsoft.com/kb/946075 doesn't help.

This is a known issue in .net setup. Installing Vista Sp1 should fix the issue. For some users, rebooting/re-installing VS also resolved the problem.