SOS CLC Help Required : 010128010153.key is not generated.

mindhedreamz · Post by **mindhedreamz** » Fri Dec 30, 2005 1:56 am

Hi,

We are accessing a VSS setup in Toronto(Canada) from a machine in Pune(India) using the latest version of source off site.
We have imported the user_name.iky using the Tools --> Import Key and system displayed the message 'User Key Imported Successfully'.
We are able to access the remote VSS using the GUI of source off site but we are not able to access the same using the CLC.
If we go throgh the help provided with the installer it says, when we import the user_name.iky, SoS generates a server_name.key in the install folder. But this server_name.key is not getting generated.

Please help us in understanding why is it happening and how to generate the server_name.key.

Regards,
Madhav Mindhe
Infosys Technologies Ltd.
Contact: +91-981122033

lbauer · Post by **lbauer** » Fri Dec 30, 2005 6:42 am

What version of SOS are you using -- client and server?

mindhedreamz · Post by **mindhedreamz** » Sat Dec 31, 2005 2:17 am

We are using the Version 4.1.2 With 128-bit cryptography.
The license is purchased by Infosys Technologies Ltd. Pune

Could you please give me the technical support contact details (preferably from India) as we need the solution very urgently ?

Many Thanks in advance,
Madhav Mindhe
Infosys Pune
Cell:+91-9881122033
mail: madhav_mindhe@infosys.com

lbauer · Post by **lbauer** » Sat Dec 31, 2005 6:40 pm

Our Technical Support is in the United States. Our offices are closed for the holiday, so this forum is the best place for support.

The information about the location of the server key sounds like it is from SOS 3.5.3 documentation -- perhaps it didn't get updated.

In SOS 4.x, the <server>.key file is in the SOS Client home directory. The default location for the home directory is
C:\Documents and Settings\<user>\Application Data\SourceGear\SOS.

If the Command Line Client connects to the secure port, it will look
for a User Key in the SourceOffSite GUI Client's home directory. In
order to use encryption, the path to this directory must be specified in your command, using the -soshome parameter or by setting a SOSHOME environment.

Documentation for the Command Line Client is in the SOS GUI Client directory, and it's named soscmd.txt.
variable.

mindhedreamz · Post by **mindhedreamz** » Sun Jan 01, 2006 12:19 pm

Hi,

There is no such directory on the machine
C:\Documents and Settings\<user>\Application Data\SourceGear\SOS.

Please let us know how should we set up one for this now ?

Please let me know US contact number and timings for support.

Many thanks in advance,
Madhav Mindhe

lbauer · Post by **lbauer** » Sun Jan 01, 2006 5:11 pm

There is no such directory on the machine
C:\Documents and Settings\<user>\Application Data\SourceGear\SOS.

Is the SOS Client on a Windows machine? What operating system?

The path "C:\Documents and Settings\<user>\Application Data\SourceGear\SOS" is not an absolute path. It is the path of the local profile for the user logged in to that client machine. So it would be "C:\Documents and Settings\Linda\Application Data\SourceGear\SOS" on my own machine.

On some XP systems, Application Data is a hidden folder, so you may need to "unhide" it using folder options.

Or are you using a Unix machine?

Our support phone number is 217-356-0105 x 700. Leave a message with your phone number and email address and I will contact you. Let me know what timezone you are in.

mindhedreamz · Post by **mindhedreamz** » Mon Jan 02, 2006 3:04 am

Thanks Linda for the support and the promt replies.
Our problem has been solved and we have found the .key file and could connect using CLC.

Happy new year to you... Have a wonderful time throughout the year!!!

Regards,
Madhav Mindhe