It seems as though the physical file "ZGMAAAAA" in your VSS repo describes a project (folder) at one point then a file at another point. I think that's actually my first time seeing that error! Hopefully it is an isolated incident of corruption in your repository.
I could imagine a few situations, where this can happen. The file "aaaaaaaa.cnt" in the data directory holds the last used physical ID. When this gets messed up and you create new physical nodes up you are in big trouble. I had a similar case in my database but in my case the user added the same file as a different user with different access rights. The biggest problem is that VSS does not know atomic comits and rollback activities if something fails during the commit.
The only solution to this problem: analyze and then manually edit the files and again analyze.
Dirk _______________________________________________ vss2svn-users mailing list Project homepage: http://www.pumacode.org/projects/vss2svn/ Subscribe/Unsubscribe/Admin: http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org Mailing list web interface (with searchable archives): http://dir.gmane.org/gmane.comp.version-control.subversion.vss2svn.user
