Hi Craig,

I'm using IIS5 on Win2K server. The cacheing is by SOS.

The other thing that will mess things up is when you use the same login to do work on another machine. You need to have separate accounts for every machine. This doesn't require extra SOS logins; but of course you are limited by the number of active licenses.

Anyway, what we do is that everyone works off SOS, whether local or not.

Hank

PS: the extra pain about this is that SOS requires a login for many operations; and pops an SSAPI error (when there is no error) before every operation. SourceGear is aware of these problems, promised to look at them, but did not promise fixes.

PPS: I've look at SiberLogic, because of its distributed server capabilities, but a) it's slower than SOS by far, even when local and b) while it supposedly has SSAPI integration, it doesn't really work, even after c) you figure out how to install it under VFP (delete the Default key under SourceControlProviders, and then recreate it without setting a value -- Frank Camp figured this one out).

Hank


>I haven't used both on the same project, but we have been looking at doing that. What server are you running this on? What about write caching on the server?
>
>
>>Hi Craig,
>>
>>have you had any luck using both VSS and SOS together for the same projects? Although the latest version of SOS allows you to switch out to VSS, what I've found is that mixing and match results in terminal confusion: SOS server caches versions, but if one user is using VSS, those changes don't make it into the cache, etc.
>>
>>Hank
>>