Hi,
We have a situation where the remote developers needs to access multiple VSS repositories. Hence, we have a dedicated machine for SOS server which will then connect to the VSS repositories on multiple servers. As per the Knowledge Base, we will be running the SOS server under a domain user account with access to these VSS repositories. The VSS repositories will be accessed by the SOS server service as UNC paths.
However, when we use the 'soscmd' command line tool, the command only accepts the username and password under which the SOS server service is running. This is a serious limitation for us as we cannot afford to reveal the SOS service user and password to everybody.
Am I missing something, or is this a limitation with the command line tool?
TIA for your help,
Anoop V. Mathew
PS. I had posted this earlier to the discussion forum, but then realized it probably fit better in this forum.
Soscmd, multiple VSS databases, SOS server and a domain user
Moderator: SourceGear
The command line tool should work with a valid VSS username and password. What error do you get when you use a VSS username and password?
It's a little unusual that the account running the SOS Server Service has access to the database itself (as opposed to the directory where the database resides).
Could you send me:
1. a copy of your command, with passwords, etc. XX'd out.
2. A screenshot of the users for the VSS database, taken from the VSS Admin Client
3. The name of account used by the SOS Server service
4. A screen shot of VSS Admin Client->General tab
Email to linda at SourceGear.com.
It's a little unusual that the account running the SOS Server Service has access to the database itself (as opposed to the directory where the database resides).
Could you send me:
1. a copy of your command, with passwords, etc. XX'd out.
2. A screenshot of the users for the VSS database, taken from the VSS Admin Client
3. The name of account used by the SOS Server service
4. A screen shot of VSS Admin Client->General tab
Email to linda at SourceGear.com.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Soscmd, multiple VSS databases, SOS server and a domain user
Hi Linda,
I think we've figured out what we were doing wrong. Our VSS database has users who don't have passwords. We finally got soscmd working by passing "" as the password parameter.
If you're interested, here is the reason why we thought only the domain user was working.
The SOS server service runs under the account DOMAINNAME\USER1.
Initially we were calling the soscmd with parameters of "-user USER1 -password USER1_DOMAINPASSWORD" and it was working. The VSS username is the same as the domain username. As mentioned before the VSS user USER1 doesn't have a password.
When we tried passing USER2, who is also a DOMAIN user, as the username along with their domain password ("-user USER2 -password USER1_DOMAINPASSWORD"), it was failing to login to the database. This prompted us to think that only the user under which the service was running would work for soscmd.
When we tried passing the VSS usernames with empty string passwords (-user USER2 -password ""), it started working.
Thanks,
Anoop Mathew
I think we've figured out what we were doing wrong. Our VSS database has users who don't have passwords. We finally got soscmd working by passing "" as the password parameter.
If you're interested, here is the reason why we thought only the domain user was working.
The SOS server service runs under the account DOMAINNAME\USER1.
Initially we were calling the soscmd with parameters of "-user USER1 -password USER1_DOMAINPASSWORD" and it was working. The VSS username is the same as the domain username. As mentioned before the VSS user USER1 doesn't have a password.
When we tried passing USER2, who is also a DOMAIN user, as the username along with their domain password ("-user USER2 -password USER1_DOMAINPASSWORD"), it was failing to login to the database. This prompted us to think that only the user under which the service was running would work for soscmd.
When we tried passing the VSS usernames with empty string passwords (-user USER2 -password ""), it started working.
Thanks,
Anoop Mathew