ABCpdf DLL 版本错误 - 接下来该怎么办？
我正在使用 Websupergoo 的 ABCpdf for ASP.NET，并尝试在代码中生成 PDF。我的问题是，当我在开发环境中测试代码时，一切正常，但是当我将代码发布到测试服务器时，它停止工作。我们的生产服务与测试服务位于同一台机器上，但它们使用不同版本的 ABCpdf，因此我被迫摆弄 DLL 版本，直到我们确认新版本的 DLL 可以与代码一起使用。我尝试过在生产服务器上使用 32 位 DLL 与 64 位 DLL，以便可以同时有不同的版本 - 但无论我做什么，测试服务器都会停止生成 PDF。更糟糕的是，服务器实际上也没有抛出错误 - 所以我无法确定问题所在。
请帮忙！！
I am using Websupergoo's ABCpdf for ASP.NET and I am trying to generate PDF's in code. My issue is that when I test the code in my development environment everything works fine, but when I publish my code to our testing server it stops working. We have our production services on the same machine as our testing services but they are using different versions of ABCpdf so I am forced to fool around with the DLL versions until we can confirm that the newer version of the DLL works with the code. I've tried using 32 vs 64 bit DLL's for the production server so that there can be different versions at the same time - but no matter what I do the testing server stops generating the PDF's. To make matters worse the server isn't actually throwing an error either - so I have no way to determine the problem.
Please help!!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
可能是权限问题。生产服务器上的安全策略通常比开发系统上的安全策略更严格，这通常会在部署过程中引起问题。
您可以尝试以管理员身份登录，并尝试使用该组件运行一个最小的测试应用程序，看看是否是这种情况。如果您的代码作为独立应用程序 (exe) 运行，但不作为 ASP.NET 应用程序运行，则可能存在权限问题。 ASP.NET 通常在受限权限帐户（例如 IUSR_MACHINENAME）下运行。
您可以使用 Doc.GetInfo(0, "ABCpdfVersion") 检查正在调用哪个版本的 ABCpdf。还可以通过从 ASP.NET 为交互式用户调用 XSettings.LicenseDescription 来检查许可证是否已正确安装。您可以在有关手动安装的产品文档中找到更多信息...
如果系统上安装了多个版本的 DLL，则可能会调用错误的版本，但通常我会期望看到某种错误消息或抛出异常。
如果您无法准确确定故障所在，请使用 进程监视器系统内部。这将让您看到哪些文件和注册表项正在被实时访问。如果您在 ABCpdf 或 IIS 工作进程上看到“访问被拒绝”或“失败”，那么您应该调查发生这些情况的原因。
Could be a permissions issue. Security policies on production servers are typically more strict than on development systems and this often causes problems during deployment.
You could try logging in as Administrator and try running a minimal test application with the component to see if this is the case. If your code runs as a standalone application (exe), but doesn't as an ASP.NET app, it's likely you have have a permissions issue. ASP.NET normally runs under a restricted permissions account such as IUSR_MACHINENAME.
You can check which version of ABCpdf is being called with Doc.GetInfo(0, "ABCpdfVersion"). Also check the license has been installed correctly by calling XSettings.LicenseDescription from ASP.NET for the interactive user. You'll find more info here in the product documentation on manual installation...
With several versions of a DLL installed on a system it's possible the wrong one is being called, but then I'd normally expect to see some sort of error message or exception being thrown.
If you can't pin down exactly where the fault is, then use Process Monitor from SystemInternals. This'll let you see which files and registry keys are being accessed real-time. If you see an 'ACCESS DENIED' or 'FAILURE' on ABCpdf or IIS worker process then you should look into why these are occurring.