Unknown revision action: 20 and empty folders

[carlosrochap]

Hi,

I cloned this repo and tried to migrate an VSS repo into git, but I got the following error when I click Go

The program keeps running, but when it finishes most of the folders are empty.

I'm using version 1.11 on windows 10. I also tried with version 1.10 but no luck either

Thanks in advance,
Carlos

[trevorr]

You can use VssDump to see if you can figure out what action 20 is. Vss2Git is based on reverse engineering the VSS repository format, since it has never been documented by Microsoft. As you can see here, actions 18, 20-22, and 24 do not have a known meaning.

I wonder if the folders are empty because that action is doing something significant or because the exception caused the processing of the current file to be aborted. It's probably the latter, so a simple fix could be ignoring unknown actions (ideally with a warning logged). Of course, it's hard to know how valid the conversion will be with actions ignored.

Since no one else has reported this error, I'd be curious to know what version of VSS created that action in your repository. Perhaps it was really new or really old?

[carlosrochap]

the VSS version is SourceSafe version v6.0c

[alberb]

I am having the same issue. Also on SourceSafe v6.0, VSS2GIT 1.0.11.0 on Windows 10.

[larsxschneider]

Any news on this topic? I am running into the same problem!

[suehshtri]

I ended up adding more to the exception so I could see what was going on.

throw new ArgumentException("Unknown revision action " + revision.Action + " at revision " + revision + " " + revision.Revision + " dt:" + revision.DateTime);
produced
ERROR: Unknown revision action MysteryAction20 at revision Hpdi.VssPhysicalLib.CommonRevisionRecord 34 dt:12/21/1998 5:33:40 PM
I was able to better dig out the exact revision of the complaint. The context in the log turned out to be misleading given my inexperience with the vss2git code. I then went to go digging, and found mention of a file being 'archived'. Vss help does not open in Windows10 and I resorted to googling until I found a book mentioning VSS archiving. I think this effects a remove of the file. I suspect other actions may restore from an archive.

[mohammedalqassar]

I have the same problem where the action is 20 and the effected folder being empty. In my case, when I looked at the history in the VSS client, the action was showing as "Archived version of ..." (where the ... is the file name).
The VssPhysicalLib>RevisionRecord.cs>Action enumeration does have an entry for ArchiveProject = 23, but not for 20.

A lazy solution to the problem but managed to work around the issue for me:

1. Add a new entry to the VssPhysicalLib>RevisionRecord.cs>Action enumeration: ArchiveUnknown = 20,

2. Add a new VSS action class to VssLogicalLib>VssAction.cs file:

   public class VssNoAction : VssAction
   {
     public override VssActionType Type { get { return VssActionType.Label;} }
   
     public VssNoAction()
     {
       //
     }
   
     public override string ToString()
     {
       return "No Action";
     }
   }
   

3. Add a new case to the switch statement in VssLogicalLib>VssRivision.cs>CreateAction() method:

   case Hpdi.VssPhysicalLib.Action.ArchiveUnknown:
      {
        return new VssNoAction();
      }