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
Related
I have to update our build-system from the old "XML-System" to the newer vNext.
Now I have the problem, that in a build progress, I'm getting errormessages from ligther.exe:
[error]light.exe(0,0): Error LGHT0217: Error executing ICE action 'ICE01'. ...
up to ICE07.
And at the end:
[error]light.exe(0,0): Error LGHT0216: An unexpected Win32 exception with error code 0x643 occurred: Action - 'ICE09' Fatal error during installation
When I make the same build with the "old" XML-Version it works without any problems, any ideas?
Thanks a lot.
Kriz
According to the error prompting message: An unexpected Win32 exception with error code 0x643 occurred: Action - 'ICE09' Fatal error during installation
It's probably a permissions problem with validation. You could try to give the build service account more privileges such as local administrator permission on the build agent.
Besides, there are no tools to convert XAML build definition to vNext directly, so please double check you have manually created fully in a accord.
I saw this issue only on the build machine, where the build task has no admin rights.
I didn't saw this on my developer machine, where I have admin rights. This error is written by the light.exe, which is the Windows Installer XML linker contained in the Wix Toolset.
In order to solve this I suppressed validation of the light.exe. This can be done in two different ways:
On the commandline of light.exe
-sval
On the commandline, when using WixSharp
Compiler.LightOptions = "-sval";
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 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
While I was upgrading from TFS2008 to TFS2012 I received an error stating:
Upgrade Failure: "The installation and configuration of Team
Foundation Server succeeded, however upgrading the data was
unsuccessful"
I then found that you can not rerun the upgrade wizard. How can you rerun the update?
First and foremost BACK UP YOUR DATABASES! REALLY!
At this point I turned to the tfsconfig import command. (http://msdn.microsoft.com/en-us/library/vstudio/ff407080.aspx)
I specifically ran:
TFSConfig Import /SQLInstance:TFS01 (my server name)
/CollectionName:(Anything you want) /confirmed
But I then got this error message:
Errors:1 Error Message: TF255235: Database TfsVersionControl on TFS01
does not exist but the current operation requires an existing
database.
So not only did the original upgrade not work, it also killed one of my DBs. That's fine because I have a backup. So open up SSMS and kill whatever database is pointing to the "TfsVersionControl.mdf" file. Then kill the actual mdf and ldf files.
Next, restore TfsVersionControl again from the database. At this point, we are reset back to pre-upgrade...
Now for the work around. It is an easy but ugly one. In SSMS make the user that is running TFS (in my case tfsService a sysadmin). That's it.
Go back into the command window and rerun the import. About 20 minutes later viola it worked perfectly.
Make sure that you remove the sysadmin permission from the user after everything is working perfectly.
I hope this helps someone.