SoS Version 4.1 Hangs when getting a previous version

check@strasz.com · Post by **check@strasz.com** » Mon Mar 07, 2005 9:43 am

I have a user getting an hourglass (timing out) when trying to get a previous version of a file. Here is the eror generated in the SoS log when he attempts the operation:

3/7/2005 10:35:21 AM - Connection accepted from 10.5.1.42:55899 on local address 10.128.10.4:8890, session id is 1332.
3/7/2005 10:35:45 AM - Connection accepted from 10.5.1.42:55903 on local address 10.128.10.4:8890, session id is 1333.
3/7/2005 10:35:58 AM - 1332: Exception getting file. Version not found
3/7/2005 10:36:14 AM - 1332: Exception: Index was outside the bounds of the array.
3/7/2005 10:36:15 AM - Connection accepted from 10.5.1.42:55949 on local address 10.128.10.4:8890, session id is 1334.
3/7/2005 10:36:34 AM - 1334: Exception getting file. Version not found
3/7/2005 10:36:43 AM - 1334: Exception: Index was outside the bounds of the array.
3/7/2005 10:36:43 AM - Connection accepted from 10.5.1.42:55950 on local address 10.128.10.4:8890, session id is 1335.
3/7/2005 10:37:45 AM - 1335: Exception getting file. Version not found

Any help is appreciated, thanks

Guest · Post by **Guest** » Mon Mar 07, 2005 2:33 pm

I am having the same problem. Did you ever find a solution?

Thanks,
Gary

lbauer · Post by **lbauer** » Thu Mar 10, 2005 12:23 pm

Can you get the file version with VSS? If you can't, then SOS won't be able to, either.

The Version not found error when getting a file from history could be caused by minor database corruption.

Try running Analyze on your database to see if that helps.

http://support.sourcegear.com/viewtopic.php?t=50

Guest · Post by **Guest** » Thu Mar 10, 2005 2:08 pm

Yeppers everything works fine when using VSS. I ran the analyze a couple of times and have come up error free, as per the instructions.

Thanks

lbauer · Post by **lbauer** » Fri Mar 11, 2005 9:33 am

Assuming Guest is not user check: what version of SOS client and server are you using? Can a different SOS user get the file version?

Enable verbose and method logging (if you're using SOS 4.x), reproduce the problem and send me a copy of the log.txt file in the SOS server directory. Be sure to reference this post.

check@strasz.com · Post by **check@strasz.com** » Fri Mar 11, 2005 10:04 am

Hi there Linda. That was me posting as guest. Somehow I was not logged into the board. I have e-mailed you the verbose log. Both server and client are running SoS 4.1 with VSS 6.0d as the underlying database version.

Thanks

Guest · Post by **Guest** » Thu Mar 17, 2005 8:33 am

You must use 6.0c + hot fix to be able to retrieve a previous version of a file that was migrated from an other VSS database.

VSS 6.0d and SoS 4.1 do not work together under these conditions.

lbauer · Post by **lbauer** » Thu Mar 17, 2005 8:49 am

Thanks for the detective work, Carey. SOS communicates with the VSS database through the SourceSafe Automation Componenet -- the ssapi.dll .

There are several ssapi.dll and SOS versions and it's hard to keep track of which operations work in certain combinations and which don't.

Our favorite version of the ssapi.dll is the one ending in 96.40, which is the Microsoft hotfix for 6.0c. SourceGear worked with Microsoft to reproduce, isolate, and identify issues with the ssapi.dll as they specifically related to SourceOffSite. Later versions of the ssapi.dll may or may not work as well. (Note: there are at least 4 different ssapi.dll versions for VSS 6.0d.)

You can download a copy of VSS 6.0c Hotfix at this link:

http://download.sourcegear.com/files/vss_60c_hotfix.zip