RE: Having connect problems

Ok quick question.  The demo version vorked fine on the machine we had =
it on to test it, and that machine did not have Visual Source Safe on =
it, It had Visual Studio .NET and was working fine.  The actual ss.ini =
file is on another server and like I said worked fine when we had the =
version for testing.  SO I don't understand why all of a sudden we have =
to have source safe installed on the same machine the offiste server is =
on for it work!!

Chris=20

-----Original Message-----
From: Ohlhaut, Marcus [mailto:[email protected]]=20
Sent: Monday, April 05, 2004 11:10 AM
To: Chris White
Subject: AW: [SOS-LIST] Having connect problems

Chris, ssapi.dll is part of Visual Source Safe. In other words, install =
(or re-install) VSS on your box.

HTH,
Marcus

-----Urspr=FCngliche Nachricht-----
Von: [email protected]
[mailto:[email protected]]Im Auftrag von Chris White
Gesendet: Montag, 5. April 2004 18:05
An: Corey Steffen
Cc: [email protected]
Betreff: RE: [SOS-LIST] Having connect problems


Corey,

I did a search for that file and it doesn't show in a search.  The only =
thing that comes up is rasspi.dll and that is in the WINNT\system32 =
directory.  Should I have downloaded the binary version of this, and not =
the one that automatically installs?  I am so confused now.  If I had =
the file you stated I could register it but it is non-existant on this =
machine.

Chris

-----Original Message-----
From: Corey Steffen [mailto:[email protected]]
Sent: Monday, April 05, 2004 9:07 AM
To: Chris White
Cc: [email protected]
Subject: RE: [SOS-LIST] 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=20
>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=20
>component is not correctly configured on the server machine.  On the=20
>SOS Server machine, go to your SourceSafe installation folder, bin=20
>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=20
>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=20
>>working, we recently just bought the Version 4.0 client and I=20
>>conffigured it the same way, but now they are not able to connect for=20
>>some reason.  Can someone please tell me what might be wrong.  I have=20
>>attached the log file and below is what they are seeing when they try=20
>>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=20
>>server
>
>>was unable to connect to the sourcesafe database.
>>-Jason
>>
>>
>>Thanks,
>>Chris
>>


_______________________________________________
This is the SourceGear sos-list.
Send postings to [email protected].
To unsubscribe or edit your mail options, go to:
http://lists.sourcegear.com/cgi-bin/mailman/listinfo/sos-list
and follow the instructions at the bottom of the page.