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

Question

Question

Retrieving the COM class factory for component with CLSID {E479E155-4F63-4E98-8B23-FCCFF569CA81} failed due to the following error: 80040154.

asked on April 25, 2014

We have a custom integration that is using the LF SDK v8. It was working fine at our client site until the client upgraded their server and client machines to LF 9. Now, full user license users are fine, but retrieval only users are getting the following error:

  • Retrieving the COM class factory for component with CLSID {E479E155-4F63-4E98-8B23-FCCFF569CA81} failed due to the following error: 80040154

 

They are running on a 64-bit machine with the 64-bit Toolkit runtime. And again, that machine works for users that have full access to the LF repository and fails for users with retrieval only access. They have tried reinstalling the toolkit which didn't help. They have also tried on a 32-bit machine with the same results (works for full users only).

 

We are out of ideas. Help!

0 0

Replies

replied on April 25, 2014

Error 80040154 is REGDB_E_CLASSNOTREG and that guid corresponds to the class "LFSO80.Application".  It sounds like the same issue as this question, you can follow the same trouble-shooting steps.

0 0
replied on April 25, 2014

What is the current Platform target for the application? This StackOverflow thread suggests that this error can be resolved by changing the Platform target to x86 instead of AnyCPU.

replied on April 28, 2014

This may have been a little bit of a red herring.

 

Without testing, I am assuming that this following line of code would throw and error for a user that has retrieval only access?

 

muLFFields.LockObject(LFSO80Lib.Lock_Type.LOCK_TYPE_WRITE); //muLFFields is of type LFSO80Lib.LFFieldData

 

I don't have a site to test on at the moment...just reading code.

0 0
replied on April 28, 2014

It should throw an error, but not the one you described in your original question.

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

Sign in to reply to this post.