< class="prominent-subhead ">

Installation Error: Retrieving the COM Class Factory for Component with CLSID 

This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.


When trying to install K2 4.7 for the use of legacy workflows (as this feature does not appear in K2 Five onwards), the following error appears post installation:

Retrieving the COM class factory for component with CLSID {2B72133B-3F5B-4602-8952-803546CE3344} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).

The K2 service does not start up and you are not able to proceed to any of the K2 sites.



From the install trace (located in Program Files x86 or Program Files > K2 Blackpearl or K2 > Set Up > Logs):

Log.WriteIndent: Navigate Panel Start :>> Main.navigateNext: Old Panel Index: 1 :>> Log.WriteIndent: Start terminate processes :>> UIHelper.TerminateProcesses: Skip process check for: K2HostServer:>> InstallTrace.WriteUnindent: End terminate processes: True :>> CommonMessages.AllowSqlVerion: Logged Error: Could not connect to SQL server. Exception: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) >> Main.navigateNext: New Panel Index: 1 >> Log.WriteUnindent: Done Navigate Panel :>> Main.CancelSetup: Setup cancelled by user >> Main.CancelSetup>> Log.WriteUnindent: Setup cancelled by user. Exiting application...

The set trace log can normally be seen at the end of the installation as well.

Troubleshooting Steps

To get around this, it is a good idea to make sure that the SQL configuration has been set up correctly via the cliconfig.exe.

Details on how to set this up with the correct steps can be accessed here:

After this, run the set up once again and allow this to go through. This should resolve the errors that were seen before.