我用c#开发了一个Windows服务。生成PDF报告。要生成PDF文件，我使用第三方dll。应用程序在我的Windows XP平台上运行。当我在Windows Server 2008 64位版本中部署服务时，我得到了这个错误:
检索的COM类工厂 带有CLSID的组件 {46521 b1f - 0 a5b - 4871 - a4c2 fd5c9276f4c6} 由于以下错误导致失败: 80040154.
我使用regsvr32命令注册了DLL。我能够在注册表中看到这个CLSID。但问题依然存在。
有什么问题吗?
当前回答
对于任何使用VSTO的人来说，我遇到的问题是缺少对办公室组件的引用。如果您试图手动实例化某些VSTO对象，也会出现这种情况。
其他回答
对于任何使用VSTO的人来说，我遇到的问题是缺少对办公室组件的引用。如果您试图手动实例化某些VSTO对象，也会出现这种情况。
如果你正在寻找一种不需要重新编译任何CPU应用程序的方法，这里有另一种潜在的解决方案:
Locate your COM object GUID under the HKey_Classes_Root\Wow6432Node\CLSID\{GUID} Once located add a new REG_SZ (string) Value. Name should be AppID and data should be the same COM object GUID you have just searched for Add a new key under HKey_Classes_Root\Wow6432Node\AppID. The new key should be called the same as the COM object GUID. Under the new key you just added, add a new String Value, and call it DllSurrogate. Leave the value empty. Create a new Key under HKey_Local_Machine\Software\Classes\AppID\ Again the new key should be called the same as the COM object’s GUID. No values are necessary to be added under this key.
这个解决方案不是我的功劳，但它对我们很有效。查看源代码链接获取更多信息和其他评论。
来源:https://techtalk.gfi.com/32bit对象environment/——64位
windows 2008服务器x64的解决方案是:
以管理员权限打开cmd.exe。 将dll拷贝到C:\Windows\SysWOW64文件夹 从C:\Windows\SysWOW64运行regsvr32 验证dll在Windows注册表中。 如果你有一个使用dll的。exe x86, exe必须在x86模式下编译。 exe必须安装在C:\Program Files (x86)文件夹中。
这个程序是有效的，是可以的
听起来你的服务是针对“任何CPU”构建的，导致你在使用COM组件的64位上出现错误。您需要为x86构建它。
该网站可能作为一个32位进程运行，这就是为什么它可以使用该组件。基于x86构建解决方案将迫使您的服务以32位的方式运行。
我发现我的问题与DLL的实际注册有关。
First run "Regedit.exe" from a CMD prompt (I raised it's security level to Administrator, "just in case") then search the Registry (by clicking on "Edit/Find" in the RegEdit menu or by pressing Ctrl+F) for the CLSID showing in the error message which you received regarding the COM class factory. My CLSID was 29AB7A12-B531-450E-8F7A-EA94C2F3C05F. When this key is found, select the sub-key "InProcServer2" under that Hive node and ascertain the filename of the problem DLL in the right hand Regedit frame. showing under "Default". If that file resides in "C:\Windows\SysWow64"(such as C:\Windows\SysWow64\Redemption.dll") then it is important that you use the "C:\Windows\SysWow64\RegSvr32.exe" file to register that DLL from the command line and NOT the default "C:\Windows\System32\RegSvr32.exe" file. So I ran a CMD prompt (under Administrative level control (just in case this level is need required) and type on the command line (in the case of my DLL): C:\Windows\SysWow64\RegSvr32.exe c:\Windows\SysWow64\Redemption.dll the press enter. Close the command window (via "Exit" then Restart your computer (always use restart instead of Close Down then start up, since (strangely) Restart perform a thorough shut down and reload of everything whereas "Shut Down" and Power-Up reloads a stored cache of drivers and other values (which may be faulty). Whenever you register a DLL in the future, remember to use the SysWow64 "RegSvr32.exe" for any DLL stored in the C:\Windows\SysWow64 folder and this problem c(if it is caused by incorrect registration) should not happen again.
