ailed due to the following error: 80040154

[bryanlee]

Hi,

Appreciate if anyone has the solution to the below problem..

8/31/2009 12:51:00 PM - Number of licenses configured: 2
8/31/2009 12:51:00 PM - SourceSafe Initialization file(s) located at:
8/31/2009 12:51:00 PM - N:\Regional VSS Library\srcsafe.ini

8/31/2009 12:51:00 PM - SERVER001 is attempting to listen for connections on secure port 9081
8/31/2009 12:51:00 PM - SERVER001 is attempting to listen for connections on unsecure port 9080

8/31/2009 12:51:00 PM - Waiting for a connection....secure = True
8/31/2009 12:51:00 PM - Waiting for a connection....secure = False
8/31/2009 12:53:39 PM - Connection accepted from 10.92.9.133:4116 on local address 10.128.40.22:9080, session id is 1.
8/31/2009 12:53:45 PM - 1: Exception during Login: Retrieving the COM class factory for component with CLSID {783CD4E4-9D54-11CF-B8EE-00608CC9A71F} failed due to the following error: 80040154.
8/31/2009 12:53:45 PM - 1: Retrieving the COM class factory for component with CLSID {783CD4E4-9D54-11CF-B8EE-00608CC9A71F} failed due to the following error: 80040154.
8/31/2009 1:04:44 PM - Connection accepted from 10.92.9.133:4341 on local address 10.128.40.22:9080, session id is 2.
8/31/2009 1:04:49 PM - 2: Exception during Login: Retrieving the COM class factory for component with CLSID {783CD4E4-9D54-11CF-B8EE-00608CC9A71F} failed due to the following error: 80040154.
8/31/2009 1:04:49 PM - 2: Retrieving the COM class factory for component with CLSID {783CD4E4-9D54-11CF-B8EE-00608CC9A71F} failed due to the following error: 80040154.

[lbauer]

There's a problem with the SourceSafe Automation Component. SOS uses this to communicate with the VSS database.

Is a new error? Has SOS been working properly before? If it has been working properly, what has changed?

What version of SOS are you using? What version of the automation component are you using? To determine which version of the SourceSafe Automation Component (ssapi.dll) is used by SOS Server, look under this registry key:

HKEY_CLASSES_ROOT\CLSID\{783CD4E4-9D54-11CF-B8EE-00608CC9A71F}\InprocServer32

The value will have the path to the specific ssapi.dll file used by SOS Server. For the version information, locate the ssapi.dll file. Right click on the ssapi.dll file, choose Properties->Version.

[bryanlee]

This installation is new one.

SosServer 4.2. It says Automation Component not found

[lbauer]

A VSS client needs to be installed on the SOS Server machine. It provides the automation component that SOS uses to communicate with the VSS database. SOS 4.2 works with VSS 2005, VSS 6.0c and 6.0d.

[beeplusplus]

Hello,

I am facing the same issue now. We have moved the SOS 4.2 server from XP to Window 2008 R2(x64).
And getting the same/below error:
12/5/2013 1:26:17 AM - 2: Retrieving the COM class factory for component with CLSID {783CD4E4-9D54-11CF-B8EE-00608CC9A71F} failed due to the following error: 80040154.


I have installed SOS Client as well but the same error occurs. Please, help

[lbauer]

Note that we have never tested SOS 4.2 on Windows 2008 R2 64 bit, and it's not officially supported. It might work, however.

The first thing to check: have you installed a Visual SourceSafe client on the server machine?

[beeplusplus]

Note that we have never tested SOS 4.2 on Windows 2008 R2 64 bit, and it's not officially supported. It might work, however.

The first thing to check: have you installed a Visual SourceSafe client on the server machine?

Thanks for the reply. Unfortunately, I did not got notification for your response, hence I thought no one had attended my question (by mistake).

Happy to share you the news that after I installed VSS client, SOS works fine. Earlier (before I post this question), I had mistaken that SOS client will do that job, hence my previous attempt of installing SOS client failed.

Anyways, things are working fine at the end; otherwise, I was thinking of changing the server to a 32 bit os.

[lbauer]

Thanks for the update. That's good news. : )

Sorry it took a while to notice the forum post.