"error reading from file"

[TabL]

visual sourcesafe has always run fine. There have
been no changes with the server or my local machine.
Suddenly I am getting an "error reading from file"
error when I try to look at one of the
folders in a project, I can see the other folders
and check out files from the rest of the project fine.
I have run the analyze database exe but it says:
"No errors or inconsistencies found." Any help is
much appreciated.

 

[DonQuichote]

See also thread722-263200 have the same problems. No application works with sourcesafe anymore (MS-Access, VB6 and VB 'dot net' ALL fail to work). The only thing I can think of is reinstalling my client machine's opeating system. I think it might have something to do with novell and windows. (It may just as well not, but I can't think of much else anymore...)

 

[TabL]

Thanks for the reply. I am not using .net or any other new apps so I don't understand why I am having this problem. Oh well, if I find anything new out I will post it here.

 

[LesleyW]

I've experienced similar.... it just seems to ocassionally corrupt itself in such a way that the analyze can't find it nor fix it.

Experience tells me that if your database gets too big (over 2Gb) and you fail to analyze regularly (at least once in 4 weeks) you can expect these problems from sourcesafe.

 

[MattJoyce]

I have also replied to your other thread - I see you are using Novell like me. Try backing out to a previous version of the client. I got it working with 4.81. Hope this helps.

Hope this works for you if so it should be raised with Novell.

 

[TabL]

I was able to fix the vss database corruption today.
I began to get a more descriptive message that said
the names.dat file was corrupt so I ran analyze -f and
it seemed to repair everything but the names.dat file.
So I checked the microsoft site where it said there is
a bug in visual sourcesafe where analyze -f doesn't fix
the names.dat file. They said this bug is addressed in
service pack 5 for visual studio. I loaded the service
pack onto the server as I was only up to service pack 3. I
then ran analyze -f again and the corruption was fixed.

 

[DonQuichote]

Whoa, MattJoyce, you were exactly right on time. I was holding the restore CD to reinstall the OS...

I was also using 4.83 of the Novell client and installed 4.81 as you suggested. When that did not work, I installed the patch as well. It still doesn't.

The problem is that all the problems I encounter are on one machine. The other machine is running fine. I have exactly the same rights and network connections on both machines. I checked all VSS settings and they are them same on both machines as well. I'm getting pretty desperate, because none of the programs I need for my work are running now on the second machine...

 

[OutCode]

I had the same problem with adding files to sourcesafe. At out company we work with Novell Client version 4.83 and that produced this bug. It is somehow related to the (long) filenames.
Solution: download the latest patch nt483pt2.exe from the Novell web site and install it.
URL:

http://support.novell.com/servlet/filedownload/pub/nt483pt2.exe

For us, this solved our problems.

Greetings, Tijmen