Migrating VSS 2005 to TFS 2008

Comments (6) | Share

I finally and succesfully migrated a VSS 2005 Database to TFS 2008.

I got soo many problems/errors.  Things like:

• Migration tool worked, but only the folders have been created in TFS. No file has been created,
• Another migration warned that TF60085:  No file or folder to migrate
• DCOM errors on the server.
• When re-creating a TFS Project, TF30162: Task "WITs" from Group "WorkItemTracking" failed

So, after migrating "empty folders" the first time, I tried to delete the projects in TFS and re-importing them...  It turned to be a mess.........  I had to run the TFSDeleteProject.exe...

Here are my findings that may or may not be evident for mortals.

• You must run the VSSConverter.exe from a "client" computer (not the TFS server)
• The account you're using must have "project creation" priviliges on the TFS server
• Check for DCOM errors on the server

If I had time and gutts, I'd start all over again (new os and all) and re-run everything with the following steps just to QA my steps!

To fix the DCOM errors,

Open Component Services

• Start-->Administrative Tools-->Component Services
• Expand Component Services, Computers, My Computer, DCOM Config.
• Find the application (IIS WAMREG Admin Service / CLSID {61738644-F196-11D0-9953-00C04FD919C1}). 
• Right-Click-->Properties and select the Security tab. 
• For the "Launch and Activation Permissions, ensure that the Customize radio button is selected, and click Edit.
• Add your service account (check the DCOM error message in the event viewer to find the right one), in my case, it was "NT AUTHORITY\NETWORK SERVICE"
  • Local Launch 
  • Remote Launch (not sure for this)
  • Local Activation
  • Remote Activation (not sure for this)
• Restart IIS and continue on.

This "should" fix the DCOM errors in the future..  hehe.. 

As for the TF30162: Task "WITs" from Group "WorkItemTracking" failed.  I don't understand, but after "browsing" IIS console, re-starting IIS, I was able to re-create a new TFS Project without the TF30162 error above.  mmm.  maybe we just need to wait a few minutes (for sub-processes to finish/garbage collect) and a restart iis to clear caching. anywhoooo

ok, now back to migration

Perform the following steps from the client computer unless noted.

Step 1. Test Project creation on TFS

Open Visual Studio, connect to the TFS Server, try to create a project and upload a file to the Source Control.  If all works, continue, if not, fix !

Step 2: Analyze the VSS

Run the Analyze.exe.  Something like

"C:\Program Files\Microsoft Visual Studio\VSS\win32\ANALYZE.EXE" -f -c -d -v1 "d:\vss\data"

Step 3: get rid of checked outs files

There will likely be files that are checked out (older/defunct projects or un-monitored projects). 

• Open VSS (client)
• Search/Status Search
• Choose "Display all checked out files"
• Search Area "Search in in all projects"

If there are files found, send an email to your team or kill/"Undo Checkout" all files.

• Open VSS client as admin
• Right click the root "$/"
• Choose Undo Checkout
• Recursive = True, Local Copy = Leave, ok
• Confirm all mesages... 

Step 4: install proper sps and hot fixes

if you run the VSSConverter and run into something like this:

Initializing...
VSSConverter has detected that Visual SourceSafe does not have the recommended u
pdates installed.  To ensure optimal results, install the updates referred to in
 Knowledge Base Article 950185.  Proceeding without these updates may lead to pr
oblems during migration.  Continue the migration without the updates (Y/N)?n

That's because the VSSConverter.exe needs to be updated (hotfix).

Well, kb950185, although the information seems to be correct, it wasn't clear that the hotfix can be found at  http://code.msdn.microsoft.com/ (the url is misleading, I think). 

Also, on that code.msdn page, to download the actual "exe", you have to click on "Current release"... Here's the direct link to the english (international) download page: http://code.msdn.microsoft.com/KB950185/Release/ProjectReleases.aspx?ReleaseId=1123

At the time of this writting, I have the following (all in English language, OSes and software):

Client:

• Visual SourceSafe 2005 + Visual SourceSafe 2005 SP1
• Visual Studio 2008 + Visual Studio 2008 SP1
• TFS 2008 Explorer

Server:

- Team Foundation Server 2008 + TFS 2008 Explorer + TFS SP1

Note that all three (VSS client, TeamFoundationClient/Explorer and VSSConverter) must have the same language in order for VSSConverter to work.

Step 5: Run!

Follow the "standard" steps to migrate.  Here's my settings.xml file:

<?xml version="1.0" encoding="utf-8"?>
<SourceControlConverter>
  <ConverterSpecificSetting>
    <Source name="VSS">
      <VSSDatabase name="E:\VSS\Patware1.0" />
      <UserMap name="E:\tfs\usermapPatware1.0.xml"  />
    </Source>
    <ProjectMap>
      <Project Source="$/" Destination="$/Patware/"/>
    </ProjectMap>
  </ConverterSpecificSetting>
  <Settings>
    <!--<Output file="E:\tfs\analysisPatware1.0.xml"  />-->
     <TeamFoundationServer name="turner" port="8080" protocol="http"></TeamFoundationServer>
  </Settings>
</SourceControlConverter>

I "basically" used the same file for the analyze and the migrate portion.  I simply commented out the proper settings portion.

Glad it can help if it does!

Pat