We have found, after installing VSS 2005, that our .pdf files get corrupted
when moving them into VSS.
If you try to open them directly from or VSS (view or edit) or Get Latest
and open them on your local machine, they are corrupted.
I get the error message:
An unrecognized token '0.0r' was found.
We have no problems with any other type of files.
We get the same error if we try to open the file using an older version of
VSS with these files.
Does anyone else have this problem?
Thanks,
Tom
Mark Tolonen - 26 Mar 2008 02:33 GMT
> We have found, after installing VSS 2005, that our .pdf files get
> corrupted when moving them into VSS.
[quoted text clipped - 12 lines]
>
> Does anyone else have this problem?
It sounds like VSS is mistaking the pdf file as a text instead of a binary
file and performing line end conversions.
Run the Visual SourceSafe Administrator program, Select "Tools, Options...",
"File Types" tab, and make sure "*.pdf" is added to the list of binary
files.
Hope that helps,
Mark
Shahid Beg - 04 May 2008 19:01 GMT
Hi Any Update on this as I also facing same problem with PDF file only.
Regards
Shahid Beg
> We have found, after installing VSS 2005, that our .pdf files get
> corrupted when moving them into VSS.
[quoted text clipped - 16 lines]
>
> Tom
Mark Tolonen - 05 May 2008 03:21 GMT
> Hi Any Update on this as I also facing same problem with PDF file only.
>
[quoted text clipped - 20 lines]
>>
>> Tom
You may not have seen my previous post:
It sounds like VSS is mistaking the pdf file as a text instead of a
binary
file and performing line end conversions.
Run the Visual SourceSafe Administrator program, Select "Tools,
Options...",
"File Types" tab, and make sure "*.pdf" is added to the list of binary
files.
Hope that helps,
Mark
Alan - 02 Jun 2008 15:28 GMT
Hi,
If you need to recover the pdf file, you may try Advanced PDF Repair
at http://www.datanumen.com/apdfr/ This tool is rather useful in
salvaging damaged PDF documents.
Alan