Some of my remote developers e-mailed me this morning with an error that has become common for most of them. They are using VSS 2005 and the latest release of SoS.
They are receiving this error within the SoS client when doing either checkout or get latest
Any help would be greatly appreciated
New error VSS2005 w/ SoS 4.2x
Moderator: SourceGear
New error VSS2005 w/ SoS 4.2x
- Attachments
-
- SoS Error.JPG (36.24 KiB) Viewed 6672 times
I noticed that myself, that's why I was grilling my folks. I have a feeling that they only THINK they have disabled integration and have the client up as well as SoS integration. Being as they're on VSS2005, I wouldn't think the concurrency issue would be a problem but you never know.
Also, if it's an error coming from VSS and not one being caught within the SoS client, you might still see the title bar of the error as it is. Just a thought.
Also, if it's an error coming from VSS and not one being caught within the SoS client, you might still see the title bar of the error as it is. Just a thought.
What I suspect about this is that there's bindings to VSS present. We have a few articles surrounding the project binding both in the SOS KB articles area and the Vault KB articles. If they want to use SOS alone, when they try to open files from VS and there's still bindings from VSS, it may complain. If no binding are wanted, then it just needs to be unbound from VSS.
I think the article for users that are trying to bind to both SOS for external users and VSS for internal users will help explain a lot: http://support.sourcegear.com/viewtopic.php?t=1149
I think the article for users that are trying to bind to both SOS for external users and VSS for internal users will help explain a lot: http://support.sourcegear.com/viewtopic.php?t=1149