VSS error

Thanks for your mail. I tried created a new temp file as you suggested but
stiill while check-in the files, we get the same error.

We have many other VSS DB's in the same server which doesnt have any issues.
Moreover, this DB size is only 4GB. Any idea!! Your help in this is greatly
appreciated

Rgds,
Prabhu

"Catherine" wrote:

> On Nov 18, 10:21 pm, prabhubhaskar
> <prabhubhas....TakeThisOut@discussions.microsoft.com> wrote:
> > Hello Group
> >
> > We are getting a error msg while performing diff or comparing of source in
> > VSS. The error is 'SourceSafe was unable to finish writing a file. Check your
> > available disk space, and ask the administrator to analyze your SourceSafe
> > database'. We are using VSS 6.0D. Their is enough space in the server. We did
> > an analyze on this DB but still the issue exists. Any Idea, what could be the
> > reason!!
> >
> > Rgds,
> > Prabhu
>
> Please check your option for "Folder for temporary files." in VSS
> Tools->Options->General Tab. See if it is a valid path, file system
> permissions are set accordingly, no virus checkers are preventing file
> writes, and there is plenty of disk space there.
>
> You may also try setting the temp folder to another path to see if the
> issue persists.
>
> Thanks.
>
> Catherine Sea
> http://www.dynamsoft.com
>
>

Prabhu:

What are you trying to Diff, a file in the working folder and a version
from history? Two versions from history?

A thought... What if it isn't that VSS couldn't write to the temp
folder. What if VSS tries to get the historical version to launch the
diff, and that fails? That *might* generate the same kind of error.

Try getting the specific historical version to disk. Try getting it to
the *same* temp folder configured in your VSS settings. Do both of
these work.

Jeff Clausius
SourceGear


prabhubhaskar wrote:
> Thanks for your mail. I tried created a new temp file as you suggested but
> stiill while check-in the files, we get the same error.
>
> We have many other VSS DB's in the same server which doesnt have any issues.
> Moreover, this DB size is only 4GB. Any idea!! Your help in this is greatly
> appreciated
>
> Rgds,
> Prabhu
>
> "Catherine" wrote:
>
>> On Nov 18, 10:21 pm, prabhubhaskar
>> <prabhubhas....DeleteThis@discussions.microsoft.com> wrote:
>>> Hello Group
>>>
>>> We are getting a error msg while performing diff or comparing of source in
>>> VSS. The error is 'SourceSafe was unable to finish writing a file. Check your
>>> available disk space, and ask the administrator to analyze your SourceSafe
>>> database'. We are using VSS 6.0D. Their is enough space in the server. We did
>>> an analyze on this DB but still the issue exists. Any Idea, what could be the
>>> reason!!
>>>
>>> Rgds,
>>> Prabhu
>> Please check your option for "Folder for temporary files." in VSS
>> Tools->Options->General Tab. See if it is a valid path, file system
>> permissions are set accordingly, no virus checkers are preventing file
>> writes, and there is plenty of disk space there.
>>
>> You may also try setting the temp folder to another path to see if the
>> issue persists.
>>
>> Thanks.
>>
>> Catherine Sea
>> http://www.dynamsoft.com
>>
>>

Jeff - You are slightly confusing me I am not able to catch you on the
last part of your mail. Anyhow,

This issue started with the error 'SourceSafe was unable to finish writing a
file. Check your available disk space, and ask the administrator to analyze
your SourceSafe database' while we were doing a diff, but after we changed
the path for 'temp files', we are getting the same error while checkin the
files. AS I mentioned below there are many other DB's(huge size) which
resides along with this DB doesnt have any issues. This DB alone is having
such issues.

Your help is greatly appreciated

Rgds,
Prabhu

"Jeff Clausius" wrote:

> Prabhu:
>
> What are you trying to Diff, a file in the working folder and a version
> from history? Two versions from history?
>
> A thought... What if it isn't that VSS couldn't write to the temp
> folder. What if VSS tries to get the historical version to launch the
> diff, and that fails? That *might* generate the same kind of error.
>
> Try getting the specific historical version to disk. Try getting it to
> the *same* temp folder configured in your VSS settings. Do both of
> these work.
>
> Jeff Clausius
> SourceGear
>
>
> prabhubhaskar wrote:
> > Thanks for your mail. I tried created a new temp file as you suggested but
> > stiill while check-in the files, we get the same error.
> >
> > We have many other VSS DB's in the same server which doesnt have any issues.
> > Moreover, this DB size is only 4GB. Any idea!! Your help in this is greatly
> > appreciated
> >
> > Rgds,
> > Prabhu
> >
> > "Catherine" wrote:
> >
> >> On Nov 18, 10:21 pm, prabhubhaskar
> >> <prabhubhas... RemoveThis @discussions.microsoft.com> wrote:
> >>> Hello Group
> >>>
> >>> We are getting a error msg while performing diff or comparing of source in
> >>> VSS. The error is 'SourceSafe was unable to finish writing a file. Check your
> >>> available disk space, and ask the administrator to analyze your SourceSafe
> >>> database'. We are using VSS 6.0D. Their is enough space in the server. We did
> >>> an analyze on this DB but still the issue exists. Any Idea, what could be the
> >>> reason!!
> >>>
> >>> Rgds,
> >>> Prabhu
> >> Please check your option for "Folder for temporary files." in VSS
> >> Tools->Options->General Tab. See if it is a valid path, file system
> >> permissions are set accordingly, no virus checkers are preventing file
> >> writes, and there is plenty of disk space there.
> >>
> >> You may also try setting the temp folder to another path to see if the
> >> issue persists.
> >>
> >> Thanks.
> >>
> >> Catherine Sea
> >> http://www.dynamsoft.com
> >>
> >>
>

Hi Prabhu,

It is possible your VSS DB is corrupted? What was the analyze result?
Could you please try using Analyze v8 to re-analyze your database to
see what it says?

Thanks.

Catherine Sea
http://www.dynamsoft.com

Hi Cat

I have done analyze on the DB as & when error was reported. It was
successful but issue still exists.

Anyhow, I will try to do analyze now as you suggested. Will ket you know
the results

Thanks for your kind support

Rgds,
Prabhu

"Catherine" wrote:

> Hi Prabhu,
>
> It is possible your VSS DB is corrupted? What was the analyze result?
> Could you please try using Analyze v8 to re-analyze your database to
> see what it says?
>
> Thanks.
>
> Catherine Sea
> http://www.dynamsoft.com
>
>
>

Hi Cat

Find the analyze result below

Analyze Visual SourceSafe Version 6.0d (Build 31222)
Database analysis in progress @ 11/21/08; 1:08p.
Minor inconsistencies were found in the header record for '' (hlbaaaaa).
No parent project for subproject file 'hlbaaaaa'.
The file 'd:\repair\data\h\hlbaaaaa' appears to be corrupt. Unable to read
the format or header.
The file 'd:\repair\data\n\nobaaaaa' appears to be corrupt. Unable to read
the format or header.
Minor inconsistencies were found in the header record for '' (iobaaaaa).
The file 'd:\repair\data\i\iobaaaaa' appears to be corrupt. Unable to read
the format or header.
Minor inconsistencies were found in the header record for '' (jobaaaaa).
The file 'd:\repair\data\j\jobaaaaa' appears to be corrupt. Unable to read
the format or header.
Minor inconsistencies were found in the header record for '' (riaaaaaa).
The file 'd:\repair\data\r\riaaaaaa' appears to be corrupt. Unable to read
the format or header.
Minor inconsistencies were found in the header record for '' (rsaaaaaa).
The file 'd:\repair\data\r\rsaaaaaa' appears to be corrupt. Unable to read
the format or header.
Analysis complete @ 11/21/08; 1:11p
Potentially serious errors or inconsistencies were found.

Results

Building the project list.
There are minor inconsistencies in the header flags for 'hlbaaaaa'.
Checking cross file relationships.
The CRC for data file '' (iobaaaaa.a) does not match the stored CRC. The
file may be corrupt.
The CRC for data file '' (jobaaaaa.a) does not match the stored CRC. The
file may be corrupt.
The CRC for data file '' (riaaaaaa.a) does not match the stored CRC. The
file may be corrupt.
The CRC for data file '' (rsaaaaaa.a) does not match the stored CRC. The
file may be corrupt.
Checking parent/child relationships.
Started analyzing user management system.
Successfully completed analyzing the user management system.
Validating the Rights system.

Rgds,
Prabhu

"prabhubhaskar" wrote:

> Hi Cat
>
> I have done analyze on the DB as & when error was reported. It was
> successful but issue still exists.
>
> Anyhow, I will try to do analyze now as you suggested. Will ket you know
> the results
>
> Thanks for your kind support
>
> Rgds,
> Prabhu
>
> "Catherine" wrote:
>
> > Hi Prabhu,
> >
> > It is possible your VSS DB is corrupted? What was the analyze result?
> > Could you please try using Analyze v8 to re-analyze your database to
> > see what it says?
> >
> > Thanks.
> >
> > Catherine Sea
> > http://www.dynamsoft.com
> >
> >
> >