RE: Incomplete History list

We don't currently have plans to install the 4.0 client, although I am
looking into the benefits of and budget for upgrading all of our
licenses.

You believe this is a known bug in SOS 3.5.3? I have never heard of it
before. Do you have any links that reference it?

-Luther
_____________________________________________________________
Luther Miller * Managing Architect * MCSD (.NET)
Softagon Corporation * www.softagon.com
1 Pier Ste 3 * San Francisco, CA 94111
(415)946-6113 * (510)387-3490 cell * (415)946-6101 fax 

-----Original Message-----
From: CPT Heath D. Carr [mailto:[email protected]] 
Sent: Tuesday, March 23, 2004 7:00 AM
To: Luther Miller; [email protected]
Subject: Re: [SOS-LIST] Incomplete History list

Luther,

I think that issue may have been fixed in SOS 4 (server side). Is it
possible for you to install SOS4 (side-by-side with 3.5.3) and test it?
The
VSS Automation component doesn't always behave as expected, even when
analyze says there are no errors. I believe SG is handling these cases
differently now in SOS4.

-heath



----- Original Message ----- 
From: "Luther Miller" <[email protected]>
To: <[email protected]>
Sent: Monday, March 22, 2004 6:03 PM
Subject: [SOS-LIST] Incomplete History list


I am experiencing a problem - I am not getting a complete list of the
history for a particular file. Part of the effect of this is that the
earliest versions that I can see are all labels, and if I try to get one
of the labels, the client hangs at 100% CPU.



I am using SOS 3.5.3 on Windows XP. I have the same problem on multiple
clients.

The server is Windows 2000, and has VSS 6.0c installed.



Note that the VSS 6.0c client, when run on the server, does not exhibit
this behavior - I can see all versions in the history and get them as
well.

At one point we have upgraded to 6.0d and archived and restored the
database. When we found out about the problems in 6.0d
(http://support.microsoft.com/default.aspx?scid=kb;en-us;822845 and the
concurrency issues
http://support.microsoft.com/default.aspx?scid=kb;en-us;826816) we
rolled back to VSS 6.0c. Everything has been working fine... until
now...



So, I am not sure if this problem is related to 6.0c or not... I am
thinking of re-upgrading to 6.0d and installing the latest patches to
fix the known issues.



Also, Analyze does not find any errors or warnings in this database.



Any ideas?



-Luther



_____________________________________________________________
Luther Miller * Managing Architect * MCSD (.NET)
Softagon Corporation * www.softagon.com <http://www.softagon.com>
1 Pier Ste 3 * San Francisco, CA 94111
(415)946-6113 * (510)387-3490 cell * (415)946-6101 fax