COM class factory: Error 80040154 on Windows Server 2008 R2 SP1 64bit

Question

Hello there,

we have Problems using a 32-Bit COM-Library within an x86 - Application on Windows Server 2008 64bit

- The COM-Server is registered in:  HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{....}
- The Target-CPU for our Application is set to x86
- The Application runs fine on Windows 7 Prof. 64 Bit. (!)

But it gets Error 80040154 'Class not registered' when running on Windows Server 2008 R2 64 Bit

Why does it works on Windows7 64 bit but not on Windows Server 64 Bit?
Whats the difference?

any ideas?

Answer 1

Hi Business,

Welcome to the MSDN Forum.

Based on the error message, please try to use Regsvr32 to register the DLL first.

Please note, please use the 32-bit edition regsvr32.

Best regards,

---

Mike Feng
MSDN Community Support | Feedback to us
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Answer 2

Thanks, but i know how to register a dll using regsvr32.
And i know the difference between the versions of regsvr32 (system and SysWOW64) 

As i wrote, the dll is registered under HKEY_CLASSES_ROOT\Wow6432Node\CLSID\.
So we already used the 32-bit edition of regsvr32. (from \SysWOW64)

Once again: My Application is targeted for x86 and it works on any 64bit edition of Windows 7 (since years ) but not on Windows Server 2008. 64bit

Answer 3

Hi Businesskasper,

Sorry for delay response.

We are performing research on this now, and will update this thread as soon as possible when we got any update.

Thank you for your patience.

Best regards,

---

Mike Feng
MSDN Community Support | Feedback to us
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Answer 4

Hi,

Please check the following reference, hope could make some help,

http://www.gfi.com/blog/32bit-object-64bit-environment/
http://stackoverflow.com/questions/2416308/is-a-comexception-of-0x80040154-always-class-not-registered

Also, you could  visit the below link to see the various paid support options that are available to better meet your needs if you requires a more in-depth level of support.

http://support.microsoft.com/default.aspx?id=fh;en-us;offerprophone 
 

Regards

Answer 5

Seems to bee that it was a configuration issue on the server.  (Found out, that dependend libraries were not loaded. e.g. atl-library. Allthough that library was registered correctly)
Since that server was'nt configured by myself, i can not say why that happend.
Anyway - after reinstalling the server the problem dissapears.

Thanks