---
title: "SSO Component - COM class factory for component with CLSID"
slug: "com-class-factory-for-component-with-clsid"
updated: 2026-11-05T06:45:38Z
published: 2026-11-05T06:45:38Z
canonical: "docs.biztalk360.com/com-class-factory-for-component-with-clsid"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.biztalk360.com/llms.txt
> Use this file to discover all available pages before exploring further.

# SSO Component - COM class factory for component with CLSID

When you encounter the following exception within BizTalk360:

StackTrace: Microsoft.BizTalk.ExplorerOM.BtsException: Could not retrieve transport type data for Receive Location " " from config store. Retrieving the COM class factory for component with CLSID {CF3C637A-0D4E-47BD-9210-DB40A33BD488} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).

You might encounter the same exception when accessing the corresponding Receive Location through the **BizTalk Server Administration Console** in BizTalk360 server

#### Cause

This issue generally indicates that the required **Enterprise Single Sign-On (SSO)** components or related BizTalk components are missing, incorrectly installed, or incompatible on the BizTalk360 server.

This connectivity issue occurs between the BizTalk360 server, BizTalk Server, and SQL Server, or because required services such as **WMI** and **MSDTC** are blocked or not configured correctly.

### Solution

To resolve the issue follow the configuration steps as mention below.

#### 1. Install the SSO Service Components

Make sure the **Enterprise SSO service components** are installed on the machine where BizTalk360 is installed. But you do not need to configure SSO on the BizTalk360 server for this purpose.

![SSOComponents.png](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/d05005a2-6d44-4045-9f0f-2772d1727c44.png)

#### 2. Verify Connectivity Using DTCPing

Verify that connectivity between the BizTalk360 server and the SQL Server is working correctly. Use **DTCPing** to test the required Distributed Transaction Coordinator connectivity.

[Download DTCPing from Microsoft](https://www.microsoft.com/en-us/download/details.aspx?id=2868)

#### 3. Troubleshoot Enterprise SSO

If the issue is related to Enterprise SSO, refer to the [**Enterprise SSO Survival Guide**](https://social.technet.microsoft.com/wiki/contents/articles/6904.biztalk-server-2010-enterprise-sso-survival-guide.aspx) for additional troubleshooting steps.

#### 4. Check Firewall, WMI, and MSDTC Configuration

Verify that no firewall rules or other services are blocking communication required by **WMI** and **MSDTC**. Make sure the required MSDTC-related services are enabled and configured correctly on all relevant machines.

For information about the ports and protocols required by BizTalk360, refer to: [BizTalk360 Dependent Ports and Protocols](https://www.biztalk360.com/blog/biztalk360-dependent-ports-protocols/)

For additional information about troubleshooting MSDTC issues, refer to: [Troubleshooting MSDTC Issues](https://msdn.microsoft.com/en-us/library/aa561924(BTS.20).aspx)

#### 5. Verify SSO and Adapter Pack Versions

Make sure the **SSO components** and **BizTalk Adapter Pack** installed on the BizTalk360 server match the versions installed on the BizTalk Server environment.

Also ensure that the architecture is consistent. For example, if the BizTalk Server environment uses **64-bit** components, the corresponding components on the BizTalk360 server should also be installed with the appropriate 64-bit architecture.

#### 6. Reinstall the Required Runtime Components

As a final troubleshooting step, install the required **runtime components** on the BizTalk360 server. This ensures that all required files are available under the SSO installation folder.

After installing the runtime feature, run the BizTalk Server setup again and remove the runtime feature if it is not required on the BizTalk360 server.