I read everything about the upgrade process from TFS 2008 to 2012.
but my situation is a bit diffrent. I need to move data from tfs 2008 (sqlserver 2003) to tfs 2012 (sqlserver 2008 R2) without damaging the TFS 2012 data.
what is the best practice?
Adding some issues:
I am trying to be as cautious as possible without damaging any of the data.
So I have:
1. old server TFS 2008 with sqlserver 2005 which is being used
2 demo server with TFS 2012 and sqlserver 2008 R2 with some collections and projects on it (this is a replica of a server we have and is being used as well).
The main purpose is to transfer all data to the 2012 server and kill the old machine.
what i did was to take a backup from the sqlserver 2005 and restore all the tfs* db's to the demo server .
TfsActivityLogging
TfsBuild
TfsIntegration
TfsVersionControl
TfsWarehouse
TfsWorkItemTracking
TfsWorkItemTrackingAttachments
Afterward I run "tfsconfig import" on the demo server.
TfsConfig Import /SQLInstance:SQLSERVERNAME /CollectionName:DemoImportCollection /confirmed
which fails:
Creating temporary structures... (169 of 502)
[Info #15:45:36.159] [2014-01-14 15:45:33Z][Error] TF400744: An error occurred while executing the following script: UpgradeTestResults_OrcasToDev10Beta1.sql. Failed batch starts on the line 613. Statement line: 23. Script line: 635. Error: 2627 Violation of PRIMARY KEY constraint 'PK__tmp_tbl___1786A43E234A136B'. Cannot insert duplicate key in object 'dbo.tmp_tbl_OrcasTestOutcomeLookUp'. The duplicate key value is (?«ƒ??????????????¢???????????ƒ). (169 of 502)
[Info #15:45:36.159] [2014-01-14 15:45:34Z][Informational] Microsoft.TeamFoundation.Framework.Server.CollectionServicingException: TF400744: An error occurred while executing the following script: UpgradeTestResults_OrcasToDev10Beta1.sql. Failed batch starts on the line 613. Statement line: 23. Script line: 635. Error: 2627 Violation of PRIMARY KEY constraint 'PK__tmp_tbl___1786A43E234A136B'. Cannot insert duplicate key in object 'dbo.tmp_tbl_OrcasTestOutcomeLookUp'. The duplicate key value is (?«ƒ??????????????¢???????????ƒ).
at Microsoft.TeamFoundation.Framework.Server.SqlScriptResourceComponent.ExecuteScripts(List`1 scripts, SqlParameter[] sqlParameters, List`1 serviceVersions, Boolean acquireLock)
at Microsoft.TeamFoundation.Server.Servicing.TFCollection.FrameworkStepPerformer.ExecuteSql(String stepData, ServicingContext servicingContext)
at Microsoft.TeamFoundation.Framework.Server.TeamFoundationStepPerformerBase.Microsoft.TeamFoundation.Framework.Server.IStepPerformer.PerformStep(String servicingOperation, String stepType, String stepData, ServicingContext servicingContext)
at Microsoft.TeamFoundation.Framework.Server.ServicingStepDriver.PerformServicingStep(ServicingStep step, ServicingContext servicingContext, ServicingStepGroup group, ServicingOperation servicingOperation) (169 of 502)
[Warning#15:45:36.596] TF255185: Encountered a warning during operation. Message=[2014-01-14 15:45:34Z] Servicing step Upgrade Test Results failed. (ServicingOperation: UpgradePreTfs2010Databases; Step group: Upgrade.TfsTestManagement).
[Info #15:45:36.627] [2014-01-14 15:45:34Z] Servicing step Upgrade Test Results failed. (ServicingOperation: UpgradePreTfs2010Databases; Step group: Upgrade.TfsTestManagement) (169 of 502)
[Info #15:45:36.627] [2014-01-14 15:45:34Z][Informational] Removing item. Key: TargetRequestContext. (169 of 502)
[Info #15:45:36.627] [2014-01-14 15:45:34Z][Informational] Clearing dictionary, removing all items. (169 of 502)
[Warning#15:45:36.659] TF255185: Encountered a warning during operation. Message=TF255271: The team project collection could not be created. The number of steps before the completion of project creation is: 502. The number of steps completed before the failure was 169..
[Warning#15:45:37.690] Warning Message: [2014-01-14 15:45:34Z] Servicing step Upgrade Test Results failed. (ServicingOperation: UpgradePreTfs2010Databases; Step group: Upgrade.TfsTestManagement)
[Warning#15:45:37.690]
[Warning#15:45:37.737] Warning Message: TF255271: The team project collection could not be created. The number of steps before the completion of project creation is: 502. The number of steps completed before the failure was 169.
[Warning#15:45:37.737]
I have a suspicion that this problem occur due to Hebrew characters in database which translate on the temp import tables as question marks ("?????")
Appreciate any help or direction solving this issue.
Regards
Erez
You can use TFS integration platform for that. It will migrate all the files and history. If you have TFS work items you can migrate those as well(if you use the same Project template on the 2012 server as well)
Two minor points you need to know:
1) After the migration, history will have the Datetime of when you migrate but you can see the actual Datetime in the comments.
2) It will also add an extra text to your comments saying you migrated using the integration platform.
http://tfsintegration.codeplex.com
After trying everything (without touching the real Data) I succeeded.
I decided to split the upgrade process to two 2008-2010 and 2010-2012.
I copied the 2008 TFS db's to the neNew SQLSERVER which is being
used by the TFS 2012
I added another VM with TFS 2010
I run from TFS 2010 the upgrade wizard which identify the 2008 copied db's
The result was a new collection attached to TFS 2010
I detached the collection On the TFS 2012
I run attach collection (the TFS 2010 one) and this upgraded the collection.
The process worked smothly.
Thanks all for the Help
Erez.h
Related
Using a few months old database copy of our production instrance running on TFS 2018.3 i tried to upgrade it to 2019.1.
During the upgrade of the collections, one of the collections failed on step 729.
Before i go back on load a fresh database, i would like to understand the error message and make sure we prevent it in the future.
Has anyone seen this error before and know how to fix it in my upgrade ? as well as make sure this does not happen for a future upgrade ?
[15:02:03.047] +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[15:02:03.047] ++ Executing - Operation: DistributedTaskOrchestrationToDev17M141Collection, Group: DistributedTaskOrchestrationToDev17M141Collection
[15:02:03.047] +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[15:02:03.047] Executing step: Start Queued Plans in PlanQueue
[15:02:03.047] Executing step: 'Start Queued Plans in PlanQueue' DistributedTaskOrchestration.StartThrottledPlans (729 of 858)
[15:02:03.313] [Error] VS402939: Release with ID 625 does not exist. Specify a valid ID and try again.
[15:02:03.327] Microsoft.VisualStudio.Services.ReleaseManagement.WebApi.Exceptions.ReleaseNotFoundException: VS402939: Release with ID 625 does not exist. Specify a valid ID and try again.
According to the error info
Executing step: 'Start Queued Plans in PlanQueue'
......
Microsoft.VisualStudio.Services.ReleaseManagement.WebApi.Exceptions.ReleaseNotFoundException:
VS402939: Release with ID xxx does not exist. Specify a valid ID and try again.......
It may caused by a release stuck processing in the pipeline queues.
There are few scenarios:
Requests are busy in the pipeline queue a Pipelines.They do not have
a 1:1 relationship with the agents. Looks like there are more
releases with environments in progress than the available licenses.
Clearing out requests that are in the queue: To clear out invalid
requests, the most recommended way is to cancel any in progress
deployments. Refer to
https://www.visualstudio.com/en-us/docs/build/actions/view-manage-releases#release-summary
Simply refresh the release using the refresh button and try again
which may also do the trick
Before you do the fresh database upgrade, kindly check if there are some releases hang in the queue for your collections. Check Pipelines--Agent Pools--Running Jobs. This may avoid the same issue which does not happen for a future upgrade.
We reported this same issue on the Microsoft Developer Community.
https://developercommunity.visualstudio.com/content/problem/720729/upgrade-to-tfs-20191-failed-with-error-vs402939.html
In our scenario, we created a production copy around May 2019 using TFS 2018.3, left it running until now and tried to upgrade this production copy into a TFS 2019.1. This failed.
It seems this issue was caused by our "outdated" production copy we left running which we later tried to upgrade to TFS 2019.
The upgrade failed because Releases have been in the queue for longer than 30 days, which caused parts to be deleted by the retention policy.
For production environment, its advisable to cancel any stuck
deployments before upgrade.
I will keep this in mind, but it would be good for Microsoft to make sure the upgrade process does not fail in case there is a stuck deployment somewhere.
I am getting the following failure when migrating from TFS to VSO (just src history, not work items).
com.opshub.eai.tfs.exception.OIMTFSApiExcpetion: OH-TFS-Connector-0030: Error occurred in executing operation getFileInformation. Server Error : Unable to read data from the transport connection: The connection was closed.
Any ideas what could cause this? I tried doing the migration from scratch and I got the same error at a similar but not identical changeset.
I'm trying to migrate from a TFS 2010 to VSO. Got 6 out 7 projects migrated. the last one, and the biggest of all, gives me this error message during the version control migration -> OH-SCM-009: Error occurred while sync. There is no working folder mapping for $/. The folder in question has been created in VSO and all the users have been mapped. When looking at the log file, I do get a java exception messages "There is no working folder mapping for $/". I'm running V1.3.1.000. Please help?
Thank you
I'm running sqlpackage.exe as park of an automated deployment script creation process, however we have synonyms in the database, which are different depending on the environment (Dev/Test/Live). The problem is that the database project has the synonyms as they are in the Dev environment, but when I run sqlpackage to compare against Test or Live, the synonyms are different and so they get scripted to be dropped and re-added to point to Dev.
I've seen on http://blogs.msdn.com/b/ssdt/archive/2015/02/23/new-advanced-publish-options-to-specify-object-types-to-exclude-or-not-drop.aspx that apparently there's a new parameter "ExcludeObjectType", but when I try running it using that parameter it gives me an error 'ExcludeObjectType' is not a valid argument for the 'Script' action (and I have the latest version of sqlpackage.exe).
Any ideas on what I can do here?
After downloading the latest SSDT for Visual Studio I still had the same issue. Next I downloaded Data-Tier Application Framework (May 2015) and used the new SqlPackage installed at C:\Program Files\Microsoft SQL Server\120\DAC\bin\sqlpackage.exe and the error went away and worked as expected.
Thank you sir! When I created the deployment script in VS, no change detected but when I tried to deploy using sqlpackage I got the error:
* The object [x] already exists in database with a different definition and will not be altered.
After adding the ExcludeObjectTypes switch I got the following error:
* 'ExcludeObjectTypes' is not a valid argument for the 'Publish' action.
But after downloading and installing latest Data-Tier App framework all works as expected with no errors.
I'm trying to move a TFS Server (see here and here), but everything is not working well. When I get to the Change Ownership step, the following command fails:
TFSConfig Accounts /ResetOwner /SQLInstance:<ServerName> /DatabaseName:<DatabaseName>
The error on the Tfs_Configuration table:
TF30065: An unhandled exception occurred.
The error on the Tfs_DefaultConfiguration table:
TF30040: The database is not correctly configured. Contact your Team Foundation Server administrator.
I skipped the marked transactions, because I could not get it working.
You must remap your TFS database before config your accounts.
Please see following links
RemapDB Command
Account Command