I can describe my feeling of mgration from TFS 2005 to TFS 2008 in one word-NIGHTMARE.
Summary of recommendations.
4. Install SP2 for the SQL Server.
5.In case of errors review C:\Documents and Settings\MyUSER\Local Settings\VSMsiLog####.txt . It is usually quite detailed.
Problems in a sequence.
I've read a few links with tips about conversion and thought that I am ready:
I've done all preliminary work as it was recommended.
When I've started installation, I've got TF220066 error.
I've install it and also uninstall TFS 2005(not mandatory, but recommended step).
And TF220066 error has been replaced with new one- TF220064
In the database TfsIntegration..tbl_service_interface replace 3 ReportsService with Netbios name
The next error I noticed in the log C:\Documents and Settings\MyUSER\Local Settings\dd_install_vstf_at_90.txt.
[09/23/08,00:07:22] TFSUI: getcurrenttfsproperties.exe: === WARNING: Unable to retrieve service account from the database. Failed to find TfsServiceAccount in database TfsIntegration table tbl_registration_extended_attributes
[09/23/08,00:07:22] TFSUI: getcurrenttfsproperties.exe: === WARNING: Unable to determine TfsServiceAccount.
In the TfsIntegration.tbl_registration_extended_attributes table I manually added fk_registration_entry_id=1, name=TfsServiceAccount value= TfsService
Next error:
[09/23/08,00:17:55] vs70uimgr: DisplayMessage_START:Setup has detected that the specified database server
is already in use by another Team Foundation Server (services) computer. Click OK to configure this computer as a stand-by Team Foundation Server (services) computer. Click Cancel to specify a different database server.
In the same TfsIntegration.tbl_registration_extended_attributes I replaced for ATMachineName FQDN to NetBios name
The next error message:
Error 32000.The Commandline '"d:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\TfsDb.exe" upgrade /server:"MyServer" /property:"TFS_SERVICE_ACCOUNT=MyDomain\TFSSERVICE;TFS_REPORTING_ACCOUNT=MyDomain\TFSREPORTS;LCID=1033;
VSTF_AS_INSTANCE=MyServer;VSTF_AS_DATABASE=
TFSWarehouse;VSTF_AS_ACCOUNT=" /showui:394070' returned non-zero value: 100.
But it didn't help for me.
I found from
http://support.microsoft.com/kb/955008 that VSMsiLog####.txt located in C:\Documents and Settings\MyUSER\Local Settings\ (note not in Temp subfolder) folder already has detailed info. If it is not enough, a few articles suggest to run the TFSdb tool from the command line (e.g.
here ), Note that you should it when "Retry Cancel" message still open.
So details of the Error 32000 are the following:
Upgrading the Warehouse Database (TfsWarehouse)
d:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\SetupWarehouse.exe
-upgrade -int TfsIntegration -s WEBJET011 -d TfsWarehouse -c "d:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\Warehouseschema.xml" -a "MyDomain\TFSSERVICE" -ra "MyDomain\TFSREPORTS" -asinst "WEBJET011" -asdbname "TFSWarehouse" -asacct ""
d:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\SetupWarehouse.exe -upgrade -int TfsIntegration -s WEBJET011 -d TfsWarehouse -c "d:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\Warehouseschema.xml" -a "MyDomain\TFSSERVICE" -ra "MyDomain\TFSREPORTS" -asinst "WEBJET011" -asdbname "TFSWarehouse" -asacct ""
An unexpected error occurred: XML parsing failed at line 1, column 0: A document must contain exactly one root element.
.
Errors in the metadata manager. An error occurred when instantiating a metadata object from the file, '\\?\D:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\TFSWarehouse.0.db\Outcome.622.dim.xml'.
5
d:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\SetupWarehouse.exe 5 20547
Microsoft.TeamFoundation.DatabaseInstaller.DatabaseException: d:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\SetupWarehouse.exe 5 20547
at Microsoft.TeamFoundation.DatabaseInstaller.ProcessDeployer.ExecuteCommand(String filePath, String arguments, Boolean continueOnError)
Microsoft.TeamFoundation.DatabaseInstaller.DatabaseException: d:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\SetupWarehouse.exe 5 20547
at Microsoft.TeamFoundation.DatabaseInstaller.ProcessDeployer.ExecuteCommand(String filePath, String arguments, Boolean continueOnError)
at Microsoft.TeamFoundation.DatabaseInstaller.Installer.RunDbActions(InstallerMode mode, String server, Boolean preview)
at Microsoft.TeamFoundation.DatabaseInstaller.Installer.RunSteps(InstallerMode mode, String server, IPropertyCollection properties, Boolean preview)
at Microsoft.TeamFoundation.DatabaseInstaller.Installer.Upgrade(String server, IPropertyCollection properties, Boolean preview)
at Microsoft.TeamFoundation.DatabaseInstaller.CommandLine.Commands.CommandUpgrade.OnRun()
at Microsoft.TeamFoundation.DatabaseInstaller.CommandLine.Commands.InstallerCommand.Run()
at Microsoft.TeamFoundation.DatabaseInstaller.CommandLine.CommandLine.RunCommand(String args)
As it suggested in
http://translate.google.com.au/translate?hl=en&sl=fr&u=http://batswirl.com/blogs/batswirl_fr/archive/2008/04/29/erreur-32000-lors-de-la-migration-de-tfs-2008.aspx&sa=X&oi=translate&resnum=7&ct=result&prev=/search%3Fq%3DTFSWarehouse%2BXML%2BTfsDb%26hl%3Den%26sa%3DG
I've just deleted the problematic xml file.
The next issue:Upgrade hang after "Starting execution of steps from step06_MigrateOpenedWorkItems.sql.resources",
But Customer Support was not aware about the number.
The install failed after 6 hours and growing TEMPDB to more than 50GB with "Disk Full" message.
I installed VS 2008 with SP1 prior to the running combined TFS 2008+SP1 setup
The setup failed with Error 29250.Team Build Upgrade failed to complete successfully.
I was able to hack the errors by manually adding missing columns tbl_Build.DropLocationRoot and REASON and tbl_Schedule.LastEvaluatedOn
After this the TFS 2008 setup has been completed successfully.
USE TFSBuild
GO
Alter table tbl_Build
drop COLUMN DropLocationRoot --nvarchar(260) NULL
GO
Alter table tbl_Build
drop COLUMN REASON --int NULL
GO
Alter table tbl_Schedule
drop CONSTRAINT DF__tbl_Sched__LastE__5A1A5A11
GO
Alter table tbl_Schedule
drop COLUMN LastEvaluatedOn --[datetime] NULL Default(GetDate())
GO
and 've run Setup.exe to repair the TFS installation. It fixed the database, but when a build was run, it coused the error.
Detailed Message: TF50309: The following account does not have sufficient permissions to complete the operation: NT AUTHORITY\NETWORK SERVICE. Check the permissions for the account and grant the appropriate permissions to perform this operation.
| TF215085: An error occurred while connecting to agent \TfsServer\TfsServer011: TF209009: The account NT AUTHORITY\NETWORK SERVICE is not authorized to communicate with Team Foundation Server TfsServer011. Verify that the account is a member of the Build Services security group for the appropriate team project on the Team Foundation Server and that the account's password has not expired. |
I've found that after repair Visual Studio Team Foundation Build Windows Service(TFSBuildService.exe) was running under NT AUTHORITY\NETWORK SERVICE.I've changed it to TfsServer\TFSBuild (TFSService account didn't have Remoting permissions, and wasn't able to create drop folders)
To restore fully-qualified domain names (FQDN, e.g., tfsserver.mycompany.com) for TFS
But command "tfsadminutil activateat <FullyQualifiedDomainName>" changed all references and Team client on my TFS server didn't see connection using Netbios name(e.g. http://tfsserver).
and for (FQDN, e.g., tfsserver.mycompany.com) it wasn't able to authenticate user (Logon failure for NTLM).
So I had manually in TfsIntegration.tbl_registration_extended_attributes replace for ATMachineName back to FQDN
Install removed SSL settings on the TFS virtual directory, and I had to restore reference to certificates.
Actually I tried to use http: instead of https, but for remote machines outside TFS domain I wasn't able to pass domain credentials(the same login failure).
But after this I am not able to open Project Portals(access is denied for the user).
- /SharepointURI:http://wssserver:80
- /SharepointSitesUri:http://<wssserver:80/sites
- /SharepointAdminUri:http://wssserver:adminport
- /SharepointUnc:\\wssserver\sites
and do not forget to Migrate content or sites after upgrade (Windows SharePoint Services).