You are viewing limited content. For full access, please sign in.

Question

Question

Retrieving the COM class factory failed

SDK
asked on April 25, 2014

Hi,

 

I am getting a 'Retrieving the COM class factory failed' error when Running a 32 bits VB (2010) SDK 9.1 service program on a 64 bits Windows 2008 SP2 Enterprise SP1 using runtime SDK 9.1.1.118. This error does not occur on Windows 7 OS. The exact error is:

 

'Retrieving the COM class factory for component with CLSID {46918080-746B-40A4-824B-85D91B1F3D68} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).'

 

The error happens when the service is trying to OCR a document that was searched and found by the service program so the service is running correctly for repository access.

 

In the registry the CLSID points to :

 

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{46918080-746B-40A4-824B-85D91B1F3D68}\InprocServer32

 C:\Program Files\Common Files\Laserfiche\Batch Processor\BPObjectsClient.dll

 

I have registered BPObjectsClient.dll using syswow64\regsvr32 but I am getting the same result. Is there any reasons why this Windows service program works on a W7 OS but not on a W2008 enterprise? Also, the service used to work fine in the past few months with no  problems. I am therefor suspecting a Windows update.

 

Regards,

0 0

Answer

APPROVED ANSWER
replied on April 29, 2014

I was able to reach the 32 bit OCR libraries in 64 bits W2008 by adding a reference to interopt BPContainerClient91 (Interopt.BPContainerLib.dll) and changing the platform to AnyCPU in the Advanced Compiler Settings of my project.

1 0

Replies

replied on April 25, 2014 Show version history

The 32 bit OCR libraries are no longer included with the 9.1 SDK, that's why only the 64 bit libraries are found. If you want the 32 bit libraries, you should install a product that includes OCR (or just install the 9.1 standalone OCR engine installation). We included the 64 bit libraries because they aren't as common in our installations.

1 0
replied on November 15, 2016

Hi Howard

The SDK 10 Runtime x64 msi installs BPObjectsClient91.dll on C:\Program Files\Common Files\Laserfiche\Batch Processor.


If you need the BPObjectsClient dll in C:\Program Files (x86)\Common Files\Laserfiche\Batch Processor, you can install the OCR ( there is a OCR folder in the Laserfiche Rio or Avante autorun package).

1 0
replied on April 25, 2014

That registry entry looks like the registration for the 64-bit library.  Did you install the 32-bit SDK runtime?  You would end up with a similar entry, except the file path and registry path would refer to 32-bit locations.

0 0
replied on April 25, 2014

I did a standard install of the SDK runtime from the GUI. This means that it will install as 64 bits by default. How do we install the 32 bits SDK on a 64 bits machine? Also this service used to work fine in the past and also works fine on a 64 bits W7 OS. I now fails on a 64 bits W2008 server.

 

0 0
replied on April 25, 2014

I have installed LF Client 9.1.486 with Laserfiche Scanning. I can see that the Batch Processor 91 dll's are in C:\Program Files (x86)\Common Files\Laserfiche\Batch Processor along with BPOmniOCR185 folder that contains the 32 bits OCR engine, but the issue is still there. The error seems to come from the fact that the 64 bits SDK 9.1 is calling the C:\Program Files\Common Files\Laserfiche\Batch Processor\BPObjectsClient.dll because it is installed on a 64 bits machine Also please note that the same SDK and the same program installed in Windows 7 works just fine.

 

0 0
replied on November 15, 2016

Hi Justin

Is there any harm in installing the SDK 9.0 after installing SDK 10? For some reason, my app also wants BPObjectsClient.dll.

Thanks, Howard

0 0
replied on November 15, 2016 Show version history

And does the SDK or SDK Runtime install files into Program Files\Common Files\Laserfiche\Batch Processor?

In particular, BPObjectsClient.dll?

0 0
replied on November 15, 2016

And the answer is - I installed SDK 9.0.1, then SDK 10.0, and all is well. The missing dlls were installed.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.