Hi,
 
I think you should open a ticket with Customer Support Services (CSS), deleting 
the build information is not an acceptable solution.
 
 
Wes

________________________________

From: [EMAIL PROTECTED] on behalf of Jonathan Zack
Sent: Fri 07/12/2007 11:04 AM
To: [email protected]
Subject: Re: [OzTFS] Issues upgrading Team Foundation Server 2005 to 2008


Hi,
 
Wesley - Thank you very much for all of your links.
 
I had come across the comments from Buck Hodges but it sounds like the final 
remedy was deleting everything in TfsBuild. Do they mean actually truncating 
the TfsBuild database? Sounds a bit aggressive. What would be the outcome of 
doing that if it got us over the hump? We wouldn't have any build definitions 
available and all of the historical build information would be gone? 
 
Regards,
Jonathan


On Dec 7, 2007 5:47 AM, Wesley MacDonald <[EMAIL PROTECTED]> wrote:


        Buck Hodges actually comments on this exact problem "Error 29250.Team 
Build Upgrade failed to complete successfully" fixed after Beta 2 was released. 
 A work around was posted also. 

         

        http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2245293&SiteID=1 

         

         

         

        From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] <mailto:[EMAIL 
PROTECTED]> ] On Behalf Of Jonathan Zack
        Sent: Thursday, December 06, 2007 12:42 PM
        To: [email protected]
        Subject: [OzTFS] Issues upgrading Team Foundation Server 2005 to 2008

         

        Hi,

         

        I did tons of up-front research and prep before attempting the 
installation including following each recommended step in this post 
<http://ozgrant.com/2007/11/24/tips-for-upgrading-from-tfs2005-to-tfs2008/>  . 
I was pretty optimistic considering that there are very few issues reported so 
far.

         

        I had never installed SQL Server 2005 SP1 on my single-box TFS machine 
so I installed it. Everything passed in the System Health Check afterwards.

         

        The installation process was fairly smooth and quick until the progress 
bar made it to just a little bit left and then it appears to just sit for over 
an hour. It basically looks like it sits until it depleted all of the room left 
on the C:\ drive of the server (which had 7 GB available at the beginning of 
the installation). 

         

        After rerunning the installation a few times, I figured out that 
something was indeed going on behind the scenes and that the tempdb log was 
growing and growing (when the install finally failed, the tempdb log was 5 GB 
in size). The message box from the installation simply states, "Error 
29250.Team Build Upgrade failed to complete successfully".

         

        I opened up the logs and the last couple of lines have this:

                Starting execution of steps from 
prereq01_PrepareUpgrade.sql.resources 

                Finished execution of steps from 
prereq01_PrepareUpgrade.sql.resources

                Starting execution of steps from 
step01_MigrateBuilds.sql.resources

                Finished execution of steps from 
step01_MigrateBuilds.sql.resources

                Starting execution of steps from 
step02_MigrateBuildQualities.sql.resources

                Finished execution of steps from 
step02_MigrateBuildQualities.sql.resources

                Starting execution of steps from 
step03_MigrateBuildSteps.sql.resources

                Finished execution of steps from 
step03_MigrateBuildSteps.sql.resources

                Starting execution of steps from 
step04_MigrateAssociatedChangesets.sql.resources

                Finished execution of steps from 
step04_MigrateAssociatedChangesets.sql.resources

                Starting execution of steps from 
step05_MigrateAssociatedWorkItems.sql.resources

                Finished execution of steps from 
step05_MigrateAssociatedWorkItems.sql.resources

                Starting execution of steps from 
step06_MigrateOpenedWorkItems.sql.resources

        I then cleaned up the C:\ drive to have 13 GB of disk space available 
and reran the installation. It still took a long while and depleted all of the 
space on the C:\ drive but made it one step further to "step07" (I don't have 
the text in front of me but I believe it mentions migrating Projects or 
something). 

         

        So I am now on my 7th run of the installation. This time, I have setup 
SQL Server to create the tempdb files on a separate drive which has 26 GB 
available. It has been running for a while and has depleted 7 GB of disk space. 

         

        All of this seems a bit crazy. Why would the logs be growing like this?

         

        One important thing to note is that I never installed TFS 2005 SP1 on 
this machine but I don't know why this would make a difference (it wasn't 
flagged in the System Health Check either).

         

        Any help would be greatly appreciated.

         

        Regards,

        JZ

        OzTFS.com - to unsubscribe from this list, send a message back to the 
list with 'unsubscribe' as the subject. View the web archives at 
http://www.mail-archive.com/[email protected]/
        Powered by mailenable.com <http://mailenable.com/> , supported by 
www.readify.net <http://www.readify.net/>  

        OzTFS.com - to unsubscribe from this list, send a message back to the 
list with 'unsubscribe' as the subject. View the web archives at 
http://www.mail-archive.com/[email protected]/
        Powered by mailenable.com <http://mailenable.com/> , supported by 
www.readify.net <http://www.readify.net/>  


OzTFS.com - to unsubscribe from this list, send a message back to the list with 
'unsubscribe' as the subject. View the web archives at 
http://www.mail-archive.com/[email protected]/
Powered by mailenable.com, supported by www.readify.net 



OzTFS.com - to unsubscribe from this list, send a message back to the list with 
'unsubscribe' as the subject. View the web archives at 
http://www.mail-archive.com/[email protected]/

Powered by mailenable.com, supported by www.readify.net

<<winmail.dat>>

Reply via email to