Everything you want to know about Visual Studio ALM and Farming
Brian Harry is a Microsoft Technical Fellow working as the Product Unit Manager for Team Foundation Server. Learn more about Brian.
More videos »
I'll let this post be a running list of issues that I hear about as people try installing SP1. So far I've heard mostly good things about the installation process but a few problems as well. Here's a few things to know:
1) If you get a Windows Update prompt to reboot during SP1 installation, ignore it (don't reboot). Wait until after the SP1 installation completes and then reboot.
2) If you have a prerelease of the Team System for Database Development GDR (that supports SQL 2008) installed, you will need to uninstall and 2reinstall it after upgrading to SP1.
3) Apparently you can't create the admin mode/slipstream TFS installer when running on a Vista 64-bit OS. I suspect it won't work on any 64-bit OS but the customer report I saw said it was 64-bit Vista but it worked on 32-bit Vista. Of course TFS itself can only be installed on Windows 2003 or Windows 2008 and the application tier still only supports 32 bit. Yes, I know, I know. We've gotten tons of feedback about how bad it is not supporting 64-bit. That's coming in our Rosario release.
4) We've had numerous reports of checkin notification failures when users user tfsadminutil configureconnections to configure a Team System Web Access Url. We have confirmed that this is a bug and and working on a patch now. Watch for it on Code Gallery here: http://code.msdn.microsoft.com/Project/ProjectDirectory.aspx?TagName=Hotfix%2ctfs.
Good luck and let me know what you learn so we can share it with others,
Brian
PingBack from http://blog.a-foton.ru/2008/08/more-things-to-know-about-installing-sp1/
Is there a list of fixes included in the service pack available at all?
@J: http://support.microsoft.com/kb/945140
In relation to ignoring the reboot prompt, which SP1 does that apply to? TFS or VS2008?
That looks like a good list for VS & .NET. I will produce a list for TFS in the next couple of days.
The reboot issues applies to .NET 3.5 SP1 and any other SP that includes it. That means VS, but not TFS.
How long (roughly as you like), I've been running my install for nearly 4 hours, (The only indication I have it's actually running is through ProcMon)
The install for Visual Studio Team System 2008 Development Edition SP1 took approximately 2 hours on my machine. Nothing fancy, Vista Enterprise, 2GB RAM, 3.2 GHZ Pentium D.
Much longer than I though it would when I began, however, I did not have any issues. I did notice a prompt to reboot from Windows Update, but I ignored it until the install was complete.
That's a little longer than what I have heard is "typical" - not sure why. However, the install is not fast no matter how you slice it. Over an hour is pretty normal.
I had an issue installing TFS SP1. Kept getting a unique key failure when trying to create an index on the dbo.Constants table in one of the database tables. There were somehow 4-5 entries with the same username and RemovedDate (or DateRemoved, I am at home now and don't remember the exact name) which caused the setup to have a fatal error and left TFS in an unusable state until I figured out what was going on by looking at the msi log file. To resolve the issue, I simply changed the minute value of each duplicate entry to make them unique and then re-ran the installation. Not sure if this is a known bug or what but you may want to look into it.
Thanks for the info. I'll ask someone to look into it.
Will there be a seperate installation for the Team Explorer. We have a team where there is a need for installing the Team Explorer to get access to work items, sources, etc. but member do not work with Visual Studio for coding etc. Installing a 800mb sp1 where the original installation is 387mb seems overkill.
Other thing: when installing I only had 600mb free space. Installation could only start when I had 2.3gb available. After freeing up until 2.3gb I ended up with having 1.7gb free after installation. Is the 2.3gb really needed?
No, there won't be a separate Team Explorer patch. You must use the VS patch. However, if you only have the Team Explorer installed, it will only update the Team Explorer components.
I believe the need for all of that extra space is for temporary files that it uses during setup.
Brian Harry on VS/VSTS/TFS/.NET 3.5 SP1 is shipping! and More things to know about installing SP1 Etienne...
Brian, our developers would like to upgrade to SP1 right away. Meaning we should probably upgrade our build machines as well so we compile against the same versions as they do.
However, I think we're going to wait a few weeks before we update our TFS 2008 server to SP1 so that we can test the install on our DEV TFS instance first.
Have you heard of any issues with Developer Machines (running VS 2008 SP1) or Build Machines (running VS 2008 SP1, .NET 3.5 SP1, and Team Build SP1) against a TFS 2008 server running RTM?