Cannot get project by label - "Operation Failed"

[shbinga]

I cannot get a project by label from either Linux or Windows clients. When I try, the client returns immediately with the message "Operation Failed - $/Projectname". Getting individual files by label works fine, as does getting the latest version of the project.

Version numbers and what I have tried:

Server:
Visual Source Safe 6.0d on Windows XP Professional

Started with SOS 4.0, today tried upgrading to 4.1, same problem.

Client:
Windows - Windows XP Home Edition, Started with SOS 4.0, tried upgrading server first then upgraded client to 4.1 as well.

Linux - Slackware 10.1 distribution, kernal 2.4.29. SOS 4.0 initially, with patch to fix the "January" problem. Upgraded to 4.1 after upgrading server, still the same problem.

I have tried getting a single subproject and the entire project. I've also tried setting the working directory to an empty folder and getting the project. In all cases, I can get the latest version but not the labeled version.

I did run VSS Analyze and Fix, no problems were found.

I found some old posts referring to this problem suggesting it might be an old VSS problem, but that is not the case here.

Any suggestions?

Thanks,
Steve

[lbauer]

Can you apply a new label to a project and then try to get by that label?

Is there anything in the log file that correponds to the failed label get?

Do other users have the same problem with these labels?

[shbinga]

If I create a new label and get the project it works. I can even check in, add, delete etc and the new label works. The only thing I see different is that 1) I am now on 4.1, the previous labels were created in 4.0 and 2) I used the windows client to create the label, previously I used the Linux client. I also have not changed anything in the project since the new label with the Linux client, I'll try that from the office tomorrw.

If I try to get any previous label it does not work - even if the label is the topmost history item on the project.

I don't know if the other developer on the project has the same problem, he hasn't responded yet. But i am using two different client systems so it seems likely to me that it is a server problem, not client.

Below is the log from a single session where I tried to get a project by label. I'm guessing message 117 is get history and 111 is get by label? So the error #80004005 is probably what you are looking for.


3/13/2005 12:37:36 PM - 1: Received message number 102.
3/13/2005 12:37:36 PM - 1: Ignore remote dates = False
3/13/2005 12:37:36 PM - 1: GetFileList project: $/Clientracs/xslt/clientracs
3/13/2005 12:37:38 PM - 1: Time to execute: 0 minutes, 1 seconds, 968 milliseconds.
3/13/2005 12:37:52 PM - 1: Received message number 117.
3/13/2005 12:38:02 PM - 1: Received message number 111.
3/13/2005 12:38:02 PM - 1: Unspecified error (80004005)
3/13/2005 12:38:07 PM - 1: ParseStream created a null message!

Thanks,
Steve

[DiRTy_GaRRy]

Same problem on SOS 4.1.2. Any solutions?

[lbauer]

This is generally an issue with the database. If the get by label fails after retrieving some files, it might be a network issue -- something could be closing the connection.

If there's an immediate error message, it probably means the VSS automation component can't get the label. SOS Server communicates with the VSS database via the automation component.

Can you get the label with VSS?

Do you run Analyze on your VSS database regularly? Database corruption is common in VSS, and the automation component is more sensitive to corruption than the VSS Client.

Is there an error in the SOS Server log file (log.txt file in the SOS Server directory.)

What version of the VSS automation component is the SOS Server using? Here's how to find out:

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

[rasty]

maybe anyone is still looking for the solution...
It has something to do with label format

getting label that looks like "4.5.6" will crash the SoS, adding (rename label) leading zero like "0.4.5.6" solves the problem, adding letter to label, like "4.5.6a" solves problem too.

hope this will help to someone

[lbauer]

Thanks for the information. It's possible the label format could make a difference, depending on the version of SourceSafe automation component and the version of SourceOffSite.

However, using the VSS 2005 Update automation component and SourceOffSite 5.0.2, I could not reproduce a crash when I used the label "4.5.6."

[rasty]

we use 4.2.1 version of SoS client/server.

I found another reason for crash.
SoS client crashes if database contains deleted but NOT purged directory AND existing non-empty directory with the same name and at the same place. Purging a deleted directory solves the problem.

I tried version 5.
I didn't like it because
1. It frequently hangs
2. Most important - It does not show files in certain folders - prints error message that files cannot be retrieved from data base.
2. Some other problem that I could not recall.

[lbauer]

SOS Version 5 works best with specific versions of the VSS automation component, specifically 6.0.48.98 and the VSS 2005 update. It's possible different ssapi.dll versions can cause the problems you were seeing with SOS 5.

[R MALA]

Hi,

I am also facing the same "Operation Failed:$projectName" problem.
In SOS log file, i could see that for a file access is denied.
I run analyze utility and repair the VSS Data. No errors or inconsistencies found.

Please help me to solve the problem.

[lbauer]

What version of SOS are you using?

Which version of the VSS Automation Component is the SOS Server using?

To determine the SourceSafe Automation Component (ssapi.dll) version used by SOS Server, look under this registry key:

HKEY_CLASSES_ROOT\CLSID\{783CD4E4-9D54-11CF-B8EE-00608CC9A71F}\InprocServer32

The value will have the path to the specific ssapi.dll file used by SOS Server. For the version information, locate the ssapi.dll file. Right click on the ssapi.dll file, choose Properties->Version.

We'd like to see a copy of the SOS Server log ith the Get label error. Send the it zipped up to support at sourcegear.com, Attn: Linda. Please include a link to this forum post.

[R MALA]

4.1.2.184 - SOS Server

6.0.31222.0 - SSAPI.dll

Log file :

2/25/2011 4:25:21 AM - 1: Access to file "D:\VSSD\ProjectName\data\a\aaaaaaaa.b" denied (8004d84b)

[lbauer]

Make sure the account running the SOS Server service has full access to the VSS data directory.

Can you get historical versions a file that's in the label?