Start a conversation
  1. Pivotal Support
  2. Pivotal Articles
  3. Articles

Troubleshooting Pivotal CRM 6.6.5 Client Fails to Connect After New Server Install (CLSID 0x80040154 “Class not registered”)

Overview

After installing Pivotal CRM 6.6.5 (or 6.6.5.1) on a new server and pointing it to an existing database previously used with Pivotal CRM 6.6.3.x, the Pivotal CRM client may fail to connect to the Business Server with a COM activation error (CLSID) and HRESULT 0x80040154.

Pivotal CRM 6.6.3.x databases are confirmed compatible with Pivotal CRM 6.6.5.x (no interim 6.6.4.10 upgrade and no schema changes required). This error is most commonly caused by missing or outdated mandatory prerequisites on the new 6.6.5 server—specifically Microsoft .NET Framework 4.8 and SQL Server Native Client version 10.53.6560.0.

Troubleshooting

Error message (verbatim)

Unable to connect to system medicis in Pivotal Client because a connection to the Pivotal Business Server http://<business_server_host>
could not be established. Contact your system administrator.

Retrieving the COM class factory for component with CLSID
{192AB8A4-7D0B-4657-ABBD-2CC3792B761D} failed due to the following error: 80040154 Class not registered
(Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).

When this happens

  • Pivotal CRM 6.6.5 / 6.6.5.1 is installed on a new server.
  • The new installation is configured to use an existing Pivotal CRM database that was previously used by Pivotal CRM 6.6.3.x (for example, 6.6.3.10) on another server.
  • The Pivotal CRM client fails on launch/connection with a COM registration error (CLSID + 0x80040154).

Compatibility confirmation

  • The Pivotal CRM 6.6.3.x database is compatible with Pivotal CRM 6.6.5.x.
  • An interim upgrade to 6.6.4.10 is not required for database/schema compatibility in this scenario.

Most likely cause

Mandatory prerequisites on the new Pivotal CRM 6.6.5 server are missing or out-of-date, causing COM components to fail to register/load:

  1. Microsoft .NET Framework 4.8 is required on the new server.
  2. SQL Server Native Client must be updated to 10.53.6560.0 (the version included with the Pivotal CRM 6.6.5 installer).

Troubleshooting steps:

1) Verify/install Microsoft .NET Framework 4.8

  1. On the new server, confirm that .NET Framework 4.8 is installed.
  2. If not installed, install .NET Framework 4.8 (a server reboot may be required after installation).
  3. After installation and reboot (if applicable), re-test launching the Pivotal CRM client.

2) Verify/update SQL Server Native Client to 10.53.6560.0

  1. On the new server, check the installed version of SQL Server Native Client.
  2. If the version is not 10.53.6560.0, update it using the SQL Server Native Client package shipped with the Pivotal CRM 6.6.5 installer media.
  3. Reboot if required by the installation.
  4. Re-test launching the Pivotal CRM client.

3) Re-test the Pivotal CRM client connection

  1. Launch the Pivotal CRM client.
  2. Confirm the client can connect to the Pivotal Business Server at http://<business_server_host>.
  3. Confirm the CLSID / 0x80040154 error no longer appears.

Validation (how to confirm the fix)

The issue is considered resolved when:

  • The Pivotal CRM client opens successfully, and
  • The connection to the Pivotal Business Server is established without the CLSID/0x80040154 COM error.

If the issue persists after prerequisites are correct

If .NET Framework 4.8 and SQL Server Native Client 10.53.6560.0 are confirmed installed and the same CLSID/0x80040154 error persists:

  • Investigate OS/DCOM-level configuration (DCOM permissions can contribute to COM activation failures in some environments).
  • Check PBS logs

Frequently Asked Questions

1. How do I know this article applies to my issue?
You can apply the troubleshooting steps if you see the COM error with CLSID {192AB8A4-7D0B-4657-ABBD-2CC3792B761D} and 80040154 Class not registered (REGDB_E_CLASSNOTREG) while launching the Pivotal CRM client, typically after installing Pivotal CRM 6.6.5 on a new server.
2. Is the error caused by pointing Pivotal CRM 6.6.5 to a database last used by Pivotal CRM 6.6.3.x?
No. Database compatibility was confirmed for this path (a 6.6.3.x database works with 6.6.5.x). The issue is more likely missing/outdated prerequisites on the new server rather than an unsupported database version jump.
3. What exact prerequisites were identified as mandatory for Pivotal CRM 6.6.5 in this case?
Microsoft .NET Framework 4.8 and SQL Server Native Client version 10.53.6560.0 (the version included with the Pivotal CRM 6.6.5 installer).
4. After installing prerequisites, what is the simplest way to verify the fix?
Reboot the server if required, then launch the Pivotal CRM client and confirm it connects to http://<business_server_host> without showing the CLSID/0x80040154 error.

Choose files or drag and drop files
ai_initiated
atlas_studio
kb_automation
Was this article helpful?
Yes
No

  1. Priyanka Bhotika

  2. Posted

Comments