TFS 2005 to TFS 2008 Product Upgrade Fails with an Error 32000. The Commandline “C:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\TfsDB.exe” upgrade ...

Source: Microsoft Support

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

During the Upgrade of the TFS 2005 to TFS 2008 product you might get an error similar to the following:

 

Error 32000. The Commandline ‘“C:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\TfsDB.exe” upgrade /server: . . .

In this case, as a matter of trouble shooting, we copied the entire commandline including all the parameters from the MSI Verbose log in the user temp folder into a DOS Prompt Window.  To navigate to the folder Click Start, then Run, and type %temp%, and Click Okay button.  In some cases the log will be located in the parent of the resulting folder.  The file should be identifiable by its date stamp coinciding  with the installation start time.  The name should be similar to VSMsiLog####.txt.

 

The command line from the MSI Verbose log can be run multiple times.

 

In this case the result in the command line was the following:

 

>> 

H:\>"D:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\

TfsDb.exe" upgrade /server:"ntpvmsqldev1" /property:"TFS_SERVICE_ACCOUNT=XLCSTLW

F\tfsservice;TFS_REPORTING_ACCOUNT=XLCSTLWF\tfsreports;LCID=1033;VSTF_AS_INSTANC

E=ntpvmsqldev1;VSTF_AS_DATABASE=TfsWarehouse;VSTF_AS_ACCOUNT=" /showui:131420'

TfsDb - Team Foundation Server Database Utility

Copyright (c) Microsoft Corporation.  All rights reserved.

 

[01:49:13.950] [TFS_SERVICE_ACCOUNT]='XLCSTLWF\tfsservice'

. . .

Processed Workspace:2689

Microsoft.TeamFoundation.DatabaseInstaller.DatabaseException:

                                    Line 2275

                                    Error: Invalid column name 'SchemaVersion'.

Invalid column name 'SchemaVersion'. ---> System.Data.SqlClient.SqlException: In

valid column name 'SchemaVersion'.

Invalid column name 'SchemaVersion'.

   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolea

n breakConnection)

   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception

, Boolean breakConnection)

   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObj

ect stateObj)

   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cm

dHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, Tds

ParserStateObject stateObj)

   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName,

Boolean async)

   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult res

ult, String methodName, Boolean sendToPipe)

   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()

   at Microsoft.TeamFoundation.DatabaseInstaller.DataDeployer.ExecuteSql(SqlConn

ection sqlConnection, String batch)

   at Microsoft.TeamFoundation.DatabaseInstaller.DataDeployer.DeployScript(Strin

g script)

   --- End of inner exception stack trace ---

   at Microsoft.TeamFoundation.DatabaseInstaller.DataDeployer.DeployScript(Strin

g script)

   at Microsoft.TeamFoundation.DatabaseInstaller.Installer.RunDbActions(Installe

rMode mode, String server, Boolean preview)

   at Microsoft.TeamFoundation.DatabaseInstaller.Installer.RunSteps(InstallerMod

e 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.CommandUpg

rade.OnRun()

   at Microsoft.TeamFoundation.DatabaseInstaller.CommandLine.Commands.InstallerC

ommand.Run()

   at Microsoft.TeamFoundation.DatabaseInstaller.CommandLine.CommandLine.RunComm

and(String[] args)

> Inner Exception:

SQL Error #1

SQL Message: Invalid column name 'SchemaVersion'.

SQL LineNumber: 13

SQL Source: .Net SqlClient Data Provider

SQL Procedure: trg_Sp1Uninstall

SQL Error #2

SQL Message: Invalid column name 'SchemaVersion'.

SQL LineNumber: 0

SQL Source: .Net SqlClient Data Provider

SQL Procedure: trg_Sp1Uninstall

 

System.Data.SqlClient.SqlException: Invalid column name 'SchemaVersion'.

Invalid column name 'SchemaVersion'.

   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolea

n breakConnection)

   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception

, Boolean breakConnection)

   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObj

ect stateObj)

   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cm

dHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, Tds

ParserStateObject stateObj)

   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName,

Boolean async)

   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult res

ult, String methodName, Boolean sendToPipe)

   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()

   at Microsoft.TeamFoundation.DatabaseInstaller.DataDeployer.ExecuteSql(SqlConn

ection sqlConnection, String batch)

   at Microsoft.TeamFoundation.DatabaseInstaller.DataDeployer.DeployScript(Strin

g script)

Exception Data:

Key: HelpLink.ProdName, Value: Microsoft SQL Server

Key: HelpLink.ProdVer, Value: 09.00.3054

Key: HelpLink.EvtSrc, Value: MSSQLServer

Key: HelpLink.EvtID, Value: 207

Key: HelpLink.BaseHelpUrl, Value: http://go.microsoft.com/fwlink (http://go.microsoft.com/fwlink)

Key: HelpLink.LinkId, Value: 20476

 

 

                                    Line 2275

                                    Error: Invalid column name 'SchemaVersion'.

Invalid column name 'SchemaVersion'.

<< 

 

The table trigger trg_Sp1Uninstall which should have been dropped earlier still remained.  This resulted in the Alter Table command in the upgrade process failing.  (This trigger was from SP1 for TFS 2005.)

To resolve this problem the Trigger can be dropped in the TFSVERSIONCONTROL database by the following SQL script.  The script can be run from the Microsoft SQL Server Management Studio.  This Trigger should not be present and was originally used in the SP1 for TFS 2005.

 

>> 

 USE TFSVERSIONCONTROL

 GO

 DROP TRIGGER trg_Sp1Uninstall ON DATABASE

<< 

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.