RE: Having connect problems

Linda Bauer <[email protected]> Mon, 05 Apr 2004 12:59:16 -0500
Newsgroups gmane.comp.version-control.vss.sourceoffsite.classic
Message-ID <[email protected]>
Hi, Chris,

Sometimes Visual SourceSafe is installed along with VS.NET or Visual=20
Studio, so you must have had it on the machine where SOS did work.


Linda Bauer
SourceGear
Technical Support

visit our support forum at
http://support.sourcegear.com

At 11:54 AM 4/5/2004, Chris White wrote:
>Ok quick question.  The demo version vorked fine on the machine we had it=
=20
>on to test it, and that machine did not have Visual Source Safe on it, It=
=20
>had Visual Studio .NET and was working fine.  The actual ss.ini file is on=
=20
>another server and like I said worked fine when we had the version for=20
>testing.  SO I don't understand why all of a sudden we have to have source=
=20
>safe installed on the same machine the offiste server is on for it work!!
>
>Chris
>
>-----Original Message-----
>From: Ohlhaut, Marcus [mailto:[email protected]]
>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=20
>(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=20
>thing that comes up is rasspi.dll and that is in the WINNT\system32=20
>directory.  Should I have downloaded the binary version of this, and not=20
>the one that automatically installs?  I am so confused now.  If I had the=
=20
>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
> >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
> >>
>
>
>_______________________________________________
>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.
>
>
>_______________________________________________
>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.