Is there a way to prevent duplication directory names when migrating with the tool from VSS to NFS 2013. For example on the VSS side $\ProjectDemo but when I migrate that over to TFS 2013 it carries over the project name from VSS under the new project name in TFS 2013 which looks like this after the migration is complete: ServerName\DefailtCollection\ProjectDemo\ProjectDemo
Have to say I was very pleasantly surprised that this tool worked so smoothly. Upgraded from Visual SourceSafe to Visual Studio Online. All different types of projects, C#, VB.Net, VB6, database, all handled without issue.
Is there a way to change the workspace. I am running into max character for path is reached. so I want to change the workspace to e: instead of c:\converse . or is there is a way to bypass max character for path error?
having the same issue Unable to install on Win8.1. get the error: Windows Program Compatibility mode is on. Turn it off and then try Setup again. No matter what I do, unable to continue. Any solution? I tried to turn off compatibility and tried with all compatibility options with no success.
Hi, we have the same problem as Talksocke. We installed TFS 2013 in basic configuration with SQL Server Express 2012 on a Windows Server 2008 R2 machine. Teamproject "SubProject" was created wit TFS VC in DefaultCollection. Analyze runs fine. But the migration fails with ERROR: Object reference not set to an instance of an object".
We upgraded from SS 8.0 into TFS 2012 with the databases hosted on Sql 2012 SP1 cumulative update 7. We found when converting projects with history, we always got the error "Migration failed due to "TF60086: Unable to read or write to the intermediate database on Microsoft SQL Server <Instance Name>. A trigger returned a resultset and/or was running with SET NOCOUNT OFF while another outstanding result set was active." When we pointed the VSS upgrade tool to a 2008R2 instance for the temporary database it creates, we loaded the full history into our TFS repository in SQL 2012 without error.
At the first glance, every looked OK, but then we discovered that only this year history was migrated to TFS 2013.
Has anyone experienced this problem and do you know how to fix it?
We have 7 years of data and history in VSS 6. We upgraded the repository to VSS 2005, run the analyser and then used this Wizard to migrate the data to TFS 2013. Everything completed successfully, but looking at the history in TFS, it only contain the history for this year, nothing for the previous 6 years. I am in the UK so I wonder if this is some date format issue (US months mixed up with UK days).
I'm having problems installing this on my Windows 8.1 OS. I keep getting the error message "Another setup is already running. Please wait for it to finish before trying again.". I've already checked the compatibility settings on the tfs_VssUpgrade.exe file and it does not have any settings turned on. This product worked fine on Windows 8 but after upgrading to Windows 8.1 it will no longer install.
I am agree with BHPatel. The wizard is not very flexible. But after all it worked. Because I want to migrate only some selected subprojects, I tried out the command line tool... The analyze step worked fine. After that I added all information that are needed for the migration into the settings.xml. But the migration did not work. I got the following error:
> VssUpgrade migrate settings.xml
Microsoft (R) Visual SourceSafe Upgrade version 220.127.116.11 for Microsoft (R) Visual Studio 2012 Copyright (c) Microsoft Corporation. All rights reserved.
ERROR: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
The english translation of the error is "Object reference not set to an instance of an object".
I don't know how to get more error information. Any idea or bugfix?
The tool is not flexible at all. The tool does not let me pick VSS database below roots level project. In my case I did not wanted to migrate all my applications to TFS. I only wanted to migrate one application out of 10 application. The tool did not let me pick one application.
I did not want to physically log in to VSS server to run the tool. I should be able to use this tool from Client machine and pull the code out of VSS and commit the code to TFS.
I disagree with the approch of the migration used by this tool.
I have Windows 2008 Enterprise Edition SP 2. x64 which VSS 2005 is currently running on. I tried to run the wizard and it comes up "The specified program requires a never version of Windows". There doesn't seem to be listed anywhere what the system requires of this Upgrade Tool is (not even in the documentation)?