we too are getting a TFS related error that's spamming the event log. however our wording seems to be a bit different. following this thread's suggest fix we find that we do not even have a Microsoft Team Foundation 2005 folder in the Programs Folder to apply the here listed fix. so if anyone has any other suggestions please post so here.
TF53010: An unexpected condition has occurred in a Team Foundation component. The information contained here should be made available to your site administrative staff.
Technical Information (for the administrative staff):
Date (UTC): 9/19/2006 9:16:34 PM
Machine: server
Application Domain: /LM/W3SVC/3/Root/Warehouse-1-128031741891289479
Assembly: Microsoft.TeamFoundation.Warehouse, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
Process Name: w3wp
Process Id: 4012
Thread Id: 2432
Account name: domain\vstfs
Detailed Message: Failed to load adapter Microsoft.TeamFoundation.WorkItemTracking.Adapter.Adapter. Exception Info: \n System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.TeamFoundation.WorkItemTracking.Server.DataAccessLayer, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.TeamFoundation.WorkItemTracking.Server.DataAccessLayer, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
at Microsoft.TeamFoundation.WorkItemTracking.Adapter.Adapter.Initialize(IDataStore ds)
at Microsoft.TeamFoundation.Warehouse.AdapterWrapper..ctor(Type type, AdapterScheduler scheduler, String connectionString, String accessAccount, String dataReaderAccount, String analysisDbServer, String analysisDbName)
at Microsoft.TeamFoundation.Warehouse.AdapterScheduler.Initialize()
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. |