We asked some of our consultants to answer the following: What are the most commonly asked questions you’ve had by customers this year, and how did you answer it?

Here’s what they had to say: 

How should I upgrade to TFS 2010?

 

Although “it depends” is not the answer anyone wants, it truly does depend on numerous factors including your infrastructure, resources, past TFS performance, “future-proofing” your environment, and what 2010 features you want to utilize.

 

In my experience, the ideal way to upgrade is to always migrate to new hardware.  Migrating to new hardware allows for:

 

·         Your existing infrastructure to stay in place, allowing it to be easily reverted to in the case of a failed upgrade.

·         Easy upgrades to the latest operating systems (including full 64 bit support) and related applications (SharePoint, SSRS).

·         Upgrading your hardware, environment, and infrastructure architecture to boost performance.

·         Easy testing of the upgrade process without interfering with the existing infrastructure.

 

Not everyone has the luxury of migrating to new hardware or updating to the latest and greatest. New hardware or not, there are still some common mistakes to watch out for:

 

·         Ensure you have enough free disk space available for the upgrade process to complete.  You generally need free space one and a half times the size of your databases to complete the upgrade to account for temporary growth in the transaction logs.  So if your TFS databases are 40GB, ensure you have at least 60GB of disk space free (please see the installation guide for exact details on disk space requirements).

o    Plan for increased disk growth if you will be taking advantage of the new testing features including video recordings and detailed logging information.

o    Do not upgrade without a solid strategy for backups and disaster recovery. This is critical should you need to revert, as it will allow you to continue working without impacting your TFS user base.

o    Install any necessary client patches and if possible have users test connectivity on a test instance before the production upgrade to prevent unnecessary user and client connectivity issues post production.

 

There is no right answer on how a TFS 2010 upgrade should be accomplished. Each environment is unique in both needs and desires. By keeping yourself updated with latest documentation, taking your time to plan and test the process, and seeking outside help when you are unsure, you will be well on your way to a successful TFS 2010 upgrade.

 

 

  - Shad Timm

]]> http://blog.nwcadence.com/2011/11/what-are-the-most-commonly-asked-questions-youve-had-by-customers-this-year-and-how-did-you-answer-it/feed/ 0 http://blog.nwcadence.com/2011/10/adding-two-new-useful-ssrs-data-sources/ http://blog.nwcadence.com/2011/10/adding-two-new-useful-ssrs-data-sources/#comments Fri, 28 Oct 2011 22:29:11 +0000 JamesTupper http://blog.nwcadence.com/2011/10/adding-two-new-useful-ssrs-data-sources/ Continue reading →]]>  Adding Two New, Useful SSRS Data Sources- By James Tupper

Introduction

Watching the performance of your TFS 2010 server is important. And having reports that show historical trending is very useful. Luckily, Grant Holliday, Microsoft Program Manager for Visual Studio Team Foundation Server, has two blog posts featuring some excellent report packs. Both sets of reports can be used against TFS 2010 (although one set requires some extensive modifications).

You can view the blog posts here:

• TFS Performance Report Pack
• TFS Administration Report Pack

The Performance Report Pack provides a lot of great information about the state of the TFS 2010 Farm, including historical trend data for both version control and work item operations. It is great for discovering, if you are experiencing intermittent performance problems. Originally, it was written for TFS 2008, but it can be upgraded to TFS 2010.

The TFS Administration Report Pack is a set of three reports that show data about the TFS Analysis Services cube and data warehouse.

The main issue with both of these report packs is that the instructions for creating the data sources for TFS 2010 are not included, or better said, the instructions are easy to figure out, but not specific enough to be completed trivially and with ease.

The following steps make creating the required SSRS data sources trivial.

Steps for Adding Data Sources

The report data source is needed by most of the RDLs that are provided with the report packs on Grant Holliday’s blog, and it is tied to the Tfs_Warehouse database. While the configuration data source is not used by all of the reports, it is still needed and is tied to the Tfs_Configuration database.

To add the data sources, you will want to go to your report server website with the following URL structure:

• http://<servername>/Reports

Personally, I opened an RDP session with my server and used http://localhost/Reports to access the SSRS website. From here you should see the SSRS Home page.

At the top of the page there is a ribbon of buttons with “New Data Source” being the second option. Click this button to start adding a new Data Source.

Figure 1: New Data Source button

We want to configure each data source with specific names to be sure that the reports in these packs will be able to connect to them without an issue. For the Tfs_Warehouse data source we want to fill out the new Data Source Form with the following information:

Figure 2: Report Data Source Settings :

• Name : Tfs2010ReportDS
• Connection String : Data Source = <TFSServer>;Initial Catalog=Tfs_Warehouse
• Credentials stored securely in report server checked
  • User Name : This should be whatever you use for your TFS reporting services (i.e. TFSReport)
  • Use as Windows credentials when connecting to the data source

Click okay, and the first data source will be created. To create the data source that is tied to the Tfs_Configuration database, click the “New Data Source” again, as done previously, and use the following configuration:

Figure 3: Configuration Data Source Settings

• Name : Tfs2010ConfigurationDS
• Connection string : Data Source=<TFSServer>;Initial Catalog=Tfs_Configuration
• Credentials stored securely in report server checked
  • User Name : This should be whatever you use for your TFS reporting services (i.e. TFSReport)
  • Use as Windows credentials when connecting to the data source

In these two screen shots I used the Administrator account for the data sources, but I want to make it clear that the account used for the TFS reporting services is the account that should be used for these data sources.

Once all is said and done, your SSRS Home page should have the two new data source listed with a “!New” tag sitting next to them.

Figure 4 : SSRS Home Page after the two data sources have been added

Conclusion

With these data sources added to the SSRS web site, getting the reports in the TFS Performance Report Pack and the TFS Administration Report Pack to work is just a matter of uploading them. Having these reports can add a great deal of value to your Kanban or Scrum process, and being able to quickly and quite easily set them up is a huge bonus.

-James Tupper

Applying TFS 2010 SP1 may, in rare instances, cause an error which prevents the data warehouse (and, by extension, the analysis cube) from updating work item information beyond the date and time at which the SP1 was installed.  This means all work item reports will freeze at the date in which TFS 2010 SP1 was applied.  In addition, the Work Item Tracking Warehouse Sync job will hang and never complete.

Symptoms

After a TFS 2010 SP1 install, work items are no longer processed in the data warehouse, however all of the other elements (such as version control, test cases, etc) are processed. In addition, the Work Item Tracking Warehouse Sync job hangs and never finishes. If you view the data warehouse or the analysis cube, you will find no new data has been recorded since the install of TFS 2010 SP1.

In addition, you will receive an error in the event log similar to this: TF221122: An error occurred running job Work Item Tracking Warehouse Sync for team project collection or Team Foundation server DefaultCollection

Bottom Line Up Front

There was an error in TFS 2010 SP1 that set a watermark improperly. Watermarks are used to mark how many work items have been processed into the warehouse, and where to start for the next iteration. Verifying the problem requires running a SQL query against the transactional database. Fixing the problem (also described at the bottom of the post) required executing an update directly against the SQL transactional database.

WARNING: No direct changes to the database are supported by Microsoft. In order to be supported, you should contact Microsoft PSS, and explain the problem, point them to this blog post, let them do their due diligence first, and have THEM recommend running the script!! I am hesitant to even list the fix, and you run it at your OWN RISK!

Table of Contents

Because this is a relatively large post, I want to provide a quick table of contents to the remainder of the post to help clarify the structure.

• Troubleshooting Steps
  • Show that problem occurs on any work item changed AFTER SP1 was installed
  • Highlight two warnings that occurred during SP1 install (Ended up not being related to problem.)
  • Common, but strange warning in the Event Logs (Ended up not being related to problem.)
  • Event Logs show both Errors and Warnings that are directly related to problem
  • Similar Error found on Bing shows corrupted work item from upgrade caused problems.
  • Other errors caused by permissions or unsolved bugs in TFS, but doesn’t apply since these block ALL processing, not just work items
  • Rebooting doesn’t help.
  • Rebuilding the data warehouse / OLAP cube doesn’t help (and it gets stuck in the exact same place each time)
• Problem Verification
  • SQL Script that identifies that there IS a problem
• Problem Solution (WARNING: Contact MS PSS before running, since it requires making direct changes against the TFS database!)
  • SQL Script that identifies that resolves the problem

Troubleshooting Steps

The troubleshooting steps are included to walk through much of the thought process I ran through to identify the problem, and to help folks who may be running into a SIMILAR problem, but one that is not exactly the same. Feel free to go to the bottom of the post for the verification and fix steps.

First, prove that this problem occurred immediately upon install of SP1.

Here’s the strange thing: I can process all data, including all changes to the Work Item store, up until the time that SP1 was installed. So, I can only get data until that point. This shows two columns. First is the number of work items, which becomes frozen as of Sept 22 (the date of the SP1 install), however, you can see that the DATE dimension in the cube goes beyond that. That’s because everything ELSE is processing, just not the work items. Second column shows the work item revision count and it stops as of Sept 22 (the date of the SP1 install).

Second, I examined the logs for the TFS 2010 SP1 install and CU1 install. Everything was clear with the exception of one [WARNING] in each of the installs:

Warning from SP1 install:

[Warning@04:15:02.495] [2011-09-23 02:06:36Z][Warning] Servicing step data still contains "$$" after token replacement. This likely means there are undefined tokens referenced in the step data: <ArrayOfServiceDefinition><ServiceDefinition serviceType="TestResultsServiceEx" displayName="Test Results Service Ex" identifier="7826fd15-ef51-42a4-83c5-f7c659d5a835" description="$$TEST_MANAGEMENT_TEST_RESULTS_SERVICE_DESCRIPTION$$" toolId="TestManagement" relativeToSetting="0" relativePath="/TestManagement/v1.0/TestResultsEx.asmx" /></ArrayOfServiceDefinition>  

[Info   @04:15:02.495] [2011-09-23 02:06:35Z] Servicing step Upgrade Version Control database passed. (ServicingOperation: Tfs2010SP1KB2580221Install; Step group: Tfs2010SP1VersionControlInstall)
[Info   @04:15:02.495] [2011-09-23 02:06:36Z] Executing servicing step Tfs2010SP1KB2527572Install SQL servicing step. (ServicingOperation: Tfs2010SP1KB2580221Install; Step group: Tfs2010SP1KB2527572Install)
[Info   @04:15:02.495] [2011-09-23 02:06:36Z][Informational] Step Performer: Framework
[Info   @04:15:02.495] [2011-09-23 02:06:36Z][Informational] Step Type:      ExecuteSql
[Info   @04:15:02.495] [2011-09-23 02:06:36Z][Informational] Step Data Text: <SqlStepData category="Framework" resource="KB2527572CollectionInstall.sql" />
[Info   @04:15:02.495] [2011-09-23 02:06:36Z][Informational] Step Data: DatabaseCategory => Framework
[Info   @04:15:02.495] [2011-09-23 02:06:36Z][Informational] Step Data: SqlResource => KB2527572CollectionInstall.sql
[Info   @04:15:02.495] [2011-09-23 02:06:36Z][Informational] Step Data: BatchTimeout => -1
[Info   @04:15:02.495] [2011-09-23 02:06:36Z][Informational] Step Data: Parameters =>
[Info   @04:15:02.495] [2011-09-23 02:06:36Z][Informational] Step Data: RequiresExclusiveDatabaseLock => False
[Info   @04:15:02.495] [2011-09-23 02:06:36Z][Informational] Executing KB2527572CollectionInstall.sql with zero sql parameters.
[Info   @04:15:02.495] [2011-09-23 02:06:36Z][Informational] Data source: vstssql
[Info   @04:15:02.495] [2011-09-23 02:06:36Z][Informational] Database name: Tfs_DefaultCollection
[Info   @04:15:02.495] [2011-09-23 02:06:36Z][Informational] SQL Info: Creating Procedure prc_Shelve
[Info   @04:15:02.495] [2011-09-23 02:06:36Z][Informational] SQL Info: Creating Procedure prc_CreateWorkspace
[Info   @04:15:02.495] [2011-09-23 02:06:36Z][Informational] SQL Info: Creating Procedure prc_PendAdd
[Info   @04:15:02.495] [2011-09-23 02:06:36Z][Informational] SQL Info: Warning! The maximum key length is 900 bytes. The index 'PK__#73EC3F1__00FD296475D4878D' has maximum length of 1040 bytes. For some combination of large values, the insert/update operation will fail.
Warning! The maximum key length is 900 bytes. The index 'PK__#77BCCFF__3ECB18DF79A51871' has maximum length of 1041 bytes. For some combination of large values, the insert/update operation will fail.
[Info   @04:15:02.495] [2011-09-23 02:06:36Z][Informational] SQL Info: Creating Procedure prc_iCheckLockStatus
[Info   @04:15:02.495] [2011-09-23 02:06:36Z] Servicing step Tfs2010SP1KB2527572Install SQL servicing step passed. (ServicingOperation: Tfs2010SP1KB2580221Install; Step group: Tfs2010SP1KB2527572Install)
[Warning@04:15:02.495] [2011-09-23 02:06:36Z][Warning] Servicing step data still contains "$$" after token replacement. This likely means there are undefined tokens referenced in the step data: <ArrayOfServiceDefinition><ServiceDefinition serviceType="TestResultsServiceEx" displayName="Test Results Service Ex" identifier="7826fd15-ef51-42a4-83c5-f7c659d5a835" description="$$TEST_MANAGEMENT_TEST_RESULTS_SERVICE_DESCRIPTION$$" toolId="TestManagement" relativeToSetting="0" relativePath="/TestManagement/v1.0/TestResultsEx.asmx" /></ArrayOfServiceDefinition>
[Info   @04:15:02.495] [2011-09-23 02:06:36Z] Executing servicing step Add SP1 Test Management Location Data. (ServicingOperation: Tfs2010SP1KB2580221Install; Step group: Tfs2010SP1TeamTestInstall)
[Info   @04:15:02.495] [2011-09-23 02:06:36Z][Informational] Step Performer: Framework
[Info   @04:15:02.495] [2011-09-23 02:06:36Z][Informational] Step Type:      AddLocationData

Figure: Surrounding information in upgrade log (click View Source above)

Warning from the CU1 install (very similar to above):

[Warning@04:22:22.214] [2011-09-23 00:44:15Z][Warning] Servicing step data still contains "$$" after token replacement. This likely means there are undefined tokens referenced in the step data: <ArrayOfServiceDefinition><ServiceDefinition serviceType="TestResultsServiceEx" displayName="Test Results Service Ex" identifier="7826fd15-ef51-42a4-83c5-f7c659d5a835" description="$$TEST_MANAGEMENT_TEST_RESULTS_SERVICE_DESCRIPTION$$" toolId="TestManagement" relativeToSetting="0" relativePath="/TestManagement/v1.0/TestResultsEx.asmx" /></ArrayOfServiceDefinition>

[Info   @04:22:22.214] [2011-09-23 00:44:14Z] Executing servicing step Patch Collection with PS Sync. (ServicingOperation: Tfs2010SP1Install; Step group: Tfs2010SP1ProjectServerInstall)
[Info   @04:22:22.214] [2011-09-23 00:44:14Z][Informational] Step Performer: Framework
[Info   @04:22:22.214] [2011-09-23 00:44:14Z][Informational] Step Type:      ExecuteSql
[Info   @04:22:22.214] [2011-09-23 00:44:14Z][Informational] Step Data Text: <SqlStepData category="Framework" resource="Tfs2010SP1ProjectServerCollectionInstall.sql" requiresExclusiveDatabaseLock="false" />
[Info   @04:22:22.214] [2011-09-23 00:44:14Z][Informational] Step Data: DatabaseCategory => Framework
[Info   @04:22:22.214] [2011-09-23 00:44:14Z][Informational] Step Data: SqlResource => Tfs2010SP1ProjectServerCollectionInstall.sql
[Info   @04:22:22.214] [2011-09-23 00:44:14Z][Informational] Step Data: BatchTimeout => -1
[Info   @04:22:22.214] [2011-09-23 00:44:14Z][Informational] Step Data: Parameters =>
[Info   @04:22:22.214] [2011-09-23 00:44:14Z][Informational] Step Data: RequiresExclusiveDatabaseLock => False
[Info   @04:22:22.214] [2011-09-23 00:44:14Z][Informational] Executing Tfs2010SP1ProjectServerCollectionInstall.sql with zero sql parameters.
[Info   @04:22:22.214] [2011-09-23 00:44:14Z][Informational] Data source: vstssql
[Info   @04:22:22.214] [2011-09-23 00:44:14Z][Informational] Database name: Tfs_DefaultCollection
[Info   @04:22:22.214] [2011-09-23 00:44:14Z][Informational] SQL Info: Creating Procedure prc_sync_getmapping
[Info   @04:22:22.214] [2011-09-23 00:44:14Z][Informational] SQL Info: Creating Procedure prc_sync_getmappingchanged
[Info   @04:22:22.214] [2011-09-23 00:44:14Z][Informational] SQL Info: Creating Procedure prc_sync_getproperties
[Info   @04:22:22.214] [2011-09-23 00:44:14Z][Informational] SQL Info: Creating Procedure prc_sync_getproperty
[Info   @04:22:22.214] [2011-09-23 00:44:15Z][Informational] SQL Info: Creating Procedure prc_sync_savemapping
[Info   @04:22:22.214] [2011-09-23 00:44:15Z][Informational] SQL Info: Creating Procedure prc_sync_saveproperty
[Info   @04:22:22.214] [2011-09-23 00:44:15Z] Servicing step Patch Collection with PS Sync passed. (ServicingOperation: Tfs2010SP1Install; Step group: Tfs2010SP1ProjectServerInstall)
[Warning@04:22:22.214] [2011-09-23 00:44:15Z][Warning] Servicing step data still contains "$$" after token replacement. This likely means there are undefined tokens referenced in the step data: <ArrayOfServiceDefinition><ServiceDefinition serviceType="TestResultsServiceEx" displayName="Test Results Service Ex" identifier="7826fd15-ef51-42a4-83c5-f7c659d5a835" description="$$TEST_MANAGEMENT_TEST_RESULTS_SERVICE_DESCRIPTION$$" toolId="TestManagement" relativeToSetting="0" relativePath="/TestManagement/v1.0/TestResultsEx.asmx" /></ArrayOfServiceDefinition>
[Info   @04:22:22.214] [2011-09-23 00:44:15Z] Executing servicing step Add SP1 Test Management Location Data. (ServicingOperation: Tfs2010SP1Install; Step group: Tfs2010SP1TeamTestInstall)
[Info   @04:22:22.214] [2011-09-23 00:44:15Z][Informational] Step Performer: Framework

Figure: Surrounding information in upgrade log (click View Source above)

Third, here are some of the Application Event Log entries that may indicate an SP1 install failure. (Ended up NOT to be the case.)

The first is a common error each time TfsAgent throws information, warning, or error messages. You can ignore most of the content of this error log, since it happened when I’d stopped the services anyway. The only critical thing is the highlighted part. This leads me to believe there is something wrong with the SP1 install. (Google / Bing have not been helpful in this scenario, even though there were plenty of hits.)

The description for Event ID 3300 from source TFS Services cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

Log Name:      Application
Source:        TFS Services
Date:          10/8/2011 8:59:42 PM
Event ID:      3300
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      VSTS01.myCo.com
Description:
The description for Event ID 3300 from source TFS Services cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

TF53010: The following error has occurred in a Team Foundation component or extension:
Date (UTC): 10/9/2011 3:59:42 AM
Machine: VSTS01
Application Domain: TfsJobAgent.exe
Assembly: Microsoft.TeamFoundation.Framework.Server, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Service Host:
Process Details:
  Process Name: TFSJobAgent
  Process Id: 7012
  Thread Id: 1208
  Account name: MyCo\TfsService

Detailed Message: TF221107: Reporting for Team Foundation Server cannot execute job Work Item Tracking Warehouse Sync for team project collection DefaultCollection because the warehouse is offline. Use the Team Foundation Administration Console to start reporting.

the message resource is present but the message is not found in the string/message table

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="TFS Services" />
    <EventID Qualifiers="0">3300</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-10-09T03:59:42.000000000Z" />
    <EventRecordID>399224</EventRecordID>
    <Channel>Application</Channel>
    <Computer>VSTS01.myCo.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>TF53010: The following error has occurred in a Team Foundation component or extension:
Date (UTC): 10/9/2011 3:59:42 AM
Machine: VSTS01
Application Domain: TfsJobAgent.exe
Assembly: Microsoft.TeamFoundation.Framework.Server, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Service Host:
Process Details:
  Process Name: TFSJobAgent
  Process Id: 7012
  Thread Id: 1208
  Account name: MyCo\TfsService

Detailed Message: TF221107: Reporting for Team Foundation Server cannot execute job Work Item Tracking Warehouse Sync for team project collection DefaultCollection because the warehouse is offline. Use the Team Foundation Administration Console to start reporting.</Data>
  </EventData>
  </Event>

Figure: Full Text of Warning (click View Source above)

Fourth, an Error received when the Work Item Tracking Warehouse Sync runs. This one matters, since it’s the one that represents the failure. And when it fails, it will NOT stop the TFS Job from running, it will simply hang the job forever. Interesting thing, though, since the warehouse IS updated to the day that the SP1 was installed, so the cube can get the data up to that point. Notice that the highlighted areas show that it is a SQL Transport level problem. (Quick reminder to everyone that ALL the other Warehouse jobs process successfully, as do the Cube jobs.) It appears as though a network name is no longer available. (Again, recall that the Work Item job can process up to the date that the TFS 2010 SP1 was installed, so it’s not failing immediately, only after processing all the work item events up to that point – we’ve repeatedly rebuilt the warehouse and cube from scratch, and each time it can process up to the date of the SP1 install.)

Detailed Message: TF221122: An error occurred running job Work Item Tracking Warehouse Sync for team project collection or Team Foundation server DefaultCollection.
Exception Message: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (type SqlCannotOpenDatabaseException)

Log Name:      Application
Source:        TFS Services
Date:          10/8/2011 8:27:21 PM
Event ID:      3305
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      VSTS01.myCo.com
Description:
The description for Event ID 3305 from source TFS Services cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

TF53010: The following error has occurred in a Team Foundation component or extension:
Date (UTC): 10/9/2011 3:27:21 AM
Machine: VSTS01
Application Domain: TfsJobAgent.exe
Assembly: Microsoft.TeamFoundation.Framework.Server, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Service Host:
Process Details:
  Process Name: TFSJobAgent
  Process Id: 1696
  Thread Id: 1908
  Account name: MyCo\TfsService

Detailed Message: TF221122: An error occurred running job Work Item Tracking Warehouse Sync for team project collection or Team Foundation server DefaultCollection.
Exception Message: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (type SqlCannotOpenDatabaseException)

Exception Stack Trace:    at Microsoft.TeamFoundation.WorkItemTracking.Server.SqlAccess.TranslateException(SqlException sqlException)
   at Microsoft.TeamFoundation.Framework.Server.TeamFoundationSqlResourceComponent.MapException(SqlException ex, QueryExecutionState queryState)
   at Microsoft.TeamFoundation.Framework.Server.TeamFoundationSqlResourceComponent.HandleException(SqlException ex)
   at Microsoft.TeamFoundation.Framework.Server.TeamFoundationSqlResourceComponent.Execute(ExecuteType executeType, CommandBehavior behavior)
   at Microsoft.TeamFoundation.WorkItemTracking.Server.SqlAccess.ExecuteBatchPayloadImpl(String sqlBatch, List`1 parameterList, Boolean& errorOnBulkUpdate)
   at Microsoft.TeamFoundation.WorkItemTracking.Server.SqlBatchBuilder.ExecuteBatchQuery(IRequestContext context, String sqlBatch, List`1 parameterList)
   at Microsoft.TeamFoundation.WorkItemTracking.Server.SqlBatchBuilder.ExecuteBatchInternal(IRequestContext context)
   at Microsoft.TeamFoundation.WorkItemTracking.Server.DataAccessLayerImpl.GetWarehouseData(String logicalTrackingId, Int32 batchSize, String fieldLogicalTrackingId, String dimensionFieldQueryList, String measureFieldQueryList, Nullable`1 fieldId, Payload warehousePayload)
   at Microsoft.TeamFoundation.WorkItemTracking.Adapter.WorkItemTrackingWarehouseAdapter.TryGetNextWorkItemRevisionsBatch(String workItemRevisionWatermark, String workItemFieldWatermark, Int32 workItemRevisionBatchSize, String dimensionFieldQueryList, String measureFieldQueryList, Nullable`1 fieldId, Payload& workItemRevisionBatch)
   at Microsoft.TeamFoundation.WorkItemTracking.Adapter.WorkItemTrackingWarehouseAdapter.GetWorkItemRevisionBatchAndPopulate(String workItemRevisionWatermark, String workItemFieldWatermark, Int32 workItemRevisionBatchSize, WarehouseMetadata allTpcWarehouseMetadata, String& dimensionFieldQueryList, String& measureFieldQueryList, String& maxRevisionWatermark)
   at Microsoft.TeamFoundation.WorkItemTracking.Adapter.WorkItemTrackingWarehouseAdapter.SynchronizeNewWorkItems(WarehouseMetadata allTpcWarehouseMetadata)
   at Microsoft.TeamFoundation.WorkItemTracking.Adapter.WorkItemTrackingWarehouseAdapter.MakeDataChanges()
   at Microsoft.TeamFoundation.Warehouse.WarehouseSyncJobExtension`1.MakeDataChanges(TeamFoundationRequestContext requestContext, TeamFoundationJobDefinition jobDefinition, String& resultMessage)
   at Microsoft.TeamFoundation.Warehouse.WarehouseSyncJobExtension`1.RunInternal(TeamFoundationRequestContext requestContext, TeamFoundationJobDefinition jobDefinition, DateTime queueTime, String& resultMessage)
   at Microsoft.TeamFoundation.Warehouse.WarehouseJobExtension.Run(TeamFoundationRequestContext requestContext, TeamFoundationJobDefinition jobDefinition, DateTime queueTime, String& resultMessage)

Inner Exception Details:

Exception Message: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (type SqlException)
SQL Exception Class: 20
SQL Exception Number: 64
SQL Exception Procedure:
SQL Exception Line Number: 0
SQL Exception Server: vstssql
SQL Exception State: 0
SQL Error(s):

Exception Data Dictionary:
HelpLink.ProdName = Microsoft SQL Server
HelpLink.EvtSrc = MSSQLServer
HelpLink.EvtID = 64
HelpLink.BaseHelpUrl = http://go.microsoft.com/fwlink
HelpLink.LinkId = 20476

Exception Stack Trace:    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()
   at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
   at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParserStateObject.ReadNetworkPacket()
   at System.Data.SqlClient.TdsParserStateObject.ReadByte()
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
   at Microsoft.TeamFoundation.Framework.Server.TeamFoundationSqlResourceComponent.Execute(ExecuteType executeType, CommandBehavior behavior)

the message resource is present but the message is not found in the string/message table

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="TFS Services" />
    <EventID Qualifiers="0">3305</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-10-09T03:27:21.000000000Z" />
    <EventRecordID>399205</EventRecordID>
    <Channel>Application</Channel>
    <Computer>VSTS01.myCo.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>TF53010: The following error has occurred in a Team Foundation component or extension:
Date (UTC): 10/9/2011 3:27:21 AM
Machine: VSTS01
Application Domain: TfsJobAgent.exe
Assembly: Microsoft.TeamFoundation.Framework.Server, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Service Host:
Process Details:
  Process Name: TFSJobAgent
  Process Id: 1696
  Thread Id: 1908
  Account name: MyCo\TfsService

Detailed Message: TF221122: An error occurred running job Work Item Tracking Warehouse Sync for team project collection or Team Foundation server DefaultCollection.
Exception Message: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (type SqlCannotOpenDatabaseException)

Exception Stack Trace:    at Microsoft.TeamFoundation.WorkItemTracking.Server.SqlAccess.TranslateException(SqlException sqlException)
   at Microsoft.TeamFoundation.Framework.Server.TeamFoundationSqlResourceComponent.MapException(SqlException ex, QueryExecutionState queryState)
   at Microsoft.TeamFoundation.Framework.Server.TeamFoundationSqlResourceComponent.HandleException(SqlException ex)
   at Microsoft.TeamFoundation.Framework.Server.TeamFoundationSqlResourceComponent.Execute(ExecuteType executeType, CommandBehavior behavior)
   at Microsoft.TeamFoundation.WorkItemTracking.Server.SqlAccess.ExecuteBatchPayloadImpl(String sqlBatch, List`1 parameterList, Boolean&amp; errorOnBulkUpdate)
   at Microsoft.TeamFoundation.WorkItemTracking.Server.SqlBatchBuilder.ExecuteBatchQuery(IRequestContext context, String sqlBatch, List`1 parameterList)
   at Microsoft.TeamFoundation.WorkItemTracking.Server.SqlBatchBuilder.ExecuteBatchInternal(IRequestContext context)
   at Microsoft.TeamFoundation.WorkItemTracking.Server.DataAccessLayerImpl.GetWarehouseData(String logicalTrackingId, Int32 batchSize, String fieldLogicalTrackingId, String dimensionFieldQueryList, String measureFieldQueryList, Nullable`1 fieldId, Payload warehousePayload)
   at Microsoft.TeamFoundation.WorkItemTracking.Adapter.WorkItemTrackingWarehouseAdapter.TryGetNextWorkItemRevisionsBatch(String workItemRevisionWatermark, String workItemFieldWatermark, Int32 workItemRevisionBatchSize, String dimensionFieldQueryList, String measureFieldQueryList, Nullable`1 fieldId, Payload&amp; workItemRevisionBatch)
   at Microsoft.TeamFoundation.WorkItemTracking.Adapter.WorkItemTrackingWarehouseAdapter.GetWorkItemRevisionBatchAndPopulate(String workItemRevisionWatermark, String workItemFieldWatermark, Int32 workItemRevisionBatchSize, WarehouseMetadata allTpcWarehouseMetadata, String&amp; dimensionFieldQueryList, String&amp; measureFieldQueryList, String&amp; maxRevisionWatermark)
   at Microsoft.TeamFoundation.WorkItemTracking.Adapter.WorkItemTrackingWarehouseAdapter.SynchronizeNewWorkItems(WarehouseMetadata allTpcWarehouseMetadata)
   at Microsoft.TeamFoundation.WorkItemTracking.Adapter.WorkItemTrackingWarehouseAdapter.MakeDataChanges()
   at Microsoft.TeamFoundation.Warehouse.WarehouseSyncJobExtension`1.MakeDataChanges(TeamFoundationRequestContext requestContext, TeamFoundationJobDefinition jobDefinition, String&amp; resultMessage)
   at Microsoft.TeamFoundation.Warehouse.WarehouseSyncJobExtension`1.RunInternal(TeamFoundationRequestContext requestContext, TeamFoundationJobDefinition jobDefinition, DateTime queueTime, String&amp; resultMessage)
   at Microsoft.TeamFoundation.Warehouse.WarehouseJobExtension.Run(TeamFoundationRequestContext requestContext, TeamFoundationJobDefinition jobDefinition, DateTime queueTime, String&amp; resultMessage)

Inner Exception Details:

Exception Message: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (type SqlException)
SQL Exception Class: 20
SQL Exception Number: 64
SQL Exception Procedure:
SQL Exception Line Number: 0
SQL Exception Server: vstssql
SQL Exception State: 0
SQL Error(s):

Exception Data Dictionary:
HelpLink.ProdName = Microsoft SQL Server
HelpLink.EvtSrc = MSSQLServer
HelpLink.EvtID = 64
HelpLink.BaseHelpUrl = http://go.microsoft.com/fwlink
HelpLink.LinkId = 20476

Exception Stack Trace:    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()
   at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
   at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParserStateObject.ReadNetworkPacket()
   at System.Data.SqlClient.TdsParserStateObject.ReadByte()
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
   at Microsoft.TeamFoundation.Framework.Server.TeamFoundationSqlResourceComponent.Execute(ExecuteType executeType, CommandBehavior behavior)

</Data>
  </EventData>
</Event>

Figure: Entire Error message pertaining directly to the problem (click View Source)

Next is a related WARNING in the Application Event Log. It occurs just prior to the ERROR noted above. Notice that it states that a severe error has occurred and the results should not be trusted. It also mentions that the action was cancelled by the user. No HUMAN cancelled it, however, the TFS Job agent may have cancelled it.

Detailed Message: A severe error occurred on the current command.  The results, if any, should be discarded.
Operation cancelled by user.
Exception Message: A severe error occurred on the current command.  The results, if any, should be discarded.
Operation cancelled by user. (type SqlExistingConnectionForciblyClosedException)

Log Name:      Application
Source:        TFS Services
Date:          10/8/2011 10:51:03 PM
Event ID:      3200
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      VSTS01.myCo.com
Description:
The description for Event ID 3200 from source TFS Services cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

TF53010: The following error has occurred in a Team Foundation component or extension:
Date (UTC): 10/9/2011 5:51:03 AM
Machine: VSTS01
Application Domain: TfsJobAgent.exe
Assembly: Microsoft.TeamFoundation.Framework.Server, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Service Host:
Process Details:
  Process Name: TFSJobAgent
  Process Id: 4740
  Thread Id: 2492
  Account name: MyCo\TfsService

Detailed Message: A severe error occurred on the current command.  The results, if any, should be discarded.
Operation cancelled by user.
Exception Message: A severe error occurred on the current command.  The results, if any, should be discarded.
Operation cancelled by user. (type SqlExistingConnectionForciblyClosedException)

Exception Stack Trace:    at Microsoft.TeamFoundation.WorkItemTracking.Server.SqlAccess.TranslateException(SqlException sqlException)
   at Microsoft.TeamFoundation.WorkItemTracking.Server.SqlAccess.ExecuteBatchPayloadImpl(String sqlBatch, List`1 parameterList, Boolean& errorOnBulkUpdate)
   at Microsoft.TeamFoundation.WorkItemTracking.Server.SqlBatchBuilder.ExecuteBatchQuery(IRequestContext context, String sqlBatch, List`1 parameterList)
   at Microsoft.TeamFoundation.WorkItemTracking.Server.SqlBatchBuilder.ExecuteBatchInternal(IRequestContext context)
   at Microsoft.TeamFoundation.WorkItemTracking.Server.DataAccessLayerImpl.GetWarehouseData(String logicalTrackingId, Int32 batchSize, String fieldLogicalTrackingId, String dimensionFieldQueryList, String measureFieldQueryList, Nullable`1 fieldId, Payload warehousePayload)
   at Microsoft.TeamFoundation.WorkItemTracking.Adapter.WorkItemTrackingWarehouseAdapter.TryGetNextWorkItemRevisionsBatch(String workItemRevisionWatermark, String workItemFieldWatermark, Int32 workItemRevisionBatchSize, String dimensionFieldQueryList, String measureFieldQueryList, Nullable`1 fieldId, Payload& workItemRevisionBatch)
   at Microsoft.TeamFoundation.WorkItemTracking.Adapter.WorkItemTrackingWarehouseAdapter.GetWorkItemRevisionBatchAndPopulate(String workItemRevisionWatermark, String workItemFieldWatermark, Int32 workItemRevisionBatchSize, WarehouseMetadata allTpcWarehouseMetadata, String& dimensionFieldQueryList, String& measureFieldQueryList, String& maxRevisionWatermark)
   at Microsoft.TeamFoundation.WorkItemTracking.Adapter.WorkItemTrackingWarehouseAdapter.SynchronizeNewWorkItems(WarehouseMetadata allTpcWarehouseMetadata)
   at Microsoft.TeamFoundation.WorkItemTracking.Adapter.WorkItemTrackingWarehouseAdapter.MakeDataChanges()
   at Microsoft.TeamFoundation.Warehouse.WarehouseSyncJobExtension`1.MakeDataChanges(TeamFoundationRequestContext requestContext, TeamFoundationJobDefinition jobDefinition, String& resultMessage)
   at Microsoft.TeamFoundation.Warehouse.WarehouseSyncJobExtension`1.RunInternal(TeamFoundationRequestContext requestContext, TeamFoundationJobDefinition jobDefinition, DateTime queueTime, String& resultMessage)
   at Microsoft.TeamFoundation.Warehouse.WarehouseJobExtension.Run(TeamFoundationRequestContext requestContext, TeamFoundationJobDefinition jobDefinition, DateTime queueTime, String& resultMessage)

Inner Exception Details:

Exception Message: A severe error occurred on the current command.  The results, if any, should be discarded.
Operation cancelled by user. (type SqlException)
SQL Exception Class: 11
SQL Exception Number: 0
SQL Exception Procedure:
SQL Exception Line Number: 0
SQL Exception Server: vstssql
SQL Exception State: 0
SQL Error(s):
SQL Error[1]: System.Data.SqlClient.SqlError: Operation cancelled by user.
    Class: 11
    Number: 0
    Server: vstssql
    Source: .Net SqlClient Data Provider
    State: 0
    Procedure:
    Line Number: 0

Exception Data Dictionary:
HelpLink.ProdName = Microsoft SQL Server
HelpLink.ProdVer = 10.00.5500
HelpLink.EvtSrc = MSSQLServer
HelpLink.EvtID = 0
HelpLink.BaseHelpUrl = http://go.microsoft.com/fwlink
HelpLink.LinkId = 20476

Exception Stack Trace:    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlDataReader.HasMoreRows()
   at System.Data.SqlClient.SqlDataReader.ReadInternal(Boolean setTimeout)
   at Microsoft.TeamFoundation.WorkItemTracking.Server.PayloadTable.Populate(SqlDataReader reader)
   at Microsoft.TeamFoundation.WorkItemTracking.Server.PayloadTableCollection.Populate(SqlDataReader reader)
   at Microsoft.TeamFoundation.WorkItemTracking.Server.SqlAccess.ExecuteBatchPayloadImpl(String sqlBatch, List`1 parameterList, Boolean& errorOnBulkUpdate)

the message resource is present but the message is not found in the string/message table

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="TFS Services" />
    <EventID Qualifiers="0">3200</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-10-09T05:51:03.000000000Z" />
    <EventRecordID>399296</EventRecordID>
    <Channel>Application</Channel>
    <Computer>VSTS01.myCo.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>TF53010: The following error has occurred in a Team Foundation component or extension:
Date (UTC): 10/9/2011 5:51:03 AM
Machine: VSTS01
Application Domain: TfsJobAgent.exe
Assembly: Microsoft.TeamFoundation.Framework.Server, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Service Host:
Process Details:
  Process Name: TFSJobAgent
  Process Id: 4740
  Thread Id: 2492
  Account name: MyCo\TfsService

Detailed Message: A severe error occurred on the current command.  The results, if any, should be discarded.
Operation cancelled by user.
Exception Message: A severe error occurred on the current command.  The results, if any, should be discarded.
Operation cancelled by user. (type SqlExistingConnectionForciblyClosedException)

Exception Stack Trace:    at Microsoft.TeamFoundation.WorkItemTracking.Server.SqlAccess.TranslateException(SqlException sqlException)
   at Microsoft.TeamFoundation.WorkItemTracking.Server.SqlAccess.ExecuteBatchPayloadImpl(String sqlBatch, List`1 parameterList, Boolean&amp; errorOnBulkUpdate)
   at Microsoft.TeamFoundation.WorkItemTracking.Server.SqlBatchBuilder.ExecuteBatchQuery(IRequestContext context, String sqlBatch, List`1 parameterList)
   at Microsoft.TeamFoundation.WorkItemTracking.Server.SqlBatchBuilder.ExecuteBatchInternal(IRequestContext context)
   at Microsoft.TeamFoundation.WorkItemTracking.Server.DataAccessLayerImpl.GetWarehouseData(String logicalTrackingId, Int32 batchSize, String fieldLogicalTrackingId, String dimensionFieldQueryList, String measureFieldQueryList, Nullable`1 fieldId, Payload warehousePayload)
   at Microsoft.TeamFoundation.WorkItemTracking.Adapter.WorkItemTrackingWarehouseAdapter.TryGetNextWorkItemRevisionsBatch(String workItemRevisionWatermark, String workItemFieldWatermark, Int32 workItemRevisionBatchSize, String dimensionFieldQueryList, String measureFieldQueryList, Nullable`1 fieldId, Payload&amp; workItemRevisionBatch)
   at Microsoft.TeamFoundation.WorkItemTracking.Adapter.WorkItemTrackingWarehouseAdapter.GetWorkItemRevisionBatchAndPopulate(String workItemRevisionWatermark, String workItemFieldWatermark, Int32 workItemRevisionBatchSize, WarehouseMetadata allTpcWarehouseMetadata, String&amp; dimensionFieldQueryList, String&amp; measureFieldQueryList, String&amp; maxRevisionWatermark)
   at Microsoft.TeamFoundation.WorkItemTracking.Adapter.WorkItemTrackingWarehouseAdapter.SynchronizeNewWorkItems(WarehouseMetadata allTpcWarehouseMetadata)
   at Microsoft.TeamFoundation.WorkItemTracking.Adapter.WorkItemTrackingWarehouseAdapter.MakeDataChanges()
   at Microsoft.TeamFoundation.Warehouse.WarehouseSyncJobExtension`1.MakeDataChanges(TeamFoundationRequestContext requestContext, TeamFoundationJobDefinition jobDefinition, String&amp; resultMessage)
   at Microsoft.TeamFoundation.Warehouse.WarehouseSyncJobExtension`1.RunInternal(TeamFoundationRequestContext requestContext, TeamFoundationJobDefinition jobDefinition, DateTime queueTime, String&amp; resultMessage)
   at Microsoft.TeamFoundation.Warehouse.WarehouseJobExtension.Run(TeamFoundationRequestContext requestContext, TeamFoundationJobDefinition jobDefinition, DateTime queueTime, String&amp; resultMessage)

Inner Exception Details:

Exception Message: A severe error occurred on the current command.  The results, if any, should be discarded.
Operation cancelled by user. (type SqlException)
SQL Exception Class: 11
SQL Exception Number: 0
SQL Exception Procedure:
SQL Exception Line Number: 0
SQL Exception Server: vstssql
SQL Exception State: 0
SQL Error(s):
SQL Error[1]: System.Data.SqlClient.SqlError: Operation cancelled by user.
    Class: 11
    Number: 0
    Server: vstssql
    Source: .Net SqlClient Data Provider
    State: 0
    Procedure:
    Line Number: 0

Exception Data Dictionary:
HelpLink.ProdName = Microsoft SQL Server
HelpLink.ProdVer = 10.00.5500
HelpLink.EvtSrc = MSSQLServer
HelpLink.EvtID = 0
HelpLink.BaseHelpUrl = http://go.microsoft.com/fwlink
HelpLink.LinkId = 20476

Exception Stack Trace:    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlDataReader.HasMoreRows()
   at System.Data.SqlClient.SqlDataReader.ReadInternal(Boolean setTimeout)
   at Microsoft.TeamFoundation.WorkItemTracking.Server.PayloadTable.Populate(SqlDataReader reader)
   at Microsoft.TeamFoundation.WorkItemTracking.Server.PayloadTableCollection.Populate(SqlDataReader reader)
   at Microsoft.TeamFoundation.WorkItemTracking.Server.SqlAccess.ExecuteBatchPayloadImpl(String sqlBatch, List`1 parameterList, Boolean&amp; errorOnBulkUpdate)

</Data>
  </EventData>
</Event>

Figure: Full Text of Warning (click View Source above)

Fifth, a Google / Bing search reveals only ONE exactly related hit for TF221122: “An error occurred running job Work Item Tracking Warehouse” “A severe error occurred on the current command”

http://www.go4answers.com/Example/tfs-2010-warehouse-update-severe-148743.aspx – Exactly the same problem, and points to a ROGUE work item that was corrupted during the upgrade from TFS 2008 to TFS 2010. We were good till the update to SP1, so maybe we got corrupted work items there…

Using the SQL at http://blog.mohammadjalloul.com/blogs/mo/archive/2011/08/29/how-to-detect-corrupted-tfs-work-items.aspx I searched for any corrupted work items. No luck. Query returned no corrupted work items.

So I queried for every work item that was changed on Sept 22 (the date of the last work item update to the warehouse) and I manually reviewed every one of the work items changed that day. I could not find any that had an error that would not permit me to resave them back to TFS, or any other indication anything was wrong.

At this point in the exploration, I did not believe that work item corruption was the problem, or at least the corruption was very hard to spot.

Sixth, Steven St Jean ran into a similar problem here: http://sstjean.blogspot.com/2010/07/tfs-2010-rtm-throws-tf221122-error-when.html

My situation is different since Analysis Services is already running under a domain account. I could change to NETWORK SERVICE to see if that would help, however, the problem is still different. He had an Analysis Services Network Service account that was failing REPEATABLY, and changing to a domain account worked. And in his case, the ENTIRE processing of the Warehouse was failing. For me, it’s ONLY the work items.

Seventh, reboot multiple times. Declared this weekend to be open maintenance, and rebooted multiple times after trying various things. No change to the behavior.

Eighth, delete and rebuild Tfs_Warehouse and Tfs_Analysis multiple times. In each case it will process the work items up to the date and time the SP1 was installed. (I can show that the last work item change prior to SP1 makes it into the warehouse/cube, but that the very next work item change, done after the SP1 was installed, does NOT make it into the warehouse/cube.)

Ninth, work directly with some of the people at Microsoft DevDiv who built the product. (Ah, the advantages of being an MVP.) This step led to the solution.

Problem Verification

Once we understood the problem more deeply, this script was run to prove that there was an issue between the two particular tables.  It verifies that there is an incorrect change order between the WorkItemsLatest and WorkItemsAre tables.  If this SQL query returns any rows, then you have the problem.  If not rows are returned, look elsewhere, because the fix script won’t help you.

SELECT COUNT(*)
FROM [dbo].[WorkItemsLatest] L
JOIN [dbo].[WorkItemsAre] A
ON L.[ID] = A.[ID]
AND L.[Rev] = A.[Rev]
WHERE L.[Changed Order] <> A.[Changed Order]

Problem Solution

Below is the SQL Script that solves the problem by setting the valies of the Changed Order columns in the WorkItemsLatest table to the values currently in the WorkItemsAre table.

WARNING: RUN THIS AT YOUR OWN RISK!  I HIGHLY recommend you contact Microsoft PSS, and work with them through this issue.  This SQL script is provided “for entertainment purposes only”…

SET WL.[Changed Order] = WA.[Changed Order]
FROM dbo.WorkItemsLatest AS WL
JOIN dbo.WorkItemsAre AS WA
ON WL.ID = WA.ID
WHERE WL.[Changed Order] <> WA.[Changed Order]

Conclusion

I’ve done a large number of TFS 2010 SP1 migrations, and this is the first time I’ve run into this problem.  So, don’t let it freak you out.  However, if you run into this problem, get PSS on the phone right away, and get this problem solved!  (As a side note, I don’t believe you’ll be charged for the call, since it does appear to be a bug in the SP1 upgrade process.)

Installing TFS 2010 SP1 will solve the problem. (Also, please install TFS 2010 SP1 CU1 to fix the issues introduced by SP1.)

After running windows update on your TFS App Tier and your Team Build machines, automated builds will begin to fail or hang.  Looking into the event log will show the error below.  (Also, see notes below for other ways to test if you have the problem.)

The exception text reads something like:

Exception Message: Could not load file or assembly ‘System.Runtime.DurableInstancing, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35′ or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0×80131040) (type BuildServerException)

Exception Stack Trace:    at Microsoft.TeamFoundation.Client.TeamFoundationClientProxyBase.ProcessHttpResponse(HttpWebResponse response, Stream responseStream, WebException webException, XmlReader& xmlResponseReader)
   at Microsoft.TeamFoundation.Client.TeamFoundationClientProxyBase.ExecWebServiceRequest(HttpWebRequest request, XmlWriter requestXml, String methodName, HttpWebResponse& response)
   at Microsoft.TeamFoundation.Build.Client.AdministrationWebService.TestBuildControllerConnection(Uri controllerUri)
   at Microsoft.TeamFoundation.Build.Client.BuildServer.TestConnectionForBuildController(IBuildController controller)
   at Microsoft.TeamFoundation.Build.Machine.ControllerService.TestService()

Unfortunately, short of rolling back the Windows Update, you’re going to have to either install TFS 2010 SP1 immediately, or work some version re-direction magic in the GAC.  This means you’re likely installing SP1 under duress, but there are very limited options.

Don’t forget to install VS 2010 SP1 as well if you have Visual Studio 2010 or Team Explorer 2010 on any of your TFS 2010 or Team Build servers.

You can find downloads here:

• TFS 2010 SP1 (KB2182621) : http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=20506
• VS 2010 SP1 Web Installer (KB983509) : http://www.microsoft.com/download/en/details.aspx?id=23691
• TFS 2010 SP1 Cumulative Update 1 (KB2580221) : http://www.microsoft.com/download/en/details.aspx?id=26211

Your Team Builds will begin running immediately upon installing the TFS 2010 SP1 (and possibly a reboot), however, I really recommend getting everything up to the same versions while your in forced maintenance anyway.

1) Open up the TFS Administration Console, Select Build Configuration and click Properties on any of the Agents.

2) In the Build Agent Properties window, click the Test Connection button.  If you get the System.Runtime.DurableInstancing error, you have the problem and will need to install TFS 2010 SP1 to correct it.

Good luck!

In a strict world of Scrum you have a Product Backlog and when you begin a sprint you move the items that you are committing to into the Sprint Backlog and then you pull your work from there – almost like a Kanban system but not quite, because the Work In Progress (WIP) limits are at a higher level and in general it tracks work at a higher level than Kanban does as well as several other differences.

The major problem we continuously run into is the complexity of the network and the hardware involved in the work that we do. To add to the complexity is the fact that different teams (which we have no influence over) take longer to do work than we do and they are governed by a strict set of Service Level Agreements (SLA) which you will often find in large companies where some of the core work, such as server maintenance or data center maintenance, is subcontracted.

Scrum, combined with the team size gave us the perfect ability to hide our problems which was not a good thing. What would happen is that teams would run into a problem in, say, the development environment and set things in motion to solve the problem (opened a ticket with the server team) and would then move on to the QA environment. The problem would occur in the QA environment and then move to the Pre-Prod environment – all the while this problem still occurred. But because the team kept pulling items from their queue to work on, they were “busy” all of the time and reporting good progress – but not actually completing anything.

I should note that some of the user stories were straight technical stories – software being installed for instance to get various environments up and running.

The problem here was two-fold. The first is that the way the user stories were constructed, installing software and moving code from Dev to QA to Pre-Prod were all part of a single user story – it was just different parts of the requirement and Scrum doesn’t track down at the task level. The second part is that the “in progress” bucket can be huge – it is up to the practitioner to break the story down into a manageable level. So lo and behold we were building up a huge amount of technical debt that turned out to be fatal for this iteration. What happened versus what should have happened?

What happened?

First a team of 15+ people is too big for a 15 minute standup each morning. 15 people x approximately 3 minutes each = 45 minutes. That’s a bit outside of 15 minutes and our team is actually larger than 15 people. So what did we do?

Mistake #1

We eliminated the 15 minute standup meetings in favor of a once weekly team meeting.

There were other forces involved in this decision – at any large company there are going to be a lot of meetings and the team was suffering from “meeting fatigue”. As the Scrum Master I didn’t want to add to it and I couldn’t figure out how to keep the meetings to 15 minutes regardless. This, of course, led to the second problem.

Mistake #2

In a larger team meeting, people are concerned that they will be looked on negatively if they keep reporting problems. So they don’t – or they under-report the magnitude of the problem.

Our iterations are one month long. This took me two months of looking back at the data to realize. Once I figured it out, I committed mistake #3.

Mistake #3

Private conversations regarding the problems people are experiencing do not allow the team to focus their energies on the problem at hand – it becomes an individual firefighting experience.

We have a lot of very talented people on our team. By having one on one meetings with individuals who were having problems I was getting right back into the problem that mistake #1 was designed to solve – the number of meetings skyrocketed as I had to deal with a whole bunch of problems one on one. In addition, I wasn’t able to bring the knowledge of the entire team to bear on a problem – I had to schedule more meetings to do investigation instead of just having everyone pitch in at once.

To be honest, some problems – specifically those that rely on external forces – can only be solved by escalation to management. And this lead to Mistake #4.

Mistake #4

I didn’t recognize the negative impact of the groups culture – which is, they were not rewarded for bringing problems to light. The team members felt management didn’t care – that they just wanted the problem solved but they didn’t want to know about it.

I am not management – I never will be. But because of my role team members felt that reporting problems to me was the same as reporting them to management. Which they were highly reluctant to do. This lead to Mistake #5.

Mistake #5

The team members had enough work in their queue that they could simply move on to something else. By not updating their status correctly I had no visibility of this.

What they essentially did was to try to handle the problem on their own, reported that everything was okay and on track when in fact that was far from the truth. They kept hoping that things would come back on track which they never did because no effective intervention ever took place. This effectively let us hide waste. There was one more problem that came out of all of this.

Mistake #6

We didn’t recognize quickly enough that the handoffs between team members were difficult and not working well at all.

In Scrum, one person is generally responsible for a user story from beginning to end – there is a concept of ownership. We tried to do that – as the Scrum Master I had the ownership. Why not a Product Owner you might ask. Good question – the team was reporting to five product owners at the same time with approximately 8 different statements of work per month. We are a core solutions team so we provide many different solutions for different customers on the same infrastructure. The reason for individual team members not taking ownership is because there were many coordination’s that had to occur to get a single piece of work done because of the specialized skillsets required to get the work done (we recognize the need to grow the skillsets but that can’t be done overnight). Essentially there was no coordination or collaboration in the handoffs of work or even the scheduling for when work would be done.

Those are the big six mistakes that I feel, in retrospect, that I made as a scrum master with this particular team. So, what did we do about it and how did it work? I can’t tell you how it worked because this is a work in progress and this is the first month we are doing this but I’ll post back with a follow up.

Countermeasures we put in place

Solution #1 – Implement a Scrum of Scrums

The immediate step was to appoint two additional Scrum Masters and “break” the team up into three autonomous teams (that is, each team is self contained – the mix of resources is such that each team has someone with the specialized skills needed to work a particular technology or type of solution).

This was done so that the Scrum Masters could more effectively deal with problems since they were only overseeing a small number of team members. And oversee is too strong a word, the Scrum Masters did perform some work as well. This freed up my time to do some more work since I was now the Scrum Master for only 6 people (including myself). This immediately led to another quick solution…

Solution #2 – Reinstated the daily stand-ups

The smaller teams allowed each Scrum Master the ability to hold daily standups that actually last only 15 minutes.

The standups are four days a week plus one team meeting that lasts one hour. The Scrum Masters also have a once a week coordination standup meeting. We ask the same three questions but reserve the right to extend the meeting to coordinate resources to meet special demands.

Solution #3 – A “true” Kanban approach

Individuals are assigned only one requirement at a time – the other requirements are held in an iteration backlog and are assigned to the generic resource of “Product Manager”. We do not discuss these items with the team members at all during our iteration planning meeting.

This had a whole bunch of ramifications. The first is that we would not commit to a full iterations worth of work – we created a monthly “roadmap” which said, “these are our goals for the month which we will try to reach”. The upside to this approach is that our iteration planning meetings went from 7 hours to 2 hours. Nice. The downside to this approach is that our team is currently really unable to make a commitment and stick to it. We had not been doing it for the last year so this is really no change from the status quo but it leads to another benefit:

When a problem is encountered it is surfaced and dealt with in a 24 hour period. What do I mean by this? Well, since team members are only allowed to work on one item at a time (a WIP limit of 1 as it were) when something goes wrong and they cannot fix it themselves we (the Scrum Masters) either find out about it in the next standup meeting or the team member contacts the Scrum Master as soon as the problem is recognized and it can be elevated to management ASAP. Work halts until the problem is solved. We then capture the resolution to these issues and turn around and drive them back into the process.

Note that this is a work in progress and we’re still working out how to best drive the problem resolution back into the process so we avoid the problem in the future.

In addition, this alleviates some of the management role that I was playing because if team members do not escalate problems, they have to explain to their management why they were working on one tiny item with an estimate of 8 hours for a week. It also allows Scrum Masters, through empirical observation to detect problems earlier.

Did I mention that our entire team is virtual and spread out all over the US?

Solution #4 – Reward problems discovered

The last item is to celebrate when a problem is found – the earlier the better.

We are using TFS for our work and created a special area for internally created issues. We encourage team members to report issues with the process as they find them. We review these issues each iteration and take one to improve upon as part of our work structure. It remains to be seen how effective this will be but it’s a start.

Conclusion

I debated whether or not to share this experience and in the end decided that there must be other teams running into these problems. I’ve been doing this for 5 years now (stricter focus on process and methodology that is) and I knew all about these problems and yet I let the politics of the organization suck me right back into things that I have coached other teams for years on how to avoid. Talk about feeling dumb.

And I had tried other things along the way but kept running into the same problems because I could not trust the team to do things in the way they needed to be done. While I still have that problem, I was also part of the problem because I was not explicit enough in explaining to the team why we needed things done.

Hopefully, this post will help other people who might be in the same situation.

The various tables are TreeIDPairs, TreeNodes, xxTree and the views are TreePairs, TreePathParts, TreesAreUsed and TreesWereUsed. All of these views and tables have problems with them in one way or another. For example, the TreePairs view has columns called Name (all values are a ‘\’) and AboveID (all values are ‘0’) – not very useful. The TreesAreUsed contains the full Area Path but no Iteration Path. The xxTree has both but I preferred to not rely on that table (anything with an ‘xx’ to start the table name tells me it either is, or may be, deprecated). So I wrote my own query which I thought might be helpful to others.

WITH FullIterationPath (ID, ParentID, Name, tlevel, hierarchy)
AS
(
    --Anchor definition
    SELECT    a.ID,
            a.ParentID,
            a.Name,
            0 as tlevel,
            a.Name as hierarchy
    FROM    TreeNodes a
    WHERE    ID = 439    --FEC Solution-Products Root
    UNION ALL
    --Recursive definition
    SELECT    a.ID,
            a.ParentID,
            a.Name,
            tlevel + 1 as tlevel,
            cast(hierarchy + '\' + a.Name as nvarchar(255)) as hierarchy
    FROM    TreeNodes a
    JOIN    FullIterationPath b ON b.ID = a.ParentID
)

SELECT    ID,
        ParentID,
        Name,
        tlevel,
        hierarchy
FROM    FullIterationPath

You can also use this to construct the area path as well.

This can raise a couple of challenges once you start to look at how you publish these samples. The issue is that a server based system will need some way to track the client side changes and with most popular version control systems this will involve the presence of extra files around the samples directories. As a consumer of the samples, the presence of these files in the published artefacts is far from ideal. I really don’t want to have the samples trying to connect to your remote server, or even a local instance of a version control provider I might not have installed.

So how do we break the dependency on the source control provider during the packaging of these samples for publishing? We could manually go through and delete all of the binding mechanisms, but that would expose us to the following types of waste:

• Defects – manual processes are more prone to defects
• Waiting – builds need to wait on the samples to be prepared for packaging
• Extra Processing – extra steps to make our packaging pick up our manually cleansed samples

We can avoid most of this waste by automating the process. So if it’s able to be automated, how do we do it?

Prerequisites

Download the following script https://gist.github.com/967976. This script is written originally by Damian Maclennan, and essentially removes the TFS source binding files, solution and project elements that reference the TFS instance.  My fork includes the ability to decide on if you want the files backed up before removal of the version control sections. I usually choose not to, I don’t want the backup files in the output and have the actual versions in version control if I need them. In addition you may want to do the following:

• Create a batch file wrapper for the script using the approach defined by Jason Stangroome at http://bit.ly/kmyfY2
• Commit the script to a path in your repository that is part of your build workspace with the same name as the PowerShell script

First Step: Create a custom build template

• Setup a build to create your packages, and when you get to choosing the process template clone the default template into a new template
• Check the new template into source control

Second Step: Set up a folder to publish to

• Open your cloned template and navigate to the point at which MSBuild is invoked with the ‘Build’ target
• Drop in a new sequence activity and name it ‘Publish Samples’

• Create an argument named ‘SampleDropFolder’.
• This will be the configurable name for the folder placed in the output directory with our samples inside.
• We’ll talk about how to surface this on the build configuration dialogue later.

•  Create a variable to hold the full path to the output folder.
• I’ve named mine ‘SamplesDropFolder’ but that may be a bit close to the argument name for you.
• I also default this to a combination of the outputDirectory variable specified in the scope of the Compile and Test activity and the SampleDropFolder argument we’ve specified previously.

• Open up your ‘Publish Samples’ sequence activity and drop in a ‘Create Directory’ activity.
• Configure it with the ‘SamplesDropFolder’ variable we set up in the last step.
• This will set up a root directory we can copy all our samples to, and makes it easy to run our binding removal script later on.

Third Step: Copy the samples

Now we’ve got our directory, we need to work out what we want to put in it. In most cases, we’ll have more than a single set of folders to move, so we need to put some smarts around how we identify our targets.

• First create an Argument called ‘Samples’ and configure it to be of the type String[].

• Drop a ForEach activity into the ‘Publish Samples’ sequence and configure it to iterate over our Samples argument we just created.
• Add a variable to contain the local path of the sample directory we’re currently working with as a string with the name ‘sampleLocalPath’
• Inside the ForEach activity drop a ‘ConvertWorkspaceItem’ activity. This will take our server paths and work out the local path for the directories for us. You’ll need to configure it as follows:

• Drop in a ‘CopyDirectory’ activity to copy our sample directory from the source to the output directory.  Your ForEach should now look something like this:

Fourth Step: Remove the source control bindings

Now we’ve got our samples into the target directory, we need to strip out the source control bindings so our customers don’t try to connect to our server when they open the solutions.

• Add an Argument to specify the server path to the batch file we checked in back at the start of the process.

• Create a variable to house the local path of our binding removal script. I’ve named mine ‘SourceControlRemovalScriptLocalPath’
• Drop in another ‘ConvertWorkspaceItem’ activity after your ForEach activity. This will be used to convert the argument we just created with the server path to our source binding stripping script to its local path.  It should be configured like this:

Note: While the variables look like they are the same item, they aren't I promise!

• Drop in an ‘InvokeProcess’ activity after the ‘ConvertWorkspaceItem’ you just added.  A little care is required when configuring this activity to ensure we get a reliable execution, so I’ll list out how I’ve configured each property.

Arguments: Microsoft.VisualBasic.Chr(34) + SamplesDropPath + Microsoft.VisualBasic.Chr(34)

Display Name: Strip Source Control Bindings

File Name: Microsoft.VisualBasic.Chr(34) + SourceControlRemovalScriptLocalPath + Microsoft.VisualBasic.Chr(34)

Working Directory: BinariesDirectory

Any other properties remain unaltered from their default state

Your publish samples sequence activity should now look a little like this

Fifth Step: Surface the arguments

That’s nearly everything we need to do to support the publishing of samples into our output directory. However we’ve set up a few arguments in here to ensure our template is re-usable. We now need to surface them to users via the build configuration dialog. To do this:

• On the ‘Metadata’ Argument for the build workflow click the ellipsis. You should get a pop up dialog
• Configure the three arguments we’ve added as follows
• The samples list
• The samples drop folder name
• The source control removal script path
• These should be configured in the editor as follows:

The only thing that changes across the parameters are the Display Name – the name we surface to the editor, and the Parameter Name – the name we gave our argument that corresponds to this parameter

• Check in the template

Final Steps: Configure the build!

Now we’ve got our template done, let’s go configure a build! The only real point of interest here are the custom parameters we set up on our way through, so we’ll focus on them – this is a long enough read already!

The points of interest are all on the process tab, so let’s skip there. If you expand your custom section you should see something like this:

All you need to do is fill in the values, so it looks more like this:

Once that’s done, kick off a build and you should be able to locate your samples, without the binding configuration in the drop directory of your build output!

Conclusion

In this article I’ve shown you how to create a reusable template for including useful samples in your build output. I’ve used this particular approach with a few customers and what I particularly like about it is we aren’t moving too far from the out of the box activity set that comes with Team Build. This saves us on overhead, and allows the template to be put together pretty quickly.

Tagged: Publishing, Team Build, TFS

Update: Microsoft released a QFE to address the issue outlined below.

Here is a summary of the list of issues fixed by the QFE, to help you decide whether you should apply the QFE:

Issue 1: When you run tests on the test agent that is installed on a computer that has Visual Studio 2010 SP1 installed, the tests may not run, and the following error message is logged:

Attempted to access an unloaded AppDomain. (Exception from HRESULT: 0×80131014)

Issue 2: When you run a playback of a Coded UI Test on certain Windows Presentation Foundation (WPF) controls, a Microsoft.VisualStudio.TestTools.UITest.Extension.UITestControlNotFoundException exception occurs, and then you receive the following error message:

“Search may have failed at ‘<name>‘ <control type> as it may have virtualized children. If the control being searched is descendant of ‘<name>‘ <control type> then including it as the parent container may solve the problem.”

Issue 3: When you try to create a work item from the Test Results pane in Visual Studio 2010 after you connect to a Team Foundation Server (TFS) server, a System.OutOfMemory exception occurs, and the creation operation fails. This issue usually occurs if the TFS server has many builds.

Issue 4: When some tests run in a build operation, some builds that are queued in a TFS server stop responding. Additionally, the following error message is logged in the build log:

Waiting to publish…
Publishing results of test run <build name> to http://<TFS server address>:8080/tfs/DefaultCollection…
The process cannot access the file ‘<directory>\data.coverage’ because it is being used by another process.
Publish failed or canceled.

——————————————————————————————-

As I was preparing for a demo of lab management the other day I did what we tell all of our customers to do – patch everything to latest service packs which of course included TFS SP1 on all of our machines. That includes the TFS server and all build servers and virtual lab environments.

By the way, using the lab prep tool you must manually install SP1 after the VM is prepped otherwise you get a few errors. But I digress.

After I patched everything I ran a test to verify that everything worked. I created a manual test, recorded it and turned it into a CodedUI test with validations. All went smoothly. Then I ran a lab build and got a failure. Looking at the automated test run (MTM > Testing Center > Test > Analyze Test Runs I noticed the following log:

You will note the last three items. Even though the test log shows that the test executed successfully, it did not. If you remove the diagnostic data adapters, the error on line 17 will be removed but the errors on 16 and 18 continue.

It turns out that when SP1 was released, it caused a problem with the test agent running in the lab environment. A simple solution for my needs was to uninstall SP1 from the machines in the lab environment and everything ran fine again – or so I thought. However, when you do this, IntelliTrace does not work because of the mismatch between the external test controller (patched to SP1) and the internal test agent (RTM). Or so I believe right now.

Microsoft has confirmed this to be a problem and they are actively working on a QFE for this. I will drop another post once this QFE is released.

[TestCleanup()]
public void MyTestCleanup()
{
    if (TestContext.CurrentTestOutcome == UnitTestOutcome.Failed)
    {
        Image img = UITestControl.Desktop.CaptureImage();
        img.Save(Path.Combine(TestContext.TestResultsDirectory, "FailureSnapshot.png"));
    }
}

By placing this code in the TestCleanup method, whenever a test fails, the last screen of the test will be captured and saved in the test results directory which will automatically be captured at the end of the test run.

Microsoft recently launched a great site that provides all the tools and information to help you upgrade from Visual SourceSafe to Team Foundation Server right now. Visit www.microsoft.com/visualsourcesafe to access these tools.

We are pleased to be a part of this resource site. Our very own Steven Borg and Rennie Araucto are featured in the videos which explain both Why and How to migrate from VSS to TFS.  The site also features a very informative WhitePaper, “Upgrading from Visual SourceSafe to Team Foundation Server”, written by the creator of Visual SourceSafe and Team Foundation Server, Brian Harry.

You can download the WhitePaper and watch the videos here!

 

 

Looking to make the move to Visual Studio Team Foundation Server?   Northwest Cadence would love to help! 

 

We have also designed a special offering to help you manage your Visual SourceSafe migration to ensure success with TFS.  

 

 

Please contact Linda.Collier@nwcadence.com with any questions or to learn more about how Northwest Cadence can help you make the move to Visual Studio Team Foundation Server 2010.