Err Msg: retrieving the COM class factory for component with CLSID {0002E55D-0000-0000-C000-000000000046} failed due to the following error: 80040154 [modified]
-
Hi, am using a dll in my web project ("Owc11.dll") Before upgrading our production server (32 bit) it was working fine. So, recently our production server has been upgraded to 64 bit. So, while running the application one error throwing like this: "retrieving the COM class factory for component with CLSID {0002E55D-0000-0000-C000-000000000046} failed due to the following error: 80040154" Anybody could you please help me asap. These much ways i have tried, 1. dll registered in GAC also available in regedit. 2. Enabled 32 bit appln (WOW64) on 64 bit application pool by using .net command prompt. But i have 64 applns in the server. So left this method. (IIS won't support 32/64 bit applns at the same time). 3. Created Wrapper DLL and used by pre-binding method (act like interface b/w 32 bit DLL and 64 bit appln) 4. Handlers also used. thanks in advance .
Thanks & Regards, Jeneesh K. Velayudhan
modified on Tuesday, December 22, 2009 9:47 PM
-
Hi, am using a dll in my web project ("Owc11.dll") Before upgrading our production server (32 bit) it was working fine. So, recently our production server has been upgraded to 64 bit. So, while running the application one error throwing like this: "retrieving the COM class factory for component with CLSID {0002E55D-0000-0000-C000-000000000046} failed due to the following error: 80040154" Anybody could you please help me asap. These much ways i have tried, 1. dll registered in GAC also available in regedit. 2. Enabled 32 bit appln (WOW64) on 64 bit application pool by using .net command prompt. But i have 64 applns in the server. So left this method. (IIS won't support 32/64 bit applns at the same time). 3. Created Wrapper DLL and used by pre-binding method (act like interface b/w 32 bit DLL and 64 bit appln) 4. Handlers also used. thanks in advance .
Thanks & Regards, Jeneesh K. Velayudhan
modified on Tuesday, December 22, 2009 9:47 PM
This normally means that it can't find the COM class factory. In other words, it can't find the appropriate DLLs. Open up regedit, and have a look for that CLSID in HKCR\CLSID.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
-
Hi, am using a dll in my web project ("Owc11.dll") Before upgrading our production server (32 bit) it was working fine. So, recently our production server has been upgraded to 64 bit. So, while running the application one error throwing like this: "retrieving the COM class factory for component with CLSID {0002E55D-0000-0000-C000-000000000046} failed due to the following error: 80040154" Anybody could you please help me asap. These much ways i have tried, 1. dll registered in GAC also available in regedit. 2. Enabled 32 bit appln (WOW64) on 64 bit application pool by using .net command prompt. But i have 64 applns in the server. So left this method. (IIS won't support 32/64 bit applns at the same time). 3. Created Wrapper DLL and used by pre-binding method (act like interface b/w 32 bit DLL and 64 bit appln) 4. Handlers also used. thanks in advance .
Thanks & Regards, Jeneesh K. Velayudhan
modified on Tuesday, December 22, 2009 9:47 PM
I assume a typo there in that surely you have upgraded to 64bit as having a 16 bit server still running is quite impressive, more than 17 years by my reckoning, that being when Windows NT 3.1 brought 32-bit into the world. Two problems spring to mind, the first is that you will have a 32-bit interop assembly, not a 64-bit one. This is fine in a GUI based solution as you can compile for 32-bit and run in 32-bit mode, however on a server it is a little more tricky. You would have to pre-compile your web app for 32-bit, and even then you may have problems. When installing office it auto-detects your operating system and installs 64 or 32-bit as appropriate so even if you persuade your web app to run in 32-bit the underlying com object will be 64-bit. Microsoft have not released a 64-bit interop assembly package for office. Final problem is that office automation will not work running under a service such as IIS on a 64-bit server, and that usage is not supported by Microsoft. Part of the issue is the manner in which 64-bit servers initialise the office process. They fire it up in the Administrator profile rather than the profile you are running under meaning that you will not be able to access any documents you try to open. Not so much help, as bad news I'm afraid. We are facing the same issue, but thankfully are just starting to develop our app and so have no code to scrap.
If you have knowledge, let others light their candles at it. Margaret Fuller (1810 - 1850) [My Articles] [My Website]
-
I assume a typo there in that surely you have upgraded to 64bit as having a 16 bit server still running is quite impressive, more than 17 years by my reckoning, that being when Windows NT 3.1 brought 32-bit into the world. Two problems spring to mind, the first is that you will have a 32-bit interop assembly, not a 64-bit one. This is fine in a GUI based solution as you can compile for 32-bit and run in 32-bit mode, however on a server it is a little more tricky. You would have to pre-compile your web app for 32-bit, and even then you may have problems. When installing office it auto-detects your operating system and installs 64 or 32-bit as appropriate so even if you persuade your web app to run in 32-bit the underlying com object will be 64-bit. Microsoft have not released a 64-bit interop assembly package for office. Final problem is that office automation will not work running under a service such as IIS on a 64-bit server, and that usage is not supported by Microsoft. Part of the issue is the manner in which 64-bit servers initialise the office process. They fire it up in the Administrator profile rather than the profile you are running under meaning that you will not be able to access any documents you try to open. Not so much help, as bad news I'm afraid. We are facing the same issue, but thankfully are just starting to develop our app and so have no code to scrap.
If you have knowledge, let others light their candles at it. Margaret Fuller (1810 - 1850) [My Articles] [My Website]
64 bit..
-
64 bit..
please tell little bit detail !
Thanks & Regards, Jeneesh k. v.
-
This normally means that it can't find the COM class factory. In other words, it can't find the appropriate DLLs. Open up regedit, and have a look for that CLSID in HKCR\CLSID.
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
As Braveheart once said, "You can take our freedom but you'll never take our Hobnobs!" - Martin Hughes.
Hi, checked on CLSID in HKCR\CLSID. DLL is available there. So, what should i do ?
Thanks & Regards, Jeneesh k. v.