COM互操作转移到新服务器出现故障时， [英] COM Interop fails when moving to new server

问题描述

我碰到的一个问题，我似乎无法来解决。背景：几年前，我开发了一个网站，使用ASP 2.0和Ajax我的客户之一。网站中的一个功能是产生客户发票上的需求。其内部生产系统是用Visual FoxPro中8后端的SQL Server 2005。既然我已经有了这将产生一个PDF文件的发票代对象，我滚了一个COM和EXE创建使用COM包装在我的ASP页。它多年的伟大工程，但现在我们正在努力将页面移动到不同的位置，事情不工作那么大。

I've run into a problem I just can't seem to solve. The background: Years ago, I developed a web site for one of my customers using ASP 2.0 and Ajax. One function of the web site is to produce customer invoices, on demand. Their in-house production system is written in Visual Foxpro 8 with SQL Server 2005 on the back end. Since I already had an invoice generation object that would produce a PDF file, I rolled up a COM EXE and created a COM wrapper for use in my ASP page. It works great for years, but now we're trying to move the page to a different location and things aren't working so great.

的网络技术人员已重新产生的环境和网站的其他部分完全运行。我甚至可以实例化COM对象（我已经记录的init和一切都很好），但对象方法的结果之一，第一个电话在一个从HRESULT异常：0x80010105（RPC_E_SERVERFAULT））。我只是普通的卡！

The network techs have re-produced the environment and the rest of the web site runs perfectly. I can even instantiate the COM object (I've logged the init and all is well), but the very first call to one of the objects methods results in an "Exception from HRESULT: 0x80010105 (RPC_E_SERVERFAULT))". I'm just plain stuck!

下面就是不工作：

1）使用一个Visual FoxPro程序从同一台服务器，我可以实例化对象，调用生成发票的方法，并产生PDF - 没有任何问题。

1) Using a visual foxpro program from the same server I can instantiate the object, call the generate invoice method and produce the PDF - no problem whatsoever.

2）从一个很简单的ASP页面，我可以使用的Server.CreateObject（）来实例化对象，并成功地生成有发票使用VBScript。

2) Using VBScript from a very simple ASP page I can use Server.CreateObject() to instantiate the object and successfully generate the invoice from there.

到目前为止，我知道了：

So far I know:

1）对象正确注册，并推出为正确的用户，所有做它的业务所需的权利。

1) the object is registered correctly and is launching as the proper user, with all of the rights needed to do it's business.

2）为COM EXE和COM对象版本的包装匹配

2) the wrapper for the COM EXE and COM object versions are matched.

我的长期职位道歉。为了使长话短说：为什么ASP.NET无法拨打电话到VFP COM对象的任何方法，它已经成功实例化后，

I apologize for the long post. To make a long story short: Why would ASP.NET not be able to make a call to any method of a VFP COM object after it's been instantiated successfully?

在此先感谢 - 我认真地停留在这一个。

Thanks in Advance - I'm seriously stuck on this one.

埃里克

推荐答案

对于那些运行到了同样的情况，的添加COM EXE到允许对象方法的调用数据执行prevent（DEP）例外列表中。

For those running into the same situation, adding the COM EXE to the Data Execution Prevent (DEP) exception list allowed the calls to the objects methods.

这篇关于COM互操作转移到新服务器出现故障时，的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！