|
|
Scrum for Team System - v2.x Support
Started by Kirk at 10-03-2008 11:33 AM. Topic has 9 replies.
 
 
|
|
Sort Posts:
|
|
|
|
10-03-2008, 11:33 AM
|
Kirk
Joined on 11-08-2007
Posts 12
|
Cannot update TFSWarehouse - missing field value for DateDiscovered
|
|
|
|
|
My warehouse will not update. I get this message in the event log:
Detailed Message: Microsoft.TeamFoundation.WorkItemTracking.Adapter: Exception while saving fact - 3820 revision 3 with tracking id 3820|3|1 - System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: TF51218: Missing field value for: Conchango_TeamSystem_Scrum_DateDiscovered.UTCDateTime
Any ideas how I can fix this?
|
|
|
|
|
Report
|
|
|
|
10-03-2008, 11:56 PM
|
Crispin Parker
Joined on 11-13-2007
Posts 664
|
Re: Cannot update TFSWarehouse - missing field value for DateDiscovered
|
|
|
|
|
Hi Kirk,
From the look of your error message I would expect that work item 3820 has a corupt or invalid value in it's 3rd revision.
I would suggest looking in the TFS WorkItemTracking database and trying to find the revision in question. Hopefully, the error should be fairly obvious.
Once the error has been corrected, you should be able to rebuild the data warehouse.
Regards,
Crispin Parker, Technical Consultant, Conchango.
"It is better to light a candle than to curse the darkness"
|
|
|
|
|
Report
|
|
|
|
10-04-2008, 3:17 AM
|
Kirk
Joined on 11-08-2007
Posts 12
|
Re: Cannot update TFSWarehouse - missing field value for DateDiscovered
|
|
|
|
|
That was it, Crispin. I used the power tool to destroy that workitem and now it's working.
Thanks!
|
|
|
|
|
Report
|
|
|
|
10-04-2008, 10:01 PM
|
Kirk
Joined on 11-08-2007
Posts 12
|
Re: Cannot update TFSWarehouse - missing field value for DateDiscovered
Attachment: deleted.jpg
|
|
|
|
|
Actually...
It does rebuild, but it keeps finding another work item with the same problem. So far I've cleared about three out of the database. Every time I get rid of one, another pops up on the next run.
Anything else I might try?
....
I snooped around in the database a bit and found that a few fields were deleted, including the discovery date one. See the attached screen shot. I'm not sure how they got deleted, or how necessary they are, but it seems like the discovery date needs to be there.
|
|
|
|
|
Report
|
|
|
|
10-07-2008, 2:46 AM
|
Kirk
Joined on 11-08-2007
Posts 12
|
Re: Cannot update TFSWarehouse - missing field value for DateDiscovered
|
|
|
|
|
I think I finally figured out what may have initially caused this problem. I was not using the 'Bug' work item type. We created our own 'Defect'.
I used my defects for awhile and then deleted the Bug work item type. I think that may be the monkey wrench that I threw into the machine.
Do you think that if I imported the Bug work item type back into my system it might start working?
Oh... and I think I compounded my problem. Since the field had been deleted, I tried adding a new field with the same name. Now that field is in the Fields table and I cannot import the Bug work item type to get it back into the system. How can I get rid of my bogus field?
|
|
|
|
|
Report
|
|
|
|
10-07-2008, 9:58 AM
|
Crispin Parker
Joined on 11-13-2007
Posts 664
|
Re: Cannot update TFSWarehouse - missing field value for DateDiscovered
|
|
|
|
|
Hmm, sounds like you've made a bit of a rod for you're own back there. Due to the complex nature of the SfTS template, we cannot support custimised instanaces of the template. As you have seen, the scope of the problems this can cause is just too large. Supporting the standard template on the massive number and variance of environments used is daungting enough.
You're going to have to try and remove the conflicting fields you have created. The below linked MSDN artical gives some intruction on how this is accomplished.
http://msdn.microsoft.com/en-us/library/ms404864(VS.80).aspx
Once the conflicating field is removed, re-install the SfTS template. Then, import the bug definition back into the custimised project.
Please post back and let us know how you get on.
Crispin.
"It is better to light a candle than to curse the darkness"
|
|
|
|
|
Report
|
|
|
|
10-07-2008, 5:07 PM
|
Kirk
Joined on 11-08-2007
Posts 12
|
Re: Cannot update TFSWarehouse - missing field value for DateDiscovered
|
|
|
|
|
Made a rod for my own back. I'll have to remember that one. :)
I think I will set up a whole new server and start fresh. I'll have to figure out how to move my existing work items to the new server. I will probably wait until the end of the month and use the latest Rosario CTP.
Thanks for your help!
|
|
|
|
|
Report
|
|
|
|
10-07-2008, 5:31 PM
|
Crispin Parker
Joined on 11-13-2007
Posts 664
|
Re: Cannot update TFSWarehouse - missing field value for DateDiscovered
|
|
|
|
|
Ekk! The SfTS v2 template is aimed at TFS 2008, so Rosario might not work. Also, I think the Rosario CTP expires soon...
CP
"It is better to light a candle than to curse the darkness"
|
|
|
|
|
Report
|
|
|
|
10-07-2008, 5:42 PM
|
Kirk
Joined on 11-08-2007
Posts 12
|
Re: Cannot update TFSWarehouse - missing field value for DateDiscovered
|
|
|
|
|
We have a small (student) group that has been using the Rosario CTP for awhile with the Scrum templates. Seems to work fine. It's great for the student projects since it is just for the semester.
They are coming out with a new CTP at the end of the month. I'll be at the PDC, so I'll talk with the Rosario team before I proceed.
If there are any issues, I'll start over with TFS 2008. Easy to do since I'll be using a virtual server.
|
|
|
|
|
Report
|
|
|
|
10-07-2008, 6:04 PM
|
Crispin Parker
Joined on 11-13-2007
Posts 664
|
Re: Cannot update TFSWarehouse - missing field value for DateDiscovered
|
|
|
|
|
Well that's really good news. Testing the SfTS template against Rosario is on my backlog and I wasn't looking forward to it!
Glad to hear it might not be the pain I was expecting.
"It is better to light a candle than to curse the darkness"
|
|
|
|
|
Report
|
|
|
|
|
Scrum for Team ... » Version 2.x - T... » Scrum for Team ... » Re: Cannot update TFSWarehouse - missing field value for DateDiscovered
|
|
|
|