Client cannot connect to SOS 4.2

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

Moderator: SourceGear

Post Reply
hellercarl
Posts: 5
Joined: Tue Mar 11, 2008 10:23 am

Client cannot connect to SOS 4.2

Post by hellercarl » Tue Mar 11, 2008 10:27 am

I've been using SOS 4.2 for a few months now. One day, my client is unable to connect to the SOS server. Checking the error log on the server, I see the following error:

Exception during Login: Retrieving the COM class factory for component with CLSID {783CD4E4-9D54-11CF-B8EE-00608CC9A71F} failed due to the following error: 80070005.

I've uninstalled and re-installed the server portion, with no change. I've talked to the server administrator, who states that no changes have occurred on the server (W2K3, SP2).

If any further information is required, please let me know.

Carl.

Terence
Posts: 164
Joined: Thu Feb 02, 2006 2:43 pm
Location: SourceGear

Post by Terence » Tue Mar 11, 2008 10:38 am

I think your answer can be found here: http://support.sourcegear.com/viewtopic.php?t=3101
Terence McGhee
SourceGear

hellercarl
Posts: 5
Joined: Tue Mar 11, 2008 10:23 am

Post by hellercarl » Wed Mar 12, 2008 12:16 am

Thanks for the suggestion, but no change, still getting the same error.

Carl.

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

Post by lbauer » Wed Mar 12, 2008 8:38 am

Could you attach a copy log file? Or send a copy to support at sourcegear..com, ATTN: Linda

Also, what version of the VSS automation component is the SOS Server using? Here's how to find out:
http://support.sourcegear.com/viewtopic.php?t=1510
Linda Bauer
SourceGear
Technical Support Manager

hellercarl
Posts: 5
Joined: Tue Mar 11, 2008 10:23 am

Post by hellercarl » Wed Mar 12, 2008 9:44 am

VSS Version: 6.0.98.48

Log file is attached (IP address and server name changed to protect the innocent)

Carl
Attachments
log.txt
(4.64 KiB) Downloaded 673 times

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

Post by lbauer » Wed Mar 12, 2008 4:32 pm

There seems to be a problem with the SourceSafe automation component. As a first step, I'd suggest reinstalling the SourceSafe Client (ssexplorer) on the Vault Server machine.
Linda Bauer
SourceGear
Technical Support Manager

hellercarl
Posts: 5
Joined: Tue Mar 11, 2008 10:23 am

Post by hellercarl » Fri Mar 14, 2008 11:11 am

I don't know what you want me to do here. There is no Vault server, this is a Visual Source Safe server.

Carl.

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

Post by lbauer » Fri Mar 14, 2008 12:35 pm

sorry! :oops:

I meant the SourceOffSite server machine.
Linda Bauer
SourceGear
Technical Support Manager

hellercarl
Posts: 5
Joined: Tue Mar 11, 2008 10:23 am

Post by hellercarl » Fri Mar 14, 2008 12:52 pm

The SOS server is on the VSS server. Is the VSS client a separate install on a VSS server? Can I do what you're suggesting without affecting other people who are using the VSS server?

Thanks,

Carl.

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

Post by lbauer » Fri Mar 14, 2008 2:52 pm

The VSS database is separate from the VSS Explorer Client and VSS Admin Client. They don't need to be on the same machine. Your users have clients on their machines and they connect to the VSS database with those clients.

So you should be able to reinstall VSS without affecting the VSS database.
I'd suggest reinstalling the same version you have now.

SOS Server needs a VSS client on the same machine because it uses the automation component provided by the VSS Client to communicate with the VSS database.
Linda Bauer
SourceGear
Technical Support Manager

Post Reply