Server connection problems

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

Moderator: SourceGear

Post Reply
rcooper
Posts: 7
Joined: Mon Dec 19, 2005 10:20 am

Server connection problems

Post by rcooper » Mon Dec 19, 2005 10:28 am

Hi,

I've installed SOS Pro v4.1.2 server/client and am having problems in logging on. Here is a snapshot from the log file :

19/12/2005 15:58:51 - Waiting for a connection....secure = True
19/12/2005 15:58:51 - Waiting for a connection....secure = False
19/12/2005 16:09:52 - Connection accepted from XXXX on local address XXXX:8080, session id is 1.
19/12/2005 16:09:56 - 1: Unable to get hostname from address: XXXX
19/12/2005 16:11:11 - 1: Exception during Login: COM object with CLSID {783CD4E4-9D54-11CF-B8EE-00608CC9A71F} is either not valid or not registered.
19/12/2005 16:11:11 - 1: COM object with CLSID {783CD4E4-9D54-11CF-B8EE-00608CC9A71F} is either not valid or not registered.

I've got VSS 6.0 installed and working on the server machine, and the database is valid and visible on another machine. I've installed my license key on the server and have setup and started the Windows Service for the SOS server without any problems.

The above CLSID's are connected to VSS database classes and I can't seem to find them in the registry but VSS 6.0 works ok, so it seems like it's an automation problem of some kind but I'm confused as to how to solve it. Both client and server are both running Windows XP SP2 and have VS 2005 installed in addition to VS 2003.

Any ideas would be much appreciated.

Rob

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

Post by lbauer » Mon Dec 19, 2005 10:35 am

The SOS Server communicates with the VSS database via the SourceSafe automation component. The automation component is supplied by installing a VSS client on the SOS Server machine. You must be missing the VSS client on the SOS Server machine.
Linda Bauer
SourceGear
Technical Support Manager

rcooper
Posts: 7
Joined: Mon Dec 19, 2005 10:20 am

Post by rcooper » Mon Dec 19, 2005 10:45 am

Fixed the problem.

For some reason the COM objects for the VSS database classes declared in ssapi.dll were not registered. I assumed this would have been done when the VSS 6.0 was installed. Anyway, I just ran regsvr32 on the ssapi.dll and this has fixed the problem.

rob

Post Reply