I am getting an exception when using OpsHub Visual Studio Migration Utility (Trial Version) when trying to Migrate from TFS to VSTS .
I have put in the key that was emailed to me in the second step. This error was received after the validation completion. Here is the StackTrace from OpsHub.log
(com.opshub.JSON.QuartzIntializationServlet) - Unexpected error ocurred during context initialization.
java.lang.NullPointerException
at com.opshub.license.install.LicenseInstaller.installLicense(LicenseInstaller.java:77)
at com.opshub.JSON.QuartzIntializationServlet.registerLicFile(QuartzIntializationServlet.java:369)
at com.opshub.JSON.QuartzIntializationServlet.installLicenses(QuartzIntializationServlet.java:345)
----------Few lines below was the following error------------
(com.opshub.eai.config.service.ConfigServiceImpl) - Trial license is not installed
com.opshub.license.exception.LicenseNotExistException: Trial license is not installed
at com.opshub.license.verify.LicenseVerifier.validateTrialLicense(LicenseVerifier.java:440)
at com.opshub.license.verify.LicenseVerifier.validateIntegrationTerms(LicenseVerifier.java:238)
at com.opshub.license.verify.LicenseVerifier.verify(LicenseVerifier.java:168)
Any help would be appreciated . TIA
I suggest that you can migrate TFS to VSTS through TFS Data Import Service for Visual Studio.
More information, you can refer to this blog: Import your TFS Database into Visual Studio Team Services and the tool and guide can be download from here: Team Foundation Server to Visual Studio Team Services Migration Guide and Database Import Tooling.
As mentioned in the comments , the newer version of OpsHub Visual Studio Migration Utility . Thank you.
Related
We are planning to do version control for our SSIS packages. I want to know how to install TFS and configure it to checkin SSIS packages.
I have read this SSIS TFS configuration. But here I couldn't find anything about installation. it contains only connection information TFS. Should I install from SSIS extensions? Should i install Team explorer? It is showing so many options as shown below.I don't know the right one. Also is installing this requires any license? Please guide me here. Any link with the steps is also fine.
I'm using Visual Studio 2015 and SQL Server 2012.
I want to know how to install TFS and configure it to checkin SSIS packages.
Refer to Install and configure Team Foundation Server and Integration Services (SSIS) and Visual Studio Team Foundation Server for details.
Should I install from SSIS extensions? Should i install Team explorer?
Yes, to design the SSIS packages you need to download and install SSDT (SQL Server Data Tools). It's an official addon for Visual Studio which adds templates for SSIS and SSAS projects. Refer to Download and install SQL Server Data Tools (SSDT) for Visual Studio for details.
And you need to install the Team Explorer to connect to TFS and manage the source control.
is installing this requires any license?
It's based on your VS subscription, you can try community version of Visual Studio, it's free.
Besides, find following blogs for your reference, hope that helps.
SSIS 2012 with Team Foundation Server - Part I
SSIS 2012 with Team Foundation Server - Part II
Installing SSIS, SSRS and SSAS with Visual Studio 2019
I'm trying to import modified WITs to a existing project. But, It was showing the below error:
Microsoft.TeamFoundation.WorkItemTracking.Server.ProvisioningImportEventsCallback
Earlier it was working fine. But, now the issue started.
What could be the possible solution for this? I just wanted to upload WITs through Command prompt(witadmin.exe) only. Any hints/information would help
From your description, you are trying to use VS 2015 to connect to TFS 2017. Please check documentation Import, export, and manage work item types:
If you are connecting to TFS, you must use the same version of Visual
Studio or Team Explorer as TFS. For example, if you connect to a TFS
2017 instance, you must connect from Visual Studio 2017 or Team
Explorer 2017.
TFS 2018 and TFS 2017
Visual Studio 2017 or Team Explorer 2017 client:
%programfiles(x86)%\Microsoft Visual Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer
or, TeamExplorer, Professional or Enterprise in place of
Community, depending on the version you've installed.
You should install VS 2017 or Team Explorer 2017 to run this command. Although VS 2015 could run witadmin command against TFS 2017 sometimes, there would have unexpected issue.
However, I found the solution for this issue by myself.
Clear the Team Foundation cache from your server and the user system from the below path:
C:\Users\\AppData\Local\Microsoft\Team Foundation\7.0 (or 6.0)\cache
Delete everything from the cache folder and restart the server\system. Then Login to the server. Now, you won't get any error for uploading [WITs] using command prompt.
Follow the procedures as given in Microsoft Site.
https://learn.microsoft.com/en-us/vsts/work/customize/reference/witadmin/witadmin-import-export-manage-wits?view=tfs-2018
I have a simple question I am migrating tfs 2013 update 4 to vsts and I am using a microsoft's migration tool but I have come across an error which stats it cant fetch my collections installation path (error tf255003), I read somewhere that the migration tool which was provided by microsoft is only supported for migration tfs2017 or tfs2017 update 1 to vsts. So can I not migrate a tfs 2013 directly to vsts, or first I have to upgrade the TFS2013 TO TFS2017 UPDATE1 then do the migration please elaborate.
We recommend you upgrade to TFS 2017 update1 first, then following the Migration Guide step by step to do the migration.
For upgrading TFS 2013 to TFS 2017 update1, you can reference below articles:
Upgrading from TFS 2013 to TFS 2017
Upgrade to Team Foundation Server (TFS) 2017.
However, if you want to migrate from TFS 2013 directly, you can get and upload the source code manually, and use Execl to export and import the work items.
You can also have a try for VSTS Sync Migration Tools,it allows you to bulk edit and migrate data between Team Projects on both Microsoft Team Foundation Server (TFS) and Visual Studio Team Services (VSTS).
Besides, you can also use OpsHub Visual Studio Migration Utility, the Commercial Edition supports migration from either TFS or VSTS to either TFS or VSTS.
We are planning for a migration from TFS to VSTS, while going through some article online I came across the below migration tool.
**
- https://blogs.msdn.microsoft.com/visualstudioalm/2014/05/12/migrating-your-data-from-tfs-to-visual-studio-online-with-new-free-utility-from-opshub/#comments
**
I have the following questions
In the article it was mentioned that we don't need to upgrade to the latest version of TFS since the migration utility will read from TFS 2010,2012,2013.
We have few projects in TFS 2008 and few in TFS 2013, according to the above statement we don't need to upgrade TFS 2013. But, what we have to do with TFS 2008 ? will this migration tool take cares of 2008 version as well or do we need to upgrade 2008 to 2013 and then start migrating to VSTS ?
Also, if anyone already has any experience with this tool can you please share your points ?
Thank you.
Unfortunately, TFS 2008 is not supported by OpsHub Visual Studio Migration Utility. You will have to upgrade it to 2010 or higher in order to make it compatible with the migration tool.
https://github.com/Microsoft/vsts-work-item-migrator
this migrator can do all 4 types of migrations of user stories
but you will need to download zip file and point that folder to new repo in vsts
I need to migrate from Clearcase to TFS 2013, I have searched for a solution that helps me and I found the TFS Integration tool at CodePlex, but it does not seems to work with TFS 2013. So, does anyone has had need to do this and found a solution?
When I try to install the TFS integration tool in a server with TFS 2013 this error is displayed:
The process described in "Getting Started with IBM Rational to Team Foundation Server (TFS) Migrations" should work with more recent TFS version (2012, 2à13)
The error message "This tool requires the TFS client object model" can be seen in those recent versions: see "TFS Integration Tools – Issue: “This tool requires the TFS client object model”".
When installing the TFS Integration Tools on a machine that only has the Team Explorer installed, the installation fails with the error
This tool requires the TFS client object model.