SourceGear Support

the issue is that sometimes the /users/* directory ownership gets changed. I have to go back into there and change back to correct ownership. I think something in VSS sometimes changes this.

This user has no issues logging into VSS. SOS he cannot. I've delete his .sos dir and tried many times. I can login using his same machine so I know they setup is good. What am I missing?

that was it, thanks.

yes. it shows the users ip connecting, assigns a session id. the error for the session id shows the session does not have access rights.

the user can check-out, check-in and everything else to the file.

this is SourceOffsite, not Vault

User getting

Operation failed: Branch $/XXX/XXX/filename.nmc

no other data to indicate the error. another user can do the branch without issue.

the version is 06.00.9848 another reported how he got back in after he was able to login back in to the SOS server 1. exit sos 2. kill all sos processes ("ps -aef | grep -i sos", then kill any running processes) 3. remove corrupt files "rm -fr ~/.sos/servers" 4. restart sos, log ...

here is my setup. The VSS database lives on a Samba server. Windows VSS users connect with VSS 6.0d. I then have a SourceOffsite 4.2 server living on a VMware server (2 procs 4G ram) for Linux users to check out code to run scripts against (command-line) and some SOS gui users who refuse to use VSS....

Ok. I just had a user do a test. I've got the new server up and running and using 2 IP addresses. It is connected to the currently used VSS database. That database is also currently actively used by the old SOS server. On the Linux client I have added a line in the /etc/hosts to redirect traffic to ...

corrections

old server, NT5.0, SOS v4.0.2

new server, SOS v.4.2

I previously asked this question about 1 year ago. But I'm still not clear on the procedure. Current SOS Server - v4.1.2, Win XP, PIII, name exch (was old exchange server no longer serving other services) Current VSS data - Samba server, PDC, name dc1 New SOS Server - v.4.1.2, VM Win XP, name soshos...

I have a 25 user license and 1 database with several projects in it. Some users use VS to access the database. Some users prefer to use SOS, so I'm maintaining both. The VS users don't need to do anything because they have VS installed locally and connect to the database directly via Samba. The SOS ...

OK. I need some assistance with the proper way for users to move over to this new host. I created the new host 'soshost' on a VM server. Everything works great, however it appears that having 2 sos servers connected to the same VSS database is not a good idea. All client activities got extremely slo...

Now that I've got users connecting to the new server, what is the best way to remove the old connection information from the Linux|Windows clients? In Linux, can I just delete the ~/.sos/servers/oldserverinfo directory?

Thanks.

I could not get it to work using a domain account on the service, so I used a local admin (admin equiv) that had the same credentials as the domain account that has access to the VSS. VSS database is on the DC of the domain.

Strangely there was no SOS log to help me. Just the Events