Where Technology Meets Teamwork » Uncategorized http://blog.nwcadence.com Thoughts on TFS, Lean, Agile, Kanban, Scrum and other collaborative technologies and techniques Thu, 26 Jan 2012 17:15:21 +0000 en hourly 1 http://wordpress.org/?v=3.1.3 SharePoint 2010 Prerequisites for Development Environment http://blog.nwcadence.com/2012/01/sharepoint-prerequisites-for-sharepoint-2010/ http://blog.nwcadence.com/2012/01/sharepoint-prerequisites-for-sharepoint-2010/#comments Thu, 26 Jan 2012 01:30:26 +0000 Bryon Root http://blog.nwcadence.com/?p=41914 Continue reading →]]> As I was reviewing  the document “Setting Up the Development Environment for SharePoint 2010 on Windows Vista, Windows 7, and Windows Server 2008” which can be found here. I discovered some interesting information and script that I believe is valuable and worth sharing with you all.

There are a number of hotfixes, .Net framework, ASP.Net and Service Pack updates that need to be installed, referenced, and available, depending on the OS version of your SharePoint development. 

The good news is, SharePoint does include a PrerequisiteInstalle.exe tool that installs all the prerequisites you are using in Windows Server 2008.   Which in most cases, are not in a standard development machine.

Now the bad news—if you are using Windows 7 or Vista  as your development OS, the PrerequisiteInstalle.exe tool does not work. 

This leaves additional configuration steps and required several downloads, in order to get SharePoint installed.

However, there is a handy PowerShell script  “Download SharePoint 2010 Pre-Requisites” that can be found here, which downloads the prerequisites to a folder for an offline installation of SharePoint 2010 or in my case, as an extra step for “good measure” to  confirm that nothing was missed.

The PowerShell script uses BitTransfer so you can see the status of each download.  As shown below using PowerGUI.

image

You could also modify the “Download SharePoint 2010 Pre-Requisites” PowerShell script for other prerequisites software installation or configuration. 

If you are getting started or need to setup SharePoint development environments, I would highly recommend reviewing the ALM Resource Center | SharePoint 2010 site. It has a number of useful links and resources.  Also, check out our new SharePoint ALM Health Check offering that provides an independent review of your SharePoint development practices.

]]> http://blog.nwcadence.com/2012/01/sharepoint-prerequisites-for-sharepoint-2010/feed/ 0 Northwest Cadence January Team Day! http://blog.nwcadence.com/2012/01/northwest-cadence-january-team-day/ http://blog.nwcadence.com/2012/01/northwest-cadence-january-team-day/#comments Tue, 24 Jan 2012 23:13:06 +0000 laura.lamborn http://blog.nwcadence.com/2012/01/northwest-cadence-january-team-day/ Continue reading →]]> Our Quarterly Team Day is always a highlight, however this team day had perfect timing! You know after New Year’s, when it’s time to go back to work but you really want one more day off? Well, this quarter’s Team Day filled the gap! Instead of the traditional day back (filled with catching up and a backlog of to-do items), we all headed out for breakfast clip_image002at our team’s favorite restaurant- Hector’s (can you say YUMMMO!). The remainder of the day consisted of internal planning and learning how to utilize our individual strengths at work (via Strength Finder) from Henriet Schapelhouman with SemperVita Institute—sounds a bit cheesy but was so beneficial and educational! What a fantastic team building session! 

To quote from last team day’s post, Balance is key to everything, so we incorporate that into our Team Days—Work followed by Reward—are we fortunate or what?!?

]]> http://blog.nwcadence.com/2012/01/northwest-cadence-january-team-day/feed/ 0 NWC Team Day! http://blog.nwcadence.com/2012/01/nwc-team-day/ http://blog.nwcadence.com/2012/01/nwc-team-day/#comments Mon, 09 Jan 2012 23:26:00 +0000 Amanda http://blog.nwcadence.com/2012/01/nwc-team-day/ Continue reading →]]> I always look forward to our Company Quarterly Team Days.  Yes, we have workshops and are productive, but we also know how to have a good time! Balance is key to everything, so we incorporate that into our Team Days-  Work followed by Reward.
 
Our October 2011 Team Day was a particularly fun one.  What better way to kick off the day than with a delicious breakfast and team

discussion?!

 
Our Team Day morning started (as they typically do) with a hearty breakfast at Hector’s. Yum!
 
We then spent a few hours working together on internal projects.  In the afternoon, we headed south for some arcade games, go karting and lazer tag!
 
 
Here are some highlights from this October Team Day.
 
 Most Competitive: SHAD
 
  
Best Moves: CHERYL
 
 
 
Most Energetic: STEVE

 
Best Accessorized: RICK, LORI, and DAN
 
 
Fearless Driver Award: JAMES
 
 
Most Determined: MARTIN
 
Best LazerTag Shot: Laura
 
 
Reckless Racer (also our leading photographer): BRYON
 
Most Enthusiastic Team Day Organizers: AMANDA and RENNIE
 
 
 
I realize that since I play a large role in organizing our Team Days my opinion carries some bias… but I still  think we have some of Best Team Days out there!
 
What will we think of next?!…
Stay Tuned!
 
]]> http://blog.nwcadence.com/2012/01/nwc-team-day/feed/ 0 Upcoming Events http://blog.nwcadence.com/2011/10/upcoming-events/ http://blog.nwcadence.com/2011/10/upcoming-events/#comments Wed, 26 Oct 2011 20:35:51 +0000 laura.lamborn http://blog.nwcadence.com/?p=28422 Continue reading →]]> What’s more fun than talking about tough technical topics, showing amazingly cool demos, and sharing insiders tips learned through years
in the trenches?

Northwest Cadence hosts regularly-scheduled events designed with our clients and community in mind. Come ready to ask
hard questions, gain new knowledge, and be part of the social occasion.

UPCOMING TRAINING OFFERINGS

Training Course: Testing with Test Professional 2010 and VS2010 Ultimate Oct. 24-27, 2011

For Details or to Register, Click Here!

Training Course: Testing with Test Professional 2010 and VS2010 Ultimate Dec. 5-8, 2011

For Details or to Register, Click Here!

Training Course: Professional Scrum Master Dec. 6-7, 2011

For Details or to Register, Click Here!

Training Course: Professional Scrum Developer Recurring

For Details or to Register, Click Here!

 Training Course: Agile Project Management Recurring

 For Details or to Register, Click Here!

FREE ALM Training Recurring

For Details or to Register, Click Here!

UPCOMING EVENTS

Coffee Talk: Limit Work in Process (free webcast) November 4, 2011

LIVE Coffee Talk: Testers Get Professional October 27, 2011 For Details or to Register, Click Here!

LIVE Coffee Talk: vNext December 8, 2011For Details or to Register, Click Here!

Anchorage, AK: Double Feature: Testing & ALM for Agile Development November 8, 2011 For Details or to Register, Click Here!

Bellevue, WA: Double Feature: Testing & ALM for Agile Development November 9, 2011 For Details or to Register, Click Here!

Fremont, CA: Double Feature: Testing & ALM for Agile Development November 10, 2011For Details or to Register, Click Here!

San Diego, CA: Double Feature: Testing & ALM for Agile Development November 29, 2011 For Details or to Register, Click Here!

Fremont, CA: Doing Application Lifecycle Management Right December 13, 2011 For Details or to Register, Click Here!

Bellevue, WA: Doing Application Lifecycle Management Right December 14, 2011 For Details or to Register, Click Here!

Portland, OR: Doing Application Lifecycle Management Right December 15, 2011  For Details or to Register, Click Here!

Make a Service Request
Fill out a short form to let us know how we can help you. We will be back in touch within the day.

Service Request | Training & Events | info@nwcadence.com © 2010 Northwest Cadence Corporation. All Rights Reserved.

]]> http://blog.nwcadence.com/2011/10/upcoming-events/feed/ 0 Manual Testing Code Coverage–Yeah! http://blog.nwcadence.com/2011/10/manual-testing-code-coverageyeah/ http://blog.nwcadence.com/2011/10/manual-testing-code-coverageyeah/#comments Thu, 20 Oct 2011 17:38:33 +0000 Jeff Levinson http://blog.nwcadence.com/2011/10/manual-testing-code-coverageyeah/ Continue reading →]]> Much asked for and incredibly helpful but missing in Visual Studio 2010 and Microsoft Test Manager 2010 was code coverage for manual testing. In Visual Studio vNext (and Microsoft Test Manager vNext) it’s available out of the box.

To enable it, go to the test settings and select Code Coverage (there are some options but you don’t need to set anything).

CodeCoverage1

You do need to create an automated build (if you aren’t doing automated builds now, you need to be doing it NOW – it’s the fastest way to improve quality). After you set the settings and associate the automated build, run your manual test. When you’re finished, close the Test Runner and click the Analyze Test Runs page.

CodeCoverage2

Make sure you have the View: Manual runs selected and double-click your completed test run. This opens up the test run summary.

CodeCoverage3

Expand the Attachments node and you will see a data.coverage file (note that you ran more than one .NET application during the test run you will see multiple files). Double-click it to open it. This will open Visual Studio to display the code coverage results.

CodeCoverage4

This screenshot shows all of the methods in the executable and the covered and not covered blocks.

CodeCoverage5

Double-clicking a method brings up the file with code coloring enabled.

Brilliant!

Now teams can ensure that they are covering all of their code with their functional tests as well as with their unit tests.

]]> http://blog.nwcadence.com/2011/10/manual-testing-code-coverageyeah/feed/ 2 TFS 2010 SP1 Upgrade Bug May Cause Warehouse Update to Fail with Error TF221122 http://blog.nwcadence.com/2011/10/tfs-2010-sp1-upgrade-bug-may-cause-warehouse-update-to-fail/ http://blog.nwcadence.com/2011/10/tfs-2010-sp1-upgrade-bug-may-cause-warehouse-update-to-fail/#comments Wed, 12 Oct 2011 17:15:32 +0000 Steven Borg http://blog.nwcadence.com/?p=28378 Continue reading →]]> image

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).

clip_image001[4]

 

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.)

]]> http://blog.nwcadence.com/2011/10/tfs-2010-sp1-upgrade-bug-may-cause-warehouse-update-to-fail/feed/ 1 The Scrum Master has no role in Scrum http://blog.nwcadence.com/2011/09/the-scrum-master-has-no-role-in-scrum/ http://blog.nwcadence.com/2011/09/the-scrum-master-has-no-role-in-scrum/#comments Thu, 15 Sep 2011 22:41:49 +0000 JamesTupper http://blog.nwcadence.com/2011/09/the-scrum-master-has-no-role-in-scrum/ Continue reading →]]> I was asked to read the Scrum Guide, by my co-worker Martin Hinshelwood, and take the Open Scrum Guide to prepare myself for the Professional Scrum Master course that he is giving to me and a few other colleagues here at Northwest Cadence. I was happy to oblige and ready myself for a day with Martin and Scrum; however, during my assigned reading and test I found an ambiguity that was quite apparent, yet it was not alone as there were, in my mind, others like it.

First of all, I responded to Martin with a screenshot that I had completed what he asked, and got more than 75% on the Scrum Open Assessment.

clip_image002

Figure: 80% on Scrum Open Assessment

After seeing my passing grade, I quickly ran through the answers to see which ones I had gotten wrong. Question #9 caught my eye because I had thought for sure that the team was not supposed to be managed.

“[The Development Team] are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality”
– Scrum Guide 2011

Scrum_Master_is_Management
Figure: Marking me my answer, “False”, as wrong to the statement : Scrum Master is a “management” position?

Quickly, I realized that there were other management-type questions on the exam I did a simple “Ctrl+F” to search for the word “manage” (as you can see by the highlighted text in the figures). After scanning past a few questions I found question #20:

No_Management_in_Scrum
Figure: Clearly stating that Management has NO role in Scrum (Correct Answer)

A Scrum Master is on the Scrum team, and, therefore, part of “Scrum”. Yet, I was correct when I marked the answer “Management has no role in Scrum.” This ambiguity/contradiction was not alone during my initial lead-in to the Scrum world. Currently, the current issue has been made known, and, hopefully, we will be able to fix the double-entendre of the word “management.”

]]> http://blog.nwcadence.com/2011/09/the-scrum-master-has-no-role-in-scrum/feed/ 3 First release of the community build tools http://blog.nwcadence.com/2011/07/first-release-of-the-community-build-tools/ http://blog.nwcadence.com/2011/07/first-release-of-the-community-build-tools/#comments Tue, 05 Jul 2011 13:29:49 +0000 Jeff Levinson http://blog.nwcadence.com/2011/07/first-release-of-the-community-build-tools/ Continue reading →]]> Microsoft MVP’s and community contributors announced the first release of the TFS 2010 Work Flow community build activities and Actions. The plan is to ship every two to three months after another update next month (August). Download the tools from the Community TFS Build Extensions CodePlex site.

]]> http://blog.nwcadence.com/2011/07/first-release-of-the-community-build-tools/feed/ 1 TechEd 2011: Northwest Cadence talks http://blog.nwcadence.com/2011/05/teched-2011-northwest-cadence-talks/ http://blog.nwcadence.com/2011/05/teched-2011-northwest-cadence-talks/#comments Tue, 24 May 2011 19:06:18 +0000 Amanda http://blog.nwcadence.com/2011/05/teched-2011-northwest-cadence-talks/ Continue reading →]]> We are so excited to share links to the recorded sessions that Steven Borg and Jeff Levinson delivered at TechEd last week.  

Also, huge congratulations to Steven for having one of the top scores of TechEd with his Dev311 talk!

DEV311 | Deep Dive into Microsoft Visual Studio Team Foundation Server 2010 Reporting
Speaker(s): Steven Borg
http://media.ch9.ms/teched/na/2011/wmv-hq/DEV311-HD.wmv

DPR309 | Metrics That Matter: Improving Lean and Agile, Kanban and Scrum
Speaker(s): Steven Borg
http://media.ch9.ms/teched/na/2011/wmv-hq/DPR309-HD.wmv

DEV350 | Using Tests to Drive the Entire Software Development Lifecycle
Speaker(s): Jeff Levinson
http://media.ch9.ms/teched/na/2011/wmv-hq/DEV350-HD.wmv

DEV306 | Branching and Merging for Parallel Development
Speaker(s): Jeff Levinson
http://media.ch9.ms/teched/na/2011/wmv-hq/DEV306-HD.wmv

]]> http://blog.nwcadence.com/2011/05/teched-2011-northwest-cadence-talks/feed/ 1 Team Days–Day 1! http://blog.nwcadence.com/2011/04/team-daysday-1/ http://blog.nwcadence.com/2011/04/team-daysday-1/#comments Tue, 05 Apr 2011 03:41:28 +0000 Steven Borg http://blog.nwcadence.com/2011/04/team-daysday-1/ Continue reading →]]> Today was Day 1 of our quarterly Team Days, when the whole Northwest Cadence team gets together to work collaboratively on internal projects, eat way too many snacks, and talk about new strategies.  This quarter Lori brought in a massage therapist and we all got massages throughout the day.

I get to work with a wonderful team!  I know a blog isn’t really a place to gush about how wonderful your coworkers are, but I’m going to.  So, to the Northwest Cadence team – Thank you!  You’re such a wonderful group of friends, and each and every one of you makes this team great.  I am so happy to work with you.  This is, by far, the best team I’ve ever worked with in my life. 

I can’t wait to see what’s in store for tomorrow, when it’s all fun and games!  (Please, no karaoke…)

]]> http://blog.nwcadence.com/2011/04/team-daysday-1/feed/ 0