Hi Toby,
Thanks for your quick response, and the offer to investigate further.
Hopefully the following output helps. If you require anything else,
please ask. The output of the commands history, get & filetype was
simply the xml header tag.
F:\>ssphys.exe info e:\sourcesafe\data\z\ZGMAAAAA
<?xml version="1.0" encoding="windows-1252" ?>
<File Name="e:\sourcesafe\data\z\ZGMAAAAA">
<ItemInfo offset="52">
<SSName offset="0" type="project">Export</SSName>
<NumberOfActions>1</NumberOfActions>
<LatestExt>.A</LatestExt>
<DataFileName>e:\sourcesafe\data\z\ZGMAAAAA.A</DataFileName>
<Type>1</Type>
<NumberOfProjects>0</NumberOfProjects>
<NumberOfItems>0</NumberOfItems>
<ParentPhys>YWKAAAAA</ParentPhys>
<ParentSpec>$/Time and People/Payrolls</ParentSpec>
</ItemInfo>
<Version offset="416">
<Action ActionId="CreatedProject">
<SSName offset="0" type="project">Export</SSName>
<Physical>ZGMAAAAA</Physical>
</Action>
<Date>793281168</Date>
<UserName>TRE</UserName>
<VersionNumber>1</VersionNumber>
</Version>
</File>
F:\>ssphys.exe validate e:\sourcesafe\data\z\ZGMAAAAA
ssphys.exe: could not read record at offset behind file size
Try `ssphys.exe --help` for more information
Regards,
Mathew
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Toby
Johnson
Sent: Tuesday, 6 February 2007 1:05 AM
To: Vss2Svn Users
Subject: Re: inconsistent item type error
Pole, Mathew wrote:
> I tried running vss2svn tonight for the first time.
> Unfortunately it crashed. These are the last few lines of output. The
error at line 706 is repeated numerous times before the actual crash.
>
> ERROR -- Attempt to add entry 'PIQAAAAA' with unknown version number
(probably d
> estroyed)
> at vss2svn.pl line 706
> ERROR -- Attempt to add entry 'XGQAAAAA' with unknown version number
(probably d
> estroyed)
> at vss2svn.pl line 706
> ERROR -- Inconsistent item type for 'ZGMAAAAA'; '2' unexpected
> at vss2svn.pl line 691
> DBI::db=HASH(0x100cf14)->disconnect invalidates 1 active statement
handle (eithe
> r destroy statement handles or call finish on them before
disconnecting) at vss2
> svn.pl line 1245.
>
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.
At any rate, the script should not consider such an error fatal; I just
checked in a change to fix this. If you want us to investigate further
on your particular case, then run ssphys.exe on the file data\z\zgmaaaaa
in your VSS repository and capture the output. Then look at the
<ItemInfo> element in the output and find its member <ParentPhys>, and
run ssphys.exe on the physical file mentioned there also, then send both
outputs.
toby
_______________________________________________
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
