Upgrading TFS 2010 and hit error TF246062: Two or more databases are in conflict


If you are using TFS2010 Beta2 or RC and used different formats to identify your SQL Database instances ie (localhost, ., servername, servername.company.com, IP address) when creating your project collection databases, you may hit one of the following errors during the readiness checks of the TFS 2010 RTM Upgrade Wizard. 


TF246062: Two or more databases are in conflict because they are each designated as the owners of the following schema: Framework. The schema is for the host with the following name and ID: CollectionName, 4bace481-2439-49c8-b017-77ee3da4ce29. The databases with this conflict are: Data Source=SQLInstance1;Initial Catalog=Tfs_CollectionName;Integrated Security=True, Data Source=SQLInstance2;Initial Catalog=Tfs_CollectionName;Integrated Security=True. You must specify one and only one database owner for the schema in the searchable SQL Server instances for this deployment of Team Foundation Server.


TF246064: No database could be found for the following host: MyCollection. The host has the following ID: 4bace481-2439-49c8-b017-77ee3da4ce29. To fix this problem, use the TFSConfig RemapDBs command-line tool and make sure that you specify the SQL Server instance that contains this database.. 


Some examples scenarios that would cause this issue:


1. You used the FQDN of your SQL instance when installing Beta2, but in the RTM upgrade wizard you used the simple machine name.  In this case another easy workaround is to use the FQDN again in the upgrade wizard.


2. You used the machine name of the local machine when installing Beta2, and later created a new team project collection using the SQL identifier "localhost"


The workaround to both errors is to run 'RemapDbs' to use a consistent naming convention for your SQL databases.


C:\program files\Microsoft Team Foundation Server 2010\tools\tfsconfig remapdbs /sqlinstances:MyServer,MyOtherServer /databaseName:MyServer;Tfs_Configuration /AnalysisInstance:AnalysisServerName


 


Comments (0)

Skip to main content