RE: Having connect problems

Chris,

NOT the "source gear folder".  The ssapi.dll is in the bin directory
of the SourceSafe folder (see my initial email below).

Corey

At 05:00 PM 4/2/2004 -0600, Chris White wrote:
>Ok I looked in program files and then the source gear folder and found
>no ssapi.dll file so now what..... 
>
>-----Original Message-----
>From: Corey Steffen [mailto:[email protected]] 
>Sent: Friday, April 02, 2004 4:43 PM
>To: Chris White; Linda Bauer; [email protected]
>Subject: Re: [SOS-LIST] Having connect problems
>
>
>According to the log file, it appears your SourceSafe Automation
>component is not correctly configured on the server machine.  On the SOS
>Server machine, go to your SourceSafe installation folder, bin subdir,
>and using a command prompt, type "regsvr32 ssapi.dll".
>
>As far as crypto key file problems, if your users were previously using
>SOS 3.5, make sure they copy their .key files from their
>3.5 Client installation paths to their 4.0 Client installation, and on
>the server machine, make sure you copy your sossvr.kys file from your
>3.5 Server installation folder to your 4.0 Server.
>
>Corey Steffen
>SourceGear LLC
>
>At 04:34 PM 4/2/2004 -0600, Chris White wrote:
>>Got a question.  I had the demo version configured correctly and 
>>working, we recently just bought the Version 4.0 client and I 
>>conffigured it the same way, but now they are not able to connect for 
>>some reason.  Can someone please tell me what might be wrong.  I have 
>>attached the log file and below is what they are seeing when they try 
>>to
>>connect:
>>
>> Hi Chris,
>>I am having problems connecting. On port 8890 it says I am missing the 
>>rhea.key file for the encryption.  For port 8888 it tells me the server
>
>>was unable to connect to the sourcesafe database.
>>-Jason
>>
>>
>>Thanks,
>>Chris
>>