index > Team Foundation Server - Version Control > There was an error looking up the SID

There was an error looking up the SID

I've hit a conversion issue during a run of vssconverter.exe. The following error was reported in several cases:

TF60096: Unable to migrate due to Team Foundation Error: TF50605: There was an error looking up the SID for <USER>.

The associated files never made it from VSS into TFS. A quick spot check of the VSS history showed the file was created by the <USER> mentioned in the error message. This occurred for approximately 50 files across 4 different users. Other files were converted successfully and the users in question do exist in VSS.

Anybody run into this before?

Sterling Swartwout

Hi:

Does that user currently exists in your Active Directory? The most probable cause is that the <user> is no longer in Active Directory or has been deleted and readded with another SID.

thanks, mario

MSFT

Mario Rodriguez

Mario,

You are correct - those users do not exist in AD. This leads to an interesting problem as the VSS user in question is no longer with our company and we are reluctant to recreate the user for the import. I imagine we may run into cases where the VSS user does not match the AD user character for character.

Is this a hard requirement of the migration process or is there some way to skip the AD lookup step? Thanks and regards,

Sterling Swartwout

I am getting the same error - same scenario - users have left our company. I did tests of random files, comparing the VSS and TFS versions and they are identical.

I am not so concerned if some history data does not come over. I do, however, want to be sure that the latest versions of these files are identical. Can someone confirm this?

DQM

I'm sorry to hear that you are having difficulty with your migration due to user mapping issues.

In those cases where you have AD users that are no longer valid you need to edit the UserMap.xml file that the VSS converter uses to map VSS user names to TFS users. This file is generated during the analysis phase and is documented here:

http://msdn2.microsoft.com/en-us/library/ms253175.aspx

If the user is no longer valid make sure that the "To" side of the map is not a valid domain user (or a SID look-up will be attempted). A non-domain name (e.g. "Betty", "FormerEmployee", "Unknown", etc) can be used instead. This will attribute the changeset to that user name but will not require a "real" TFS user (i.e. this name can only be used for reporting purposes - it can not be authenticated against).

Robert.

Robert Horvick - SDE - TFS Version Control

Robert Horvick MSFT

Thank you Robert!

That did solve the problem for us. For those of you with similar issues, edit the UserMap.xml as described in the link above and add a <UserMap name="[path to usermap.xml file]"/> tag in the <Source name="VSS"> section of your migration_settings.xml file. I found the following link very helpful http://msdn2.microsoft.com/en-us/library/ms253123.aspx

S-

Sterling Swartwout

reply 6