While installing Team Foundation Server 2010 Beta 1, I ran in some troubles with WSS 3.0. After the default configuration wizard finished, I got some warnings that the initial team project collection wasn’t created. The whole sharepoint installation, which should be done by the TFS configuration wizard, failed somehow and I ended up uninstalling and reinstalling TFS.
The problem was that i didn’t RTFM: http://download.microsoft.com/download/7/A/0/7A023209-096F-4F7D-B2BC-831ECC68FF5B/VS2010Beta1Readme.htm
1.3.4 Initial Configuration of Team Foundation Server Should be Run From MSI Program or by Command Line
Initial Team Foundation Server configuration fails on Windows SharePoint configuration if you access the Team Foundation Configuration Tool by clicking the link in the Team Foundation Administration Console instead of by launching Team Foundation Configuration Tool at the end of the installation phase.To resolve this issue:
If you want to setup Windows SharePoint Server during Team Foundation Server configuration, you must launch the Team Foundation Server Configuration Tool by using one of the two following methods:
· Launch the Team Foundation Configuration Tool by selecting the check box at the end of the Team Foundation Server installation
· If you exited Team Foundation Server MSI program (setup.exe) without launching Team Foundation Configuration Tool, do not start the Administration Console from the Start menu item shortcut. Instead use following command line:
%programfiles%Microsoft team foundation server 10.0toolstfsmgmt.exe configure
After Team Foundation Server has installed and configured Windows SharePoint, you can configure Team Foundation Server by using the Start menu to launch Team Foundation Server Administration Console.
Apparently I closed the configuration wizard after it fired up by the installer and restarted it over the TFS admin console.
After deleting all DB’s and reinstalling, it worked for me. Perhaps even rerunning the configuration wizard would have solved the problem.
Saw your tweet about your issue. Glad to see you solved the problem.
It turns out it would not have helped to re-run the configuration wizard because the damage was already done (bad data had been introduced into a SharePoint database).
Your solution of deleting everything and starting over was the right one.
Regards,
Robert.
The safest thing to do for beta 1 is to pre-install SharePoint yourself. The “bad data” that Robert refers to only gets in the database if the TFS configuration wizard installs SharePoint. So, if it is already installed then you should not run into this issue.
Note that this problem should not exist in the next beta 2.