Unable to open key file - error at command line

If you are having a problem using SourceOffSite, post a message here.

Moderator: SourceGear

Post Reply
Satish
Posts: 3
Joined: Tue May 04, 2010 5:10 am

Unable to open key file - error at command line

Post by Satish » Tue May 04, 2010 5:55 am

I have been using SourceOffsite 4.2 for accessing source safe over internet, I have imported encryption file successfully and could see and get latest source from GUI, BUT when it comes to commandline it gives error "Unable to open key file .." I have searched .Key file on my local and could find. I read somewhere that key file gets generated when we import encryption file??

this is command that I tried -

soscmd.exe -command GetFileList -server s.xxxx.com:8081 -name aaaaa -password bbbb -database \\xx-sourcesafeyy\SourceSafeData\Source-Offshore\srcsafe.ini -project $/Rel_12_3/NET/FF/Source/Offshore/XXX.Common -soshome c:\AppData\SourceGear\SOS -workdir C:\AppData\source

Can you pls. help me to locate key file?

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: Unable to open key file - error at command line

Post by lbauer » Tue May 04, 2010 7:40 am

What operating system are you running the SOS Client on?
Linda Bauer
SourceGear
Technical Support Manager

Satish
Posts: 3
Joined: Tue May 04, 2010 5:10 am

Re: Unable to open key file - error at command line

Post by Satish » Tue May 04, 2010 11:11 pm

Windows 7 Enterprise

Satish
Posts: 3
Joined: Tue May 04, 2010 5:10 am

Re: Unable to open key file - error at command line

Post by Satish » Tue May 04, 2010 11:24 pm

Ignore last reply, I am running SOS client on windows server 2003

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: Unable to open key file - error at command line

Post by lbauer » Wed May 05, 2010 4:18 pm

If the SOS client is on Windows 2003 server, the path to -soshome would be C:\Documents and Settings\username\Application Data\SourceGear\SOS. The encryption key should be in that directory.

Also, make sure the server name in the soscmd script is the same as the the servername used to create the encryption key. For instance, if the key was created with the IP address of the server, then the -server parameter must use the IP address and not the domain name, etc.
Linda Bauer
SourceGear
Technical Support Manager

Post Reply